I’ve been happy with my setup for two years, I’ve got 15 devices, ikea light bulbs, ikea switches and motion sensors, it all works perfectly until last month or two.
Motion sensors start to change the status to “clear” which triggers the lights off while I’m still moving in the kitchen and bathroom.
Quite often now lags happen between motion sensor switching on the lights or the switch turning lights on or off - it always used to be instant.
My setup is not the newest as I’ve got RaspberryPi with CC2531 but I’ve been running old software all that time so that’s not the case, I’ve only updated everyone now hoping it will fix my issues but that didn’t help…
I know probably you will say I need to check logs but did anyone experience this?
I don’t use my setup for anything else like Plex Server or FTP etc…
That’s some examples errors I found when I was using ikea switch to turn the lights on.
Is it best to have HA on Windows instead using different dongle like SkyConnect?
Update:
Thanks to @sidewalker@thesidewalkends.io for pointing me in the right direction.
Somehow I never considered interference to be an issue.
Recently I bought a Google Wi-Fi mesh system (pack of three) and I didn’t realise it could have caused interference with zigbee…
I changed the channel from the default 11 to 25 and the whole setup is working perfectly again!
I also moved the RPi closer to most of the smart devices and I’ve put the USB coordinator on an extension cable but I’m 99% sure the channel 11 was the main issue.
In my experience, almost all stability problems I’ve had with Home Assistant are either due to the devices (not HA or the hardware I’m running it on, individual lights and switches, etc) or dead batteries in same.
What protocols are you using for your devices? Zigbee, Zwave, Wifi, something else?
The error message is a timeout. That implies a few things:
probably nothing wrong at the controller. Timeouts aren’t the controllers fault.
of course, something must be wrong at the device
or in between
Since you ruled out obvious stuff like batteries and updates at the device…
I would check in between - check the connectors of any network cables involved. For anything wireless, also check if there’s a device priority table you can prioritize your controller in. I would also try turning off a few devices to see if there’s just too much traffic on the network.
Source: That image contains a stack trace. I am fluent in stack trace WTF. Timeout means the message was sent and there was no timely no response.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !homeassistant@lemmy.world
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
That’s some examples errors I found when I was using ikea switch to turn the lights on.
Maybe your SD-card is giving up? For example: https://community.home-assistant.io/t/rpi-sd-card-reliability/232115
That’s what I thought too. I’ve installed HA on a new SD card, restored the backup but the issue still remains…
In my experience, almost all stability problems I’ve had with Home Assistant are either due to the devices (not HA or the hardware I’m running it on, individual lights and switches, etc) or dead batteries in same.
What protocols are you using for your devices? Zigbee, Zwave, Wifi, something else?
It’s not batteries as I swapped them all.
I don’t think it’s the devices I think it affects all of them, unless ikea released some buggy firmware.
It’s all Zigbee devices.
I know this is silly. But did you try restarting the server. Or updating it ?
I did, multiple times, I installed newest HA on a new microSD card, restored a backup but the lag is still there…
The error message is a timeout. That implies a few things:
Since you ruled out obvious stuff like batteries and updates at the device…
I would check in between - check the connectors of any network cables involved. For anything wireless, also check if there’s a device priority table you can prioritize your controller in. I would also try turning off a few devices to see if there’s just too much traffic on the network.
Source: That image contains a stack trace. I am fluent in stack trace WTF. Timeout means the message was sent and there was no timely no response.