Open roperstv opened 1 year ago
I have the same problem, but it seems rather a Gecko Server Issue, is your inTouch app working? Mine did not, i had to restart the device then my intouch App got connected again. Initialisation now takes a while in HA, will update later.
i had to reboot HA (the whole system) to get Gecko working again
Thanks for your suggestions tried the phone app and it works fine,
There doesn't apear to be an option to select the ID, fairly certain there was when I initially installed this a few months ago.
Any help would be much appreciated , thanks
I'm having the same issue, I'm able to reconnect it, but it becomes unavailable again after several minutes later. My Bullfrog app is working fine.
Ahh, I’m away at present but I’ll do the HA upgrade and then try to fix the integration when I’m back.
Thanks Gazoodle, If you need any logs or any help testing, please feel free to reach out.
Cheers
Thank you!
Thanks for taking the time to look at it. I have the same symptoms as roperstv but mine was a new installation as I've only connected the in.touch 2 this week. Assumed initially it was an issue at my end.
Hope all is well with everyone. Just want to check on the status on this.
Still not working for me, it installs fine and finds the spa but won't list any entities.
I can't get the development container to run, so I'm in the process of diagnosing why this is the case ... might be related to HA requirement for Python 3.11 in 2023.8.* This integration was based on @ludeeus's blueprint integration which has changed quite a bit since I last fired it up and so I need to relearn how to get the development environment running which I'm struggling with at the moment.
I'm still working through getting the development environment running, but I have just done a full upgrade to HA 2023.9.1 and I don't get any of the symptoms that are mentioned in this thread. That's both good news (in that it's probably not code/build/HA related) but bad news because it might be tough to diagnose.
I need HA logs to see what is going on. In configuration.yaml
please add the following code:
logger:
default: info
The ought to be some traffic in home-assistant.log
from [custom_components.gecko]
and [geckolib.*]
. Please post here (but do redact any private data that you're worried about).
It might also make sense to check if anyone has fallen into this (as yet unfixed) bug : No entities created #67 . There is an issue if the watercare mode is out of range. It can be fixed from the in.touch app by ensuring that a valid watercare mode is actually selected...
That's got it working. I hadn't set a Watercare, it was using the default setting of twice daily for 2 hours which is fine. I modified the Standard profile to match that and the integration is now seeing the data.
With this discussion ongoing, does anyone know how to modulate the temperature?
Kind Regards John
On Tue, 19 Sept 2023 at 15:03, unjoking @.***> wrote:
That's got it working. I hadn't set a Watercare, it was using the default setting of twice daily for 2 hours which is fine. I modified the Standard profile to match that and the integration is now seeing the data.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>
": No entities created https://github.com/gazoodle/gecko-home-assistant/issues/67 . There is an issue if the watercare mode is out of range. It can be fixed from the in.touch app by ensuring that a valid watercare mode is actually selected..."
This fixed my issue too! :)
Thanks again gazoodle
I re-enabled the integration it was working great for a few hours and then again went unavailable, however the app works just fine. Latest build of HAOS. Please let me know whatever you need. I used this integration heavily. Is there any way to bring this up to the HS devs?
Same here, works for a few hours, then becomes unavailable. Restarting the integration fixes it, until it becomes unavailable again after a while.
Just wondering if there is a movement on this issue?
Logs would be useful to have. Default level is fine at present, hopefully there is some indication of why the sensor become unavailable.
Noticed since the latest update 2023.8.4 this integration apears to be broken,
full uninstall and re-install did not fix it either.
Integrations asks for IP address or auto but doesn't ask for the geko product module number.