Thank you for reporting this. I let our firmware developer know.
I was just coming here to report this. My router is attached to an old UPS that decided it isn’t going to work anymore this morning. I swapped the UPS with another one, but the airgradients were stuck in “WiFi N/A” mode until I power cycled them.
If the AG is going to revert to the AP mode, maybe it should try to reconnect periodically. It would be nice to have a switch to disable this behavior entirely as well.
Kai
1 Like
How do I tell my 3.0.9 model to use my mqtt broker, which is mosquito running on a pi3, at address 192.168.1.21. No security, default everything, nothing fancy (all very local).
Whatever I put in the mqtt field under place settings, it won’t let me proceed.
Set up MQTT parameter on the cloud UI. The AG device Will grab it from the cloud portal and use it locally
My question was more ‘what do I type in’ since just putting in the IP address of the server doesn’t work. It also ought be possible to set/reset this stuff on the local device, without relying on clouds!!
By the way, anyone using the restful .json access described back in post31 needs to adjust it since several of the items have been relabeled since then … the new data output looks like:
{“wifi”:-55,“serialno”:“xxxxx”,“rco2”:978,“pm01”:0,“pm02”:0,“pm10”:0,“pm003Count”:0,“atmp”:22.65,“rhum”:49,“tvocIndex”:130,“tvoc_raw”:30728,“noxIndex”:1,“nox_raw”:17124,“boot”:320,“ledMode”:“co2”,“firmwareVersion”:“3.0.9”,“fwMode”:“I-1PSL”}
so the underscores have been replaced and letters have changed case, in pm003Count, tvocIndex, and noxIndex.
The regex is probably too aggressive. We will fix it to allow without authentication
Yes we have a few changes to make it consistent with our general API. One of them is to move to camel case.
Please keep in mind that this is still in beta.
Ah thanks, I was not giving it the user id, on the assumption it would default to something. Will try again…
Just loaded 3.0.9 onto some new one v9 sensors and noticed that the air quality values don’t show up in the prometheus /metrics ? The values however show up on the air gradient dashboard and the device oled.
curl ag/metrics | grep -v #
airgradient_info{airgradient_serial_number="<snip>",airgradient_device_type="ONE_INDOOR",airgradient_library_version="3.0.9"} 1
airgradient_config_ok{} 1
airgradient_post_ok{} 1
airgradient_wifi_rssi_dbm{} -43
airgradient_co2_ppm{} 891
airgradient_tvoc_index{} 101
airgradient_tvoc_raw{} 29016
airgradient_nox_index{} 1
airgradient_nox_raw{} 16255
airgradient_temperature_celsius{} 27.26
airgradient_humidity_percent{} 47.00
Was there any changes lately that might cause this ?
That’s a known issue that is being fixed, see Report PM data to metrics API for AirGradient ONE by danielmoore · Pull Request #96 · airgradienthq/arduino · GitHub.
1 Like