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
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
Bail out of failed reaction?
T
Topic thumbnail image
Multi-System Reactor
Arming Envisalink panel from MSR
T
Topic thumbnail image
Multi-System Reactor
[Solved] DynamicGroupController updating members issue
CrilleC
Edit: Solved in latest-26221. Bare-metal latest-26193 I have this group: "OKforLarm": name: OK för Larm select: - include_controller: vera - include_capability: door_sensor filter_expression: entity.attributes.door_sensor.state It contains the entities I expect but behaves a bit odd. When I open vera>device_10097 the entity attribute door_sensor.state changes to true but it won't show up as member in the group, when I also open vera>device_10095 they both shows as members and when I close vera>device_10095 it disappear from the group but when I close vera>device_10097 it lingers in the group until I restart Reactor.
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
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
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

x_vera_device.failed=true Question

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

                • DynamicGroupController and attributes
                  therealdbT
                  therealdb
                  1
                  8
                  168

                • Bail out of failed reaction?
                  T
                  tamorgen
                  0
                  3
                  57

                • Arming Envisalink panel from MSR
                  T
                  tamorgen
                  0
                  7
                  274

                • [Solved] DynamicGroupController updating members issue
                  CrilleC
                  Crille
                  0
                  5
                  194

                • Reactor (Multi-System/Multi-Hub) Announcements
                  toggledbitsT
                  toggledbits
                  5
                  148
                  132.0k

                • Upgrade Issues
                  T
                  tbully
                  0
                  9
                  300

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

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

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

                • Logon screen timeout
                  G
                  gwp1
                  0
                  5
                  217

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

                • Upgrade advice - upgrade from aarch64 to ARM64 image
                  toggledbitsT
                  toggledbits
                  0
                  4
                  243
                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