Closed JtwoA closed 3 months ago
Please take a look at #42 for details to see if you have the same issue. Please include debug logs from and the version of the AWNET add-on.
Please take a look at #42 for details to see if you have the same issue. Please include debug logs from and the version of the AWNET add-on.
I noted the version is 1.2.0 of the add-on.
As for logs - I've enabled debug and reviewed the log output and see nothing pertaining to this add-on. It's like it simply doesn't exist anymore. Uninstalled, reinstalled (as noted) and it doesn't see any sensors any longer.
I noted the version is 1.2.0 of the add-on.
That's the version of the integration. I'm looking for the version and debug logs from the add-on. This can be found on the page for your add-ons in HA.
42 points to the MAC address format - this integration has been working flawlessly for many, many months.
This integration works hand-in-hand with the add-on mentioned above to deliver the data to HA from the weather station. If both components are not configured and working properly, you won't get any data in HA. The debug logs from the add-on are critical to troubleshooting further since there are no errors in the HA logs.
I noted the version is 1.2.0 of the add-on.
That's the version of the integration. I'm looking for the version and debug logs from the add-on. This can be found on the page for your add-ons in HA.
42 points to the MAC address format - this integration has been working flawlessly for many, many months.
42 is about more than the format. It ultimately led to the discovery of a change in the data format sent by the weather station due to an update on the firmware. Specifically in this comment I overview an update to the add-on mentioned above to add an option to override the MAC sent by the station. This can cause the same symptoms as what you are facing.
This integration works hand-in-hand with the add-on mentioned above to deliver the data to HA from the weather station. If both components are not configured and working properly, you won't get any data in HA. The debug logs from the add-on are critical to troubleshooting further since there are no errors in the HA logs.
I had completely missed that this is an add-on/integration combo.
Add-on version is 1.1.1
I noted the version is 1.2.0 of the add-on.
That's the version of the integration. I'm looking for the version and debug logs from the add-on. This can be found on the page for your add-ons in HA.
42 points to the MAC address format - this integration has been working flawlessly for many, many months.
42 is about more than the format. It ultimately led to the discovery of a change in the data format sent by the weather station due to an update on the firmware. Specifically in this comment I overview an update to the add-on mentioned above to add an option to override the MAC sent by the station. This can cause the same symptoms as what you are facing.
This integration works hand-in-hand with the add-on mentioned above to deliver the data to HA from the weather station. If both components are not configured and working properly, you won't get any data in HA. The debug logs from the add-on are critical to troubleshooting further since there are no errors in the HA logs.
I had completely missed that this is an add-on/integration combo.
Add-on version is 1.1.1
And the MAC address override did it. (I did have the ALL CAPS issue but saw that noted later in #42's comments.)
There was a new firmware pushed to these and I don't recall for certain if I pushed that before or after the data stoppage.
Thanks VERY much! We're good to close here.
Integration Version: 1.2.0
Home Assistant Version: 2024.5.5
Describe the bug All sensors show "unavailable". Reloading the integration has no effect. Removed integration, readded integration, one device/one entity (instead of 20+ entities)
To Reproduce Steps to reproduce the behavior:
Expected behavior Expectation is multiple sensors showing live data vs "unavailable"
Screenshots![image](https://github.com/tlskinneriv/awnet_local/assets/12992040/33da3e12-ebd5-4be0-9be0-75b345ee4085)
Additional context Add any other context about the problem here.
Debug log output from the integration (see Home Assistant docs for how to enable debug logging for an integration; integration name: "custom_components.awnet_local")
Debug log enabled, reloaded integration:![image](https://github.com/tlskinneriv/awnet_local/assets/12992040/e80bba06-0e5a-4f1c-94a1-9614d76e2b97)