Page 1 of 1

Dashboard Gauges Work, Graph and MQTT Stop Working Minutes to Hours after Reboot

Posted: Sun Dec 24, 2023 5:39 pm
by JohnH
I am consistently getting "Major Setback! I've Lost Contact with the Solar Controller. Verify Integrity of Communication Cable."

Things had been working up until 3-4 months ago.

When the issue occurs, the gauges still update live as normal, but the graph is blank, the log to SD is not updating, and MQTT is not firing.

It usually takes several software reboots to get it to start working again. It will continue to run properly for a few minutes, to hours, or not at all and I give up rebooting. There have been no changes to the deployment since the last issue I had in February 2023 that was resolved be switching to edge, and allowing an update from 5.0-0dc546-2023-01-22-20-34 to 6.1-3360eb-2023-03-07-03-57.

I have since switched back to stable, hoping there is a new firmware that resolves this as well.

Re: Dashboard Gauges Work, Graph and MQTT Stop Working Minutes to Hours after Reboot

Posted: Wed Jan 24, 2024 8:22 am
by PCMM
I get this same message every time I open the dashabord, IT eventually goes away and the graphs display. Usually taks 15-20 seconds a bit weird but it seems to be "the way of it"

Re: Dashboard Gauges Work, Graph and MQTT Stop Working Minutes to Hours after Reboot

Posted: Thu Jan 25, 2024 12:25 am
by jonathan
Yes there's a new issue that causes a 1 minute delay every time it boots up until it starts working right is this what you're seeing? Post your logs

Re: Dashboard Gauges Work, Graph and MQTT Stop Working Minutes to Hours after Reboot

Posted: Sat Mar 23, 2024 7:03 pm
by JohnH
That's what it looks to be. It's working now.

Re: Dashboard Gauges Work, Graph and MQTT Stop Working Minutes to Hours after Reboot

Posted: Sun Mar 24, 2024 9:40 am
by JohnH
I do not know ow what resolved the issue, but it went completely unresponsive a few months ago, and would not advertise its own ssid or connect to my ap. All of those reboots wouldn't recover it for more than a few minutes or hours, then offline again.

Yesterday I disconnected the USB and modus cables, amd connected the bt-1 to test the modus port. It worked properly and I was able to read/write setpoints. After reconnecting the snekdash, it has been working for a whole day without issue, like it has been doing for a couple years now.