Ah, ok. So do the service calls work now, too?
1 Like
Apparently so! But they definitely didn’t yesterday. That may have been all pre “press the Configuration” button as i was having hit or miss success with this device before clicking on that
** edit ** i did go back into my Node-RED flow and ditched the GET node call to Hubitat and turned it into a “Call Service” node and now it’s working great.
I have a question too. Don’t know if it’s Hubitat or HA that gives me a pain. I have some generic shutter module from AliExpress. It works, but the calibration is not. So totally open is like 89 and closed is 81. And if I press the calibrate button in HE it changes to some other value pair. But never 0 to 100. (Using the qubino z-wave shutter driver in HE)
Is there any way to configure two hubitat hubs to interface with home assistant?
You should be able to add two instances of the integration, and point each one at a different hub.
1 Like
Edited: Ok so I just decided to ignore HACS in the end, because none of the options in the instructions were actually on offer, and installed this integration manually. Working now, thanks.
Ignore below
I feel as if the readme is missing a step or something. I am ok until here:
To configure the hubitat integration, go to Configuration -> Integrations in the Home Assistant UI and click the “+” button to add a new integration. Pick “Hubitat”,
Hubitat isn’t in the list. I have already tried a restart of HA.
NB I had to install HACS manually, as the install script kept dropping straight through to the Else, but I do have seem to have HACS installed properly, since it now appears as a device and an entity after adding it as an integration.
Sorry about that – HACS has had some significant updates lately, and my installation instructions…haven’t.
1 Like
Lol! That’s life. And it would be even worse if everything stayed the same just so instructions didn’t get out of date. 
First, thank you Jason for your awesome support of us newcomers. Your integration has been amazing and really has made the home automation process possible.
I’m trying to learn how to use node red at this point for HA automations. You had previously provided assistance in how to use additional buttons on my inovelli light switches natively through HA (came up in automations when they were selected from the config->devices menu).
I’m running into a road block with node-red, however, when I try and listen on event.state with a debug node looking for all messages when pushing these additional buttons. I know this is a little off topic, but was wondering if you had any idea why I wouldn’t be seeing these events through node-red? I know the buttons work as I’m using them through native HA automation. Again, incredibly appreciative of all the effort you provide to the community. A separate question, do you have a donation page or anything to help support your projects?
1 Like
Hi! I’m in the same boat as some other users have been. Regardless of installation method, HACS or Manually the Hubitat Integration will not show after clicking the + in the Integrations menu.
I run a Home-Assistant-Core docker instance (v 0.114.4), I have restarted the Home Assistant through the menu and also my container multiple times, but I can not find the issue. I only get the message in the Home Assistant log that states “You are using a custom integration for hubitat which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.” But the Integration will not show.
What can I do? Thanks.
Edit:
Sorry got it… Browser Cache, Ctrl+F5 to refresh, and there it was… Thanks.
Thanks! I’m glad the integration is working out for you! 
How are you listening for events in NR? If you add an events: all node and set its event type to hubitat_event, you should be able to see any events emitted by the integration. Note that the only events emitted right now are for triggerable events (button presses and lock events).
2 Likes
<-- makes a note to suggest the hubitat_event in the future. I was trying to help @bgreet out on the NR subforum and couldn’t for the life of me figure out what event the integration was supposed to be firing. 
1 Like
Something else I need to mention in the README…
2 Likes
What’s the domain for the hubitat_event?
There is no domain – events just have names (so far as I’m aware).
1 Like
What’re you trying to do in NR? Take some action when particular button is pushed?
exactly. ie kitchen lights button 7 pushed turn on x lights
A simple example of a function node that would do the trick
let evt = msg.payload.event;
if (evt.device_id === "866" && evt.attribute === "pushed" && evt.value === "7") {
return { "payload": "take_action_through_output" };
}
else {
return null; // won't continue through the output
}
2 Likes
Your button press is found in msg.payload.event.value
I run it through 2 switch nodes.
I have my Events:all listening to hubitat_event
This feeds a switch node to detect which light switch is used. msg.payload.event.device_name
Then another switch node to detect which button is pushed. msg.payload.event.value
Finally I have it run whatever actions I want.
One thing I did have to do is put an RBE node after hubitat_event. For every button press I make I get 4 identical hubitat_events so it would trigger every action 4 times. The RBE node prevents the duplicates from moving forward.
2 Likes