core: Problem with Fibaro Integration after updating to 2023.11
The problem
Hi, I found this problem after updating to this new version. There is a random slight-delay to major-delay from Fibaro to send updated device states to Home Assistant. Please see the attached vdo from the google drive link. However, for Home Assistant to send commands, such as turning on/off the lights, there is no delay. I’ve never experience this kind of device state update delay problem before (I use this Fibaro and Home Assistant for over a year). Now, all my motion triggers are useless because sometime, it trigger very late in home assistant (by tens seconds). Please help fix the problem. Here is the link to the video demonstrates problem and the diagnostics data saved from the integration debug.
https://drive.google.com/drive/folders/1EUdrmRc_3PqACEGT7b3gA3FwuJM22Hlr?usp=sharing
What version of Home Assistant Core has the issue?
core-2023.11.2
What was the last working version of Home Assistant Core?
before 2023.11
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Fibaro
Link to integration documentation on our website
https://www.home-assistant.io/integrations/fibaro
Diagnostics information
please download the diagnostic data from the google drive link here.
https://drive.google.com/drive/folders/1EUdrmRc_3PqACEGT7b3gA3FwuJM22Hlr?usp=sharing
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Here is the link to the video demonstrates problem and the diagnostics data saved from the integration debug.
https://drive.google.com/drive/folders/1EUdrmRc_3PqACEGT7b3gA3FwuJM22Hlr?usp=sharing
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 7 months ago
- Reactions: 4
- Comments: 18 (3 by maintainers)
Just again the information for all which have a look at this issue: The bug is fixed by #103193 and will be released in version 2023.12.
I confirm. Have the same issue after HA update. Delays on fibaro entities 5-30 seconds.
Edit: Just downgraded to 2023.10.5 and everything works fast and smooth. No delays. Waiting for update without this issue.
@home-assistant close
Most likely related problem: Error Message: Logger: pyfibaro.fibaro_state_handler Source: /usr/local/lib/python3.11/site-packages/pyfibaro/fibaro_state_handler.py:57 First occurred: November 26, 2023 at 5:09:43 PM (3288 occurrences) Last logged: 5:54:32 PM
Connection Error (19). Error: int() argument must be a string, a bytes-like object or a real number, not ‘NoneType’ Connection Error (20). Error: int() argument must be a string, a bytes-like object or a real number, not ‘NoneType’ Connection Error (21). Error: int() argument must be a string, a bytes-like object or a real number, not ‘NoneType’ Connection Error (22). Error: int() argument must be a string, a bytes-like object or a real number, not ‘NoneType’ Connection Error (23). Error: int() argument must be a string, a bytes-like object or a real number, not ‘NoneType’
Core 2023.11.3 Supervisor 2023.11.3 Operating System 11.1 Frontend 20231030.2
I have Fibaro HC2 and I updated HA core to 2023.11.3 yesterday and I still have 20-40s delay. If I restart the system i can toggle lights 5-10 times (does not have to be the same light) without any delay, then the delay gets longer and longer, up to 40 sec. Toggling lights with motion is also delayed.
Edit: Downgraded to 2023.10.5 yesterday, delay is gone
I also hav been experiencing the same issues, for me its random, sometimes turning on a light connected in HA in response to motion from Fibaro HC3 / Fibaro Motion Sensor is “instant” other times its a 10s, 20s delay.
No problem with lights controled by Fibaro HC3
I also tried the fix from issue#103193 and it made no difference.
Hi @Poomvst , i can confirm this behaviour. I have also issues with the motion sensors, but also with the lights itself. If you turn them on, the react instantly or with a delay. Some automation scenes in HA don’t run properly because the motion trigger is not coming from fibaro (al my sensors are in fibaro). I still have a lot of scrips working in fibaro and they al do work fine. So for me its clear it has something to do with the communication between fibaro and HA.