Closed PencilDH closed 2 years ago
Hello @PencilDHz. From my experience this kind of error messages appear when the plug-in isn't able, for some reason, to communicate with the device. I hadn't had any time lately to look further into this, but I'll do as soon as I find some time.
I have the exact error. The plugin still works, but after a few minutes after a restart, it stops getting the devices’ status. A few clicks on the toggles seems to get it communicating again (only with the device that i switched on and off. Couldn’t find anything about this anywhere except this post. Weird Edit: the problem was an outdated version of Homebridge. It appeared up to date, but the Node.js version was out of date, updated through the docker app and the problem went away
In the latest versions of the plugin, if this error is encountered the plugin will retry to connect to the Tapo device.
Unfortunately after the last updates the whole plugin became almost unusable and throwing different error codes like: 371 Error: aborted, 111 Error: timeout of 5000ms exceeded, Error: connect ENETUNREACH, This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! with the previous mentioned expected boolean without error code this time
Hi first off all awesome plug-in thanks
I had this error come up on my tapo p100 plug (firmware 1.4.5) it seem to work but just wanted to let you know![705476EB-B29C-4F5D-9FA5-6FE1FBCE3140](https://user-images.githubusercontent.com/19908009/122451612-44262680-cfa0-11eb-86c6-4566768fe914.jpeg)