It looks like there has been a change in Policy by Rainbird after 4.36.0. I do see some messages that rainbird change the access does go via cload authentication with the new firmware, and that local access is then blocked. If I do understand it well!
The hints and tips I can find (e.g ChatGPT) is not to update to prevent loosing local access.
I think we do have to contact Rainbird and ask them to create a solution for owners of a home automation system (like homey).
Pehaps the staff of the Homey organisation can help us with that , and for sure you should write a Complain / Problem Report
I will try to keep my system on the old firmware . . .
If other people have some Id what to do next they are welkome!
Did you leave the Homey mobile app while setting up the device? In that case, the “pairing session” expires and this error appears when you perform an action. You should not leave the Homey app during pairing
No, I didn’t leave it, but for now i also had a conversation with the US Rain Bird and they told me that they’re not interested in this problem. Also they went to cloud, not local anymore and because of this it won’t work.
But the error you mentioned is a Homey error. Those are usually triggered on timeouts (f.e. if Homey hasn’t received any response from your phone during the pairing). It’s likely unrelated to Rainbird
It might be possible to reverse engineer the mobile app though, depending on how hard they’re trying to block it. If they use a CAPTCHA, then it’s almost impossible (you’d have to use a paid captcha solver service, which is usually also against the ToS of the manufacturer). But in most cases it’s just a simple API/WebSocket, which can be easily reverse engineered
I don’t know if this helps but I just installed a rain bird today. I looked for he best soloution and I thought this was it. But I now see the connection issues on the 2.0 platform. I found this on the home assistant forum maybe this helps?
Integration based on the cloud.
I’m new to the rainbird but I can help test something’s if you need any help
I updated the test version of the app, which MIGHT be able to fix the issue.
My controller hasn’t been updated to v2 yet, and I dont get a notification about it either. But there are hints in both that Home Assistant topic, but also the Homebridge version which I incorporated in the Homey version.
You might need to pair again, using the PIN you set up, as a password. The IP address should still be fetched from your router if needed.
It’s been a while that I was active with my version of Rain Bird. I have a new test version with tons of new features. Not perfect yet, but getting there.
Is the interface / connection for the ESP-TM2 different of ESP-RZXe Series? @Luca_Lorenzi I updated the app with some extra options. Can you test it? Can you also test the app of Sorted.bits. If his app does the job I will delete mine.
This is the diagnostic report for your version: b7e121d3-8945-40f4-a0ef-3198384059fb
It seems like it is not able to connect to it. It goes on time out.
I don’t know if this is because the ESP-TM2 is on a different SSID (the 2.4 ghz only). Homey connects via ethernet.
Here are a few checks to determine whether your ESP-TM2 is still available through the local Rain Bird LNK/LNK2 API or whether it has been migrated to the newer Rain Bird 2.0 / IQ4 cloud firmware.
Which Rain Bird app are you using?
If you use the Rain Bird 2.0 app and log in with a Rain Bird IQ4 account, your controller may be using the new cloud-based connection.
If you use the older Rain Bird / Rain Bird Mobile app, local LNK/LNK2 access is more likely.
Check the controller firmware
In the Rain Bird 2.0 app:
Open the controller
Tap the settings/gear icon
Go to Controller Info
Note the controller firmware version and the LNK2 firmware version, if shown
Check whether the local API port is reachable
From a computer on the same network as the Rain Bird controller, run:
nc -vz 10.0.0.54 80
Please replace 10.0.0.54 with the IP address of your controller if different.
Result meaning:
succeeded / open: the local API port is reachable
connection refused: the device is reachable, but the local Rain Bird API is not listening on port 80
timed out: network, firewall, VLAN, Wi-Fi isolation, or wrong IP issue
Also try opening this in a browser on the same network:
http://10.0.0.54
A blank/error page is not always a problem, but if the browser immediately says the connection was refused, that confirms the local HTTP port is closed.
Please share the following information:
Controller model: ESP-TM2, and number of zones
Which app you use: Rain Bird or Rain Bird 2.0
Whether IQ4 is mentioned in the app/account
Controller firmware version
LNK2 firmware version
Result of nc -vz <controller-ip> 80
The Homey app currently uses the local Rain Bird LNK/LNK2 API at:
http://<controller-ip>/stick
This uses HTTP port 80. If the controller has been migrated to Rain Bird 2.0 / IQ4 cloud firmware, this local API may no longer be available, and the Homey app cannot connect to it yet.
Hi Brian, sorry I did not understand the question about the interface! Yes the controller is on the new cloud interface and I am using the Rain Bird 2.0 app. I downloaded the latest version of your work.
I am able to connect the ESP-TM2 to Homey. I’ll check in the next 48 hours if it updates correctly!
Hello, I installed the app and everything worked locally, magically nothing goes and if I enter the IP address of the control unit in homey, the latter works vice versa. I also downloaded the test version but you have no solutions?
