You should but this is done on your hub and not via GitHub or HPM. Go to apps and click Add User App and choose HADB and this will install another instance along with your existing.
Now this said you should rename the other instance first so you can determine which app is for which HA instance. You can do this by opening the existing app and scroll to the last App Name setting and adjust and save.
Thanks for verifying this. When I said GitHub I was referring to the user app in my hub that was there from GitHub via Package Manager. Anyway worked perfectly and now I have two bridges! All are running well on my Synology NAS.
I just did this last month. I took a backup on my PI, copied that up to my NAS storage, then imported it as part of the setup on my Synology.
At that point, I went into the HADB app, and changed the IP address to that of my NAS and everything just worked instantly. Whole process took me all of 20 minutes. (NOTE: This included Ecobee over Homekit as well as the My Subaru and a few other cloud integrations that I thought would be problematic but were not at all)
I was going from HA in a docker on RPI to HA on a VM in synology. (Note: I was actually running both instances of HA for about 5 minutes without issue - Just remember to point your phone HA app and browser bookmarks to the new location as well).
I should note that I did not have any Zwave or Zigbee devices connected directly to HA. If that is the case, I am not sure how the restore process works. But, I have read it brings EVERYTHING over as is.
Yep no issues IF you aren't using Zwave or Zigbee dongles. My efforts were/are two fold:
It's mainly the HA Zigbee2Mqtt I want as all of my Zwave is already on ethernet and not in HA/HT. When you get them all on ethernet if something were ever to go down (HA/HT/HS) just by changing a few addresses you're up and running in 10 minutes WITHOUT repairing (including/excluding/pairing) all of your devices.
My main automation system is Homeseer (HS). I've been using it for about 10 years now but I also use HT and HA because I like some of the apps/integrations better on HT/HA. I can easily pull them (devices) into HS from either platform. HS is very powerful. The event/automation engine works extremely well. I could run everything in HS just using their plugins, etc. that I currently use in HA/HT but I like the best of all three worlds. All of the working together is easier than most would think but not for the faint hearted!
Since I'm retired and I like to tinker with the systems It keeps me occupied when I want fool around with them. Also it keeps me out of the bars!
What?
Probably this on HomeSeer, which I thought they upgraded to 700-series at some point but can't find anymore and wasn't entirely sure if they were selling at all:
Apparently, it can also be used with Z-Wave JS directly over TCP (I wasn't sure what level this worked at, like maybe it was a tiny HomeSeer client or Hub Mesh-type solution--but that's what their docs say, so you don't really need HS at all). I've seen similar coordinators for Zigbee2MQTT, and apparently you can even use one on the USB port of this device the same way on the same Ethernet (or Wi-Fi, though not recommended) connection.
Yes I'm using the Znet 700-series so it is Zwave to ethernet. The Znet (basically a RPI) has a Zwave-700 hat so yes you are using the internal Zwave coordinator hat in the Znet to communicate ethernet With the Znet you can also add a Zigbee dongle to it and have your Zigbee devices communicate over it as well.
HS made a great decision awhile back and are now using Zwavejs for their ZwavePlus plugin interface. Also the are now using Zigbee2Mqtt for their ZigbeePlus plugin interface. Both work extremely well and they can be backed up and restored if needed in minutes.
There are some over at the HS forum that have made homebrews of the Znet. Basically a RPI that has ser2net installed to open up ethernet and expose the USB ports if you want to hang a dongle in one for Zwave Or Zigbee. For me I don't think the bang for the buck is there as you can get a Znet for less than an RPI and a dongle for Zwave but to each their own.
Zigbee is another story as I'm using the SMLight SLZB-06-M (you want the M as it's doing ember) ethernet. You can put one anywhere you have ethernet, power it up (very low power USB C or POE) and away you go. You can also use them wifi and I have tested them that way and they worked fine. For me where I have them (two) there is ethernet available and I trust it more than wifi.
My main goal is if something ever goes down, which I haven't had in a very long time I want to be able to get back up in minutes AND I don't want to be going around hell's half acre joining/pairing devices/dongles etc.
By the way I forgot that you can get an older Znet-500 series (Zwave Plus) and if it has 1.0.25 firmware (which most do) on it you're fine. You can buy them for about $50.00
I connected my LG Washer and Dryer in HA, since the Hubitat integration available does not work to keep the account connected, and that integration is not being worked on by anyone to fix that.
The HA bridge creates a device for each entity, so I ended up with about 24 devices as child devices, between both the washer and dryer, with one for each attribute.
I wrote an app that subscribes to the value attribute of all of these single attributes devices created, and then it pushes them into two virtual custom drivers I wrote for the washer and dryer, so I now have a washer device and a dryer devices that contain all the attributes as if they were single devices with many attributes.
This is working well, but I wondered if there is an easier way for me to just get all the attributes from the bridge in one swoop and put them into a custom washer or dryer device in one shot, and not need 24 devices to control what is actually two devices.
The drivers provided with HADB have these lines, as it parses through each description:
//All attributes passed from HA are available and can be leveraged by a custom driver
if (it.name in ["attributes"]) {
state.attributes = it.value
if (txtEnable) log.info it.value
}
I added some debug statements to this loop and each device only gets the value attribute for that one device. Is there no way to get every attribute into a description map to parse all the attributes in one shot with a single custom driver to assign them to the correct attributes in the custom driver?
Probably not, but it can't hurt to ask. The "consolidation" app I wrote is working fine, but I was looking to make this more efficient to get all the attributes assigned into a single custom driver directly.
This depends entirely on HA. If a HA integration define only one entity for each attribute, that's what we get. If an entity pack multiple attribute in the same entity then they are showing in a single HE child device.
Edit: Sensors are a different story. HE often use separate generic component for each capability. This how and why sensors were mapped this way from the begining in HADB. It would require a significant rewrite of HADB to behave differently.
Edit2: Thinking about it, each sensor would end-up being an omni sensor with all conceivable capability... not realy better.
Yes, that is what I expected, like how HE creates a child device for every switch on a relay board.
I was thinking of a map containing each entity and its value, for every entity I have checked in HADB, stored in a child device as an attribute so I could parse it out to my washer dryer. But that would need to be updated whenever any entity checked was updated...
I'm good with what I am doing now, and it is nothing worth updating code for.
Thanks for the feedback!
Edit:
Yes, in HA it is two devices in the ThinQ integration, with 42 entities, and they are almost all sensors.
I am no longer able to add additional devices from Home Assistant to Hubitat through the Home Assistant Device Bridge. I am able to click on the new devices that I want to add, but after I click "done" the new devices don't come through. I tried to repair the app under the Hubitat Package Manager but that didn't help. Any ideas?
Unless the devices receive state updates at the HA end, new child devices will not be created on Hubitat.
These are motion sensors so would receive state updates -- I have several others similar to the ones I'm trying to add that I was able to bring into Hubitat from Home Assistant.
Trigger each motion sensor and see if a Hubitat child device is created. Also turn on logging.
BTW, I'm moving this thread to the HADB thread.
Are you seeing motion on the HA side?
Thanks for moving thread to proper area. I trigger the motion sensors -- hubitat child still not created.
from the log:
dev:50432025-02-23 07:29:49.132 PM
debug
parse(): description = {"id":1,"type":"result","success":true,"result":null}
dev:50432025-02-23 07:29:49.124 PM
debug
parse(): description = {"type":"auth_ok","ha_version":"2025.1.4"}
dev:50432025-02-23 07:29:49.116 PM
debug
parse(): description = {"type":"auth_required","ha_version":"2025.1.4"}
Yes, seeing motion on the Home Assistant side.
Double check that you have selected the correct entity in the HADB app. I have done this by accident before. Checked the one above or below the occupancy entity by mistake.
Confirm the entity name on HA is the same one you're selecting in HADB.
Also, open the HADB driver and make sure it's still online. Click Initialize just for good measure.
I'm confused, I don't see an "initialize" option available under the app.
I tried to select other entities -- nothing new will come into Hubitat from Home Assistant, but I can see current status for the devices I was able to bring from HA to HE without a problem -- just won't let me add any new ones.
