-
Notifications
You must be signed in to change notification settings - Fork 13
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
Heatmiser Neo Thermostat doesn't respond to Home App #79
Comments
If it responds to normal thermostat commands then I'm not sure why it would not work. Please use the Advanced Plugin Actions menu option -> Device and select your server then Simulate as an action and that thermostat and post the results of that simulation here. |
|
This should be resolved in the next release. I think you are probably the first user using 'ProgramHeat' or 'ProgramCool' so this was never caught before. You should be able to immediately use this until the next release if you want by changing it instead to just 'Heat' or 'Cool' instead of the program mode - maybe that's why it worked before. |
* Added additional sanity check on SecuritySpy servers that if they don't have the xaddress populated to get the address from a different field ([Issue #81](#81)) * Added 'ProgramHeat' and 'ProgramCool' to conditions for sending temperature set commands to a thermostat ([Issue #79](#79)) * Fixed bug where if a thermostat was set to auto heat/cool that changing temperatures in HomeKit would time out in the plugin because the plugin didn't know what to set, it will now increase the heat if the target temp is warmer than the current temp and increase cooling if it is cooler * Fixed bug where read-only HomeKit services may not get updates if not specifically programmed (i.e., for DSC alarms) ([Issue #86](#86)) * [Issue #81](#81) resolved * [Issue #79](#79) resolved * [Issue #86](#86) resolved
The latest release should resolve your issue, let me know if it does not. |
Excellent work - problem resolved. |
Awesome :).
|
As per forum comment the thermostat doesn't respond to any set points. The log entry is as follows:
HomeKit Bridge Error Maximum time exceeded while setting the 'TargetTemperature' HomeKit characteristic for 'Sitting Room' (HomeKit device 'Sitting Room'), aborting attempt. This can happen if you try to set a device to a state is is already in (i.e., turning off a device that is already off).
I believe this successfully worked in a previous Beta version.
The text was updated successfully, but these errors were encountered: