Because the current z-wave integration in HA isn’t up to par. But there is hard work done to make it up to par soon. The Future of Z-Wave in HA - QT-OpenZWave
2 Likes
Mine has been working well but one or twice in a week there’ll be a switch that’s not showing the correct state. When in Hubitat, the switch is off but in HA, its on. I wonder why is that
Tough to say. Possibly Hubitat didn’t send an event when the switch status changed, or there could be a race condition in HA that caused an event to be lost. If you enable debug logging for the integration you can see what events are being received from Hubitat, which could help track down what’s happening.
It might help for the integration to do periodic forced updates from Hubitat, as well.
ya going to turn on the logging and see how it goes. thanks
Does this work in HassOS 4.11? I can’t add the repository to the Add-on store. I click on the three dots, put “jason0x43/hacs-hubitat” and then click add and it doesn’t do anything. If I try to install manually by downloading and placing the files in custom_components folder the log shows that it’s installed but I don’t see it listed on the Add-ons Dashboard.
It does work with 4.11. However, this is a custom component rather than an add on, so it’s installed using HACS (or manually) rather than through the Add-ons interface.
Thank you! Guess I need to read a little more carefully next time. Got everything installed and running great.
I finally got around to really giving Node-RED a more thorough try. Wow, I’ve been missing out. Flows are easier to reason about (to me) and test than AppDaemon apps, and the scheduler has been more reliable (I was seeing a lot of flakiness with solar timers in AD). Interestingly enough, NR is also much less CPU intensive; According to Glances, AD idled at around 9% of a core, even with just a single active app, and peaked at around 15%, while NR idles at 0% and peaks at 1-2%.
4 Likes
Welcome to the rabbit hole 
I love it!
My friend rags on me all the time.
I’ma very visual guy.
I love watching flows execute when I can’t figure out what’s going on.
Now if they’d just put out a new release that fixes the mobile scrolling bug. I always want to look at flows on my phone or tablet, but that’s a pain right now.
Yeah it’s not overly useful on mobile.
Still a hands full of things that aren’t great on mobile.
.
This integration is going to be a life saver in Ecobee-land
Every time a restore is needed in HA (which seems to be often enough), the Ecobee “official” HA integration gets broken.
So this time I am trying the Ecobee built-in app for HE exposed to HA via this add-on… this should fix the issue of “uninstall-and-resinstall” to re-authenticate.
I’ve been loving this integration thus far… Hubitat is fantastic at pairing/drivers and this component has been spot on on bringing them into HA (and as a result, exposing to Node-RED).
The only device i’ve run into problems with is the SecurrFi Peanut Plug, so from Node-RED i’m just doing straight up GET calls to HE’s MakerAPI as using the “Call Service” node doesn’t seem to do anything… that’s alright, I wasn’t/am-not expecting 100% here, but 98% is perfectly fine by me!
Any reason you don’t use the Homekit integration for EcoBee control? It also has the added benefit of being fully local and not reliant on their cloud.
1 Like
Is there a way to install this integration when HA is running in a virtual machine?
If you already have HACS installed, use that. If not, you’ll need access to HA’s config/ directory, which could be in the VM, or in some external mapped directory. Once you’ve found the config directory, follow the manual install instructions in the README (or install HACS and use that).
1 Like
What kind of issue have you been running into with the Peanut Plug?
I’m trying to stay as far away from HomeKit as possible… i’m literally down to one single HomeKit device in the house and i can’t wait to get rid of it, as soon as money allows
Using the Call Service stuff to change state to “on” or “off” was having no effect on the device (either from the Developer Tools tab or from within Node-RED.
Does the device show up as a controllable entity in HA? Like, if you’ve added the switch to the HA UI and you toggle it, does the physical switch change state?
It does now, i can set up an entity card with the id for the peanut plug (that is ported in via this component).
The issue may have been the need to click the “Config” button in Hubitat Dashboard after pairing it.