not sure whats up but all my sensors are in a reboot loop updating constantly, the dashboard is reflecting each repeated update showing a new last update time.
1 Like
I’ve tried to select the previous version in the dashboard but doesnt seem to be helping.
I would send a message to support@airgradient.com and include your serial number in the e-mail for them to look at more
yep, all my monitors are offline in a reboot combined with some led blinking. I have two Airgradient One and one Outdoor. All three same problem since today
I opened a support case to have them take a look and reply here
It looks like they finally added 3.2.0 and 3.3.6 to the dashboard, so if you had the “always update to the latest version” checked (it’s the default), that’s why you’re getting the update now.
And it means everyone who didn’t uncheck that is presumably also getting updated today.
I have an indoor unit in one location and an outdoor unit in another location. Based on what I see in HA, they both got (successfully) updated this morning (UTC). I’ve attached a screenshot of how HA saw the process of the indoor unit. It looks very similar for the outdoor unit.
What’s weird is that I have another indoor unit in the same location with the outdoor unit and HA doesn’t show any change for it. So either this unit’s been on 3.3.6 for a longer time or somehow HA missed its update.
Any chance the one that didn’t get the update is set for Local for Configuration Source inside of HomeAssistant?
In the Dashboard, if you scroll down to your devices and click the three dots on the far right under Admin and select “Show Monitor Information” you can see what version it is reportedly running
Nah, all 3 devices are set to cloud. From the mentioned device:
[user@laptop ~]$ curl -s http://esp32c3-xxxxxx.home.arpa/config | jq .configurationControl
"cloud"
[user@laptop ~]$ curl -s http://esp32c3-xxxxxx.home.arpa/measures/current | jq '.model,.firmware'
"I-9PSL"
"3.3.6"
Also a screenshot from HomeAssistant with both the outdoor and indoor device. I’ve marked when the outdoor was updated in the lower right part.
Edit: forgot to mention, I see the same in the Dashboard.
Are you seeing the regular reboots the other users reported, or just noticed that all of your devices didn’t update at the same time?
I believe there is a rollout process, so not all devices are supposed to update at the same time, but I’m not sure if the details of the rollout plan
Thank you for bringing this issue to our attention and to everyone who reached out to support.
We are aware of this issue and are working to fix it. Please expect an update soon.
Same here. They’ve been down since yesterday at the same time.
Both my v9 indoor and outdoor updated to 3.3.6 and went into a crashloop.
I’ve rolled back my indoor to 3.0.8 to get it back online.
Hi @everyone
Just want to make sure, do you using prometheus monitoring to fetch from /metrics local server? If it is, it might relate to this issue: I-9PSL unit reset itself when calling /metrics endpoint · Issue #309 · airgradienthq/arduino · GitHub
We’ll create the official release to fix this very soon.
1 Like
Thanks! Yes, I am using Prometheus monitoring of /metrics
So am I.
I think it should be this commit that introduced prometheus
3e4e2affa828eff0eb44de0380602be5d9ea706c
The fix has been posted, see PR #310 on github.
No reboots here (at least I haven’t noticed any), just saw this issue in the forum and checked my devices and noticed the one that wasn’t upgraded at the same time as the other two.
Is the fix also addressing connection error (console readout):
[5776534][E][ssl_client.cpp:37] _handle_error(): [start_ssl_client():273]: (-80) UNKNOWN ERROR CODE (0050)
[5776647][E][WiFiClientSecure.cpp:144] connect(): start_ssl_client: -80
Posted here: Repeatedly failing OTA update - #15 by Evv
1 Like
Today my Airgradient(KIT) which is connected to my Homeassistnat suddenly also started rebooting/firmware updating 3.3.6 in circles…
I blocked internet access on my paloalto Firewall for the Airgradient, which (temporarily) stopped it updating in circles now and working fine and showing data in Homeassistant also. I just cannot access it via browser via http or https but not sure if this should work.
From my homeassistant history the issue started tonight at 2:55AM UTC Time.
Once i unblock it on firewall and reboot it, the circle starts again…
Why is this happening and how can this be fixed permanently? - i still see 3.3.6 is the last version on github.
1 Like