Emergency Heat and setpoints

[digidoc]

I recently updated to the latest version (3.2.0.5) on HS3. I was using version 1 for quite sometime. In the older version everything worked VERY well and I have been using the plugin for a long time. With the update, my system said I needed to install dot net 4.8 so I did. Homeseer on the whole was brought to its knees for a day or so and then started working again after some head banging and re-booting etc. I have completely removed the Wifi plugin and all remnants I could find. properly. I reinstalled it 3 times and I just can't get it working. This help request is the result.
OK.....
All system modes work as they should.
Cool and heat set points work for cool and heat only.
Emergency Heat mode works but only with the preset temperatures, and the set points can not be changed.
The plugin thinks the system is OFF when system mode is EM Heat. (It works but I can't adjust temps.) I have been using the Total Comfort app for any temp adjusting.

Has anyone else experienced this? It worked in the older version.

[shill]

I'm actually surprised any older version worked with a mono version that old - it doesn't support modern TLS protocols and I had to force that requirement because people were unable to connect when they made a change to their certificates. Glad to hear you got it back to (almost) working, though, and I'm sure we can work out the rest.

This has always been a tough part for me since I don't have a system with Emergency Heat. What would really help is a TRACE plugin log file from startup > update (with the system set to EM Heat via your app) > attempts to change the Heat setpoint. There's never been an "emergency heat" setpoint in the plugin, so I'm not quite sure what you mean by "the preset temperatures").

[digidoc]

That was fast. Sorry I didn't say OS is Windows 10 Pro on a Hometroller. The presets I refered to are the scheduled temps from the thermostat.
Here is a trace from this morning.

In the HS mobile app the up and down arrows for heat and cool are the ones I was refering to as well as the temperature change for setpoints in the web version.
Thanks

[shill]

Looks like I'm missing some logging in the plugin - can you also grab me the JSON that shows on the Honeywell WiFi Thermostat tab of your root device (while it's in Emergency Heat mode)? I need to trick my test instance into thinking it's getting data exactly like yours in order to replicate and fix this.

[digidoc]

If this doesn't help, please explain what I need to do to get the JSON you need.

[shill]

Sorry I wasn't clear. My logging logic is not recording what I need to see in this version. What I need is on the Thermostat root device in the HS web interface, under the "Honeywell WiFi Thermostat" tab. Copy and paste that text here.

[digidoc]

Except for the plugins tab I don't have another "Honeywell WiFi Thermostat" .

[shill]

There should be a parent/root device. Can't see it in the screenshot you posted though.

[digidoc]

After more digging I found another Thermostat entry under device type. I think this is what you wanted.

{
"success": true,
"deviceLive": true,
"communicationLost": false,
"latestData": {
"uiData": {
"DispTemperature": 72,
"HeatSetpoint": 72,
"CoolSetpoint": 73,
"DisplayUnits": "F",
"StatusHeat": 0,
"StatusCool": 0,
"HoldUntilCapable": true,
"ScheduleCapable": true,
"VacationHold": 0,
"DualSetpointStatus": false,
"HeatNextPeriod": 76,
"CoolNextPeriod": 76,
"HeatLowerSetptLimit": 40,
"HeatUpperSetptLimit": 90,
"CoolLowerSetptLimit": 50,
"CoolUpperSetptLimit": 99,
"ScheduleHeatSp": 72,
"ScheduleCoolSp": 73,
"SwitchAutoAllowed": false,
"SwitchCoolAllowed": true,
"SwitchOffAllowed": true,
"SwitchHeatAllowed": true,
"SwitchEmergencyHeatAllowed": true,
"SystemSwitchPosition": 0,
"Deadband": 0,
"IndoorHumidity": 128,
"DeviceID": 36660,
"Commercial": false,
"DispTemperatureAvailable": true,
"IndoorHumiditySensorAvailable": false,
"IndoorHumiditySensorNotFault": true,
"VacationHoldUntilTime": 0,
"TemporaryHoldUntilTime": 0,
"IsInVacationHoldMode": false,
"VacationHoldCancelable": true,
"SetpointChangeAllowed": true,
"OutdoorTemperature": 128,
"OutdoorHumidity": 128,
"OutdoorHumidityAvailable": false,
"OutdoorTemperatureAvailable": false,
"DispTemperatureStatus": 0,
"IndoorHumidStatus": 128,
"OutdoorTempStatus": 128,
"OutdoorHumidStatus": 128,
"OutdoorTemperatureSensorNotFault": true,
"OutdoorHumiditySensorNotFault": true,
"CurrentSetpointStatus": 0,
"EquipmentOutputStatus": 0
},
"fanData": {
"fanMode": 0,
"fanModeAutoAllowed": true,
"fanModeOnAllowed": true,
"fanModeCirculateAllowed": true,
"fanModeFollowScheduleAllowed": false,
"fanIsRunning": false
},
"hasFan": true,
"canControlHumidification": false,
"drData": {
"CoolSetpLimit": null,
"HeatSetpLimit": null,
"Phase": -1,
"OptOutable": false,
"DeltaCoolSP": null,
"DeltaHeatSP": null,
"Load": null
}
},
"alerts": ""
}

[shill]

Yep - that's it. And I can already see the problem: the thermostat is reporting Off as the Mode:"SystemSwitchPosition": 0

Is it possible to get a similar snapshot when your thermostat is ACTUALY turned off?

[digidoc]

Sure, and thanks for the help

{
"success": true,
"deviceLive": true,
"communicationLost": false,
"latestData": {
"uiData": {
"DispTemperature": 72,
"HeatSetpoint": 72,
"CoolSetpoint": 73,
"DisplayUnits": "F",
"StatusHeat": 0,
"StatusCool": 0,
"HoldUntilCapable": true,
"ScheduleCapable": true,
"VacationHold": 0,
"DualSetpointStatus": false,
"HeatNextPeriod": 76,
"CoolNextPeriod": 76,
"HeatLowerSetptLimit": 40,
"HeatUpperSetptLimit": 90,
"CoolLowerSetptLimit": 50,
"CoolUpperSetptLimit": 99,
"ScheduleHeatSp": 72,
"ScheduleCoolSp": 73,
"SwitchAutoAllowed": false,
"SwitchCoolAllowed": true,
"SwitchOffAllowed": true,
"SwitchHeatAllowed": true,
"SwitchEmergencyHeatAllowed": true,
"SystemSwitchPosition": 2,
"Deadband": 0,
"IndoorHumidity": 128,
"DeviceID": 36660,
"Commercial": false,
"DispTemperatureAvailable": true,
"IndoorHumiditySensorAvailable": false,
"IndoorHumiditySensorNotFault": true,
"VacationHoldUntilTime": 0,
"TemporaryHoldUntilTime": 0,
"IsInVacationHoldMode": false,
"VacationHoldCancelable": true,
"SetpointChangeAllowed": false,
"OutdoorTemperature": 128,
"OutdoorHumidity": 128,
"OutdoorHumidityAvailable": false,
"OutdoorTemperatureAvailable": false,
"DispTemperatureStatus": 0,
"IndoorHumidStatus": 128,
"OutdoorTempStatus": 128,
"OutdoorHumidStatus": 128,
"OutdoorTemperatureSensorNotFault": true,
"OutdoorHumiditySensorNotFault": true,
"CurrentSetpointStatus": 0,
"EquipmentOutputStatus": 0
},
"fanData": {
"fanMode": 0,
"fanModeAutoAllowed": true,
"fanModeOnAllowed": true,
"fanModeCirculateAllowed": true,
"fanModeFollowScheduleAllowed": false,
"fanIsRunning": false
},
"hasFan": true,
"canControlHumidification": false,
"drData": {
"CoolSetpLimit": null,
"HeatSetpLimit": null,
"Phase": -1,
"OptOutable": false,
"DeltaCoolSP": null,
"DeltaHeatSP": null,
"Load": null
}
},
"alerts": ""
}

[shill]

Ah, I had it wrong in my earlier comment. 0 = emergency heat, 2 = off. I'll work on this tonight!

[shill]

That was the easiest bug to fix in history Working on a couple of other reported issues but you'll see this fixed in 4.2.0.7 soon.

[digidoc]

Fantastic, thank you very much. Looking forward to it.

[digidoc]

That was the easiest bug to fix in history Working on a couple of other reported issues but you'll see this fixed in 4.2.0.7 soon.

Got it, beat it up, and all seems to be working perfectly. Thanks for the super fast fix, and may your holidays be joyful !