Open Alundran opened 2 years ago
There looks to be an error with the watercare mode which might be affecting the sensor creation (although I don’t think it ought to, it’s still an error we should fix).
It seems to be an out-of-range setting which again, shouldn’t happen, but … if you can try to ensure that your tub is using the water care mode “Standard” and the Econ mode is disabled then try removing the integration, restart HA, then re-add the integration.
There looks to be an error with the watercare mode which might be affecting the sensor creation (although I don’t think it ought to, it’s still an error we should fix).
It seems to be an out-of-range setting which again, shouldn’t happen, but … if you can try to ensure that your tub is using the water care mode “Standard” and the Econ mode is disabled then try removing the integration, restart HA, then re-add the integration.
That worked! In the app, no water care option was selected. Set it to Standard and now the entities show.
Thanks again!
Good. I’m going to leave this open as a reminder to put some try/catch logic in startup to prevent this from occurring in future. Just a bit busy with other things at present, hopefully get back to the gecko stuff later in the autumn.
Just had the same problem. All the sudden the integration stopped working and when I tried to reload it I was told that I needed to restart HA to get it up and running again. Following error was found in the logs:
2022-11-06 10:31:35.527 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/geckolib/automation/async_facade.py", line 90, in _facade_update
self._water_care.change_watercare_mode(
File "/usr/local/lib/python3.10/site-packages/geckolib/automation/watercare.py", line 83, in change_watercare_mode
self._on_change(self, old_mode, self.active_mode)
File "/usr/local/lib/python3.10/site-packages/geckolib/driver/observable.py", line 39, in _on_change
f"{self.__class__.__name__} {sender} changed "
File "/usr/local/lib/python3.10/site-packages/geckolib/automation/watercare.py", line 92, in __str__
return f"{self.name}: {GeckoConstants.WATERCARE_MODE_STRING[self.active_mode]}"
IndexError: list index out of range
When I looked in the in.touch app on the phone there was no schedule selected.
So this bug causes the hole integration to stop working, and the device becomes unavailable. But by selecting a schedule in the app, and then restart HA it all started working again.
As a side note I can tell you that I have not been using the in.touch app in a long time. The reason the water care schedule was disabled must have been when my son played with the light button on the spa, trying to get it shine in only one color. When he long pushed the light button it entered some kind of setting mode on the local controlpanel.
This bug is still present. Not sure how it was even possible for no water care mode to be selected (other than I factory reset the tub recently). I did all the same troubleshooting steps (and more) you listed in your post, and it wouldn't work until I opened the official app and selected “Standard”. Good thing I found this report buried down in the list.
I powered off the hot tub for cleaning, and it wasn't reconnecting afterwards. Confirming that setting "Water Care" to "Standard" in the app did the trick and I was able to re-add the tub to HA.
Version of the custom_component
0.1.8
Configuration
Describe the bug
I've had the integration running for a long time (around 8 months). Some network configurations changed on my side so the IP address of the SPA and other things changed. The Gecko integration stopped working. I thought that it just need to be setup again and re-configured so I deleted the integration and then attempted to re-add it. When re-adding it, it finds the SPA but no entities are created.
I've done the following:
Any thoughts would be appreciated! I wish I had never removed the integration as that seems to be the point it's all went wrong!
Debug log