Open YunsuChoi opened 6 days ago
MallocArray
commented
5 days ago I haven't seen that before. Since the display isn't showing values, this isnt a Home assistant specific issue.
I would try removing the power cable for 10 seconds and then connect it again. I've seen some odd issues that require more than just a software reset.
putz612
commented
5 days ago I am having issues as well, it seems to get into a boot loop. I have tired factory resets but it still happens where it just says nan on a few of the sensors. If I watch it enough I will see the boot message again.
MallocArray
commented
5 days ago If it looks like the while device is rebooting try either disabling the AirGradient Upload switch in Home Assistant, or comment out the API package and reinstall.
When the server is having issues, it can cause the devices to reboot regularly
putz612
commented
5 days ago I have been running without the API package enabled.
MallocArray
commented
5 days ago Interesting. I'll try the latest esphome with my devices. I havent done the last minor patch
YunsuChoi
commented
4 days ago I've flahsing compiled full-config ag-pro.yaml version but it displayed version 4.0.6. seems odd. please check release package itself.
MallocArray
commented
4 days ago @YunsuChoi I updated the full-config folder with the latest yaml files
MallocArray
commented
4 days ago @putz612
I just checked and my install on a Pro 4.2 is on the latest generally available build 2024.9.2, so not sure why you are getting the boot loop, especially without the API package.
If you want to try you could add another package
factory_reset: github://MallocArray/airgradient_esphome/packages/button_factory_reset.yaml
which will add a button to do a Factory Reset, which sounds more scary than it is. It will remove all of your settings you changed on your device compared to the defaults, but doesn't fully erase your ESP device. Sometimes I've gotten messages that I ran out of space in the nvram and have to do this. So if you changed from F to C for temperature, it would reset this back to the default.
YunsuChoi
commented
4 days ago @YunsuChoi I updated the full-config folder with the latest yaml files
Okay then, Should I try from git main branch > full_config > ag-pro.yaml?
MallocArray
commented
2 days ago @YunsuChoi
It all depends on how you are running your personal setup.
My recommendation would be to have ESPHome installed locally and use the ag-pro.yaml file from the main branch main folder as the content of your personal device config. You can change the substitutions to make the name what you want, add your own encryption keys or wifi settings, etc. To update, you would just do an Install from your ESPHome and it should pull the latest config from this repo and send to your personal device.
Option 2 is to use the file from the full_config folder, but you won't get the updates regularly from there, since it is completely standalone and doesn't refer back to this repo, so updating as changes are made here become a more manual process
Option 3 is to install the .bin files manually which doesn't let you configure anything yourself since they are already compiled as they are configured in this repo and you can't update without having to manually install the latest .bin, but this option doesn't require that you have ESPHome in your own environment.
So the option is up to you as to how you want to do it, but there are considerations.
That being said, I just updated the .bin files with the latest config. I still need to automate that process and I have to manually generate them at this time and I didn't do it after the last update.
YunsuChoi
commented
2 days ago @YunsuChoi It all depends on how you are running your personal setup. My recommendation would be to have ESPHome installed locally and use the
ag-pro.yamlfile from the main branch main folder as the content of your personal device config. You can change the substitutions to make the name what you want, add your own encryption keys or wifi settings, etc. To update, you would just do an Install from your ESPHome and it should pull the latest config from this repo and send to your personal device.Option 2 is to use the file from the
full_configfolder, but you won't get the updates regularly from there, since it is completely standalone and doesn't refer back to this repo, so updating as changes are made here become a more manual processOption 3 is to install the .bin files manually which doesn't let you configure anything yourself since they are already compiled as they are configured in this repo and you can't update without having to manually install the latest .bin, but this option doesn't require that you have ESPHome in your own environment.
So the option is up to you as to how you want to do it, but there are considerations.
That being said, I just updated the .bin files with the latest config. I still need to automate that process and I have to manually generate them at this time and I didn't do it after the last update.
Thanks for detailed manual. However some of my module(SGP41) is broken. So I think real world testing is going to be quite delayed. Thanks again.
Hello. I've applied your 4.0.7 release to my Airgradient DIY PRO v4.2 board with all components. When I using airgradient's software every sensor data was visible but 4.0.7 isn't. Only what I did is complied airgradient-pro.yaml with wifi SSID and PASSWD and here is the result. please review the attachment. Thanks.
PS. Also incluide compile messages. but no errors.