-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reconnect wibeee after become online #31
Comments
@t3lmoazevedo please include logs in a code block or attachment instead of a screenshot as it makes it possible to search, copy values, etc. It looks like your device is not responding at http://192.168.7.63/services/user/devices.xml and therefore the integration is not able to start for that Wibeee. You can read in the logs that the integration has made 5 attempts before giving up. Are you able to access it at the same time as the error is logged? |
Today, went offline at 11:49... and thats a problem I need to solve with the device wireless coverage. I just avoid to paste the full logs because of the size... |
The error you've included in the first message occurred when fetching http://192.168.7.63/services/user/devices.xml and that is during the setup of the integration, when trying to determine the device data (such as the Wibeee MAC address to determine the device's unique id in HA). During this time it is not possible to wait for long periods of time because it is the setup stage in HA and HA will give up after some time; at least it used to be the case the the entire platform would be disabled after too long a wait, I haven't tried again with the config entry approach that is in v3. This will cause the device to never come online in HA. I know this is a problem with other integrations as well because I get this with the built-in Solax integration (if I restart HA overnight when the inverter is off) so I'm not sure there is a way around it. I will try to have a look but in any case it shouldn't be a problem except after HA starts up or you add a new device. In the logs included in #31 (comment), however, I can see that the error is in fetching http://192.168.7.63/en/status.xml and this has been failing continually up to 12:57. That is after start up and you can see that the retries are happening and the device is still failing? Can you confirm? |
The device is still offline and that why the amount of retries in progress in the log. |
When the device back comes back online it will become available in Home Assistant. :) By design the custom component will continue to poll the device forever with the configured polling interval, which you can change as shown in #23. The only exception is if setup did not complete as I explained above. If that happens you can manually reload the integration when the device comes online. Retries were one of the first things that I implemented in #9 back in August and this gave a big boost in reliability of the wibeee custom component. All of this happens within a single poll cycle and is shown in your logs. Enabling DEBUG logs will show all the retry attempts.
Basically what you are asking for is already implemented. Please give us an update when your Wibeee comes back online. 👍 |
Did you check the firmware version of your device? I had some issue in the past, the connection fall down without a reason and it was related to a specific firmware version. I upgraded to version 4.4.157 and everything works!!! My 2 cents |
I did it with the Wibeee Business App. With the Home App is not possible! |
I have both apps and websites, for home and business. |
Using the new Wibeee Nest interface, seems my devices are working with the latest firmware. |
Looking at the MAC address of your device I can see that it's a different manufacturer/hardware to mine. It's possible that the older versions are not able to run the newer firmware—you could raise a support case with Wibeee to know for sure. |
Did your Wibeee ever come back? |
Yes it did after a restart, but seems this device in particular has network issues since the other one never hangs. |
@t3lmoazevedo I recommend double-checking with Wibeee support what is the latest available firmware for your devices. On my device, for example, I know there is a newer firmware but I do not get the option to upgrade. It's not a very old device so I doubt that it could not run the newest firmware. In any case I'm closing this issue as there is nothing the integration can do if a device is unreachable/offline. |
After a Wibeee device comes online after being disconnected, its possible to retry the connetion to get the status again?
Only works after a HA restart.
Logs:
The text was updated successfully, but these errors were encountered: