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
UI not loading after upgrading to 26318
tunnusT
Sorry for a hasty post, will update some details later, but the scenario is that I managed to type a wrong password for too many times and had the following users.yaml section: authtrack: max_attempts: 4 within_minutes: 180 # 180 minutes = 3 hrs block_expiration_minutes: 10080 # 7 days At this time I used build 26298. Then noticed there's a new build with a bypass blocking feature (and yes, it said it won't remove existing block). Anyway, went ahead and upgraded to 26318, but the problem now is that UI is not loading at all (page does not answer). This also means that I cannot use "http://reactor_host:port/diag/clear_authtrack?askauth" command to clear the block (or use any other source IP for login). Docker container stays up & running and does not exit. I'll try to dig up some logs, but anything that I could immediately try out (could I delete a particular file for example)? EDIT: some logs [latest-26318]2026-11-17T20:42:32.337Z <Rule:INFO> MSR startup (rule-lculfnhm in Miscellaneous) started [latest-26318]2026-11-17T20:42:32.343Z <httpapi:NOTICE> httpapi#1 HTTP server listening on :::8111 [latest-26318]2026-11-17T20:42:32.347Z <httpapi:INFO> httpapi#1 local docs found in /opt/reactor/docs/html; setting up static service [latest-26318]2026-11-17T20:42:32.354Z <app:NOTICE> Starting WSAPI... [latest-26318]2026-11-17T20:42:32.355Z <wsapi:NOTICE> wsapi: starting version 26298 protocol [latest-26318]2026-11-17T20:42:32.523Z <Engine:INFO> Engine#1 master timer tick, local time "17/11/2026 22:42:32" (TZ offset 120 mins from UTC) [latest-26318]2026-11-17T20:42:32.542Z <Engine:NOTICE> Starting reaction MSR startup<SET> (rule-lculfnhm:S) [latest-26318]2026-11-17T20:42:32.545Z <Notifier:null> Module Notifier v26186 [latest-26318]2026-11-17T20:42:32.545Z <Engine:INFO> MSR startup<SET> all actions completed. [latest-26318]2026-11-17T20:42:32.557Z <Rule:INFO> Rule#rule-lculfnhm reaction rule-lculfnhm:S completed [latest-26318]2026-11-17T20:42:32.558Z <default:null> Module NotifyTelegram v26177
Multi-System Reactor
[Resolved] Hubitat upgrade 2.5.3.123 may have broken login
3
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
Reactor Inspect - a small read-only helper panel for MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Reverse proxy & API ACL
tunnusT
I'm trying to allow anonymous access from a local network to /api/v1/log, but the problem now with the reverse proxy configuration is that this access is open via proxy to the internet. At least I wasn't able to configure ACL so that only an access from a local network would be permitted. reactor.yaml: baseurl: "http://192.168.1.12:8111" proxy_baseurl: "https://external.com:30000" trusted_proxy: "192.168.1.12" Local traffic would originate from 192.168.1.0/24 network. Synology is acting as a reverse proxy and hosting MSR as a docker container (which has its own network and IP 172.18.0.5). MSR build is latest-26298-fbb75fb8 users.yaml: - url: "/api/v1/log" method: "GET" source_ip: 172.18.0.0/24 allow: true Using the above ACL works, but it enables access via proxy also. If I use source_ip: 192.168.1.0/24, then it doesn't work either locally or remotely. So I'm kinda lost what should I use as source_ip in this case?
Multi-System Reactor
MFA
T
Topic thumbnail image
Multi-System Reactor
Grouped devices
G
I've seen many of you using Dynamic Group Controller. I'm using it myself for monitoring device battery levels. I've read and re-read the Dynamic Group Controller docs and still cannot come to an answer for my question so let me paint my scenario: I've migrated from EchoSpeaks in Hubitat ('cause borked and seemingly unmaintained) to Alexa Devices in Home Assistant ('cause not borked in 2026.11.0) to be able to send TTS to my Echo devices. In EchoSpeaks I could create groups. Sweet. In Alexa Devices I don't seem to be able to do so. As such, my thought was "wait - isn't there a way in MSR?" Is this an effective scenario that Dynamic Group Controller can be used for?
Multi-System Reactor
Login protections
tunnusT
Topic thumbnail image
Multi-System Reactor
Reactor Build 26284 stuck at Loading Reactor UI
T
Topic thumbnail image
Multi-System Reactor
MSR with reverse proxy
tunnusT
I'm trying to use MSR via reserve proxy in Synology DSM, but MSR page does not load https://<public ip>:30000/reactor/en-US/ At the same time logging page loads normally https://<public ip>:30000/api/v1/log I thought maybe authentication was messing it up, but there was no deny entries in the log, and also disabling authentication did not make any difference. For this use case VPN is not an option (that works, but as said not an option for this particular use case). Any ideas what could cause this? MSR build latest-26242-28d69aa8, Chrome browser
Multi-System Reactor
Missing attribute after upgrade
3
Topic thumbnail image
Multi-System Reactor
[MSR] Native fan capabilty
therealdbT
Nothing more to add. I see we have hvac_blower, but, anyway, maybe a native fan on the same assumptions of the fan from HASS could be reasonable. I have a couple of them. ie, this is from ESPHome via HASS. x_hass.domain="fan" x_hass.entity_id="fan.kitchen_seashell_hood_ventilation_fan" x_hass.floor_id=null x_hass.services=["fan","esphome"] x_hass.source="esphome" x_hass.state="off" x_hass_attr.friendly_name="Seashell Hood Ventilation Fan" x_hass_attr.percentage=50 x_hass_attr.percentage_step=25 x_hass_attr.preset_mode="" x_hass_attr.preset_modes=[] x_hass_attr.supported_features=49 Thanks.
Multi-System Reactor
[MSR] Rule do not fire
therealdbT
Topic thumbnail image
Multi-System Reactor
Rule condition shows TRUE in UI but Rule never transitions to SET — survives full restart
N
Build: latest-26221-b25bb3e3, Docker on Synology. Hi, I have a Rule whose Trigger/Constraints reference other Rules via Rule State ... is TRUE. At some point it stops firing. Expanding the rule's condition tree in the UI shows every Trigger and Constraint condition green/TRUE — confirmed live by walking into the room and watching Motion go true in real time. Rule History shows no new SET, just old reset entries. Tried, on the same rule, same evening: recreating the trigger conditions with fresh IDs, recreating the constraint conditions with fresh IDs (flat and wrapped in a new Group — wrapping in a Group produced one SET, but it didn't reproduce on repeat attempts with the same structure), and finally a full container restart with a verified-correct saved rule. Still no SET, even with a fresh live motion event right after the restart. Separately, I found that this rule (and its 10 per-room clones) share identical internal condition/group IDs with each other — leftover from a batch clone done months ago, never regenerated. Not sure if that's related, since fixing the IDs didn't reliably fix the symptom either. Has anyone seen a Rule State condition show TRUE in the UI without the Rule ever producing a SET, surviving a clean restart? Thanks in advance
Multi-System Reactor
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
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API. Updates: (the latest versions first in the list) OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Multi-System Reactor
Ooops - Deleted Reactor Ex Machina II
R
I accidentally deleted Reactor Ex Machina II (REM II) from my Reactor rules. I tried to recover it by deleting the .json and .dval in the Rules subdirectory and then recreating it from Togglebits original posting, but that did not work. Does anyone know how to recover REM ll ?
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

x_vera_device.failed=true Question

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

                • UI not loading after upgrading to 26318
                  tunnusT
                  tunnus
                  0
                  5
                  119

                • [Resolved] Hubitat upgrade 2.5.3.123 may have broken login
                  toggledbitsT
                  toggledbits
                  0
                  8
                  292

                • Reactor (Multi-System/Multi-Hub) Announcements
                  toggledbitsT
                  toggledbits
                  5
                  153
                  163.3k

                • Reactor Inspect - a small read-only helper panel for MSR
                  G
                  gwp1
                  2
                  8
                  612

                • Reverse proxy & API ACL
                  tunnusT
                  tunnus
                  0
                  9
                  525

                • MFA
                  T
                  tamorgen
                  0
                  28
                  1.4k

                • Grouped devices
                  G
                  gwp1
                  0
                  3
                  200

                • Login protections
                  toggledbitsT
                  toggledbits
                  0
                  2
                  239

                • Reactor Build 26284 stuck at Loading Reactor UI
                  T
                  tamorgen
                  0
                  16
                  1.8k

                • MSR with reverse proxy
                  tunnusT
                  tunnus
                  0
                  12
                  907

                • Missing attribute after upgrade
                  3
                  3rdStng
                  0
                  3
                  695

                • Use of Google Gemini as an MSR and Hubitat configuration aid
                  therealdbT
                  therealdb
                  0
                  2
                  333
                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