I would love this, finding the older iris version is nearly impossible and this would be a perfect solution for me, but having it turn off when we leave or a leak is detected is a must
same here. i am in
Have you considered any z-wave or zigbee water valves? They can work natively with Hubitat.
Do you have a recommendation? The ones I saw on Amazon were either actuators that move a levered valve, or cost $150 and above.
Presumably, you want this for an irrigation valve and not a whole house water valve, correct? If that's the case, all you need is a motorized NC ball valve and a Hubitat controlled outlet.
An NC ball valve is about $20.
https://www.amazon.com/HFS-Electric-Solenoid-Valve-Water/dp/B018WRJYWM/
The cheapest Hubitat controlled outlet I know off is the Ikea Tradfri Control Outlet, which is $10.
2 Likes
Sigh... I just posted Drip Irrigation Controller Suggestions? and then stumbled on this thread. Would people recommend this device? I was really hoping for something that"just worked" but if I have to port this ST integration...
I’d love to see this integrated, especially since I bought one and would happily switch from using their app to hubitat, even if it’s just a manual on/off
1 Like
I've at least got this code running at this point and reporting status... allowing you to control the device is going to be a lot more work because ST required you to setup a NodeJS server on an rpi. HE supports WebSockets natively so we can code all of this directly in HE... it's just going to to be a lot of work to do!
1 Like
Maybe it won't be as bad as I thought, got manual open/closed working now via the websocket. Need to work on pulling status updates via the web socket instead of polling.
1 Like
There's still a bunch of cleanup work, but if anyone wants to give it a try, GitHub - dcmeglio/hubitat-orbitbhyve: Provides integration with a Orbit™ Bhyve Timer and SmartThings there is an app and 2 drivers you need to install. It pulls a lot of data from the valve, but the only command right now is to open/close. When you open the valve it will only stay open for the "manual run time" setting in the app. Wouldn't mind if a few people played around and let me know how it works.
All I can test with is a single hose timer with a single hub. I'm curious how it works if you have more than one! I'll try to get any feedback from people incorporated this weekend but it is a holiday so...
Edit: don’t set the refresh too frequently. I’ll likely remove that actually. Almost all the data is pulled real-time over the websocket
4 Likes
Hello There
I already installed the app and the 2 drivers..... this is status I get in my device
This is the event page
I am not 100% sure if I understood correctly your post, but just to let you know that I can see the status of the Obit device ON/off when I manually trigger the Orbit through my Obit mobile application, but I cannot switch on/off the device through the Hubitat device page... IS this the right behavior? Thanks for your work
Any thing in the logs? It should work from within hubitat. Clicking the open/close buttons from the device page should work.
Did it create a device for your bhyve wifi hub? If so could you go to the device page for it, scroll down and take a screenshot of this area:
That master setting is what I'm looking to see
Edit: I also just pushed a new version of the app that should solve the line 280 error. You're seeing two unrelated errors.
1 Like
Sorry, could you provide more information on what devices you have? That's a sprinkler, not the wifi hub. Do you not have a wifi hub? What kind of device is this? Did it add any other devices? I'm really surprised why you have component devices... I don't see anything in the code that does that. Could you click on one of those components and also show me the same screenshot?
Ok so I think you have a multi-zone sprinkler timer, NOT a hose timer, is that correct? If so you wouldn't have a hub/bridge. It would appear the original ST integration didn't support this configuration (at least not fully?) I think I got it closer to working, but I can't test because I don't own that device. If you could uninstall the app, and download the latest app and driver code I think it might work for you now. The thing I'd like help investigating is that the open/close status, both when done from the mobile app, from HE, and from the schedule, is that ONLY the correct zone is shown as open/closed at the right time. Like I said, I can't test that because I only have a single zone 
This is the device I have
Hello I have uninstalled everything and re install with the latest App & Drivers...
This is the device I am testing. I have the 6 stations and not the 12 stations
I have tested the following
1.) Obit Bhyve Sprinker timer.
I can see the device status as follow
- battery : 100
- id : XXXXXXXXXXXXXX
- is_connected : true
- lastupdate : Station 1 last connected at Tue Jun 30, 6:24 pm
- manual_preset_runtime_min : 10
- name : Orbit
- next_start_programs : Station 1: A
- preset_runtime : 10
- rain_delay : 0
- run_mode : auto
- schedulerFreq : 1
- sprinkler_type : true rotor(s)
- station : 1
- type : sprinkler_timer
- valve : closed
State Variables
- webSocketOpen : true
but I cannot switch on / off... If I switch on/off through the original Bhyve app I see the status changing in HE.
I see the same behavior... I cannot start the orbit manually. For your information I only have 1 zone working in my sprinkler system
Here the logs
[warn]
Orbit device requested to manually OPEN but scheduled_auto_on = false, ignorning request
Orbit device requested to manually OPEN but scheduled_auto_on = false, ignorning request
Orbit device requested to manually OPEN but scheduled_auto_on = false, ignorning request
I have also tested it with the Automatic schedule on and off in my Bhyve app.
2.) Orbit Bhyve Bridge.
Device is not recognized at all
And now using the orbit native devices from Hubitat ( I have 3 listed in the system)
3.) Orbit Sprinkler Controller Station Component.
Device is not recognized at all
4.) Orbit Hose Water time.
Device is not recognized at all
5.) Orbit 12 stations Sprinkler controller
Device is not recognized at all
What do you mean by “device is not recognized at all”?
It is not showing any status... I am not sure if this is because I need to link again the device with your app
