Hi Brian, I tried to start one zone and it worked with the default time irrigation.
The Controler online variable is updating correctly.
The Is Active variable seems to work.
The time left updated itself after I started the zone from homey but it seems to be blocked:
This variable does not update when the ESP-TM2 follows programs configured in the Rain Bird 2.0 app.
Other variables never updates themselfs.
Can I help you in some way?
@Luca_Lorenzi Thanks, this is very useful feedback.
I found the likely cause: the IQ4 cloud returns the live station data nested inside runStationStatuses, and the app was not reading that structure correctly yet. I have adjusted this for the next test version, 2026.8.1.
What changed in the next test build:
remainingRunTime when the cloud provides itTest instruction after updating to 2026.8.1:
Active zone and Time left update every polling cycle.Is active and Active zone within about 30-60 seconds.The most useful next diagnostic is one captured while a zone is actively running from the Rain Bird 2.0 app, because that will show whether the IQ4 cloud returns remainingRunTime for controller/program starts.
@Luca_Lorenzi The new test version 2026.8.1 has now been uploaded/published for testing.
You can install/update the test version here:
Please test with the ESP-TM2 IQ4 device like this:
Active zone, Is active and Time left update.This version specifically improves IQ4 runtime/status synchronisation by reading nested runStationStatuses, remainingRunTime and IQ4 event logs.
@Brian_Monninkhof I updated the app and I have done what you said.
now the following variables are working correctly:
Active Zone, Active Zone Number, Controller Online and Is active.
I did not test the “Rain set point reached”, next to do.
Water usage and daily water usage are always zero but i think the ESP-TM2 cannot measure these parameters.
The time left feature updates but the time displayed is not correct.
For examble I launched one zone for 1 min from the rain bird 2.0 app and it displayed 1h35min left.
I launched one zone from this panel but the irrigation time setted was 1h40min instead of 1min default time irrigation.
New test release: Rain Bird v2026.8.4
The repair flow has been redesigned based on the recent testing feedback:
The privacy-safe bug report never includes passwords, IP addresses, hostnames, usernames or tokens.
The build is available for testing here:
Please test the repair flow and report any remaining navigation or layout issues in this topic.
@Brian_Monninkhof I’m also trying to test your version of the rainbird app.
So far no luck. I’m using the old Rain Bird app and it can connect without any problem to my rainbird controller ESP-TM2.
It did work before with the original Rain Bird app but that also doesn’t work any more. It keeps connecting forever.
Can i debug something for you to see where it might go wrong?
Yes. The app has a privacy-safe diagnostics function.
Open the Rain Bird device in Homey, choose Repair, then Diagnostics and Bug report. The report removes passwords, usernames, IP addresses, hostnames, tokens and private controller IDs. Please paste the complete report here, including the error code and the Rain Bird firmware version if you can see it.
For an ESP-TM2 that has moved to Rain Bird 2.0/IQ4 firmware, a local connection to port 80 may no longer work. In that case the old local driver will keep timing out even though the official Rain Bird app still works. The controller must first be fully configured at iq4.rainbird.com, not only in the mobile app.
I have updated the next test build with an experimental IQ4 Cloud driver and a selectable authentication method. The mobile-app authentication route is now the default because the web portal route can be blocked by Rain Bird account restrictions. The change is not published yet.
For the current local test, close the official Rain Bird app and any Home Assistant/HomeBridge integration before pairing, because older LNK/LNK2 controllers generally allow only one active connection. If the new IQ4 route also fails, the diagnostics report should show whether the failure is during cloud login, token exchange or controller discovery.
I checked the app and i have controller firmware 2.29. Cannot access the webinterface on port 80.
Moving to the new app is some what difficult because i cannot access the controller that easy. But i will try to migrate later this week.
I’ve send you a diagnostics report 1ef130a7-c34a-40e2-b760-ed713529b0cd
Thanks, that confirms the important detail: firmware 2.29 no longer exposes the local port 80 interface, so the local LNK/LNK2 driver cannot connect to this controller.
The diagnostic report 1ef130a7-c34a-40e2-b760-ed713529b0cd has been received. Please complete the migration and setup at https://iq4.rainbird.com when you have time. After that, the IQ4 Cloud driver in the next Homey test build should be the correct route.
There is no need to keep testing the local IP address for now. I will use your report to compare the cloud login and controller discovery steps once the migration is complete.
I’ve migrated the controller to rain bird 2.0. Now i’m able to add it to homey now. Do you want me to test something specific or just let you know what works and want doesn’t? Thanks for all your work on this app.
Hi Keyracer, you don’t need to test anything specific. Your response is absolutely sufficient. It’s great to hear that the migration worked and that you can now add the controller to Homey. Thank you very much for testing and for the clear feedback!
Hi Brian, i cannot turn on a specific zone for x minutes. Its only turn on or off. What happens when i turn it on? I need to control my zones for a specific amount of minutes.
Which i’m able to do trough the rain bird 2.0 app. But i would like to control everything via homey if possible.
Hi Keyracer, there are two ways to configure and run a zone:
The Flow option is the most suitable when you want a fixed command for a specific zone, or when you want to start it through Siri, Alexa, or Google Assistant. Please save the Flow and run it manually once to verify the selected zone and duration.
Hi Keyracer, thanks for checking this. I found and fixed an issue in the Flow-card registration. The Rain Bird-specific cards are now exposed through the zone_control capability for both the local LNK/LNK2 driver and the IQ4 Cloud driver. This includes starting a zone, starting a zone for a selected number of minutes, stopping a zone, stopping all irrigation, and resetting water usage.
Please install or update to version 2026.8.5, open the device in a Flow, and check whether the Rain Bird-specific cards are now visible. Because your ESP-TM2 was migrated to Rain Bird 2.0, please use the Rain Bird Cloud (IQ4 / Rain Bird 2.0) device type. Let me know whether the cards and Rain Bird icon are now shown.
Hi Brian, if updated the app. I see a difference in the cards. But they only show up if you select the app instead of the device. And only THEN is changed the AND cards are still the same.
Update: when i use the card start zone for x minutes. I can select the device but i can’t select any zone. I tried to enter the zone number but this also doesn’t work.
Hi Keyracer, thanks for testing this. You were right: the previous build exposed the Rain Bird actions as App cards instead of device cards. I corrected this in version 2026.8.6.
The local LNK/LNK2 actions are now registered on the local Rain Bird device, and the IQ4 Cloud actions are registered on the Rain Bird Cloud device. I also registered the zone autocomplete for both drivers.
Please update to 2026.8.6 and create a Flow by selecting your Rain Bird device first. For your migrated ESP-TM2, use the Rain Bird Cloud (IQ4 / Rain Bird 2.0) device. The Rain Bird-specific cards should now be visible under the device, and a zone should be selectable.
Please let me know whether the cards and zone selection now work correctly.
Hi Brian,
The THEN cards work now by selecting them via the device. Zones are selectable now There is just one bug in the AND cards. Its still only one card. Thanks for your work on this app its really appreciated
