Two things:
@aaiyar Thank you, got it working with both hubs.....
your awesome for taking the time to reply %100
I seem to be having an issue. So I currently have 3 c7 hubs. I have HA running on a prox node in my Proxmox cluster. I’ve not dig into YAML yet to understand how rules and scenes are use in HA, however I recently got a C8 pro hubitat hub and installed HADB on the c8 pro hub. I’ve been moving all my ZWave and zigbee devices from my C7 hubs into HA. The issue I’m having is once a device is moved into HA and I add it into HADB, periodically HADB loses connection to HA and child devices aren’t getting updated from HA until I go back into HADB and re check mark them (they become unchecked and in some instances are still showing checked but just not responding). Has anyone else had this issue? Been wanting to use Hubitat for all my rules.
Currious why you didn't simply migrate your Zigbee and Z-Wave devices from your C7 hub to your C8 Pro hub?
Indeed, this is quite odd:
Loosing connection to HA point to some network issue. I don't remember anybody reporting such a problem. My connection to HA has been running to HA for 4 years without disconnect (unless reboot of either one and even so HADB reconnected on its own).
As for device unselecting themselves, I can't see how this can happen unless an old database is restored.
A few reasons. I want to cut down on the number of hubs in my environment. I have 4 hubs (3 c7 and 1 c4) now for zigbee and ZWave placement relative to devices. And to be honest, I’ve seen much better radio connectivity in HA with my SLZB-06M radios for zigbee and thread with POE placed strategically in my house relative to devices. The zooz 800 series LR USB stick connected to my proxmox node is in the same location as my ZWave hubitat hub. So it made sense for me to connect all my devices to HA which I also have on local backup to my NAS. I want to shut down 3 additional hubs (2 c7 and a c4). I tried to connect my zWave plus Schlage connect locks to hubitat zWave c8 pro initially but the response time on the locks was minutes before a command was picked up and issued. I saw others in the forum with the same problem with no fix from the staff other than to saw it’s a firmware issue. So I moved them over to the Zooz 800 LR in HA and response times are immediate.
So any idea why my children are falling off in HADB in hubitat?
I’ve been performing reboots on my HA to fix a few issues with the system and as I install stuff. Is it possible that that’s causing the issue? Is there a device limitation to HADB?
No device limitation on HADB. Perhaps rebooting HA is causing delayed reconnections. In that case you can press the initialize button in HADB parent driver to force an immediate reconnection.
This would not cause devices to unselect themselve though.
Also If you change entity name in HA, it won't be reflected in HE. The entity will be treated as a new device and the old one will discarded.
Here’s an example of what I’m talking about.
I have a rule to not turn on the lights if illumination from my tempest is above 8000.
The rule shows it’s one 10,000 from earlier this afternoon. But now, it’s below 8,000 and the rule hasn’t updated to reflect the new value.
In HA it’s showing
In HADB child it’s showing:
I have pressed initialize but it’s made no difference.
You said you are migrating between hubs. Is it possible you have multiple instances of HADB running between your multiple Hubitat hubs?
Yes actually I do. Should I disable the other instances?
Yes. Should only have one active and pointing at the same HA installation.
Thanks... I dug into this a little more since all my rules were broken... found this in my logs.
Went back through and retraced the steps for setup, and found in HAOS, I was missing my long lived access token. So created a new one and updated the app. Hopefully this is the smoking gun for me.
Requesting a new binary sensor device type which doesn't exist today. I've added Ring Outdoor Contact Sensors to my gates outside. In Hubitat they show up as contact sensors, but in HA, they show up as binary sensor intrusion.
See the attached debug log:
Thank you for any help you could provide.
As your logs are showing, it is a binary sensor with a device_class of "door" which is essentially a contact sensor. This is what HADB use to define the device type to map it to (door --> contact sensor). The mention of intrusion is only part of the default name given by HA and can be change to anything you like.
As for automation, the values of "open" and "close" reported by HADB for this device are readily usable as is.
Unless it has a tamper switch, it shouldn’t be functionally different from a typical contact sensor.
So you’re saying to just rename the entity from intrusion to contact?
It does have a tamper switch but that should come through as a separate entity but I honestly don’t care about that, open / close is what I need to run my rules.
Download the Hubitat app
