vinteo / hass-opensprinkler

OpenSprinkler Integration for Home Assistant
MIT License
214 stars 41 forks source link

Everything unavailable in 2024.5.1 #285

Open CZonin opened 7 months ago

CZonin commented 7 months ago

Just updated to 2024.5.1 and the integration is failing to load. The only thing I see in the logs is:

This error originated from a custom integration.

Logger: custom_components.opensprinkler
Source: helpers/update_coordinator.py:321
integration: OpenSprinkler (documentation, issues)
First occurred: 6:49:43 PM (17 occurrences)
Last logged: 7:22:00 PM

Timeout fetching OpenSprinkler resource status data

Let me know if there's anything else I can provide.

vinteo commented 7 months ago

unfortunately it seems my OS device has decided to retire after 6 or so years. Will have to order a new one. Hopefully someone else can confrim for you but just make sure its not a network issue, try restarting the OS device as well if you haven't already

CZonin commented 7 months ago

Seems like it is an issue with my controller. I'm stuck in a reboot loop. Factory reset it and still the same issue. Just opened an issue on the OpenSprinkler page. I'll see what happens.

Nick-Adams-AU commented 6 months ago

Seems like an issue with the integration and a recent HA update. Here's what I have in my logs:


Source: config_entries.py:772
First occurred: May 4, 2024 at 8:49:22 AM (7 occurrences)
Last logged: May 4, 2024 at 8:49:24 AM

Error unloading entry OpenSprinkler for select
Error unloading entry OpenSprinkler for sensor
Error unloading entry OpenSprinkler for switch
Error unloading entry OpenSprinkler for text
Error unloading entry OpenSprinkler for time
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 772, in async_unload
    result = await component.async_unload_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/binary_sensor/__init__.py", line 240, in async_unload_entry
    return await component.async_unload_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 200, in async_unload_entry
    raise ValueError("Config entry was never loaded!")
ValueError: Config entry was never loaded!```
Sweti934 commented 6 months ago

Hei - we now bought also the openSprinkler system. Is this issue still live (and is the development Team also frequently here by any chacne?) ? Just want to know, if this system is well supported (Y) Thanks all!

wauswaus commented 6 months ago

I tried uninstalling and re-installing the integration. I now get the message it cannot connect to the controller. Running Home Assistant 2024.5.5

Log entry:

2024-06-01 22:00:53.570 ERROR (MainThread) [backoff] Giving up _request_http(...) after 3 tries (pyopensprinkler.OpenSprinklerConnectionError: Cannot connect to controller) 2024-06-01 22:00:53.570 ERROR (MainThread) [custom_components.opensprinkler] Cannot connect to controller 2024-06-01 22:00:53.570 ERROR (MainThread) [custom_components.opensprinkler] Error fetching OpenSprinkler resource status data: Error fetching OpenSprinkler state

For me this is quite an issue. My Home assistant is running the complete watering schedule based on evaporation rates. The fact it can't tell opensprinkler to run is a bit of an issue, especially with the start of summer in europe

[update]: I deleted and re-added the integration again, now not using the internal DNS name but directly its IP address and it all came back alive :)

EdLeckert commented 5 months ago

Seems like an issue with the integration and a recent HA update. Here's what I have in my logs:

@Nick-Adams-AU: Did you ever resolve this?

EdLeckert commented 5 months ago

Hei - we now bought also the openSprinkler system. Is this issue still live (and is the development Team also frequently here by any chacne?) ? Just want to know, if this system is well supported (Y) Thanks all!

@Sweti934: My system is solid under HA 2024.5.4. It looks like these are controller and config issues.