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
How to upgrade from an old version of MSR?
cw-kidC
Hello I haven't updated my installation of MSR in a very long time. Its a bare metal Linux install currently on version 24366-3de60836 I see the latest version is now latest-26011-c621bbc7 I assume I cannot just jump from a very old version to the latest version? Or can I? Thanks
Multi-System Reactor
Access control - allowing anonymous user to dashboard
tunnusT
Using build 25328 and having the following users.yaml configuration: users: # This section defines your valid users. admin: ******* groups: # This section defines your user groups. Optionally, it defines application # and API access restrictions (ACLs) for the group. Users may belong to # more than one group. Again, no required or special groups here. admin_group: users: - admin applications: true # special form allows access to ALL applications guests: users: "*" applications: - dashboard api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin_group allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: true session: timeout: 7200 # (seconds) rolling: true # activity extends timeout when true # If log_acls is true, the selected ACL for every API access is logged. log_acls: true # If debug_acls is true, even more information about ACL selection is logged. debug_acls: true My goal is to allow anonymous user to dashboard, but MSR is still asking for a password when trying to access that. Nothing in the logs related to dashboard access. Probably an error in the configuration, but help needed to find that. Tried to put url: "/dashboard" under api_acls, but that was a long shot and didn't work.
Multi-System Reactor
VEC Virtual Switch Auto Off
S
I use Virtual Entity Controller virtual switches which I turn on via webhooks from other applications. Once a switch triggers and turns on, I can then activate associated rules. I would like each virtual switch to automatically turn off after a configurable time (e.g., 5 seconds, 10 seconds). Is there a better way to achieve this auto-off behavior instead of creating a separate rule for each switch that uses the 'Condition must be sustained for' option to turn it off? With a large number of these switches (and the associated turn-off rules), I'm checking to see if there is a simpler approach.If not, could this be a feature request to add an auto-off timer directly to the virtual switches. Thanks Reactor (Multi-hub) latest-26011-c621bbc7 VirtualEntityController v25356 Synology Docker
Multi-System Reactor
Upcoming Storage Change -- Got Back-ups?
toggledbitsT
TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future. In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level. Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way. I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption. A few other things to know: If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc. Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy). The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON. You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach). The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case. This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change. This thread is open for any questions or concerns.
Multi-System Reactor
Oddness in Copy/Move of Reactions
G
Topic thumbnail image
Multi-System Reactor
[Solved] function isRuleEnabled() issue
CrilleC
Topic thumbnail image
Multi-System Reactor
[Reactor] Problem with Global Reactions and groups
therealdbT
Topic thumbnail image
Multi-System Reactor
Possible feature request 2?
CatmanV2C
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks. Any chance of a 'bulk delete' option? No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices Cheers C
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
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor

Vera Thermostat trigger wrong Setpoint value

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

                      • HA and AI
                        CatmanV2C
                        CatmanV2
                        0
                        1
                        34

                      • How to upgrade from an old version of MSR?
                        CatmanV2C
                        CatmanV2
                        0
                        6
                        94

                      • Access control - allowing anonymous user to dashboard
                        toggledbitsT
                        toggledbits
                        0
                        2
                        90

                      • VEC Virtual Switch Auto Off
                        S
                        SweetGenius
                        1
                        1
                        65

                      • Upcoming Storage Change -- Got Back-ups?
                        toggledbitsT
                        toggledbits
                        3
                        1
                        59

                      • Oddness in Copy/Move of Reactions
                        G
                        gwp1
                        0
                        1
                        77

                      • [Solved] function isRuleEnabled() issue
                        CrilleC
                        Crille
                        0
                        4
                        146

                      • [Reactor] Problem with Global Reactions and groups
                        therealdbT
                        therealdb
                        0
                        3
                        147

                      • Possible feature request 2?
                        CatmanV2C
                        CatmanV2
                        0
                        3
                        120

                      • Reactor (Multi-System/Multi-Hub) Announcements
                        toggledbitsT
                        toggledbits
                        5
                        133
                        82.2k

                      • Genuinely impressed with Zigbee and HA / Reactor
                        CatmanV2C
                        CatmanV2
                        1
                        9
                        423

                      • Copying a global reaction
                        toggledbitsT
                        toggledbits
                        0
                        3
                        146
                      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