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
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
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor
[Solved] Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
Multi-System Reactor
Issue with MSR UI becoming unresponsive
S
I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all. From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only. Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again... Installation method Home Assistant Container Core 2025.7.3 Frontend 20250702.3 nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR Any help would be greatly appreciated Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node [latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined) [latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300 [latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141 [latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US [latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM" [latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326 [latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312 [latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141 [latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279 [latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314 [latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251 [latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253 [latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141 [latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258 [latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328 [latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323 [latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292 [latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325 [latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328 [latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328 [latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138 [latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141 [latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325 [latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268 [latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323 [latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092 [latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason: [-] FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason: at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:508:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:108:11) at TLSSocket.socketErrorListener (node:_http_client:575:5) at TLSSocket.emit (node:events:508:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at processTicksAndRejections (node:internal/process/task_queues:89:21
Multi-System Reactor
Date/time condition
tunnusT
Topic thumbnail image
Multi-System Reactor
Device log?
G
@toggledbits is there a log that will show me what rule is turning on a specific device? I've got a switch that has been kicking on at 2200 ET for several nights now and the reactor.log doesn't have a thing in it that I can see on a device level (it being more rules-based).
Multi-System Reactor
Midnight crossing not working in date/time condition (build 25325)
tunnusT
Topic thumbnail image
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
[Solved] Local expression in Rule does not evaluate as they used to do
CrilleC
Topic thumbnail image
Multi-System Reactor
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
Multi-System Reactor

x_vera_device.failed=true Question

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

                • Copying a global reaction
                  toggledbitsT
                  toggledbits
                  0
                  3
                  69

                • [HowTo] Using HABridge with Reactor
                  CatmanV2C
                  CatmanV2
                  0
                  9
                  368

                • [Reactor] Bug when sending MQTT boolean payloads
                  toggledbitsT
                  toggledbits
                  0
                  4
                  121

                • Genuinely impressed with Zigbee and HA / Reactor
                  therealdbT
                  therealdb
                  1
                  8
                  276

                • Difficulty defining repeating annual period
                  G
                  gwp1
                  0
                  5
                  75

                • Need help with sequence
                  therealdbT
                  therealdb
                  0
                  3
                  46

                • Possible feature request?
                  therealdbT
                  therealdb
                  0
                  5
                  159

                • Logic Assistance: Exterior Lights on when Illuminance Below Threshold
                  CatmanV2C
                  CatmanV2
                  0
                  11
                  325

                • Time series documentation
                  tunnusT
                  tunnus
                  0
                  11
                  384

                • MQTT templates for ZIgbee scene controller, or a better way?
                  CatmanV2C
                  CatmanV2
                  0
                  3
                  154

                • Reset a delay
                  CatmanV2C
                  CatmanV2
                  0
                  8
                  213
                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