@David_Graeff Can you explain section 5 of the Homie 3 spec a little more…
> ## Timings
>
> As soon as a device starts to publish any Homie related topic, it MUST finish with all topics within a timeframe of 500ms. Controllers should assume the default for topic values not received within this timeframe.
Does this mean that all nodes must supply all their details within that 500ms of the device starting up or the defaults will be applied ? This could be hundreds of nodes potentially.
I’m looking at an app that is sending a lot of nodes (50+) and it does not manage to complete the sending of that information in that time - in fact its an order of magnitude adrift based on the cpu power it has. Is there a way around this as I’m thinking it’s just not possible in this case ?
What I am seeing is the device comes online but fairly quickly goes offline on a timeout but the stats are being provided bang on the interval set. OH shows a device did not send heartbeat in time’ error, maybe I should increase the expected interval to less than the stats.
Also when trying to control a node I am getting a topic is read only which I think results from a default $settable being applied. MQTT shows the correct ‘true’ value in $settable. All nodes do appear in discovery.
Lastly .. is a topic allowed to contain a whitespace character which is valid in MQTT but is not specifically mentioned in the Homie 3 spec ?