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. x_vera_device.failed=true Question
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
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
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
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor
[Solved] Runtime error when exiting global reaction that contains a group
S
I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved. The Runtime Error is different in the two browsers Safari v18.3 @http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Google Chrome 133.0.6943.142 TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Steps to reproduce: Click the pencil to edit a global reaction with a group. Click the Exit button. Runtime error appears. or Click Create Reaction Click Add Action Select Group Add Condition such as Entity Attribute. Add an Action. Click Save Click Exit Runtime error appears. I don’t know how long the error has been there as I haven’t edited the global reaction in a long time. Reactor (Multi-hub) latest-25060-f32eaa46 Docker Mac OS: 15.3.1 Thanks
Multi-System Reactor

x_vera_device.failed=true Question

Scheduled Pinned Locked Moved Multi-System Reactor
7 Posts 2 Posters 296 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
    #1

    I have a couple of HS1DS-Z door sensors (Z-Wave) this issue is newish and hasn't always been a problem with them. I have an MSR rule that will detect any failed devices on the Vera Hub and alert me. For some reason MSR thinks these two door sensors have failed when I think they have not. As they are fully working and operational within Vera.

    Yesterday I unpaired both of them from the Vera controller and added them again to see if that might fix the issue, but I have just seen an alert in MSR about one of these door sensors being failed again.

    Looking at it in the Entities I see this:

    16553a00-775b-483a-b26e-3960afbdbd95-image.png

    Looking at this devices variables in the Vera UI7 I don't even see a CommFailure variable listed at all for some reason, not sure why.

    So how is MSR deciding the device is failed ?

    Thanks

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

      arming.state=false
      battery_power.level=0.65
      battery_power.since=1661355061000
      binary_sensor.state=false
      door_sensor.state=false
      x_vera_device.configured=true
      x_vera_device.device_number=202
      x_vera_device.device_type="urn:schemas-micasaverde-com:device:DoorSensor:1"
      x_vera_device.failed=true
      x_vera_device.mapped_by="*;device_type=urn:schemas-micasaverde-com:device:DoorSensor:1"
      x_vera_device.mapped_class="door_sensor"
      x_vera_device.parent_device=1
      x_vera_device.room_id="7"
      x_vera_svc_micasaverde_com_HaDevice1.AutoConfigure="-1"
      x_vera_svc_micasaverde_com_HaDevice1.BatteryDate="1661355061"
      x_vera_svc_micasaverde_com_HaDevice1.BatteryLevel="65"
      x_vera_svc_micasaverde_com_HaDevice1.ChildrenSameRoom="1"
      x_vera_svc_micasaverde_com_HaDevice1.CommFailure="1"
      x_vera_svc_micasaverde_com_HaDevice1.CommFailureAlarm="1656854367,1"
      x_vera_svc_micasaverde_com_HaDevice1.CommFailureTime="1661092640"
      x_vera_svc_micasaverde_com_HaDevice1.Configured="1"
      x_vera_svc_micasaverde_com_HaDevice1.FirstConfigured="1661353606"
      x_vera_svc_micasaverde_com_HaDevice1.LastUpdate="1661355061"
      x_vera_svc_micasaverde_com_HaDevice1.ModeSetting="1:;2:A;3:A;4:A"
      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_Alarm="TAMPER_ALARM"
      x_vera_svc_micasaverde_com_HaDevice1.sl_Alarm_updated=1658772103494
      x_vera_svc_micasaverde_com_HaDevice1.sl_BatteryAlarm="0"
      x_vera_svc_micasaverde_com_HaDevice1.sl_BatteryAlarm_updated=1658772103494
      x_vera_svc_micasaverde_com_HaDevice1.sl_TamperAlarm="0"
      x_vera_svc_micasaverde_com_HaDevice1.sl_TamperAlarm_updated=1661355055978
      x_vera_svc_micasaverde_com_SecuritySensor1.Armed="0"
      x_vera_svc_micasaverde_com_SecuritySensor1.ArmedTripped="0"
      x_vera_svc_micasaverde_com_SecuritySensor1.IgnoreTripTime="2"
      x_vera_svc_micasaverde_com_SecuritySensor1.LastTamper="1661355055"
      x_vera_svc_micasaverde_com_SecuritySensor1.LastTrip="1661377232"
      x_vera_svc_micasaverde_com_SecuritySensor1.Tripped="0"
      x_vera_svc_micasaverde_com_ZWaveDevice1.AgiInfo="X"
      x_vera_svc_micasaverde_com_ZWaveDevice1.AlarmType="0x6,0x7,"
      x_vera_svc_micasaverde_com_ZWaveDevice1.AlarmVersion="0,1"
      x_vera_svc_micasaverde_com_ZWaveDevice1.AssociationNum="5"
      x_vera_svc_micasaverde_com_ZWaveDevice1.Capabilities="83,156,1,4,7,1,R,B,RS,|48:2,89,90,94,113:4,114,115,128,132:2,133,134,"
      x_vera_svc_micasaverde_com_ZWaveDevice1.ConfiguredAssoc=""
      x_vera_svc_micasaverde_com_ZWaveDevice1.ConfiguredWakeupInterval="86400"
      x_vera_svc_micasaverde_com_ZWaveDevice1.LastArr="1661377143,2"
      x_vera_svc_micasaverde_com_ZWaveDevice1.LastNnu="1661375951,2"
      x_vera_svc_micasaverde_com_ZWaveDevice1.LastReset="1661353599"
      x_vera_svc_micasaverde_com_ZWaveDevice1.LastRouteUpdate="1661354768"
      x_vera_svc_micasaverde_com_ZWaveDevice1.LastWakeup="1661377235"
      x_vera_svc_micasaverde_com_ZWaveDevice1.ManufacturerInfo="608,360,360"
      x_vera_svc_micasaverde_com_ZWaveDevice1.NodeInfo="30,59,5a,5e,71,72,73,80,84,85,86,"
      x_vera_svc_micasaverde_com_ZWaveDevice1.PlusInfo="1,6,0,12,6,12,6"
      x_vera_svc_micasaverde_com_ZWaveDevice1.PollNoReply="131"
      x_vera_svc_micasaverde_com_ZWaveDevice1.PollOk="2"
      x_vera_svc_micasaverde_com_ZWaveDevice1.PollSettings="0"
      x_vera_svc_micasaverde_com_ZWaveDevice1.SensorBiType="10"
      x_vera_svc_micasaverde_com_ZWaveDevice1.SubscribedAlarms=",0x6,0x7,"
      x_vera_svc_micasaverde_com_ZWaveDevice1.VersionInfo="6,4,5,1,1"
      x_vera_svc_micasaverde_com_ZWaveDevice1.WakeupCapabilities="60,86400,10800,60"
      x_vera_svc_micasaverde_com_ZWaveDevice1.WakeupInterval="86400"
      x_vera_svc_micasaverde_com_ZWaveNetwork1.ConsecutivePollFails="0"
      x_vera_svc_micasaverde_com_ZWaveNetwork1.LastPollSuccess="1661355061"
      x_vera_svc_upnp_org_SwitchPower1.Status="0"
      zwave_device.capabilities="83,156,1,4,7,1,R,B,RS,|48:2,89,90,94,113:4,114,115,128,132:2,133,134,"
      zwave_device.failed=true
      zwave_device.manufacturer_info="608,360,360"
      zwave_device.node_id=147
      zwave_device.version_info="6,4,5,1,1"
      Capabilities: arming, battery_power, binary_sensor, door_sensor, x_vera_device, x_vera_security, x_vera_svc_micasaverde_com_HaDevice1, x_vera_svc_micasaverde_com_SecuritySensor1, x_vera_svc_micasaverde_com_ZWaveDevice1, x_vera_svc_micasaverde_com_ZWaveNetwork1, x_vera_svc_upnp_org_SwitchPower1, zwave_device
      Actions: arming.arm, arming.disarm, x_vera_device.set_variable, x_vera_security.trip, x_vera_security.untrip, 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_SecuritySensor1.SetArmed, 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.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_SwitchPower1.SetTarget, zwave_device.debug, zwave_device.heal, zwave_device.interview, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.remove_failed, zwave_device.replace_failed, zwave_device.reset_meters, zwave_device.set_config, zwave_device.set_location, zwave_device.set_name, zwave_device.set_value

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

        Just spotted "x_vera_svc_micasaverde_com_HaDevice1.CommFailure="1"" in that output above. Yet I cannot see that in the Vera UI7 web GUI for this device in its variables. Also I do not have that red banner that says "Can't detect device". As far as Vera looks the device looks to be all OK and working fine.

        Obviously that variable should be 0 not 1.

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

          This is the device variables in Vera UI7

          a23a4a58-eff6-4c79-96c5-f84c0c277cf3-image.png

          0d911613-0233-43d5-89b3-89f59c6cf61b-image.png

          19f2bc2e-b95c-4b02-a585-4e9ad2d919a6-image.png

          588b63e8-394d-417b-91b4-d2ca5e680fc9-image.png

          9eabd1ce-c6d7-4654-8795-c8efed2790bf-image.png

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

            Just create the CommFailure variable on the Vera using the service ID given with a value of 0. That variable should exist for all Z-Wave devices, so if it isn't there, it either got deleted somehow (corruption?) or its a bug in the device handler (on the Vera).

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

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

              Looking on another different device I made a note of these:

              CommFailure - urn:micasaverde-com:serviceId:HaDevice1
              CommFailureTime - urn:micasaverde-com:serviceId:HaDevice1
              CommFailureAlarm - urn:micasaverde-com:serviceId:HaDevice1

              Then on one of the problematic Door contact sensors I added the new services.

              c696d666-9571-44fd-9f49-fc0e943b74d0-image.png

              Now under its Variables tab I see them:

              8eae935d-749c-4db8-94d6-5f85ec9d2a6c-image.png

              I will monitor and see if CommFailure goes back to 1 ?

              Thanks

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

                The issue isn't that CommFailure was 0 or 1, it was that it wasn't there at all. That suggests it may have existed at some point with value 1, then disappeared, leaving the attribute value on the MSR side stuck (because it had no variable from Vera to use to change it). It's possible the Vera device handler has a bug and instead of setting 0 when the device is configured, it sets it to blank, which as of a couple of firmware versions ago, deletes the variable rather than setting it to an empty value. Having now created it manually, if it later disappears, that would confirm this theory -- something in the firmware is removing for some reason (or worst case, there's user_data corruption). In any case, CommFailure should always exist for Z-Wave devices, so something isn't right there, but of course, no chance that it would be researched or fixed these days. The Vera firmware thread has been long dead, no updates have been published, and questions and requests are left unanswered; I have my doubts that anyone with the knowledge (and will) is still there. Everyone's busy filling the holes in the new firmware (now four years since the acquisition).

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

                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

                • Errors after updating to MQTTController build 25139
                  toggledbitsT
                  toggledbits
                  0
                  2
                  9
                • Set Reaction > Script Action
                  toggledbitsT
                  toggledbits
                  0
                  4
                  25
                • Wiring Samotech SM308-S into light fitting
                  F
                  Freemanator
                  0
                  1
                  9
                • Advice reqeusted to migrate MSR from Bare Metal to Container
                  T
                  tamorgen
                  0
                  5
                  74
                • Reactor (Multi-System/Multi-Hub) Announcements
                  toggledbitsT
                  toggledbits
                  5
                  122
                  37.3k
                • Z-Wave Future....
                  CatmanV2C
                  CatmanV2
                  0
                  5
                  162
                • Can´t restart or upgrade/deploy MSR
                  toggledbitsT
                  toggledbits
                  0
                  4
                  112
                • [Solved] Limit HA Entity in MSR
                  wmarcolinW
                  wmarcolin
                  0
                  7
                  233
                • Disaster recovery and virtualisation
                  CatmanV2C
                  CatmanV2
                  0
                  5
                  687
                • Remote access of Zwave stick from Z-wave server
                  CatmanV2C
                  CatmanV2
                  0
                  3
                  407
                • Organizing/ structuring rule sets and rules
                  G
                  gwp1
                  0
                  5
                  396
                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