Thank you for the very clear report and for listing your firmware versions, that is very helpful.
This does not look like a Gecko firmware compatibility problem.
The error “Missing Capability Listener” points to an app-side issue in the current InTouch2 release path, where read values can still work but write handlers are not correctly active.
A beta is now available with updated support (including the newer in.touch platform), and I would be very grateful if you could test that version.
After installing beta, please remove and add the device once more, then test changing target temperature and water care mode again.
If it still fails, please share:
Homey firmware version
Exact app beta version
A short diagnostics log right after one failed write attempt
Thanks again for helping test and improve this app.
Hi Thomas,
Thank you very much for your quick reply and for the explanation.
I’m currently travelling and won’t have access to my Homey or spa for a little while, so unfortunately I’m not able to test the beta version right now.
As soon as I’m back home, I’ll install the beta app, remove and re-add the device, and test both target temperature and water care mode as you suggested.
If the problem still remains, I’ll send you:
● Homey firmware version
● Exact app beta version
● A diagnostics log immediately after a failed write attempt
Thank you for continuing to work on this app. I really appreciate your support and I’m happy to help with the testing.
Bästa hälsningar ,
Tomas
I currently have Gecko InTouch2 version 1.4.0 installed from the Homey App Store.
Is this already the beta version with in.touch 3 support, or do I need to install a separate beta build? If so, could you please send me the beta link?
I have one observation that may help with troubleshooting.
A few days before leaving for vacation I was still running version 1.4.0. Without me changing anything, the app suddenly started working correctly. Homey read all values correctly and I could control both Water Care Mode and Target Temperature, both directly from the device page and from Flows.
The day before leaving, Water Care Mode stopped working again, but Target Temperature was still fully controllable.
I assumed at the time that you had changed something on the app or backend, but later I saw your announcement about the beta version.
Unfortunately, after installing version 2.0.1, I still have exactly the same behaviour as before.
Since the old version actually worked for a while without any local changes on my side, I wonder if this could indicate some intermittent registration or synchronization issue rather than a firmware compatibility problem.
Hi, really appreciate the effort going into this. However, I’m not able to get this to work. Keep getting an error (From Gecko site) about unregisterted callback url. See attached picture.
Tried adding my Gecko InTouch3 from both web apps and iphone/Ipad apps.
This happens after entering the IP and MAC address.
I just got back from vacation and saw your posts. I haven’t made any changes since I released beta version 2.0.1. Which version are you testing at the moment?
Hi,
A new beta version of Gecko InTouch for Homey is now available, adding support for both Gecko InTouch 2 and Gecko InTouch 3 controllers.
What’s new
Added Gecko InTouch 3 support through Gecko Cloud.
Improved the reliability of the local InTouch 2 connection.
Improved temperature and target-temperature synchronization.
Improved handling of multiple local InTouch 2 sessions.
Added separate pairing flows for each controller generation.
Updated documentation and troubleshooting information.
Connection methods
InTouch 2 connects locally using the controller’s IP and MAC addresses. No Gecko account is required.
InTouch 3 connects through Gecko Cloud using secure OAuth2 authentication.
InTouch 2 and InTouch 3 are handled by separate Homey drivers because the two controller generations use different communication protocols.
Supported features
Current water temperature
Target-temperature adjustment
Water-care modes
Homey Flow cards for temperature and water care
Light control for InTouch 3
As this beta release introduces support for both InTouch 2 and InTouch 3, your feedback is greatly appreciated. If you encounter any issues, unexpected behavior, or incorrect values, please report them with details about your controller model and Homey setup.
Version 2.0.7 — Added dynamic in.touch 3 pump and lighting controls based on the spa’s reported configuration. Improved accessory naming and state synchronization in Homey.
In the latest version, 2.1.0, the Homey app reads the correct values, but the hot tub does not register the values entered into the Homey app. After a few seconds, the value reverts to the one currently held by the hot tub.
In the two versions prior to 2.1.0, it was the exact opposite.
Thank you for reporting this. The issue affected InTouch2 and was caused by the temperature command taking longer than Homey’s timeout limit. I have prepared and tested a fix where the new target temperature was accepted by the hot tub and remained correct after the app refreshed its values.
InTouch2 is a little more challenging to support than InTouch3 because it communicates directly with the spa over the local network using an older UDP-based protocol. Commands require several handshake and confirmation steps, and responses can vary between spa controllers. InTouch3 uses Gecko’s newer cloud connection, which provides a more structured and predictable way to read and update values.
The fix will be included in the next update 2.1.1.
In the latest version (2.1.1), Homey is not reading the changing values from the spa, and the spa is not accepting the setpoints specified in the Homey app.
No error messages appear in Homey.
If I uninstall the device in Homey and then reinstall the device, the correct values are read, but they remain static.
The same thing happens if I restart the app. Best regards, Tomas
I’ve made a new fix for in.touch 2 (version 2.1.2) that should improve status updates and apply temperature changes within approximately 1–3 seconds without the value reverting in Homey.
Could you please test changing the target temperature a few times and also verify that changes made directly on the spa appear in Homey? If the issue remains, it may be related to the local network, as in.touch 2 communicates over UDP and can be affected by weak Wi-Fi, interference, mesh access-point switching, or packet loss. I haven’t received similar reports from other users, which may indicate that the problem is specific to your spa or local network environment.
The app successfully connects to the spa and reads the current values correctly immediately after startup.
However, after the initial read there is no further communication:
Changes made on the spa are never reflected in Homey.
Changes made in Homey are never applied to the spa.
Restarting Homey does not help.
Restarting the Gecko gateway does not help.
Both Homey Pro and the Gecko gateway are connected by Ethernet to the same network, so this does not appear to be related to Wi-Fi, mesh roaming or weak signal.
What is interesting is that earlier versions of the app have worked correctly on exactly the same hardware and network. For example, version 1.0.4 worked perfectly for me for several days just before my vacation, with both live status updates and control of target temperature and Water Care mode.
To help narrow this down, I can test the previous app versions one by one and identify the last version that works and the first version that doesn’t. That may help pinpoint where the problem was introduced.
Hello Thomas, thank you very much for the great app unfortunately I have problems with the login that in.touch3 see screenshot do you have an idea about it?
