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
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
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
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor

Vera Thermostat trigger wrong Setpoint value

Scheduled Pinned Locked Moved Multi-System Reactor
10 Posts 2 Posters 517 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

                      • Gradually turn on lights.
                        G
                        gwp1
                        0
                        4
                        153

                      • Stop the MSR by an external switch on Hubitat.
                        wmarcolinW
                        wmarcolin
                        0
                        1
                        42

                      • Error After Upgrade
                        G
                        gwp1
                        0
                        4
                        107

                      • Reset attribute value of entity in event handler
                        R
                        RHCPNG
                        0
                        5
                        213

                      • Need help figuring out how to delay a reset on reaction
                        G
                        gwp1
                        0
                        22
                        939

                      • Way to search for rules (rule state) in other rules
                        T
                        tamorgen
                        0
                        3
                        107

                      • Links to MSR from HA
                        Tom_DT
                        Tom_D
                        0
                        1
                        96

                      • Set Reaction > Script Action
                        wmarcolinW
                        wmarcolin
                        0
                        11
                        444

                      • Wiring Samotech SM308-S into light fitting
                        akbooerA
                        akbooer
                        0
                        2
                        156

                      • Errors after updating to MQTTController build 25139
                        toggledbitsT
                        toggledbits
                        0
                        6
                        247

                      • 🎉 My very first MSR controller: OpenSprinkler
                        therealdbT
                        therealdb
                        5
                        13
                        923

                      • Advice reqeusted to migrate MSR from Bare Metal to Container
                        T
                        tamorgen
                        0
                        5
                        269
                      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