this post was submitted on 20 Apr 2024
77 points (96.4% liked)

homeassistant

12102 readers
16 users here now

Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] d2k1@lemmy.dbzer0.com 7 points 7 months ago* (last edited 7 months ago) (3 children)

I wonder what his big ZigBee issue was that took him months to solve.

From the vague description it could be that his ZigBee stick was plugged directly into the USB port instead of using a USB extension cable, thus subjecting the ZigBee stick to all sorts of RF interference from the motherboard.

Or maybe the USB pass-through to the home assistant VM was wonky?

Edit: he talks about getting 30$ worth of hardware to fix the issue so it is probably not just a USB extension cable 🤔

[–] sabreW4K3@lazysoci.al 3 points 7 months ago (2 children)

I think it was probably where the coordinator was plugged in

[–] d2k1@lemmy.dbzer0.com 5 points 7 months ago

The reveal will be interesting 🙂

[–] d2k1@lemmy.dbzer0.com 2 points 6 months ago

Looks like you were pretty spot-on!

[–] KairuByte@lemmy.dbzer0.com 3 points 7 months ago* (last edited 7 months ago)

An issue a lot of people don’t think about is placement. If you’ve got the fob directly next to a device that’s broadcasting WiFi, you’re gonna have a bad time. Similarly, if it’s surrounded by thick wood or metal, you’re not going to have decent signal.

$30 could definitely fix those issues.

[–] Doxin@pawb.social 1 points 7 months ago

Or he was using the conbee II which a fair number of top google results suggest you get. Don't, it's terrible.