Did you by any chance inadvertently turn off this option?
If so, the app will allow all entities to be included. Since these 30 devices are created at once, I suspect they are quite chatty, therefore generating lots of events to process. This will cause a big load on the hub at first run while it creates numerous child devices.
A nuance question about the above from the OP -- if I use entityID to add an entity to HADB, should I still have to wait for an event for that device to show up in HE, or should this method create the device immediately?
It will still take an event on the entity in order for the child to be created. This just allows that to happen, similarly to when you select the entity in the dropdown list on the main configuration page.
Yeah I was afraid that was the case. What I'm realizing is that for a device that doesn't change its value very often (like a battery device), it can take days (or longer) for the device to show up. Is there anyway for me to verify that I set it up correctly in the meantime?
On another HADB topic….
Is there a way to bring a helper from HA into HE just like one an do with any other entity?
I use HA for dashboarding and HE for zwave/zigbee and automations. As part of this setup we use HSM for alarm, but I’d like to also control the alarm from our HA dashboard. I’ve setup a drop-down helper in HA to enable selection, but I just realized the helper entity is not available in HADB afaict.
For that kind of thing I would just install the HE > HA integration and share virtual switches with HA to control HE devices and act on triggers from HE. There's no problem running the two simultaniously, just be sure you don't share those particular HE devices back to HE via HADB.
Yeah that makes sense thx.
BTW I take that to mean that HADB doesn't support helper entities, correct? I tried using the manual Add-an-Entity option in Advanced, and it didn't appear to work, so I'm assuming this is the case.
No, some do work. I haven't tried all of them, but I can tell you for sure that Toggle helper entities do work. I just prefer the HA > HE integration. I'm using that integration for other things, so I just take advantage of it for HE virtual swithes too.
FYI - Apparently sharing too many devices through the HA Bridge does impact the Hub Mesh. See my post separately on this issue.
Not quite my post that elicits this "solution", but not a big deal for me... Feels a little unfair to label HADB as being the root cause... feels like the combination of the devices involved and (potentially) the the use of HADB are likely the cause of your issue, but that is (not /un)likely the case for everyone who shares devices from a HE hub via HADB. I get that you have tried to clarify this in your comment, so am not wanting to criticise too heavily, but I would not want to see people view the HADB as being flawed in situations it can cater for...
I was under the impression that all HA events were sent via the event stream from HA to HE, and the HADB app has to filter out the events according to what devices are selected. I originally saw a performance hit and ameliorated it by disabling/deleting HA devices that I wasn’t using (and putting HADB on my spare hub).
Yes, all events (state change only) are sent through the bridge regardless what is selected in the app. But if an entity sit idle, no event will be sent for it. So a bunch of inactive devices won't add anything to the number of event that HADB has to handle.
I personnaly have over 300 entities on HA. Most of them seldom used. The app usage is 0.018% and the driver is 0.045%. I don't see this as being problematic. That said, if someone's HA devices are reporting a lot, they would probably tell a different story.
As for the impact on the mesh, I don't know enough about it to offer an opinion.
I had not clue. Was interesting to find out. Shows how little I pay attention since HADB just works, with no issues on my hubs either. Turns out I have over 600 entities coming in from HA, but only 194 of them are active. HADB is installed on my main hub where all my rules (nearly 200) run, and Homebridge, Hue integration, Lutron integrator, Amazon Echo Skill, and Google Home are all generating network traffic as well.
It's important to note that I also share devices via Hub Mesh, on both my active hubs, in both directions (62 devices in total). So while it may be that something is bogging things down, as @ymerj suggested, it could be a device that is reporting a lot.
I agree it is better to add media players direct to HE, but the issue is HE does not support all commands for ex. Google Nest devices, the devices are treated as a speech device, with the result functions are missing such as next and previous tracks, toggle play/pause, etc.
I did, at some point, look into this and it appears to be quite an andeavor. Maybe a limited feature support coud be acheive but it is bound to spark requests for more feature.
Furthermore, I hate to have to move yet another device to HA in order to alleviate shortcomings of HE, especially when that device is in use by millions all over the world.
In a cases like this, where something is running fine on HA, and there’s a loss of features or other problems with moving it to HE, I simply use the reverse integration HE > HA and share HE virtual switches set to momentary in order to trigger things. This keeps things separate with no resource load on my HE hubs, yet I still have control of the device from HE.
I run my Sonos on HA, because the IKEA Symfonisk remote that I have for it works better over there. It’s a heavy resource user that seems to have been a suspect in the overall health of my HE hubs when I had issues in the past. I’m sure some people don’t have a problem and will be happy to chime in about that fact, but I have no need or desire to move it from my HA hub. Control through the Symfonisk remote is a bonus, not a necessity for me.
I'm trying to see the state of my LG TV in Home Assistant. It works great there (I used to have the HE integration working, but it stopped and I can't get it working again). But the LG TV doesn't show up in HE via the bridge. I'm not sure if I need a specific device driver for it on the HE side or if I need to create a virtual switch in HA. Any help or ideas would be helpful.
It does not show-up because HADB does not support media_player entities. For On/Off state, my guess would be to go the virtual switch route, unless there is a better solution. @SmartHomePrimer is the master of workarounds.
I turned of the electricity in my house to do some electrical work. When I turned the power back on I noticed that none of the Aqara Curtain motors was working any more.
I investigated a bit to try and find the cause of this and eventually I found an error message in HA stating:
As the HA integration was not entirely easy to get working when I installed it, and since I am no expert and don't really understand the technology behind this integration, I am a bit hesitant to randomly try things.
Any thoughts on how to fix this?
My ill-informed opinion would be to restart HA... The typical IT response... But would understand waiting for the experts to respond....
Download the Hubitat app
