Closed cybernard closed 1 year ago
Have you set up the accompanying add-on mentioned in the Overview and Configuration sections of the README? https://github.com/tlskinneriv/hassio-addons/tree/master/awnet
Does the observer2 support sending the Ambient Weather protocol type calls to a custom server? If so, it would likely already work. If not, I'd need to know exactly what the API calls look like to be able to adjust the add-on to work properly. I do not have an observer2 to test with.
Yes, the observer2, supports the upload to a custom server. I went in and entered the IP of my homeassistant leaving everything else at the default.
Did the documentation change because the README you referenced only contains a section called "About". I see nothing about overview or configuration in the README.
There is an "Installation" section below the "About" section at the link sent prior. There's also a DOCS.md file in that directory that documents the configuration of the add-on and the station to have it work properly with the integration.
Were you able to get this set up? Has this issue been resolved?
In the event that this is still not working with your WS-5000/Observer2, please install the latest version of the add-on (1.0.1), which should have fixes for an issue where the request from the weather station is malformed. Please re-open this issue or open a new issue if the problem persists.
Integration Version: 1.13
Home Assistant Version: newest 2023.7.3
Can not detect my device I have a ws-5000 and an observer2 and neither is detected.
To Reproduce Steps to reproduce the behavior: Added the integration filled in the station name and mac address click Ok Got nothing I tried turning on logging and got nothing it could not find the device. It shows up on my ambient weather account.
Expected behavior I was expecting it to find my device.
Screenshots
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")