What issue do you have? Please be as thorough and explicit as possible.
I have a 7130 configured with homebridge. When I set the target temperature with homekit, the heater continues heating well past the temperature threshold. It will not stop heating.
Turning on auto in homebridge and/or autostop in the govee app causes the homekit thermostat to completely stop responding until I turn off autostop in the govee app.
Details of your setup.
Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
homebridge ui-x
Which version of Homebridge/HOOBS do you have?
homebridge 1.7.0
Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?
10.5.0
I haven't paid attention to the version, but I think this issue has always been present.
Which Govee devices do you have that are causing issues? Please include product models if applicable.
heater 7130
What issue do you have? Please be as thorough and explicit as possible.
I have a 7130 configured with homebridge. When I set the target temperature with homekit, the heater continues heating well past the temperature threshold. It will not stop heating.
Turning on auto in homebridge and/or autostop in the govee app causes the homekit thermostat to completely stop responding until I turn off autostop in the govee app.
Details of your setup.
Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
Which version of Homebridge/HOOBS do you have? homebridge 1.7.0
Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.![image](https://github.com/bwp91/homebridge-govee/assets/4069325/07628f89-eab0-4683-b631-e996c52e27c7)
Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version? 10.5.0
I haven't paid attention to the version, but I think this issue has always been present.
Please paste any relevant logs below.