-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[homebridge-edomoticz] This plugin slows down Homebridge. The read handler for the characteristic 'Current Temperature' didn't respond at all! See https://git.io/JtMGR for more info. #237
Comments
I suspect this is something Domoticz is doing, or Raspbian... I get the same, in batches consistently an hour apart usually (within a few seconds). Will see what I can find... note, it's not to do with sensor type as it does it with Color Temperature. I suspect it reports this for everything that isn't a switch, and switches just timeout / don't respond until Domoticz / MQTT starts responding again. I don't think the error is impacting the performance of switch devices... I suspect the two issues have the same cause - domoticz or mqtt not replying / accepting requests.
|
Hmmm... whenever it happens on mine it co-incides with:
(from Domoticz log) |
Have disabled automatic backup in Domoticz, cleared my logs and will keep an eye out. |
I removed all the Temp/Humidity sensors from the Roomplan in Domoticz so they are not showing up in Apple Homekit. The messages have not been seen for past 12 hours so far. I don't have automatic backup turned on. I'm getting value from the devices from MQTT, which in turn updates the devices in Domoticz. I also have a device updating an Influx DB every 5 minutes. Perhaps it is a conflict with Domiticz writes and reads. Will try running some continuous scripts to see if I notice any issue with this. |
I haven't had the error since turning off auto-backup in Domoticz at my end - that's all I've changed. The read handler it's talking about is a http get request and Domoticz isn't replying. MQTT doesn't request a 'read' as such. It's told... data is pushed to eDomoticz via MQTT so wouldn't trigger an error of this kind. |
On MQTT, yes - was clear in my wording. Meant that there was possibly some writing activity update sensors in Domoticz as result of the MQTT/NodeRed updates. After some more digging through logs, the only thing I can find is perhaps related to InfluxDB. Seems that at/around the same time this error pops up, I have an influx Error:
Could be related to (at least in my case) a similar issues posted here |
Proper solution to this is tied to #197 Need to replace request.js with something more modern that handles async / promise requests... |
Running Homebridge v1.3.4 Release and started noticing a lot of these messages, which seem in turn to impact on the performance of switch devices on/off through Home app. They are either 'didn't respond at all, or 'was slow to respond'. This is all running on an 8GB Raspberry Pi 4, which is showing and average of around 6% load
Note that the only devices that seem to generate this message are from a number of tempErature/humidity devies in Domoticz. I have 8 of these sensors around the house, which update Domoticz using MQTT & NodeRed. The full list of messages per device is as follows:
Anyone seen the same or got some thoughts?
The text was updated successfully, but these errors were encountered: