@jkandasa Following a period of relative calm in my setup, yesterday I got 2 ghost nodes appear again. One was a single temperature reading (which if correct was from the heating boiler) and the second was a single on/off.
I wonder if there is some way that a malformed message could do this? The temp one showed +58.4C and the only thing to get that hot is the heating system.
I have some nice new power supplies now (not from ali or ebay!) and will be building a UPS with these to improve stability and performance during power black/brown outs.
So nothing to do on myc front unless this still happens after all the above is done. The new supplies have cured issues on other pi builds, so hopeful on this one too....
@jkandasa Something that would be good is a way to flag aged data or node down on the dashboard display.
As it stands we cannot know 'when' the last data arrived or if the node is still sending data.
It would be good to have a method where by if no data is received after a certain amount of time (setting individually for each node or better still each sensor) then the display on the dashboard can change text colour.
So lets say I have a node or sensor that sends data every 5 minutes. I can have a setting that says 'If no data after 12 mins' then the text turns amber. Next if no data after 30 mins then the text turns red. The times should be individually selectable by user.
Whilst it's relatively easier to see the time of data with graphs, it's still possible to glance at a graph without taking note of the times and assume data is current.
@manutremo OTA works in the following way,
send available firmware details(version, checksum, etc.,) to the node
If node thinks, it is a different sketch, it will request block by block.
MyController sends firmware block data(requested block)