SOLVED--See last post.
Slowly moving over from HS3 to HS4 (Windows 10). I have a Hubitat which I use with Racine's NextManager to connect with my Nest thermostats since there's no HS plugin yet. Maker brings them over to HS4 through mcsHubitat as devices. They work. In HS3 EasyTrigger was an easy way to increment and decrement the heat and cool setpoints with Set Device to Expression--Set Device.....HeatingSetpoint to $DEVICEVALUE +1. That worked reliably. I tried the same thing in HS4 but cannot get it to work. The device value won't change even when I just try to set it to a number. From HS4 itself--no problem. I can enter a temperature number and it will change the device value and the thermostat quickly.
The log below is a debug record of just trying to set the device value to 70. Although it says 871 (which is the heating setpoint) is changed to 70 it wasn't. Any help appreciated with how to set this up to work.
Legacy-Plugin
EasyTrigger
DEBUG Device 7 value set from -2147482649 to -2147482649
Legacy-Plugin
EasyTrigger
DEBUG Device 8 value set from -2147482649 to -2147482649
Legacy-Plugin
EasyTrigger
DEBUG Device 8 value set from -2147482649 to -2147482649
Legacy-Plugin
EasyTrigger
DEBUG Device 717 value changed from 20 to 30
Legacy-Plugin
EasyTrigger
DEBUG Device 7 value set from -2147482649 to -2147482649
Legacy-Plugin
EasyTrigger
DEBUG Device 8 value set from -2147482649 to -2147482649
Legacy-Plugin
EasyTrigger
DEBUG Device 8 value set from -2147482649 to -2147482649
Legacy-Plugin
EasyTrigger
DEBUG Device 871 value changed from 68 to 70
Legacy-Plugin
EasyTrigger
DEBUG SetDeviceValue: Cannot find control value 70 for device 871, will set device value instead of controlling it using CAPI
Legacy-Plugin
EasyTrigger
DEBUG Expression 70 evaluated to 70
HomeSeer
Event
Event Trigger "Thermostats Increment Heat Setpoint"
HomeSeer
Event
Event Thermostats Increment Heat Setpoint triggered by the event page 'Run' button.
Slowly moving over from HS3 to HS4 (Windows 10). I have a Hubitat which I use with Racine's NextManager to connect with my Nest thermostats since there's no HS plugin yet. Maker brings them over to HS4 through mcsHubitat as devices. They work. In HS3 EasyTrigger was an easy way to increment and decrement the heat and cool setpoints with Set Device to Expression--Set Device.....HeatingSetpoint to $DEVICEVALUE +1. That worked reliably. I tried the same thing in HS4 but cannot get it to work. The device value won't change even when I just try to set it to a number. From HS4 itself--no problem. I can enter a temperature number and it will change the device value and the thermostat quickly.
The log below is a debug record of just trying to set the device value to 70. Although it says 871 (which is the heating setpoint) is changed to 70 it wasn't. Any help appreciated with how to set this up to work.
10/7/2021 7:06:27 AM
Legacy-Plugin
EasyTrigger
DEBUG Device 7 value set from -2147482649 to -2147482649
10/7/2021 7:06:27 AM
Legacy-Plugin
EasyTrigger
DEBUG Device 8 value set from -2147482649 to -2147482649
10/7/2021 7:06:27 AM
Legacy-Plugin
EasyTrigger
DEBUG Device 8 value set from -2147482649 to -2147482649
10/7/2021 7:06:25 AM
Legacy-Plugin
EasyTrigger
DEBUG Device 717 value changed from 20 to 30
10/7/2021 7:06:23 AM
Legacy-Plugin
EasyTrigger
DEBUG Device 7 value set from -2147482649 to -2147482649
10/7/2021 7:06:23 AM
Legacy-Plugin
EasyTrigger
DEBUG Device 8 value set from -2147482649 to -2147482649
10/7/2021 7:06:23 AM
Legacy-Plugin
EasyTrigger
DEBUG Device 8 value set from -2147482649 to -2147482649
10/7/2021 7:06:21 AM
Legacy-Plugin
EasyTrigger
DEBUG Device 871 value changed from 68 to 70
10/7/2021 7:06:21 AM
Legacy-Plugin
EasyTrigger
DEBUG SetDeviceValue: Cannot find control value 70 for device 871, will set device value instead of controlling it using CAPI
10/7/2021 7:06:21 AM
Legacy-Plugin
EasyTrigger
DEBUG Expression 70 evaluated to 70
10/7/2021 7:06:21 AM
HomeSeer
Event
Event Trigger "Thermostats Increment Heat Setpoint"
10/7/2021 7:06:21 AM
HomeSeer
Event
Event Thermostats Increment Heat Setpoint triggered by the event page 'Run' button.
Comment