03-03-2025, 01:14 AM
The unexpected 'o' easy to answer.
The topicprefix/status topic is NOT a JSON value, but I'm suspecting it is trying to decode as such...?
All that lives in that topic is "online" or "offline", the latter being inserted by the broker if the LWT gets enacted (ie apparently dead connection to the AB)
The only thing I can think of for stopping after days is free memory exhaustion. This sort of issue is incredibly difficult to diagnose, and may simply be due to fragmentation of free space as memory is randomly allocated and freed.
About the only solution is a scheduled reboot to start afresh.
GPIO output#1 looped back to the EN input could be used, along with a repeat every day timer set to activate that GPIO signal.
GPIO2 has the unfortunate behaviour during the startup code to momentarily activate, and thus you'd never boot up.
The topicprefix/status topic is NOT a JSON value, but I'm suspecting it is trying to decode as such...?
All that lives in that topic is "online" or "offline", the latter being inserted by the broker if the LWT gets enacted (ie apparently dead connection to the AB)
The only thing I can think of for stopping after days is free memory exhaustion. This sort of issue is incredibly difficult to diagnose, and may simply be due to fragmentation of free space as memory is randomly allocated and freed.
About the only solution is a scheduled reboot to start afresh.
GPIO output#1 looped back to the EN input could be used, along with a repeat every day timer set to activate that GPIO signal.
GPIO2 has the unfortunate behaviour during the startup code to momentarily activate, and thus you'd never boot up.