Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. Vera Thermostat trigger wrong Setpoint value
DynamicGroupController and attributes
therealdbT
Hey @toggledbits I'm back to trying to optimize a couple of things based on dynamic group. First of all, I think I found a typo in the doc: primary_attribute: "binary_sensor.state" primary_attribute_value: | d = false; each id in members: d = getEntity(id)?.attributes?.power_switch?.state or d, d I think the correct code snippet is d = false, All that said, my use case for dynamic groups is to group 3 different climate devices, so I could easily command them at the same time. Commands are good, but sometimes I want to check if any of the devices are on, and that's easily done with a similar snippet as the one you have in the docs. But this is limited to the primary attribute, while I want to have any of the attributes in the group to be driven by a similar logic (while all are null in the group). ie, access hvac_control.mode and see if any of the unit is set to cool, or heat. Is that possible, without re-defining an expression in each of my rules? Thanks!
Multi-System Reactor
Arming Envisalink panel from MSR
T
Topic thumbnail image
Multi-System Reactor
Upgrade Issues
T
Topic thumbnail image
Multi-System Reactor
[SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
G
Topic thumbnail image
Multi-System Reactor
[SOLVED] Question regarding "in" vs "contains" vs contents of the string
G
Topic thumbnail image
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Logon screen timeout
G
Noticing since 170 that the lock screen doesn't switch to the logon prompt but, rather, stays on the active UI until such time as you go to click something within it. Then it jumps to the login screen. Brave browser Brave 1.92.139 (Official Build) (arm64) Chromium: 150.0.7871.114
Multi-System Reactor
[MSR] Copy&past of actions and/or drag&drop between set/reset
therealdbT
Hey @toggledbits One thing that bothers me while doing work on new systems/new features, is that I cannot copy&paste actions, and I cannot drag&drop between set and resets. #1 is for when I want to copy an action between different rules opened in two separate browser windows, while #2 is when I just need to flip a bunch of actions in the reset, or move some logic back and forth. Both will be appreciated, but I understand the technical challenges. Thanks!
Multi-System Reactor
Upgrade advice - upgrade from aarch64 to ARM64 image
T
I'm currently on version 26011. I understand that the aarch64 image is no longer supported. So, I therefore need to update to the ARM64 image. Can anyone possibly suggest how I update my docker compose.yaml file (see below). Ideally I'd like to keep my existing reactions etc. rather than start from scratch. # Multi-System Reactor template docker-compose.yml (version 22160) # # Change the lines indicated by "DO"... # services: reactor: container_name: reactor environment: # DO change the TZ: line to set your local time zone. # See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones TZ: GB # # DO NOT change this path. Your directory location is in "source" below. REACTOR_DATA_PREFIX: /var/reactor # DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4) image: toggledbits/reactor:latest-aarch64 restart: "always" expose: - 8111 ports: - 8111:8111 volumes: # DO change the /home/username/reactor below to the directory you created for # your local data; DO NOT change the /var/reactor part - /home/pi/docker/reactor:/var/reactor - /etc/localtime:/etc/localtime:ro tmpfs: /tmp
Multi-System Reactor
Alexa for MSR, any interest?
MikeReadingtonM
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Telegram notification broke with latest update
3
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Phantom device, “INFO” appears
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Mode Status NULL
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] HTTP query failing after version 26177
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Question about the find function
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[Answered] OK to remove old json files?
3
Topic thumbnail image
Multi-System Reactor
Deprecation Announcement: 32-bit ARM *docker* images
toggledbitsT
If you are using the armv7l docker image, the OpenJS Foundation that publishes node is no longer producing 32-bit builds as of v24. That means the last supported LTS version of node for armv7l is v22, which will go End-of-Life in May 2027. Therefore, the Reactor armv7l image is now deprecated and will only be produced until node v22 goes EOL, and I will not publish armv7l images beyond that date. If you are running an RPi 3 or earlier with Reactor, you are on this image, and will need to upgrade hardware to a 64-bit model and use the arm64 image. If you need help getting it done, ask in this category.
Multi-System Reactor
[Solved] build 26150 - engine not starting
G
@toggledbits I pulled the image (well, Watchtower did) and within minutes the whole system went offline. The log looks like it ends with 26143. [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mkahsmgf/26qq82mw-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lqyfljfi/22f8on0t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lsb61rw8/24oenqi2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/rule-lrh58he0:S-1c00gfib-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1c00dylr-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1nam9w5u-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miuh2qqi/22ls4lql-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1vj8sdfc-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1qanz01x-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/24lq19p6-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mk0o8iox/23oy468y-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miscg2h3/rule-miscg2h3:S-22gmbq1c-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrfjke/238p0old-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-m7ccsso5/re-m7ccsso5-1r0myjxa-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/19nl9wq2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3xk9t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3vv5m-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/re-ln7j2nqp-22mx9lzd-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/22mx87c8-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-licneppy/1mzwe7ht-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ml3194ih/25jqt1j4-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrg7kf/227hshak-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13ua1p95-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13uagam7-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x4cbv-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x2fyl-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-lscjrws1/238p5c22-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lbwr0jvq/1xkczf03-cons [latest-26143]2026-05-31T15:23:44.547Z <Structure:NOTICE> Structure Structure#1 stopped [latest-26143]2026-05-31T15:23:44.547Z <app:NOTICE> Closing APIs... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: closing... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: disconnecting from "192.168.1.23#82" (1001 service closing) [latest-26143]2026-05-31T15:23:44.548Z <httpapi:NOTICE> HTTP API closing... [latest-26143]2026-05-31T15:23:44.549Z <wsapi:NOTICE> wsapi: server closed [latest-26143]2026-05-31T15:23:44.549Z <httpapi:INFO> HTTP server closed. [latest-26143]2026-05-31T15:23:44.549Z <app:NOTICE> Stopping timers... [latest-26143]2026-05-31T15:23:44.551Z <app:null> Shutdown complete, process ID 1 [latest-26143]2026-05-31T15:23:44.551Z <app:null> Closing logs... [latest-26143]2026-05-31T15:23:44.551Z <default:null> Closing log I can SSH to the VM. Alas, I do not have the previous image for 26143 as I'm a little too quick sometimes on housekeeping.
Multi-System Reactor
http request action & digest auth
tunnusT
I’m using the HTTP Request action in MSR and need to authenticate against an endpoint that uses HTTP Digest authentication. Now that endpoint was changed to use SHA-256 in digest auth, so I would like to know if MSR supports it, or is it limited to MD5-based digest auth?
Multi-System Reactor
Cloning actions in reactions does not work
tunnusT
With build 26140 (on Docker) I'm not able to clone any actions in reactions. Using Chrome if it has any relevance.
Multi-System Reactor

Vera Thermostat trigger wrong Setpoint value

Scheduled Pinned Locked Moved Multi-System Reactor
10 Posts 2 Posters 1.8k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by cw-kid
    #1

    This was working and tested previously, but now doesn't seem to be.

    caecaac3-2c49-4aa0-b911-ff1d16029883-image.png

    I turned the heating on earlier, however I have since turned if off again. However the trigger in this rule still says the current set point value is 21. Its not its currently 10.

    A window was just opened and a TTS heard, which drew my attention to this rule now as it should not of fired its actions.

    dbf42371-5cef-49ff-9b26-87c15ad212ea-image.png

    Vera variable now:

    072f3f45-ef90-4ffe-a721-50eea18327ef-image.png

    Thermostat device information from the Entities:

    battery_power.level=0.49
    battery_power.since=1620139135000
    hvac_control.mode=null
    hvac_control.state=null
    hvac_heating_unit.setpoint=21
    hvac_heating_unit.state=null
    hvac_heating_unit.units="c"
    power_switch.state=null
    value_sensor.units="c"
    value_sensor.value=18.1
    x_vera_device.configured=true
    x_vera_device.device_number=189
    x_vera_device.device_type="urn:schemas-upnp-org:device:Heater:1"
    x_vera_device.failed=false
    x_vera_device.mapped_by="*;device_type=urn:schemas-upnp-org:device:Heater:1"
    x_vera_device.mapped_class="heatonly_thermostat"
    x_vera_svc_micasaverde_com_HaDevice1.AutoConfigure="-1"
    x_vera_svc_micasaverde_com_HaDevice1.BatteryDate="1620139135"
    x_vera_svc_micasaverde_com_HaDevice1.BatteryLevel="49"
    x_vera_svc_micasaverde_com_HaDevice1.CommFailure="0"
    x_vera_svc_micasaverde_com_HaDevice1.CommFailureAlarm="1612455867,0"
    x_vera_svc_micasaverde_com_HaDevice1.CommFailureTime="0"
    x_vera_svc_micasaverde_com_HaDevice1.Commands="heater_setpoint"
    x_vera_svc_micasaverde_com_HaDevice1.Configured="1"
    x_vera_svc_micasaverde_com_HaDevice1.FirstConfigured="1485879775"
    x_vera_svc_micasaverde_com_HaDevice1.LastUpdate="1607103908"
    x_vera_svc_micasaverde_com_HaDevice1.ModeSetting="1:;2:H,10.0;3:H,10.0;4:H,10.0"
    x_vera_svc_micasaverde_com_HaDevice1.PollRatings="5.00"
    x_vera_svc_micasaverde_com_HaDevice1.WakeupRatings="5.00"
    x_vera_svc_micasaverde_com_HaDevice1.sl_BatteryAlarm="0"
    x_vera_svc_micasaverde_com_ZWaveDevice1.AssociationGet="2,190,;"
    x_vera_svc_micasaverde_com_ZWaveDevice1.AssociationNum="5"
    x_vera_svc_micasaverde_com_ZWaveDevice1.AssociationSet="2,190"
    x_vera_svc_micasaverde_com_ZWaveDevice1.Capabilities="18,150,0,1,8,0,B,|49:1,67,112,114,128,132:2,133,134,"
    x_vera_svc_micasaverde_com_ZWaveDevice1.ConfiguredAssoc="2,190"
    x_vera_svc_micasaverde_com_ZWaveDevice1.ConfiguredName=""
    x_vera_svc_micasaverde_com_ZWaveDevice1.ConfiguredVariable="1-variable 1,1d,255,2-variable 2,1d,1,3-variable 3,1d,10"
    x_vera_svc_micasaverde_com_ZWaveDevice1.ConfiguredWakeupInterval="300"
    x_vera_svc_micasaverde_com_ZWaveDevice1.FirmwareInfo=""
    x_vera_svc_micasaverde_com_ZWaveDevice1.LastArr="1620138237,69"
    x_vera_svc_micasaverde_com_ZWaveDevice1.LastNnu="1620137632,69"
    x_vera_svc_micasaverde_com_ZWaveDevice1.LastReset="1485882104"
    x_vera_svc_micasaverde_com_ZWaveDevice1.LastRouteUpdate="1620109432"
    x_vera_svc_micasaverde_com_ZWaveDevice1.LastWakeup="1620152934"
    x_vera_svc_micasaverde_com_ZWaveDevice1.ManufacturerInfo="89,1,3"
    x_vera_svc_micasaverde_com_ZWaveDevice1.MeterScale=""
    x_vera_svc_micasaverde_com_ZWaveDevice1.MeterType=""
    x_vera_svc_micasaverde_com_ZWaveDevice1.MultiChCapabilities=""
    x_vera_svc_micasaverde_com_ZWaveDevice1.MultiChEndpoint=""
    x_vera_svc_micasaverde_com_ZWaveDevice1.NodeInfo="31,43,70,72,80,84,85,86,"
    x_vera_svc_micasaverde_com_ZWaveDevice1.PollNoReply="378"
    x_vera_svc_micasaverde_com_ZWaveDevice1.PollOk="16295"
    x_vera_svc_micasaverde_com_ZWaveDevice1.PollSettings="10800"
    x_vera_svc_micasaverde_com_ZWaveDevice1.SensorBiType=""
    x_vera_svc_micasaverde_com_ZWaveDevice1.SensorMlScale=""
    x_vera_svc_micasaverde_com_ZWaveDevice1.SensorMlType=""
    x_vera_svc_micasaverde_com_ZWaveDevice1.SetPointInfo="H1,"
    x_vera_svc_micasaverde_com_ZWaveDevice1.SubscribedAlarms=""
    x_vera_svc_micasaverde_com_ZWaveDevice1.TemperatureScale="1,0,2"
    x_vera_svc_micasaverde_com_ZWaveDevice1.VariablesGet="1,255,2,1,3,10,"
    x_vera_svc_micasaverde_com_ZWaveDevice1.VariablesSet="1-variable 1,1d,255,2-variable 2,1d,1,3-variable 3,1d,10"
    x_vera_svc_micasaverde_com_ZWaveDevice1.VersionInfo="2,2,78,6,0"
    x_vera_svc_micasaverde_com_ZWaveDevice1.WakeupInterval="300"
    x_vera_svc_micasaverde_com_ZWaveNetwork1.ConsecutivePollFails="0"
    x_vera_svc_micasaverde_com_ZWaveNetwork1.LastPollSuccess="1620149034"
    x_vera_svc_upnp_org_Dimming1.LoadLevelTarget="58"
    x_vera_svc_upnp_org_HVAC_UserOperatingMode1.ModeStatus="HeatOn"
    x_vera_svc_upnp_org_SwitchPower1.Target="0"
    x_vera_svc_upnp_org_TemperatureSensor1.CurrentTemperature="18.10"
    x_vera_svc_upnp_org_TemperatureSetpoint1.AllSetpoints="10.00,0.00,5.00"
    x_vera_svc_upnp_org_TemperatureSetpoint1.CurrentSetpoint="10.00"
    x_vera_svc_upnp_org_TemperatureSetpoint1.NewCurrentSetpointC="23"
    x_vera_svc_upnp_org_TemperatureSetpoint1.NewCurrentSetpointF="73.4"
    x_vera_svc_upnp_org_TemperatureSetpoint1.Range="0,0/0,0;0,0/0,0;5,30/41,86"
    x_vera_svc_upnp_org_TemperatureSetpoint1.SetpointTarget="10.00"
    x_vera_svc_upnp_org_TemperatureSetpoint1_Heat.CurrentSetpoint="21.00"
    zwave_device.capabilities="18,150,0,1,8,0,B,|49:1,67,112,114,128,132:2,133,134,"
    zwave_device.failed=false
    zwave_device.manufacturer_info="89,1,3"
    zwave_device.node_id=57
    zwave_device.version_info="2,2,78,6,0"
    Capabilities: battery_power, hvac_control, hvac_heating_unit, power_switch, toggle, value_sensor, x_vera_device, x_vera_svc_micasaverde_com_HVAC_OperatingState1, x_vera_svc_micasaverde_com_HaDevice1, x_vera_svc_micasaverde_com_ZWaveDevice1, x_vera_svc_micasaverde_com_ZWaveNetwork1, x_vera_svc_upnp_org_Dimming1, x_vera_svc_upnp_org_HVAC_UserOperatingMode1, x_vera_svc_upnp_org_SwitchPower1, x_vera_svc_upnp_org_TemperatureSensor1, x_vera_svc_upnp_org_TemperatureSetpoint1, x_vera_svc_upnp_org_TemperatureSetpoint1_Heat, zwave_device
    Actions: hvac_control.set_mode, hvac_heating_unit.set_setpoint, power_switch.off, power_switch.on, toggle.toggle, x_vera_device.set_variable, x_vera_svc_micasaverde_com_HaDevice1.AllowPairing, x_vera_svc_micasaverde_com_HaDevice1.Poll, x_vera_svc_micasaverde_com_HaDevice1.Reconfigure, x_vera_svc_micasaverde_com_HaDevice1.Remove, x_vera_svc_micasaverde_com_HaDevice1.SetPollFrequency, x_vera_svc_micasaverde_com_HaDevice1.StressTest, x_vera_svc_micasaverde_com_HaDevice1.ToggleState, x_vera_svc_micasaverde_com_ZWaveNetwork1.AddNodes, x_vera_svc_micasaverde_com_ZWaveNetwork1.BackupDongle, x_vera_svc_micasaverde_com_ZWaveNetwork1.DownloadNetwork, x_vera_svc_micasaverde_com_ZWaveNetwork1.HealNetwork, x_vera_svc_micasaverde_com_ZWaveNetwork1.PollAllNodes, x_vera_svc_micasaverde_com_ZWaveNetwork1.PutByte, x_vera_svc_micasaverde_com_ZWaveNetwork1.ReconfigureAllNodes, x_vera_svc_micasaverde_com_ZWaveNetwork1.RemoveNodes, x_vera_svc_micasaverde_com_ZWaveNetwork1.ResetNetwork, x_vera_svc_micasaverde_com_ZWaveNetwork1.SendData, x_vera_svc_micasaverde_com_ZWaveNetwork1.SetPolling, x_vera_svc_micasaverde_com_ZWaveNetwork1.SimulateIncomingData, x_vera_svc_micasaverde_com_ZWaveNetwork1.UpdateNeighbors, x_vera_svc_micasaverde_com_ZWaveNetwork1.UpdateNetwork, x_vera_svc_upnp_org_Dimming1.PauseRamp, x_vera_svc_upnp_org_Dimming1.ResumeRamp, x_vera_svc_upnp_org_Dimming1.SetLoadLevelTarget, x_vera_svc_upnp_org_Dimming1.SetOnEffect, x_vera_svc_upnp_org_Dimming1.SetOnEffectLevel, x_vera_svc_upnp_org_Dimming1.SetRampRate, x_vera_svc_upnp_org_Dimming1.SetStepDelta, x_vera_svc_upnp_org_Dimming1.StartRampDown, x_vera_svc_upnp_org_Dimming1.StartRampToLevel, x_vera_svc_upnp_org_Dimming1.StartRampUp, x_vera_svc_upnp_org_Dimming1.StepDown, x_vera_svc_upnp_org_Dimming1.StepUp, x_vera_svc_upnp_org_Dimming1.StopRamp, x_vera_svc_upnp_org_HVAC_UserOperatingMode1.SetEnergyModeTarget, x_vera_svc_upnp_org_HVAC_UserOperatingMode1.SetModeTarget, x_vera_svc_upnp_org_HVAC_UserOperatingMode1.SetName, x_vera_svc_upnp_org_SwitchPower1.SetTarget, x_vera_svc_upnp_org_TemperatureSensor1.SetApplication, x_vera_svc_upnp_org_TemperatureSensor1.SetName, x_vera_svc_upnp_org_TemperatureSetpoint1.SetApplication, x_vera_svc_upnp_org_TemperatureSetpoint1.SetCurrentSetpoint, x_vera_svc_upnp_org_TemperatureSetpoint1.SetName, x_vera_svc_upnp_org_TemperatureSetpoint1_Heat.SetApplication, x_vera_svc_upnp_org_TemperatureSetpoint1_Heat.SetCurrentSetpoint, x_vera_svc_upnp_org_TemperatureSetpoint1_Heat.SetName, zwave_device.poll
    

    In the rule if I change the trigger to use this Entity Attribute instead, then now its correctly showing 10 as the current set point.

    70833da9-d55d-4f89-8abf-724960e04a46-image.png

    1 Reply Last reply
    0
    • toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by
      #2

      There's nothing new here. The device type Heater1 implements both the TemperatureSetpoint_Heat and TemperatureSetpoint services, so it's ambiguous as to which would be the correct one to use, and one might hope that Vera (or the plugin responsible for this device) would keep them in sync. What kind of device is this?

      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

      cw-kidC 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        There's nothing new here. The device type Heater1 implements both the TemperatureSetpoint_Heat and TemperatureSetpoint services, so it's ambiguous as to which would be the correct one to use, and one might hope that Vera (or the plugin responsible for this device) would keep them in sync. What kind of device is this?

        cw-kidC Offline
        cw-kidC Offline
        cw-kid
        wrote on last edited by cw-kid
        #3

        @toggledbits

        It's a Secure SRT321 thermostat.

        Something has changed somewhere, as I said when I created this rule I tested it was working as intended.

        Today MSR had detected that I'd set the thermostat to 21 degrees. But when I set it back to 10 degrees, MSR didn't detect that.

        Thanks

        1 Reply Last reply
        0
        • toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote on last edited by toggledbits
          #4

          Did you set it the same way each time? Or perhaps through your dashboard one time and the Vera UI the other? Did you upgrade firmware since setting it up?

          Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

          cw-kidC 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            Did you set it the same way each time? Or perhaps through your dashboard one time and the Vera UI the other? Did you upgrade firmware since setting it up?

            cw-kidC Offline
            cw-kidC Offline
            cw-kid
            wrote on last edited by
            #5

            @toggledbits

            Pretty sure both times I manually turned the dial on the front of the actual thermostat device.

            No I have not updated the Vera firmware.

            I will set the Entity Attribute back to the MSR native one and test again some more.

            Thanks.

            1 Reply Last reply
            0
            • cw-kidC Offline
              cw-kidC Offline
              cw-kid
              wrote on last edited by
              #6

              hvac_heating_unit.setpoint seems to be working OK again now. The setpoint current value is changing in the rules trigger OK, when I move the dial up or down on the thermostat device.

              So not sure why it got stuck at 21 yesterday and didn't change back to 10 when I turned the heating off by setting it to 10.

              Will keep an eye on it.

              Thanks

              1 Reply Last reply
              0
              • toggledbitsT Offline
                toggledbitsT Offline
                toggledbits
                wrote on last edited by
                #7

                Test by dial and by Vera UI and by MSR UI. I'm guessing there may be an inconsistency in the 'driver" (Vera internals) and there may be one or more cases where the variables aren't kept in sync.

                Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                cw-kidC 1 Reply Last reply
                1
                • toggledbitsT toggledbits

                  Test by dial and by Vera UI and by MSR UI. I'm guessing there may be an inconsistency in the 'driver" (Vera internals) and there may be one or more cases where the variables aren't kept in sync.

                  cw-kidC Offline
                  cw-kidC Offline
                  cw-kid
                  wrote on last edited by
                  #8

                  @toggledbits

                  Think I see what's happening here.

                  I just turned on the Heating via a Vera scene, this scene sets the Setpoint to 23 degrees.

                  However the MSR rule is now still reporting the Current Set Point value as 10 degrees which is incorrect.

                  So I think what happened yesterday when I noticed this issue, was that I turned on the heating by using the dial on the thermostat device, but I must of turned the heating off via the Vera "Heating Off" scene which I called via a voice command to the Google Home speaker.

                  The Vera "Heating Off" scene sets the Set Point to 10 degrees.

                  Here is a screenshot of the "Heating On" scene in Vera.

                  Screenshot_20210505_195408_com.android.chrome.jpg

                  Thinking about it, when I first created this MSR rule some weeks ago, I only tested it by using the dial on the actual thermostat device.

                  I didn't also test the rule by running my Vera scenes that also turn on / off the heating.

                  1 Reply Last reply
                  0
                  • toggledbitsT Offline
                    toggledbitsT Offline
                    toggledbits
                    wrote on last edited by
                    #9

                    So then it appears then that when Vera updates the device from itself (ZWave), it sets both variables, but when you run the action, they only apply the change to one. Well, I'll switch it to the one the UI uses. That's sure to break some other device, but we can cross that bridge when we come to it.

                    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                    cw-kidC 1 Reply Last reply
                    0
                    • toggledbitsT toggledbits

                      So then it appears then that when Vera updates the device from itself (ZWave), it sets both variables, but when you run the action, they only apply the change to one. Well, I'll switch it to the one the UI uses. That's sure to break some other device, but we can cross that bridge when we come to it.

                      cw-kidC Offline
                      cw-kidC Offline
                      cw-kid
                      wrote on last edited by
                      #10

                      @toggledbits

                      Don't break anything on my account, I can just use the x_vera_svc Entity Attribute instead as that one seems to work OK.

                      1 Reply Last reply
                      0
                      • toggledbitsT toggledbits locked this topic on
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      Recent Topics

                      • DynamicGroupController and attributes
                        toggledbitsT
                        toggledbits
                        1
                        4
                        27

                      • Arming Envisalink panel from MSR
                        toggledbitsT
                        toggledbits
                        0
                        5
                        51

                      • Upgrade Issues
                        T
                        tbully
                        0
                        9
                        158

                      • [SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
                        toggledbitsT
                        toggledbits
                        0
                        10
                        142

                      • [SOLVED] Question regarding "in" vs "contains" vs contents of the string
                        G
                        gwp1
                        0
                        5
                        69

                      • Reactor (Multi-System/Multi-Hub) Announcements
                        toggledbitsT
                        toggledbits
                        5
                        147
                        128.0k

                      • openLuup console disappeared - 500 - Internal Server Error
                        A
                        a-lurker
                        0
                        2
                        152

                      • Logon screen timeout
                        G
                        gwp1
                        0
                        5
                        177

                      • [MSR] Copy&past of actions and/or drag&drop between set/reset
                        toggledbitsT
                        toggledbits
                        0
                        9
                        329

                      • Upgrade advice - upgrade from aarch64 to ARM64 image
                        toggledbitsT
                        toggledbits
                        0
                        4
                        192

                      • Alexa for MSR, any interest?
                        CatmanV2C
                        CatmanV2
                        2
                        4
                        327
                      Powered by NodeBB | Contributors
                      Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Unsolved