Noticed a glitch in the matrix.
This morning at 0200 the clocks were supposed to go back 1 hour. My RPI3 and Cumulus MX went back to 0100 but the Pro2+ receiver didn't go back 1 hour until 0300. It appears Cumulus MX handled the time change fine for uploading to wunderground and logging.
Is there a setting where can I tell it to go back 1hr at 0200 instead of 0300? And on March 11 the time change comes at 0200, is there a setting for that as well?
I noticed my WirelessDisplay had the incorrect time at ~0230. When I went to the receiver I noticed there was no green indicator for the RTC. I stopped Cumulus MX and rebooted the Pro2+ and the RTC green dot came back. At 0300 it went back 1hr.
I'm still running v320_b002 because it has been raining and cold and I'm not changing the software on the TX until spring so I haven't changed the receiver software either.
TIA
This morning at 0200 the clocks were supposed to go back 1 hour. My RPI3 and Cumulus MX went back to 0100 but the Pro2+ receiver didn't go back 1 hour until 0300. It appears Cumulus MX handled the time change fine for uploading to wunderground and logging.
Is there a setting where can I tell it to go back 1hr at 0200 instead of 0300? And on March 11 the time change comes at 0200, is there a setting for that as well?
I noticed my WirelessDisplay had the incorrect time at ~0230. When I went to the receiver I noticed there was no green indicator for the RTC. I stopped Cumulus MX and rebooted the Pro2+ and the RTC green dot came back. At 0300 it went back 1hr.
I'm still running v320_b002 because it has been raining and cold and I'm not changing the software on the TX until spring so I haven't changed the receiver software either.
TIA