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 @[email protected] 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.
Is it best to have HA on Windows instead
No, certainly not.
Could you be having issues with the batteries in the motion sensors? You could also try setting up your zigbee network from scratch, although that is obviously annoying.
I was thinking that too but it doesnāt look like itās batteries. In the past the motion sensors would die without this wired behaviour, now the batteries were like at 20%, I put fresh ones in but it didnāt helpā¦
Iāve been running core-2021.8.6 before, now I installed the newest version on new microSD, it was annoying to when restoring a backup as I had to restore Zigbee devices separately and also the automations didnāt transfer, then the devices wouldnāt show in HA despite showing in Zigbee2MQTTā¦
Iāve got it all working now but the lag still remains.
Iām guessing itās maybe the USB sniffer being old and breaking down?
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āve definitely not experienced this and I use a CC2531-based network in a very large home with about 40 zigbee devices. My setup was originally deployed for Zigbee a few years ago and has been pretty reliable. A quick Googlinā indicates that the MAC access error can be caused by WiFi interference though. Have you tried changing the zigbee channel?
EDIT: Meant to include the link to the zigbee docs about the Mac access error youāre seeing. https://www.zigbee2mqtt.io/guide/faq/#common-error-codes
I second this. 2 updates ago I got a repair warning stating my Zigbee and Matter were using different channels. During that time I noticed delays with my devices. As soon as I put them on the same channel I noticed an immediate improvement. But I am using Skyconnect as multi-protocol so this may differ from OPs setup.
This might be it actually, Iāve bought google Wi-Fi mesh with three access points about a month ago, two of them are running in ethernet backhaul mode but one is not, I wouldnāt be surprised if this was causing interferenceā¦
Thanks for this, Iāll look into it.
Many thanks for the suggestion, I changed the channel from 11 to 25 and itās working perfectly again!
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.
Iāve had janky things start happening when my Pi started to run out of resources. For me it was my daemon.log on the Pi getting full of messages from HA. Once I deleted the log (there was a bunch that were saved old logs there too) my Pi worked good again and all the delays i was experiencing with my lights went away.
What I did was found a Linux command to find the biggest files on my system after working out that I had no memory, then using that list to track down the files taking up all my space.
Hope that helps
deleted by creator
Maybe, could be something to look into. I donāt have a āregularā install though, Iām running Supervised in Docker somehow, maybe that has something to do with it.
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ā¦
deleted by creator
Iāve got it plugged in directly to usb ports in a Belkin extension lead (2.4A), itās been fine all that time so I doubt itās that.
deleted by creator
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ā¦