Closed suhajda3 closed 2 years ago
That’s a breaking change on the Tasmota side. They used to return an empty object, see https://github.com/ebaauw/homebridge-hue/issues/512.
BTW you’re getting a timeout, not an error. What happens if you increase timeout
?
I increased the timeout
but homebridge-hue still prevents Homebridge from starting.
I believe the root cause of this issue when Tasmota compressed more strings with UnishoxStrings: https://github.com/arendst/Tasmota/commit/0ed519184bb1c6afd050e0789bfe7a8e8cf2a7e9
It looks like resourcelinks is still supported but somehow it causes an error.
Best open an issue with Tasmota, then.
The last version of Tasmota to support resourcelinks is 9.2.0. OTA update: http://ota.tasmota.com/tasmota/release-9.2.0/tasmota.bin
They have no plans to fix this issue so it's advised to stick with Tasmota 9.2.0.
The beauty about updating is that something will brake.
I have updated to homebridge-hue v0.13.29 and Tasmota 10.0.0. It looks like homebridge-hue tries to get the resourcelinks and since Tasmota doesn't support it, it cannot start.
$ ph -H 192...13 get /
At least the manufacturername is now "Tasmota". 👍