I have mine on my qnap running on container station
1 Like
I was planning on using maybe 3 or 4. As I’ve only got 20 devices in my mesh, I don’t think it’ll cater major issues. Only one way to find out tho.
I don't see any evidence for concern that the Moes/Linptech will take down a mesh, so I don't think you need to worry too much. As I noted one user has around 10-12 of them w/out experiencing issues, I haver four and they have been fine - actually had a fifth hooked up next to me on coner table in fam room for testing for several weeks and w/five going no issues.
2 Likes
I’m doing the same thing but with Synolgy Virtual Machine Manager.
Good to know. Do the have detect multiple zones functionality that the Aquara FP units have?
Agree. Definitely doesn't perform as "advertised"
HA is fine in my book though. 
1 Like
Not that I'm aware of, but I'm using the simplified driver from the Linptech/Moes topic, not @kkossev's more extensive 4 in 1 driver from that topic. My sensing needs in each location I'm using them are very straightforward.
They will sense pets/ceiling fans so you may have to do some playing around w/sensitivity and placement for your needs.
1 Like
So I got frustrated with HA again today and deleted the VM it lived in. I wanted to give it visibility of my lot VLAN, but it was a total nightmare.
I wasn’t actually doing anything with it aside from using it as an energy dashboard, so no great loss.
You would think you could just change each integration config to point at the new IP address, but nope, that would be too f’n easy! 
Ps, My primary network were the VM lived has full access to the IoT network but only my 2 Hubitat hubs have access from the IoT network back to the primary network.
So you are saying giving HA access to your IOT Vlan is not enough? I thought all the integrations within HA don't need network settings since it's part of HA.
I don't run my HA on VM hence the question.
Yep, and you can’t just go into most of the integrations and give them the device IP address like you can with most community drivers in Hubitat.
What integration are you trying to run? My HA is mostly for dashboard, Wifi integration and oddball Tuya sensors such as chatty energy/ZigBee MmWave sponsors. Everything else is on HE.
I was only using the Tesla Powerwall and Fronius inverter integrations to supply the energy dashboard.
A lot of these settings are in a hidden subdirectory - .storage - under config in text files. They're not always easy to find. I don't know why it is so difficult to find/manage these settings.
2 Likes
No great loss, I’ll just use my Powerwall app for the info,
I run HA in docker on a linux computer with two physical NIC. One for each VLAN. HA sees and access everything on both VLAN.
I could have assigned one of my 2 spare (of 4 total) NIC ports to my IoT VLAN, but TBH I just dont need HA for anything useful ATM. I backed up the VM before I deleted it, so I can always re-add it later if I change my mind.
I recently put HA on a Beelink Mini PC. I really haven't done much with it, I primarily did it so I could bring my LitterRobot into HE. Beyond that I really havent had much desire to do much else with it. Oh, I look at it and try to find other ways to use it, but I just don't have the patience to sit down and play with it yet.
1 Like
I thought about this but honestly, I get all the notifications for our LR4 through the native app. Don't see a real reason for myself to run it through HA then hubitat.
My wife “claims” she doesn’t get the notifications, so I’m looking at setting it up with RGB lite strips on the back of the entertainment center to turn the whole wall red when it’s full. Then she has no excuse.
1 Like
No good will come of this. 
7 Likes
