Got this fixed for anyone who's interested. When the heating and cooling setpoint devices were created in HS4, they were created as Dim devices with a single value, not a range. Took me awhile to see this as I'm just getting used to the HS4 interface. Changing the control type to HeatSetPoint and so on with a range of values instead of a single value enables EasyTrigger to find the specified value and control the device and Hubitat NextManager device correctly. Thermostat itself responds correctly and quickly.
So, finally, I have HS4 control over my Nest devices.
Announcement
Collapse
No announcement yet.
Hubitat Nest devices and Easy Trigger
Collapse
X
-
With a little further investigation, when I set the heat setpoint from the HS4 device itself, I get the following so it appears that CAPI methods (about which I know practically nothing) are being used.
10/7/2021 5:14:00 PM
Legacy-Plugin
EasyTrigger
DEBUG Device 871 value set from 68 to 68
10/7/2021 5:14:00 PM
Legacy-Plugin
EasyTrigger
DEBUG Device 7 value set from -2147482649 to -2147482649
10/7/2021 5:14:00 PM
Legacy-Plugin
EasyTrigger
DEBUG Device 8 value set from -2147482649 to -2147482649
10/7/2021 5:14:00 PM
Legacy-Plugin
EasyTrigger
DEBUG Device 8 value set from -2147482649 to -2147482649
10/7/2021 5:14:00 PM
Legacy-Plugin
EasyTrigger
DEBUG Device 869 value changed from 70 to 68
10/7/2021 5:14:00 PM
Legacy-Plugin
EasyTrigger
DEBUG Device 871 value changed from 70 to 68
10/7/2021 5:13:59 PM
Legacy-Plugin
EasyTrigger
DEBUG Device 717 value set from 0 to 0
10/7/2021 5:13:59 PM
HomeSeer
Device Control
Device: Hubitat Kitchen HeatingSetpoint to heating setpoint (68) by/from: CAPI Control Handler
Leave a comment:
-
Hubitat Nest devices and Easy Trigger
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.10/7/2021 7:06:27 AM
Legacy-Plugin
EasyTrigger
DEBUG Device 7 value set from -2147482649 to -214748264910/7/2021 7:06:27 AM
Legacy-Plugin
EasyTrigger
DEBUG Device 8 value set from -2147482649 to -214748264910/7/2021 7:06:27 AM
Legacy-Plugin
EasyTrigger
DEBUG Device 8 value set from -2147482649 to -214748264910/7/2021 7:06:25 AM
Legacy-Plugin
EasyTrigger
DEBUG Device 717 value changed from 20 to 3010/7/2021 7:06:23 AM
Legacy-Plugin
EasyTrigger
DEBUG Device 7 value set from -2147482649 to -214748264910/7/2021 7:06:23 AM
Legacy-Plugin
EasyTrigger
DEBUG Device 8 value set from -2147482649 to -214748264910/7/2021 7:06:23 AM
Legacy-Plugin
EasyTrigger
DEBUG Device 8 value set from -2147482649 to -214748264910/7/2021 7:06:21 AM
Legacy-Plugin
EasyTrigger
DEBUG Device 871 value changed from 68 to 7010/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 CAPI10/7/2021 7:06:21 AM
Legacy-Plugin
EasyTrigger
DEBUG Expression 70 evaluated to 7010/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.Tags: None
Leave a comment: