schaze

Der Issue ist zwar schon etwas älter aber ich hätte ein ähnliches Problem mit dem RPC node. Hier wird auch ein neues MSG objekt erstellt. In diesem Fall wäre es...

Hi all, as I have been mentioned in @Tieske's first comment I received mail notifications about this topic and I have been reading your comments with a lot of interest....

@Thalhammer wrote: > my home solution is about on par, though with different design choices (e.g. a "monolith" with container based plugins) and I know how much time I put...

> let's save the format discussion for later. I think we have some 'process' to set up first. > > I've seen @ogghst list. That sort of seems to start...

While I understand the intent and potential use cases I believe any implementation for handling a "secure" property would be very specific. In your example above what should the behavior...

IMHO this should be handled by an extension to the convention. The core convention should not be concerned about UI representation of the devices/nodes/properties. How should a device make assumptions...

> yes agree, it makes sense as an extension. Very good, then I vote to close this issue with this comment. > That leaves me with a specific mqtt topic...

**For the first argument:** > But imo that argument is moot because QoS 1 (minimum once) delivery also requires persistent storage. Not sure if it needs to be persistent storage...

After over a year of intermittent issues with docker-in-docker builds on drone in kubernetes this finally helped. Please add a line of documentation for this. It will help A LOT...

Was this waiting for another approval? If yes then I missed it sry...