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. EzloController error
Local expression in Rule does not evaluate as they used to do
CrilleC
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
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
Multi-System Reactor
Notice to Docker + ARM Users (RPi 3/4/5 and others)
toggledbitsT
This post does not apply to users of Intel/AMD-based systems. If you are using a Reactor image tagged latest-amd64 or stable-amd64, then this post does not apply to you. It also does not apply to bare-metal installs; it's for users of docker images on ARM-based systems only (principally Raspberry Pi hosts, but could be others). After January 15, 2026, I will no longer produce the aarch64-tagged docker image for Reactor. The ARM images will be arm64 for 64-bit operating systems, and armv7l for 32-bit operating systems. For those of you running a container from the aarch64 image today, this will be a relatively simple change: you just need to switch the image used for your docker container to a differently-tagged image. If you are using docker-compose, then this is a relatively simple matter of changing the image line in your docker-compose.yaml file and then stopping (docker-compose down) and restarting (docker-compose up -d) your Reactor daemon. But there's a catch... not all of you can safely just switch from the aarch64 image to the arm64 image. And, you can't just trust the output of uname -m, for example, because this exposes the CPU architecture, but not the word size of the OS running on that CPU. For Raspberry Pi systems, the transition to 64-bit operating systems was long (starting in 2016) and not always obvious — although there was a first "official" 64-bit OS for RPis in 2020, it did not become a default recommendation in the Raspberry Pi Imager until 2021, and then that was only the default for Pi 3/4 systems with >4GB RAM; it was 2022 before it was universally recommended for all 64-bit CPUs regardless of RAM size. Depending on when you first imaged your RPi system and what default you may have been offered/chosen, you could today easily have a 64-bit CPU Raspberry Pi running a 32-bit version of the operating system. Upgrades along the way would not change this; changing it to fully 64-bit requires a full reimage of the system. To establish if your OS is 64- or 32-bit, log in to your Pi and run: sudo dpkg-architecture -q DEB_HOST_ARCH. If the response is arm64 or aarch64, then you are running a 64-bit OS and you should use the arm64-tagged image. If it's anything else, you are running a 32-bit OS, and you should use the armv7l-tagged image. pi@rpi4-1:~ $ sudo dpkg-architecture -q DEB_HOST_ARCH armhf pi@rpi4-1:~ $ uname -m aarch64 pi@rpi4-1:~ $ In the example above, the uname command reports that the CPU is 64-bit architecture (aarch64), which is true for the host on which I ran these commands, but the DEB_HOST_ARCH value is armhf, indicating a 32-bit operating system. This system has to use the armv7l-tagged image. Other systems will have their own ways of determining the word size of the running OS. Since the majority of Reactor users running ARM systems are on Raspberry Pis, I am able to supply the above instructions, but if you happen to have a different ARM system, you'll need to do some web searching to figure out how to expose that information. Or, you can just try the arm64 image, and if it doesn't start up, try the armv7l image. Remember to always back up your system before making any changes. For everyone, please make this change as soon as possible, and if you have any trouble finding a working image, please (1) go back to the current aarch64 image; and (2) let me know in this thread along with as much detail about your host system as you can offer (including the output of the dpkg-architecture command mentioned above).
Multi-System Reactor
Requesting a proper ARM64/aarch64 Docker image (Pi 5 support)
M
Hi, I'm in the process of migrating from a Raspberry Pi 4 (ARMv7) to a Raspberry Pi 5 (ARMv8/aarch64), but I’ve run into an issue: there is no proper ARMv8/aarch64 image available. None of the existing images run on the Pi 5 - they all exit immediately with code 139 (segmentation fault), which typically indicates that the binaries inside the image are not compatible with the ARM64/aarch64 architecture used by the Pi 5. Would it be possible to publish a correct ARMv8/aarch64 (linux/arm64) image? Building one should be relatively straightforward using docker buildx with multi-arch support. For example, my own Node.js images are built this way: docker buildx build --push \ -t <localrepo>/<project>:<tag> \ --platform=linux/arm64,linux/amd64 \ --file ./apps/<project>/Dockerfile . This produces both the AMD64 and ARM64/v8 variants automatically. Also, as a side note, it may be best to avoid using Alpine as the base image for the ARM64 build, since musl-based builds often cause compatibility issues and unnecessary headaches. A glibc-based base image (e.g., Debian or Ubuntu) tends to work far more reliably on ARM64, especially for Node.js applications. @toggledbits - tagging you in case you missed this. Thanks, mgvra
Multi-System Reactor
Script action and custom timers
therealdbT
Sorry to write here without trying, but I’m flying today. Am I correct if i say that script action with alarm() makes it possible to execute a reaction in a given interval, lets say 15 seconds or 3.5 minutes? That sounds amazing, since I’ve used weird tricks, including a custom controller, just to do this.
Multi-System Reactor
Help resolve change in behaviour post update
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reactor w/HA 2025.11 error on set_datetime service call setting only time
CrilleC
@toggledbits Do you know if this is related to that PR or is it a change they made in 2025.11.1? [latest-25310]2025-11-11T13:16:24.319Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag with { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.320Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag action: { "type": "call_service", "service_data": { "date": (null), "time": "10:45", "datetime": (null), "timestamp": (null) }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_dag" } } [latest-25310]2025-11-11T13:16:24.321Z <HassController:ERR> HassController#hass request 1762866984320<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.321Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "10:45" }) on Entity#hass>input_datetime_vvb_dag failed! [latest-25310]2025-11-11T13:16:24.321Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"10:45","datetime":null,"timestamp":null},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_dag"},"id":1762866984320} [latest-25310]2025-11-11T13:16:24.322Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.322Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 0 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Engine#1 action args: { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 1 [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt with { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt action: { "type": "call_service", "service_data": { "date": (null), "time": "03:00", "datetime": (null), "timestamp": 0 }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_natt" } } [latest-25310]2025-11-11T13:16:24.324Z <HassController:ERR> HassController#hass request 1762866984323<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "03:00", "timestamp": 0 }) on Entity#hass>input_datetime_vvb_natt failed! [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"03:00","datetime":null,"timestamp":0},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_natt"},"id":1762866984323} [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.324Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 1 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <Engine:INFO> Engine#1 action args: { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 2 [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Sätt Schema VVB i Home Assistant<AKTIV> all actions completed.
Multi-System Reactor
Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
P
Hello, I currently have an office light (connected via a Leviton Zwave Dimmer switch) controlled from a Gen5 Aeotech Zwave switch installed on my Synology 720+ NAS. I run HA(2025.11.10) in a virtual machine from my NAS and Reactor on the container manager of the same NAS. Prior to updating to 25304 the rule I had set to turn the light on to a specific dimming value worked correctly. Now the rule appears to follow the decision tree, however the reaction does not trigger setting the dimming or turning on the office light? Strangely I can still turn the light on and off as well as dim it directly from HASS..? I have tried using the ''try this action'' button in the rules reaction setting and it will not control the light and does not throw an error flagÉ Please help, P.S Reactor has been rock steady for me over the last few years and I'm a big fan of this solution.
Multi-System Reactor
[Solved] alarm() in global expression throws error in log.
CrilleC
Topic thumbnail image
Multi-System Reactor
[Solved] Define function issue in latest-25304
CrilleC
Topic thumbnail image
Multi-System Reactor
No Upgrade Notification for Build 25308?
CatmanV2C
FWIW I'm no longer getting a notification from MSR that there's an update. Just thought I'd mention it C
Multi-System Reactor
Strange behavior in MSR latest-25304 with disabled groups in Reaction
therealdbT
Topic thumbnail image
Multi-System Reactor
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
Multi-System Reactor
Handling Dead Entities and Renamed Entities
PablaP
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down. I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor). My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
Multi-System Reactor
Strange behavior for MQTT templates using payload and attributes
therealdbT
Topic thumbnail image
Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only). Anyway, here's my reactor-mqtt-contrib package: https://github.com/dbochicchio/reactor-mqtt-contrib Simply download yaml files (everything or just the ones you need) and you're good to go. I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them. The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression. Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
Multi-System Reactor
HA 2025.9.4 Supported Yet?
CatmanV2C
Tangentially did I miss 2025.9.4 getting blessed in MSR? I've been holding off Cheers C
Multi-System Reactor
Rule Set UI bug - RESOLVED
3
Topic thumbnail image
Multi-System Reactor

EzloController error

Scheduled Pinned Locked Moved Multi-System Reactor
20 Posts 3 Posters 1.9k Views 3 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.
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #4

    The Set Variable issue is specific to Vera controllers only and does not apply to eZLO or any other.

    The variable hm associated with rule Notifiering - House mode (Rule#rule-ksw26xod): can you tell me if that's a rule variable, or a global variable?

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

    CrilleC 1 Reply Last reply
    0
    • toggledbitsT toggledbits

      The Set Variable issue is specific to Vera controllers only and does not apply to eZLO or any other.

      The variable hm associated with rule Notifiering - House mode (Rule#rule-ksw26xod): can you tell me if that's a rule variable, or a global variable?

      CrilleC Offline
      CrilleC Offline
      Crille
      wrote on last edited by
      #5

      @toggledbits Yes, in one of the rules I set the openLuup house mode via house mode plugin to push the mode to my Vera (That is otherwise primary for openLuup's house mode).

      The variable hm is an old test I did and does no longer exist and is not referenced anywhere visible to me?

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

        Variables hm and HouseMode both are referenced somewhere, but appear to not be global. If you don't see hm in the list of global variables, it's probably buried in a rule somewhere. What about HouseMode? Global or rule?

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

        CrilleC 1 Reply Last reply
        0
        • toggledbitsT toggledbits

          Variables hm and HouseMode both are referenced somewhere, but appear to not be global. If you don't see hm in the list of global variables, it's probably buried in a rule somewhere. What about HouseMode? Global or rule?

          CrilleC Offline
          CrilleC Offline
          Crille
          wrote on last edited by
          #7

          @toggledbits After going through every Rule Set I have, I deleted the global HouseMode hours before I got this error since it was not referenced anywhere.
          hm was a local in Notifiering - House mode (Rule#rule-ksw26xod) but was replaced weeks ago with a new local named housemode

          rule_1.PNG rule_2.PNG

          This rule has been untouched for weaks and never failed, the thing I changed yesterday was the Trigger from housemode plugin to vera>housemode since it seems you fixed the housemode change issue from openLuup and native is snappier than the polling plugin.

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

            OK. Great detail. That helps, thank you. Let me see what I can do here...

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

            CrilleC 1 Reply Last reply
            0
            • toggledbitsT toggledbits

              OK. Great detail. That helps, thank you. Let me see what I can do here...

              CrilleC Offline
              CrilleC Offline
              Crille
              wrote on last edited by Crille
              #9

              @toggledbits I'm still having some problem with variables being referenced when deleted. Looks like the Engine is looking for an old global expression (undefined)? that I think I had a time ago with matchEntities
              and
              @ 2021-10-04T14:11:00.003Z
              This rule triggers: Rule:INFO Notifiering - Ezlo devices (Rule#rule-ku32xyj5) SET!
              ezlo_triggers.PNG ezlo_expression.PNG

              I've now put a sustianed for 3 secs on the first variable trigger to ignore flapping.

              global_expressions.PNG

              None of the other rules triggered in the log snippet has any local expression or referenced global expressions and the "Error: Object does not exist" is present from:

              2021-10-04T10:31:08.900Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005
              2021-10-04T10:31:08.901Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005
              2021-10-04T10:31:08.905Z <Engine:5:Engine.js:948> Engine#1 set global Medeltemp; value=(number)22
              2021-10-04T10:31:08.908Z <Engine:5:Engine.js:948> Engine#1 set global Luftfuktighet; value=(number)0.8148148148148148
              2021-10-04T10:31:10.074Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005
              2021-10-04T10:31:10.075Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005
              2021-10-04T10:31:25.061Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005
              2021-10-04T10:31:25.061Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005
              2021-10-04T10:32:00.014Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [  ] }) took 0ms and returned 22 entities
              2021-10-04T10:32:00.027Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [  ] }) took 0ms and returned 22 entities
              2021-10-04T10:32:09.094Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005
              2021-10-04T10:32:09.095Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005
              2021-10-04T10:32:10.297Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005
              2021-10-04T10:32:10.297Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005
              2021-10-04T10:32:24.996Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005
              2021-10-04T10:32:24.996Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005
              2021-10-04T10:33:00.002Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [  ] }) took 0ms and returned 22 entities
              2021-10-04T10:33:00.015Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [  ] }) took 0ms and returned 22 entities
              2021-10-04T10:33:09.142Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005
              2021-10-04T10:33:09.143Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005
              2021-10-04T10:33:09.148Z <Engine:5:Engine.js:948> Engine#1 set global Luftfuktighet; value=(number)0.7901234567901234
              2021-10-04T10:33:10.387Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005
              2021-10-04T10:33:10.388Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005
              2021-10-04T10:33:25.394Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005
              2021-10-04T10:33:25.394Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005
              2021-10-04T10:33:30.894Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_603a0373129e0715cf4a765f
              2021-10-04T10:33:30.897Z <default:CRIT> Error: Object does not exist
              Error: Object does not exist
                  at Function.getInstance (/home/homebridge/reactor/server/lib/GlobalExpression.js:130:27)
                  at Engine._expr_dependency (/home/homebridge/reactor/server/lib/Engine.js:1109:59)
                  at /home/homebridge/reactor/server/lib/MessageBus.js:99:208
                  at Array.forEach (<anonymous>)
                  at MessageBus._sendToBus (/home/homebridge/reactor/server/lib/MessageBus.js:96:47)
                  at /home/homebridge/reactor/server/lib/MessageBus.js:109:48
                  at new Promise (<anonymous>)
                  at MessageBus.send (/home/homebridge/reactor/server/lib/MessageBus.js:106:16)
                  at Entity.publish (/home/homebridge/reactor/server/lib/Observable.js:71:44)
                  at Entity.deferNotifies (/home/homebridge/reactor/server/lib/Entity.js:248:207)
              

              Where everything above the error is just repeating.

              Log from rule SET in next post...

              CrilleC 1 Reply Last reply
              0
              • CrilleC Crille

                @toggledbits I'm still having some problem with variables being referenced when deleted. Looks like the Engine is looking for an old global expression (undefined)? that I think I had a time ago with matchEntities
                and
                @ 2021-10-04T14:11:00.003Z
                This rule triggers: Rule:INFO Notifiering - Ezlo devices (Rule#rule-ku32xyj5) SET!
                ezlo_triggers.PNG ezlo_expression.PNG

                I've now put a sustianed for 3 secs on the first variable trigger to ignore flapping.

                global_expressions.PNG

                None of the other rules triggered in the log snippet has any local expression or referenced global expressions and the "Error: Object does not exist" is present from:

                2021-10-04T10:31:08.900Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005
                2021-10-04T10:31:08.901Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005
                2021-10-04T10:31:08.905Z <Engine:5:Engine.js:948> Engine#1 set global Medeltemp; value=(number)22
                2021-10-04T10:31:08.908Z <Engine:5:Engine.js:948> Engine#1 set global Luftfuktighet; value=(number)0.8148148148148148
                2021-10-04T10:31:10.074Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005
                2021-10-04T10:31:10.075Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005
                2021-10-04T10:31:25.061Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005
                2021-10-04T10:31:25.061Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005
                2021-10-04T10:32:00.014Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [  ] }) took 0ms and returned 22 entities
                2021-10-04T10:32:00.027Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [  ] }) took 0ms and returned 22 entities
                2021-10-04T10:32:09.094Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005
                2021-10-04T10:32:09.095Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005
                2021-10-04T10:32:10.297Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005
                2021-10-04T10:32:10.297Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005
                2021-10-04T10:32:24.996Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005
                2021-10-04T10:32:24.996Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005
                2021-10-04T10:33:00.002Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [  ] }) took 0ms and returned 22 entities
                2021-10-04T10:33:00.015Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [  ] }) took 0ms and returned 22 entities
                2021-10-04T10:33:09.142Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005
                2021-10-04T10:33:09.143Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005
                2021-10-04T10:33:09.148Z <Engine:5:Engine.js:948> Engine#1 set global Luftfuktighet; value=(number)0.7901234567901234
                2021-10-04T10:33:10.387Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005
                2021-10-04T10:33:10.388Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005
                2021-10-04T10:33:25.394Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005
                2021-10-04T10:33:25.394Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005
                2021-10-04T10:33:30.894Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_603a0373129e0715cf4a765f
                2021-10-04T10:33:30.897Z <default:CRIT> Error: Object does not exist
                Error: Object does not exist
                    at Function.getInstance (/home/homebridge/reactor/server/lib/GlobalExpression.js:130:27)
                    at Engine._expr_dependency (/home/homebridge/reactor/server/lib/Engine.js:1109:59)
                    at /home/homebridge/reactor/server/lib/MessageBus.js:99:208
                    at Array.forEach (<anonymous>)
                    at MessageBus._sendToBus (/home/homebridge/reactor/server/lib/MessageBus.js:96:47)
                    at /home/homebridge/reactor/server/lib/MessageBus.js:109:48
                    at new Promise (<anonymous>)
                    at MessageBus.send (/home/homebridge/reactor/server/lib/MessageBus.js:106:16)
                    at Entity.publish (/home/homebridge/reactor/server/lib/Observable.js:71:44)
                    at Entity.deferNotifies (/home/homebridge/reactor/server/lib/Entity.js:248:207)
                

                Where everything above the error is just repeating.

                Log from rule SET in next post...

                CrilleC Offline
                CrilleC Offline
                Crille
                wrote on last edited by
                #10

                First lines looks interesting

                2021-10-04T14:10:33.692Z <EzloController:WARN> EzloController#ezlo warning: update parameter serviceNotification for Entity#ezlo>device_603a0367129e0715cf4a7604 not previously defined! (value now (boolean)false)
                2021-10-04T14:10:33.693Z <EzloController:WARN> EzloController#ezlo warning: update parameter syncNotification for Entity#ezlo>device_603a0367129e0715cf4a7604 not previously defined! (value now (boolean)false)
                2021-10-04T14:10:33.694Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_603a0367129e0715cf4a7604
                2021-10-04T14:10:33.697Z <default:CRIT> Error: Object does not exist
                Error: Object does not exist
                    at Function.getInstance (/home/username/reactor/server/lib/GlobalExpression.js:130:27)
                    at Engine._expr_dependency (/home/username/reactor/server/lib/Engine.js:1109:59)
                    at /home/username/reactor/server/lib/MessageBus.js:99:208
                    at Array.forEach (<anonymous>)
                    at MessageBus._sendToBus (/home/username/reactor/server/lib/MessageBus.js:96:47)
                    at /home/username/reactor/server/lib/MessageBus.js:109:48
                    at new Promise (<anonymous>)
                    at MessageBus.send (/home/username/reactor/server/lib/MessageBus.js:106:16)
                    at Entity.publish (/home/username/reactor/server/lib/Observable.js:71:44)
                    at Entity.deferNotifies (/home/username/reactor/server/lib/Entity.js:248:207)
                2021-10-04T14:10:35.317Z <EzloController:WARN> EzloController#ezlo warning: update parameter serviceNotification for Entity#ezlo>device_603a036a129e0715cf4a761d not previously defined! (value now (boolean)false)
                2021-10-04T14:10:35.318Z <EzloController:WARN> EzloController#ezlo warning: update parameter syncNotification for Entity#ezlo>device_603a036a129e0715cf4a761d not previously defined! (value now (boolean)false)
                2021-10-04T14:10:35.318Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_603a036a129e0715cf4a761d
                2021-10-04T14:10:35.318Z <default:CRIT> Error: Object does not exist
                Error: Object does not exist
                    at Function.getInstance (/home/username/reactor/server/lib/GlobalExpression.js:130:27)
                    at Engine._expr_dependency (/home/username/reactor/server/lib/Engine.js:1109:59)
                    at /home/username/reactor/server/lib/MessageBus.js:99:208
                    at Array.forEach (<anonymous>)
                    at MessageBus._sendToBus (/home/username/reactor/server/lib/MessageBus.js:96:47)
                    at /home/username/reactor/server/lib/MessageBus.js:109:48
                    at new Promise (<anonymous>)
                    at MessageBus.send (/home/username/reactor/server/lib/MessageBus.js:106:16)
                    at Entity.publish (/home/username/reactor/server/lib/Observable.js:71:44)
                    at Entity.deferNotifies (/home/username/reactor/server/lib/Entity.js:248:207)
                2021-10-04T14:10:35.439Z <EzloController:WARN> EzloController#ezlo warning: update parameter serviceNotification for Entity#ezlo>device_6107edd0129e071241a25469 not previously defined! (value now (boolean)false)
                2021-10-04T14:10:35.439Z <EzloController:WARN> EzloController#ezlo warning: update parameter syncNotification for Entity#ezlo>device_6107edd0129e071241a25469 not previously defined! (value now (boolean)false)
                2021-10-04T14:10:35.440Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_6107edd0129e071241a25469
                2021-10-04T14:10:35.440Z <default:CRIT> Error: Object does not exist
                Error: Object does not exist
                    at Function.getInstance (/home/username/reactor/server/lib/GlobalExpression.js:130:27)
                    at Engine._expr_dependency (/home/username/reactor/server/lib/Engine.js:1109:59)
                    at /home/username/reactor/server/lib/MessageBus.js:99:208
                    at Array.forEach (<anonymous>)
                    at MessageBus._sendToBus (/home/username/reactor/server/lib/MessageBus.js:96:47)
                    at /home/username/reactor/server/lib/MessageBus.js:109:48
                    at new Promise (<anonymous>)
                    at MessageBus.send (/home/username/reactor/server/lib/MessageBus.js:106:16)
                    at Entity.publish (/home/username/reactor/server/lib/Observable.js:71:44)
                    at Entity.deferNotifies (/home/username/reactor/server/lib/Entity.js:248:207)
                2021-10-04T14:10:39.201Z <EzloController:WARN> EzloController#ezlo warning: update parameter serviceNotification for Entity#ezlo>device_603a60dc129e071231a7f95e not previously defined! (value now (boolean)false)
                2021-10-04T14:10:39.201Z <EzloController:WARN> EzloController#ezlo warning: update parameter syncNotification for Entity#ezlo>device_603a60dc129e071231a7f95e not previously defined! (value now (boolean)false)
                2021-10-04T14:10:39.203Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_603a60dc129e071231a7f95e
                2021-10-04T14:10:39.205Z <default:CRIT> Error: Object does not exist
                Error: Object does not exist
                    at Function.getInstance (/home/username/reactor/server/lib/GlobalExpression.js:130:27)
                    at Engine._expr_dependency (/home/username/reactor/server/lib/Engine.js:1109:59)
                    at /home/username/reactor/server/lib/MessageBus.js:99:208
                    at Array.forEach (<anonymous>)
                    at MessageBus._sendToBus (/home/username/reactor/server/lib/MessageBus.js:96:47)
                    at /home/username/reactor/server/lib/MessageBus.js:109:48
                    at new Promise (<anonymous>)
                    at MessageBus.send (/home/username/reactor/server/lib/MessageBus.js:106:16)
                    at Entity.publish (/home/username/reactor/server/lib/Observable.js:71:44)
                    at Entity.deferNotifies (/home/username/reactor/server/lib/Entity.js:248:207)
                2021-10-04T14:11:00.002Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [  ] }) took 0ms and returned 22 entities
                2021-10-04T14:11:00.003Z <Rule:INFO> Notifiering - Ezlo devices (Rule#rule-ku32xyj5) SET!
                2021-10-04T14:11:00.005Z <Engine:5:Engine.js:1386> _process_reaction_queue() wake-up!
                2021-10-04T14:11:00.005Z <Engine:INFO> Enqueueing "Notifiering - Ezlo devices<SET>" (rule-ku32xyj5:S)
                2021-10-04T14:11:00.006Z <Engine:5:Engine.js:1246> Engine#1 enqueued reaction rule-ku32xyj5:S as 70
                2021-10-04T14:11:00.006Z <Engine:5:Engine.js:1386> _process_reaction_queue() ending with 1 in queue; waiting for 1633356660006<10/4/2021, 4:11:00 PM> (next delayed task)
                2021-10-04T14:11:00.013Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [  ] }) took 0ms and returned 22 entities
                2021-10-04T14:11:00.014Z <Rule:INFO> Notifiering - Ezlo devices (Rule#rule-ku32xyj5) RESET!
                2021-10-04T14:11:00.015Z <Engine:5:Engine.js:1386> _process_reaction_queue() wake-up!
                2021-10-04T14:11:00.015Z <Engine:5:Engine.js:1347> _process_reaction_queue() running task 70 { "tid": 70, "id": "rule-ku32xyj5:S", "rule": "rule-ku32xyj5", "__reaction": [RuleReaction#rule-ku32xyj5:S], "next_step": 0, "status": 0, "ts": 1633356660005, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise], "halt": true }
                2021-10-04T14:11:00.015Z <Engine:INFO> Halting reaction Notifiering - Ezlo devices<SET> (rule-ku32xyj5:S) at step 0
                2021-10-04T14:11:00.016Z <Engine:NOTICE> Handling reaction halt request for Notifiering - Ezlo devices<SET> at step 0
                2021-10-04T14:11:00.016Z <Engine:5:Engine.js:1351> _process_reaction_queue() task returned, new status -1; task 70
                2021-10-04T14:11:00.016Z <Engine:NOTICE> Engine#1 entry 70 reaction rule-ku32xyj5:S: terminated
                2021-10-04T14:11:00.016Z <Engine:CRIT> !terminated
                2021-10-04T14:11:00.017Z <Engine:5:Engine.js:1386> _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting
                2021-10-04T14:11:00.021Z <Engine:INFO> Enqueueing "Notifiering - Ezlo devices<RESET>" (rule-ku32xyj5:R)
                2021-10-04T14:11:00.021Z <Engine:5:Engine.js:1246> Engine#1 enqueued reaction rule-ku32xyj5:R as 71
                2021-10-04T14:11:00.021Z <Engine:5:Engine.js:1386> _process_reaction_queue() wake-up!
                2021-10-04T14:11:00.022Z <Engine:5:Engine.js:1347> _process_reaction_queue() running task 71 { "tid": 71, "id": "rule-ku32xyj5:R", "rule": "rule-ku32xyj5", "__reaction": [RuleReaction#rule-ku32xyj5:R], "next_step": 0, "status": 0, "ts": 1633356660021, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise] }
                2021-10-04T14:11:00.022Z <Engine:NOTICE> Starting reaction Notifiering - Ezlo devices<RESET> (rule-ku32xyj5:R)
                2021-10-04T14:11:00.023Z <Engine:5:Engine.js:1496> Engine#1 reaction rule-ku32xyj5:R step 0 notify Pushover with { "message": "Alla enheter svarar igen.", "profile": "MSR", "title": "Ezlo-enheter svarar igen.", "priority": "0" }
                2021-10-04T14:11:00.023Z <NotifyPushover:5:NotifyPushover.js:216> NotifyPushover sending profile MSR notification request: Alla enheter svarar igen.
                2021-10-04T14:11:00.024Z <Engine:INFO> Notifiering - Ezlo devices<RESET> all actions completed.
                2021-10-04T14:11:00.024Z <Engine:5:Engine.js:1351> _process_reaction_queue() task returned, new status -1; task 71
                2021-10-04T14:11:00.025Z <Engine:5:Engine.js:1386> _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting
                2021-10-04T14:11:00.647Z <NotifyPushover:5:NotifyPushover.js:224> NotifyPushover successful endpoint exchange (message sent)
                2021-10-04T14:11:03.822Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_603a036e129e0715cf4a763e
                2021-10-04T14:11:03.825Z <default:CRIT> Error: Object does not exist
                Error: Object does not exist
                    at Function.getInstance (/home/username/reactor/server/lib/GlobalExpression.js:130:27)
                    at Engine._expr_dependency (/home/username/reactor/server/lib/Engine.js:1109:59)
                    at /home/username/reactor/server/lib/MessageBus.js:99:208
                    at Array.forEach (<anonymous>)
                    at MessageBus._sendToBus (/home/username/reactor/server/lib/MessageBus.js:96:47)
                    at /home/username/reactor/server/lib/MessageBus.js:109:48
                    at new Promise (<anonymous>)
                    at MessageBus.send (/home/username/reactor/server/lib/MessageBus.js:106:16)
                    at Entity.publish (/home/username/reactor/server/lib/Observable.js:71:44)
                    at Entity.deferNotifies (/home/username/reactor/server/lib/Entity.js:248:207)
                2021-10-04T14:11:03.828Z <Rule:INFO> Tänd i Källaren beroende på Ljus (Rule#rule-kmuwu2tk) RESET!
                2021-10-04T14:11:03.835Z <Engine:5:Engine.js:1386> _process_reaction_queue() wake-up!
                2021-10-04T14:11:03.836Z <Engine:INFO> Enqueueing "Tänd i Källaren beroende på Ljus<RESET>" (rule-kmuwu2tk:R)
                2021-10-04T14:11:03.837Z <Engine:5:Engine.js:1246> Engine#1 enqueued reaction rule-kmuwu2tk:R as 72
                2021-10-04T14:11:03.838Z <Engine:5:Engine.js:1386> _process_reaction_queue() ending with 1 in queue; waiting for 1633356663837<10/4/2021, 4:11:03 PM> (next delayed task)
                2021-10-04T14:11:03.840Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_603a036e129e0715cf4a763a
                2021-10-04T14:11:03.842Z <default:CRIT> Error: Object does not exist
                Error: Object does not exist
                    at Function.getInstance (/home/username/reactor/server/lib/GlobalExpression.js:130:27)
                    at Engine._expr_dependency (/home/username/reactor/server/lib/Engine.js:1109:59)
                    at /home/username/reactor/server/lib/MessageBus.js:99:208
                    at Array.forEach (<anonymous>)
                    at MessageBus._sendToBus (/home/username/reactor/server/lib/MessageBus.js:96:47)
                    at /home/username/reactor/server/lib/MessageBus.js:109:48
                    at new Promise (<anonymous>)
                    at MessageBus.send (/home/username/reactor/server/lib/MessageBus.js:106:16)
                    at Entity.publish (/home/username/reactor/server/lib/Observable.js:71:44)
                    at Entity.deferNotifies (/home/username/reactor/server/lib/Entity.js:248:207)
                2021-10-04T14:11:03.845Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_603a036e129e0715cf4a763a
                2021-10-04T14:11:03.848Z <default:CRIT> Error: Object does not exist
                Error: Object does not exist
                    at Function.getInstance (/home/username/reactor/server/lib/GlobalExpression.js:130:27)
                    at Engine._expr_dependency (/home/username/reactor/server/lib/Engine.js:1109:59)
                    at /home/username/reactor/server/lib/MessageBus.js:99:208
                    at Array.forEach (<anonymous>)
                    at MessageBus._sendToBus (/home/username/reactor/server/lib/MessageBus.js:96:47)
                    at /home/username/reactor/server/lib/MessageBus.js:109:48
                    at new Promise (<anonymous>)
                    at MessageBus.send (/home/username/reactor/server/lib/MessageBus.js:106:16)
                    at Entity.publish (/home/username/reactor/server/lib/Observable.js:71:44)
                    at Entity.deferNotifies (/home/username/reactor/server/lib/Entity.js:248:207)
                2021-10-04T14:11:03.850Z <Engine:5:Engine.js:1386> _process_reaction_queue() wake-up!
                2021-10-04T14:11:03.851Z <Engine:5:Engine.js:1347> _process_reaction_queue() running task 72 { "tid": 72, "id": "rule-kmuwu2tk:R", "rule": "rule-kmuwu2tk", "__reaction": [RuleReaction#rule-kmuwu2tk:R], "next_step": 0, "status": 0, "ts": 1633356663836, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise] }
                2021-10-04T14:11:03.852Z <Engine:NOTICE> Starting reaction Tänd i Källaren beroende på Ljus<RESET> (rule-kmuwu2tk:R)
                2021-10-04T14:11:03.852Z <Engine:5:Engine.js:1416> Engine#1 reaction rule-kmuwu2tk:R handling group rule-kmuwu2tk:R-7pjfxee constraints state true
                2021-10-04T14:11:03.852Z <Engine:5:Engine.js:1418> Engine#1 constraints OK for reaction rule-kmuwu2tk:R group rule-kmuwu2tk:R-7pjfxee, queueing
                2021-10-04T14:11:03.853Z <Engine:5:Engine.js:1430> Engine#1 reaction rule-kmuwu2tk:R group rule-kmuwu2tk:R-7pjfxee enqueued, waiting for completion
                2021-10-04T14:11:03.853Z <Engine:5:Engine.js:1351> _process_reaction_queue() task returned, new status 3; task 72
                2021-10-04T14:11:03.855Z <Engine:5:Engine.js:1246> Engine#1 enqueued reaction rule-kmuwu2tk:R-7pjfxee as 73
                2021-10-04T14:11:03.856Z <Engine:5:Engine.js:1386> _process_reaction_queue() ending with 2 in queue; waiting for 1633356663855<10/4/2021, 4:11:03 PM> (next delayed task)
                2021-10-04T14:11:03.856Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_603a036e129e0715cf4a763a
                2021-10-04T14:11:03.857Z <default:CRIT> Error: Object does not exist
                Error: Object does not exist
                    at Function.getInstance (/home/username/reactor/server/lib/GlobalExpression.js:130:27)
                    at Engine._expr_dependency (/home/username/reactor/server/lib/Engine.js:1109:59)
                    at /home/username/reactor/server/lib/MessageBus.js:99:208
                    at Array.forEach (<anonymous>)
                    at MessageBus._sendToBus (/home/username/reactor/server/lib/MessageBus.js:96:47)
                    at /home/username/reactor/server/lib/MessageBus.js:109:48
                    at new Promise (<anonymous>)
                    at MessageBus.send (/home/username/reactor/server/lib/MessageBus.js:106:16)
                    at Entity.publish (/home/username/reactor/server/lib/Observable.js:71:44)
                    at Entity.deferNotifies (/home/username/reactor/server/lib/Entity.js:248:207)
                2021-10-04T14:11:03.858Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_603a036e129e0715cf4a763a
                2021-10-04T14:11:03.859Z <default:CRIT> Error: Object does not exist
                Error: Object does not exist
                
                1 Reply Last reply
                0
                • toggledbitsT Offline
                  toggledbitsT Offline
                  toggledbits
                  wrote on last edited by
                  #11

                  Is this on 21275?

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

                  CrilleC 1 Reply Last reply
                  0
                  • toggledbitsT toggledbits

                    Is this on 21275?

                    CrilleC Offline
                    CrilleC Offline
                    Crille
                    wrote on last edited by Crille
                    #12

                    @toggledbits Sorry, yes. latest-21275-df3d784

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

                      OK. I think I see this. I was at least able to reproduce one case. It's not to do with deleting global variables, or global variables at all, really; it. It has to do with the subcontexts that are created by lexpjs in each statements, and the MSR Engine looking for private data in the current context and not realizing that it was operating from a subcontext. And in this case, it was your rule expression that exposed the problem. Sounds messy, but not hard to fix. I think.

                      Build coming later today.

                      FYI, just an observation on what you're doing in this rule expression:

                      join(each name in (each id in (matchEntities( { controller: 'ezlo', capability: 'x_ezlo_device' } )):
                          getEntity( id ).attributes.x_ezlo_device.reachable == false ? id : null ):
                              getEntity( name ).name, ', ' )
                      

                      If you use a compound statement (do...done) as the body of a single each loop, and store the getEntity() result in a temporary variable, you only need one loop, it looks a bit cleaner, and runs a lot faster (because you're only fetching the entity once):

                      join( 
                        each id in matchEntities( { controller: 'ezlo', capability: 'x_ezlo_device' } ): do
                          e=getEntity( id ), 
                          e.attributes.x_ezlo_device.reachable ? null : e.name
                        done, ", " )
                      

                      This compound statement loop first stores the result of getEntity() into a variable e. This variable, since it is being defined by the loop, can only be used within the loop. But, as you can see on the next line, it can be used both to make the reachable test, and to return name as the loop body result for each. Also note that since the reachable attribute is already a boolean, you can use it directly (without a comparison against another boolean), you just need to reverse the ternary operands (so when reachable is true, null is returned, and when not reachable, the entity name is returned).

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

                      CrilleC 1 Reply Last reply
                      0
                      • toggledbitsT toggledbits

                        OK. I think I see this. I was at least able to reproduce one case. It's not to do with deleting global variables, or global variables at all, really; it. It has to do with the subcontexts that are created by lexpjs in each statements, and the MSR Engine looking for private data in the current context and not realizing that it was operating from a subcontext. And in this case, it was your rule expression that exposed the problem. Sounds messy, but not hard to fix. I think.

                        Build coming later today.

                        FYI, just an observation on what you're doing in this rule expression:

                        join(each name in (each id in (matchEntities( { controller: 'ezlo', capability: 'x_ezlo_device' } )):
                            getEntity( id ).attributes.x_ezlo_device.reachable == false ? id : null ):
                                getEntity( name ).name, ', ' )
                        

                        If you use a compound statement (do...done) as the body of a single each loop, and store the getEntity() result in a temporary variable, you only need one loop, it looks a bit cleaner, and runs a lot faster (because you're only fetching the entity once):

                        join( 
                          each id in matchEntities( { controller: 'ezlo', capability: 'x_ezlo_device' } ): do
                            e=getEntity( id ), 
                            e.attributes.x_ezlo_device.reachable ? null : e.name
                          done, ", " )
                        

                        This compound statement loop first stores the result of getEntity() into a variable e. This variable, since it is being defined by the loop, can only be used within the loop. But, as you can see on the next line, it can be used both to make the reachable test, and to return name as the loop body result for each. Also note that since the reachable attribute is already a boolean, you can use it directly (without a comparison against another boolean), you just need to reverse the ternary operands (so when reachable is true, null is returned, and when not reachable, the entity name is returned).

                        CrilleC Offline
                        CrilleC Offline
                        Crille
                        wrote on last edited by Crille
                        #14

                        @toggledbits Ok, great explanation!
                        I do like cleaner expressions and will absolutely switch to do...done, thank you for the example.
                        I knew it was doing double gets but each run took 0ms so I did not bother, but optimization is always welcomed.

                        FYI: I have some devices paired that are not usable yet and they return x_ezlo_device.reachable=null so until they are integrated correctly I'll keep the boolean comparison for now.

                        1 Reply Last reply
                        1
                        • N Offline
                          N Offline
                          noelab
                          wrote on last edited by noelab
                          #15

                          Hi, updated MSR latest-21281-c4807c0
                          I have connection with ezloplus in set_anonymous_access: true

                          MSR starts to be connected and disconnected.
                          Ezlo is not connected
                          sys_system.state=false

                          `

                          [latest-21281]2021-10-08T20:29:30.398Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1
                          [latest-21281]2021-10-08T20:29:33.849Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
                          [latest-21281]2021-10-08T20:29:33.850Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
                          [latest-21281]2021-10-08T20:29:33.850Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
                          [latest-21281]2021-10-08T20:29:38.850Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
                          [latest-21281]2021-10-08T20:29:38.851Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
                          [latest-21281]2021-10-08T20:29:38.851Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
                          [latest-21281]2021-10-08T20:29:59.226Z <Structure:WARN> Structure#1 promiseEntity(ezlo>housemode,30000) timeout!
                          [latest-21281]2021-10-08T20:29:59.227Z <Rule:CRIT> Rule#rule-ks210svp failed subscription to ezlo>housemode
                          [latest-21281]2021-10-08T20:29:59.227Z <Rule:CRIT> !timeout
                          [latest-21281]2021-10-08T20:29:59.251Z <Structure:WARN> Structure#1 promiseEntity(ezlo>housemode,30000) timeout!
                          [latest-21281]2021-10-08T20:29:59.251Z <Rule:CRIT> Rule#rule-ks210svp failed subscription to ezlo>housemode
                          [latest-21281]2021-10-08T20:29:59.252Z <Rule:CRIT> !timeout
                          [latest-21281]2021-10-08T20:29:59.252Z <Rule:5:Rule.js:704> Rule#rule-ks210svp start() dependencies resolved, performing initial evaluation
                          [latest-21281]2021-10-08T20:29:59.252Z <Rule:5:Rule.js:982> Rule#rule-ks210svp (v0 Function DayMode OverNight) evaluate() acquiring mutex
                          [latest-21281]2021-10-08T20:29:59.252Z <Rule:5:Rule.js:986> Rule#rule-ks210svp._evaluate() mutex acquired, evaluating
                          [latest-21281]2021-10-08T20:29:59.253Z <Rule:5:Rule.js:990> Rule#rule-ks210svp update rate is 0/min limit 60/min
                          [latest-21281]2021-10-08T20:29:59.253Z <Rule:5:Rule.js:914> Rule#rule-ks210svp evaluateExpressions() with 0 expressions
                          [latest-21281]2021-10-08T20:29:59.254Z <Rule:5:Rule.js:1002> Rule#rule-ks210svp._evaluate() trigger state now false (was false)
                          [latest-21281]2021-10-08T20:29:59.259Z <Rule:CRIT> ReferenceError: Can't find entity ezlo>housemode
                          ReferenceError: Can't find entity ezlo>housemode
                              at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1294:27)
                              at Rule._evaluateGroup (/opt/reactor/server/lib/Rule.js:1658:99)
                              at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1283:47)
                              at Rule._evaluateConstraints (/opt/reactor/server/lib/Rule.js:1689:42)
                              at Rule._evaluate (/opt/reactor/server/lib/Rule.js:1003:55)
                              at processTicksAndRejections (internal/process/task_queues.js:95:5)
                              at async /opt/reactor/server/lib/Rule.js:969:17
                          [latest-21281]2021-10-08T20:29:59.261Z <Structure:WARN> Structure#1 promiseEntity(ezlo>device_613e233f129e2912114c0941,30000) timeout!
                          [latest-21281]2021-10-08T20:29:59.262Z <Rule:CRIT> Rule#rule-ktmit785 failed subscription to ezlo>device_613e233f129e2912114c0941
                          [latest-21281]2021-10-08T20:29:59.262Z <Rule:CRIT> !timeout
                          [latest-21281]2021-10-08T20:29:59.262Z <Rule:5:Rule.js:704> Rule#rule-ktmit785 start() dependencies resolved, performing initial evaluation
                          [latest-21281]2021-10-08T20:29:59.262Z <Rule:5:Rule.js:982> Rule#rule-ktmit785 (vT DLT 1 Bulb ID ) evaluate() acquiring mutex
                          [latest-21281]2021-10-08T20:29:59.263Z <Rule:5:Rule.js:986> Rule#rule-ktmit785._evaluate() mutex acquired, evaluating
                          [latest-21281]2021-10-08T20:29:59.263Z <Rule:5:Rule.js:990> Rule#rule-ktmit785 update rate is 0/min limit 60/min
                          [latest-21281]2021-10-08T20:29:59.263Z <Rule:5:Rule.js:914> Rule#rule-ktmit785 evaluateExpressions() with 0 expressions
                          [latest-21281]2021-10-08T20:29:59.279Z <Rule:CRIT> ReferenceError: Can't find entity ezlo>device_613e233f129e2912114c0941
                          ReferenceError: Can't find entity ezlo>device_613e233f129e2912114c0941
                              at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1294:27)
                              at Rule._evaluateGroup (/opt/reactor/server/lib/Rule.js:1658:99)
                              at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1283:47)
                              at Rule._evaluateTriggers (/opt/reactor/server/lib/Rule.js:1675:38)
                              at Rule._evaluate (/opt/reactor/server/lib/Rule.js:1001:55)
                              at processTicksAndRejections (internal/process/task_queues.js:95:5)
                              at async /opt/reactor/server/lib/Rule.js:969:17
                          [latest-21281]2021-10-08T20:29:59.280Z <Structure:WARN> Structure#1 promiseEntity(ezlo>device_613e2b02129e2912114c0993,30000) timeout!
                          [latest-21281]2021-10-08T20:29:59.280Z <Rule:CRIT> Rule#rule-kthqmgb6 failed subscription to ezlo>device_613e2b02129e2912114c0993
                          [latest-21281]2021-10-08T20:29:59.280Z <Rule:CRIT> !timeout
                          [latest-21281]2021-10-08T20:29:59.280Z <Rule:5:Rule.js:704> Rule#rule-kthqmgb6 start() dependencies resolved, performing initial evaluation
                          [latest-21281]2021-10-08T20:29:59.281Z <Rule:5:Rule.js:982> Rule#rule-kthqmgb6 (vR4 DLT 1 Bulb ID ) evaluate() acquiring mutex
                          [latest-21281]2021-10-08T20:29:59.281Z <Rule:5:Rule.js:986> Rule#rule-kthqmgb6._evaluate() mutex acquired, evaluating
                          [latest-21281]2021-10-08T20:29:59.281Z <Rule:5:Rule.js:990> Rule#rule-kthqmgb6 update rate is 0/min limit 60/min
                          [latest-21281]2021-10-08T20:29:59.282Z <Rule:5:Rule.js:914> Rule#rule-kthqmgb6 evaluateExpressions() with 0 expressions
                          [latest-21281]2021-10-08T20:29:59.284Z <Rule:CRIT> ReferenceError: Can't find entity ezlo>device_613e2b02129e2912114c0993
                          ReferenceError: Can't find entity ezlo>device_613e2b02129e2912114c0993
                              at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1294:27)
                              at Rule._evaluateGroup (/opt/reactor/server/lib/Rule.js:1658:99)
                              at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1283:47)
                              at Rule._evaluateTriggers (/opt/reactor/server/lib/Rule.js:1675:38)
                              at Rule._evaluate (/opt/reactor/server/lib/Rule.js:1001:55)
                              at processTicksAndRejections (internal/process/task_queues.js:95:5)
                              at runNextTicks (internal/process/task_queues.js:64:3)
                              at listOnTimeout (internal/timers.js:526:9)
                              at processTimers (internal/timers.js:500:7)
                              at async /opt/reactor/server/lib/Rule.js:969:17
                          [latest-21281]2021-10-08T20:29:59.285Z <Structure:WARN> Structure#1 promiseEntity(ezlo>device_613e2959129e2912114c098f,30000) timeout!
                          [latest-21281]2021-10-08T20:29:59.285Z <Rule:CRIT> Rule#rule-kthqpda8 failed subscription to ezlo>device_613e2959129e2912114c098f
                          [latest-21281]2021-10-08T20:29:59.286Z <Rule:CRIT> !timeout
                          [latest-21281]2021-10-08T20:29:59.286Z <Rule:5:Rule.js:704> Rule#rule-kthqpda8 start() dependencies resolved, performing initial evaluation
                          [latest-21281]2021-10-08T20:29:59.286Z <Rule:5:Rule.js:982> Rule#rule-kthqpda8 (vR4 DLT 3 Lux ID  ) evaluate() acquiring mutex
                          [latest-21281]2021-10-08T20:29:59.287Z <Rule:5:Rule.js:986> Rule#rule-kthqpda8._evaluate() mutex acquired, evaluating
                          [latest-21281]2021-10-08T20:29:59.287Z <Rule:5:Rule.js:990> Rule#rule-kthqpda8 update rate is 0/min limit 60/min
                          [latest-21281]2021-10-08T20:29:59.287Z <Rule:5:Rule.js:914> Rule#rule-kthqpda8 evaluateExpressions() with 1 expressions
                          [latest-21281]2021-10-08T20:29:59.290Z <Rule:ERR> Rule#rule-kthqpda8: error evaluating expression test: TypeError: Cannot read property 'log' of null
                          [latest-21281]2021-10-08T20:29:59.290Z <Rule:ERR> Rule#rule-kthqpda8: expression: round((abs(int( getEntity( "ezlo>device_613e2959129e2912114c098f" ).attributes.light_sensor.value ) * (100/300) -100) - int((  getEntity( "ezlo>device_613e2959129e2912114c098f" ).attributes.light_sensor.value  * (100/300) ) - 100))/2)
                          [latest-21281]2021-10-08T20:29:59.291Z <Rule:CRIT> TypeError: Cannot read property 'log' of null
                          TypeError: Cannot read property 'log' of null
                              at _0x2f8d77 (/opt/reactor/server/lib/Engine.js:984:21)
                              at _run (/opt/reactor/common/lexp.js:1383:34)
                              at _run (/opt/reactor/common/lexp.js:1338:33)
                              at _run (/opt/reactor/common/lexp.js:1338:33)
                              at _run (/opt/reactor/common/lexp.js:1338:33)
                              at /opt/reactor/common/lexp.js:1381:33
                              at Array.forEach (<anonymous>)
                              at _run (/opt/reactor/common/lexp.js:1380:28)
                              at _run (/opt/reactor/common/lexp.js:1208:34)
                              at _run (/opt/reactor/common/lexp.js:1208:34)
                          [latest-21281]2021-10-08T20:29:59.295Z <Rule:CRIT> ReferenceError: Can't find entity ezlo>device_613e2959129e2912114c098f
                          ReferenceError: Can't find entity ezlo>device_613e2959129e2912114c098f
                              at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1294:27)
                              at Rule._evaluateGroup (/opt/reactor/server/lib/Rule.js:1658:99)
                              at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1283:47)
                              at Rule._evaluateTriggers (/opt/reactor/server/lib/Rule.js:1675:38)
                              at Rule._evaluate (/opt/reactor/server/lib/Rule.js:1001:55)
                              at processTicksAndRejections (internal/process/task_queues.js:95:5)
                              at runNextTicks (internal/process/task_queues.js:64:3)
                              at listOnTimeout (internal/timers.js:526:9)
                              at processTimers (internal/timers.js:500:7)
                              at async /opt/reactor/server/lib/Rule.js:969:17
                          [latest-21281]2021-10-08T20:29:59.296Z <Structure:WARN> Structure#1 promiseEntity(ezlo>device_613e2959129e2912114c0982,30000) timeout!
                          [latest-21281]2021-10-08T20:29:59.296Z <Rule:CRIT> Rule#rule-kthqljcu failed subscription to ezlo>device_613e2959129e2912114c0982
                          [latest-21281]2021-10-08T20:29:59.296Z <Rule:CRIT> !timeout
                          [latest-21281]2021-10-08T20:29:59.296Z <Rule:5:Rule.js:704> Rule#rule-kthqljcu start() dependencies resolved, performing initial evaluation
                          [latest-21281]2021-10-08T20:29:59.297Z <Rule:5:Rule.js:982> Rule#rule-kthqljcu (vR4 DLT 2 Motion ID ) evaluate() acquiring mutex
                          [latest-21281]2021-10-08T20:29:59.297Z <Rule:5:Rule.js:986> Rule#rule-kthqljcu._evaluate() mutex acquired, evaluating
                          [latest-21281]2021-10-08T20:29:59.297Z <Rule:5:Rule.js:990> Rule#rule-kthqljcu update rate is 0/min limit 60/min
                          [latest-21281]2021-10-08T20:29:59.297Z <Rule:5:Rule.js:914> Rule#rule-kthqljcu evaluateExpressions() with 0 expressions
                          [latest-21281]2021-10-08T20:29:59.299Z <Rule:CRIT> ReferenceError: Can't find entity ezlo>device_613e2959129e2912114c0982
                          ReferenceError: Can't find entity ezlo>device_613e2959129e2912114c0982
                              at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1294:27)
                              at Rule._evaluateGroup (/opt/reactor/server/lib/Rule.js:1658:99)
                              at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1283:47)
                              at Rule._evaluateTriggers (/opt/reactor/server/lib/Rule.js:1675:38)
                              at Rule._evaluate (/opt/reactor/server/lib/Rule.js:1001:55)
                              at processTicksAndRejections (internal/process/task_queues.js:95:5)
                              at runNextTicks (internal/process/task_queues.js:64:3)
                              at listOnTimeout (internal/timers.js:526:9)
                              at processTimers (internal/timers.js:500:7)
                              at async /opt/reactor/server/lib/Rule.js:969:17
                          [latest-21281]2021-10-08T20:29:59.300Z <Structure:WARN> Structure#1 promiseEntity(ezlo>device_614e0c2f129e29124dfcd825,30000) timeout!
                          [latest-21281]2021-10-08T20:29:59.300Z <Rule:CRIT> Rule#rule-ktpv9g18 failed subscription to ezlo>device_614e0c2f129e29124dfcd825
                          [latest-21281]2021-10-08T20:29:59.300Z <Rule:CRIT> !timeout
                          [latest-21281]2021-10-08T20:29:59.301Z <Rule:5:Rule.js:704> Rule#rule-ktpv9g18 start() dependencies resolved, performing initial evaluation
                          [latest-21281]2021-10-08T20:29:59.301Z <Rule:5:Rule.js:982> Rule#rule-ktpv9g18 (vR3 DLT 1 Bulb ID) evaluate() acquiring mutex
                          [latest-21281]2021-10-08T20:29:59.301Z <Rule:5:Rule.js:986> Rule#rule-ktpv9g18._evaluate() mutex acquired, evaluating
                          [latest-21281]2021-10-08T20:29:59.301Z <Rule:5:Rule.js:990> Rule#rule-ktpv9g18 update rate is 0/min limit 60/min
                          [latest-21281]2021-10-08T20:29:59.301Z <Rule:5:Rule.js:914> Rule#rule-ktpv9g18 evaluateExpressions() with 0 expressions
                          [latest-21281]2021-10-08T20:29:59.304Z <Rule:CRIT> ReferenceError: Can't find entity ezlo>device_614e0c2f129e29124dfcd825
                          

                          `

                          -Reactor (Multi-hub) 25082-3c348de6
                          -Docker on Synology NAS
                          -Ezlo firmware version 2.0.59.2471.8
                          -HASS Docker 2025.2.5
                          -ZWaveJSUI 10.1.3
                          -Update 30/03/2025

                          N 1 Reply Last reply
                          0
                          • N noelab

                            Hi, updated MSR latest-21281-c4807c0
                            I have connection with ezloplus in set_anonymous_access: true

                            MSR starts to be connected and disconnected.
                            Ezlo is not connected
                            sys_system.state=false

                            `

                            [latest-21281]2021-10-08T20:29:30.398Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1
                            [latest-21281]2021-10-08T20:29:33.849Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
                            [latest-21281]2021-10-08T20:29:33.850Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
                            [latest-21281]2021-10-08T20:29:33.850Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
                            [latest-21281]2021-10-08T20:29:38.850Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
                            [latest-21281]2021-10-08T20:29:38.851Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:29:38.851Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:29:59.226Z <Structure:WARN> Structure#1 promiseEntity(ezlo>housemode,30000) timeout!
                            [latest-21281]2021-10-08T20:29:59.227Z <Rule:CRIT> Rule#rule-ks210svp failed subscription to ezlo>housemode
                            [latest-21281]2021-10-08T20:29:59.227Z <Rule:CRIT> !timeout
                            [latest-21281]2021-10-08T20:29:59.251Z <Structure:WARN> Structure#1 promiseEntity(ezlo>housemode,30000) timeout!
                            [latest-21281]2021-10-08T20:29:59.251Z <Rule:CRIT> Rule#rule-ks210svp failed subscription to ezlo>housemode
                            [latest-21281]2021-10-08T20:29:59.252Z <Rule:CRIT> !timeout
                            [latest-21281]2021-10-08T20:29:59.252Z <Rule:5:Rule.js:704> Rule#rule-ks210svp start() dependencies resolved, performing initial evaluation
                            [latest-21281]2021-10-08T20:29:59.252Z <Rule:5:Rule.js:982> Rule#rule-ks210svp (v0 Function DayMode OverNight) evaluate() acquiring mutex
                            [latest-21281]2021-10-08T20:29:59.252Z <Rule:5:Rule.js:986> Rule#rule-ks210svp._evaluate() mutex acquired, evaluating
                            [latest-21281]2021-10-08T20:29:59.253Z <Rule:5:Rule.js:990> Rule#rule-ks210svp update rate is 0/min limit 60/min
                            [latest-21281]2021-10-08T20:29:59.253Z <Rule:5:Rule.js:914> Rule#rule-ks210svp evaluateExpressions() with 0 expressions
                            [latest-21281]2021-10-08T20:29:59.254Z <Rule:5:Rule.js:1002> Rule#rule-ks210svp._evaluate() trigger state now false (was false)
                            [latest-21281]2021-10-08T20:29:59.259Z <Rule:CRIT> ReferenceError: Can't find entity ezlo>housemode
                            ReferenceError: Can't find entity ezlo>housemode
                                at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1294:27)
                                at Rule._evaluateGroup (/opt/reactor/server/lib/Rule.js:1658:99)
                                at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1283:47)
                                at Rule._evaluateConstraints (/opt/reactor/server/lib/Rule.js:1689:42)
                                at Rule._evaluate (/opt/reactor/server/lib/Rule.js:1003:55)
                                at processTicksAndRejections (internal/process/task_queues.js:95:5)
                                at async /opt/reactor/server/lib/Rule.js:969:17
                            [latest-21281]2021-10-08T20:29:59.261Z <Structure:WARN> Structure#1 promiseEntity(ezlo>device_613e233f129e2912114c0941,30000) timeout!
                            [latest-21281]2021-10-08T20:29:59.262Z <Rule:CRIT> Rule#rule-ktmit785 failed subscription to ezlo>device_613e233f129e2912114c0941
                            [latest-21281]2021-10-08T20:29:59.262Z <Rule:CRIT> !timeout
                            [latest-21281]2021-10-08T20:29:59.262Z <Rule:5:Rule.js:704> Rule#rule-ktmit785 start() dependencies resolved, performing initial evaluation
                            [latest-21281]2021-10-08T20:29:59.262Z <Rule:5:Rule.js:982> Rule#rule-ktmit785 (vT DLT 1 Bulb ID ) evaluate() acquiring mutex
                            [latest-21281]2021-10-08T20:29:59.263Z <Rule:5:Rule.js:986> Rule#rule-ktmit785._evaluate() mutex acquired, evaluating
                            [latest-21281]2021-10-08T20:29:59.263Z <Rule:5:Rule.js:990> Rule#rule-ktmit785 update rate is 0/min limit 60/min
                            [latest-21281]2021-10-08T20:29:59.263Z <Rule:5:Rule.js:914> Rule#rule-ktmit785 evaluateExpressions() with 0 expressions
                            [latest-21281]2021-10-08T20:29:59.279Z <Rule:CRIT> ReferenceError: Can't find entity ezlo>device_613e233f129e2912114c0941
                            ReferenceError: Can't find entity ezlo>device_613e233f129e2912114c0941
                                at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1294:27)
                                at Rule._evaluateGroup (/opt/reactor/server/lib/Rule.js:1658:99)
                                at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1283:47)
                                at Rule._evaluateTriggers (/opt/reactor/server/lib/Rule.js:1675:38)
                                at Rule._evaluate (/opt/reactor/server/lib/Rule.js:1001:55)
                                at processTicksAndRejections (internal/process/task_queues.js:95:5)
                                at async /opt/reactor/server/lib/Rule.js:969:17
                            [latest-21281]2021-10-08T20:29:59.280Z <Structure:WARN> Structure#1 promiseEntity(ezlo>device_613e2b02129e2912114c0993,30000) timeout!
                            [latest-21281]2021-10-08T20:29:59.280Z <Rule:CRIT> Rule#rule-kthqmgb6 failed subscription to ezlo>device_613e2b02129e2912114c0993
                            [latest-21281]2021-10-08T20:29:59.280Z <Rule:CRIT> !timeout
                            [latest-21281]2021-10-08T20:29:59.280Z <Rule:5:Rule.js:704> Rule#rule-kthqmgb6 start() dependencies resolved, performing initial evaluation
                            [latest-21281]2021-10-08T20:29:59.281Z <Rule:5:Rule.js:982> Rule#rule-kthqmgb6 (vR4 DLT 1 Bulb ID ) evaluate() acquiring mutex
                            [latest-21281]2021-10-08T20:29:59.281Z <Rule:5:Rule.js:986> Rule#rule-kthqmgb6._evaluate() mutex acquired, evaluating
                            [latest-21281]2021-10-08T20:29:59.281Z <Rule:5:Rule.js:990> Rule#rule-kthqmgb6 update rate is 0/min limit 60/min
                            [latest-21281]2021-10-08T20:29:59.282Z <Rule:5:Rule.js:914> Rule#rule-kthqmgb6 evaluateExpressions() with 0 expressions
                            [latest-21281]2021-10-08T20:29:59.284Z <Rule:CRIT> ReferenceError: Can't find entity ezlo>device_613e2b02129e2912114c0993
                            ReferenceError: Can't find entity ezlo>device_613e2b02129e2912114c0993
                                at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1294:27)
                                at Rule._evaluateGroup (/opt/reactor/server/lib/Rule.js:1658:99)
                                at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1283:47)
                                at Rule._evaluateTriggers (/opt/reactor/server/lib/Rule.js:1675:38)
                                at Rule._evaluate (/opt/reactor/server/lib/Rule.js:1001:55)
                                at processTicksAndRejections (internal/process/task_queues.js:95:5)
                                at runNextTicks (internal/process/task_queues.js:64:3)
                                at listOnTimeout (internal/timers.js:526:9)
                                at processTimers (internal/timers.js:500:7)
                                at async /opt/reactor/server/lib/Rule.js:969:17
                            [latest-21281]2021-10-08T20:29:59.285Z <Structure:WARN> Structure#1 promiseEntity(ezlo>device_613e2959129e2912114c098f,30000) timeout!
                            [latest-21281]2021-10-08T20:29:59.285Z <Rule:CRIT> Rule#rule-kthqpda8 failed subscription to ezlo>device_613e2959129e2912114c098f
                            [latest-21281]2021-10-08T20:29:59.286Z <Rule:CRIT> !timeout
                            [latest-21281]2021-10-08T20:29:59.286Z <Rule:5:Rule.js:704> Rule#rule-kthqpda8 start() dependencies resolved, performing initial evaluation
                            [latest-21281]2021-10-08T20:29:59.286Z <Rule:5:Rule.js:982> Rule#rule-kthqpda8 (vR4 DLT 3 Lux ID  ) evaluate() acquiring mutex
                            [latest-21281]2021-10-08T20:29:59.287Z <Rule:5:Rule.js:986> Rule#rule-kthqpda8._evaluate() mutex acquired, evaluating
                            [latest-21281]2021-10-08T20:29:59.287Z <Rule:5:Rule.js:990> Rule#rule-kthqpda8 update rate is 0/min limit 60/min
                            [latest-21281]2021-10-08T20:29:59.287Z <Rule:5:Rule.js:914> Rule#rule-kthqpda8 evaluateExpressions() with 1 expressions
                            [latest-21281]2021-10-08T20:29:59.290Z <Rule:ERR> Rule#rule-kthqpda8: error evaluating expression test: TypeError: Cannot read property 'log' of null
                            [latest-21281]2021-10-08T20:29:59.290Z <Rule:ERR> Rule#rule-kthqpda8: expression: round((abs(int( getEntity( "ezlo>device_613e2959129e2912114c098f" ).attributes.light_sensor.value ) * (100/300) -100) - int((  getEntity( "ezlo>device_613e2959129e2912114c098f" ).attributes.light_sensor.value  * (100/300) ) - 100))/2)
                            [latest-21281]2021-10-08T20:29:59.291Z <Rule:CRIT> TypeError: Cannot read property 'log' of null
                            TypeError: Cannot read property 'log' of null
                                at _0x2f8d77 (/opt/reactor/server/lib/Engine.js:984:21)
                                at _run (/opt/reactor/common/lexp.js:1383:34)
                                at _run (/opt/reactor/common/lexp.js:1338:33)
                                at _run (/opt/reactor/common/lexp.js:1338:33)
                                at _run (/opt/reactor/common/lexp.js:1338:33)
                                at /opt/reactor/common/lexp.js:1381:33
                                at Array.forEach (<anonymous>)
                                at _run (/opt/reactor/common/lexp.js:1380:28)
                                at _run (/opt/reactor/common/lexp.js:1208:34)
                                at _run (/opt/reactor/common/lexp.js:1208:34)
                            [latest-21281]2021-10-08T20:29:59.295Z <Rule:CRIT> ReferenceError: Can't find entity ezlo>device_613e2959129e2912114c098f
                            ReferenceError: Can't find entity ezlo>device_613e2959129e2912114c098f
                                at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1294:27)
                                at Rule._evaluateGroup (/opt/reactor/server/lib/Rule.js:1658:99)
                                at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1283:47)
                                at Rule._evaluateTriggers (/opt/reactor/server/lib/Rule.js:1675:38)
                                at Rule._evaluate (/opt/reactor/server/lib/Rule.js:1001:55)
                                at processTicksAndRejections (internal/process/task_queues.js:95:5)
                                at runNextTicks (internal/process/task_queues.js:64:3)
                                at listOnTimeout (internal/timers.js:526:9)
                                at processTimers (internal/timers.js:500:7)
                                at async /opt/reactor/server/lib/Rule.js:969:17
                            [latest-21281]2021-10-08T20:29:59.296Z <Structure:WARN> Structure#1 promiseEntity(ezlo>device_613e2959129e2912114c0982,30000) timeout!
                            [latest-21281]2021-10-08T20:29:59.296Z <Rule:CRIT> Rule#rule-kthqljcu failed subscription to ezlo>device_613e2959129e2912114c0982
                            [latest-21281]2021-10-08T20:29:59.296Z <Rule:CRIT> !timeout
                            [latest-21281]2021-10-08T20:29:59.296Z <Rule:5:Rule.js:704> Rule#rule-kthqljcu start() dependencies resolved, performing initial evaluation
                            [latest-21281]2021-10-08T20:29:59.297Z <Rule:5:Rule.js:982> Rule#rule-kthqljcu (vR4 DLT 2 Motion ID ) evaluate() acquiring mutex
                            [latest-21281]2021-10-08T20:29:59.297Z <Rule:5:Rule.js:986> Rule#rule-kthqljcu._evaluate() mutex acquired, evaluating
                            [latest-21281]2021-10-08T20:29:59.297Z <Rule:5:Rule.js:990> Rule#rule-kthqljcu update rate is 0/min limit 60/min
                            [latest-21281]2021-10-08T20:29:59.297Z <Rule:5:Rule.js:914> Rule#rule-kthqljcu evaluateExpressions() with 0 expressions
                            [latest-21281]2021-10-08T20:29:59.299Z <Rule:CRIT> ReferenceError: Can't find entity ezlo>device_613e2959129e2912114c0982
                            ReferenceError: Can't find entity ezlo>device_613e2959129e2912114c0982
                                at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1294:27)
                                at Rule._evaluateGroup (/opt/reactor/server/lib/Rule.js:1658:99)
                                at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1283:47)
                                at Rule._evaluateTriggers (/opt/reactor/server/lib/Rule.js:1675:38)
                                at Rule._evaluate (/opt/reactor/server/lib/Rule.js:1001:55)
                                at processTicksAndRejections (internal/process/task_queues.js:95:5)
                                at runNextTicks (internal/process/task_queues.js:64:3)
                                at listOnTimeout (internal/timers.js:526:9)
                                at processTimers (internal/timers.js:500:7)
                                at async /opt/reactor/server/lib/Rule.js:969:17
                            [latest-21281]2021-10-08T20:29:59.300Z <Structure:WARN> Structure#1 promiseEntity(ezlo>device_614e0c2f129e29124dfcd825,30000) timeout!
                            [latest-21281]2021-10-08T20:29:59.300Z <Rule:CRIT> Rule#rule-ktpv9g18 failed subscription to ezlo>device_614e0c2f129e29124dfcd825
                            [latest-21281]2021-10-08T20:29:59.300Z <Rule:CRIT> !timeout
                            [latest-21281]2021-10-08T20:29:59.301Z <Rule:5:Rule.js:704> Rule#rule-ktpv9g18 start() dependencies resolved, performing initial evaluation
                            [latest-21281]2021-10-08T20:29:59.301Z <Rule:5:Rule.js:982> Rule#rule-ktpv9g18 (vR3 DLT 1 Bulb ID) evaluate() acquiring mutex
                            [latest-21281]2021-10-08T20:29:59.301Z <Rule:5:Rule.js:986> Rule#rule-ktpv9g18._evaluate() mutex acquired, evaluating
                            [latest-21281]2021-10-08T20:29:59.301Z <Rule:5:Rule.js:990> Rule#rule-ktpv9g18 update rate is 0/min limit 60/min
                            [latest-21281]2021-10-08T20:29:59.301Z <Rule:5:Rule.js:914> Rule#rule-ktpv9g18 evaluateExpressions() with 0 expressions
                            [latest-21281]2021-10-08T20:29:59.304Z <Rule:CRIT> ReferenceError: Can't find entity ezlo>device_614e0c2f129e29124dfcd825
                            

                            `

                            N Offline
                            N Offline
                            noelab
                            wrote on last edited by
                            #16

                            @noelab

                            [latest-21281]2021-10-08T20:37:59.635Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
                            [latest-21281]2021-10-08T20:38:06.565Z <Rule:5:Rule.js:763> Rule#rule-ks56pa4y dependency notification timer-trigger Timer#rule-ks56pa4y from Timer#rule-ks56pa4y
                            [latest-21281]2021-10-08T20:38:06.566Z <Rule:5:Rule.js:769> Rule#rule-ks56pa4y requesting eval; timer-trigger Timer#rule-ks56pa4y
                            [latest-21281]2021-10-08T20:38:06.566Z <Rule:5:Rule.js:982> Rule#rule-ks56pa4y (vK DLT 8 Delay OFF ) evaluate() acquiring mutex
                            [latest-21281]2021-10-08T20:38:06.569Z <Rule:5:Rule.js:986> Rule#rule-ks56pa4y._evaluate() mutex acquired, evaluating
                            [latest-21281]2021-10-08T20:38:06.570Z <Rule:5:Rule.js:990> Rule#rule-ks56pa4y update rate is 0/min limit 60/min
                            [latest-21281]2021-10-08T20:38:06.570Z <Rule:5:Rule.js:914> Rule#rule-ks56pa4y evaluateExpressions() with 0 expressions
                            [latest-21281]2021-10-08T20:38:06.571Z <Rule:5:Rule.js:1650> cond condcxc7czr evaluation state false->true
                            [latest-21281]2021-10-08T20:38:06.576Z <Rule:5:Rule.js:1002> Rule#rule-ks56pa4y._evaluate() trigger state now false (was false)
                            [latest-21281]2021-10-08T20:38:06.576Z <Rule:5:Rule.js:1004> Rule#rule-ks56pa4y._evaluate() constraints state true
                            [latest-21281]2021-10-08T20:38:06.576Z <Rule:5:Rule.js:1013> Rule#rule-ks56pa4y rule state now false, changed no
                            [latest-21281]2021-10-08T20:38:07.815Z <Rule:5:Rule.js:763> Rule#rule-ktrefqfy dependency notification timer-trigger Timer#rule-ktrefqfy from Timer#rule-ktrefqfy
                            [latest-21281]2021-10-08T20:38:07.815Z <Rule:5:Rule.js:769> Rule#rule-ktrefqfy requesting eval; timer-trigger Timer#rule-ktrefqfy
                            [latest-21281]2021-10-08T20:38:07.816Z <Rule:5:Rule.js:982> Rule#rule-ktrefqfy (vH DLT 8 Delay OFF  ) evaluate() acquiring mutex
                            [latest-21281]2021-10-08T20:38:07.816Z <Rule:5:Rule.js:986> Rule#rule-ktrefqfy._evaluate() mutex acquired, evaluating
                            [latest-21281]2021-10-08T20:38:07.816Z <Rule:5:Rule.js:990> Rule#rule-ktrefqfy update rate is 0/min limit 60/min
                            [latest-21281]2021-10-08T20:38:07.816Z <Rule:5:Rule.js:914> Rule#rule-ktrefqfy evaluateExpressions() with 0 expressions
                            [latest-21281]2021-10-08T20:38:07.817Z <Rule:5:Rule.js:1650> cond condcxc7czr evaluation state false->true
                            [latest-21281]2021-10-08T20:38:07.818Z <Rule:5:Rule.js:1002> Rule#rule-ktrefqfy._evaluate() trigger state now false (was false)
                            [latest-21281]2021-10-08T20:38:07.818Z <Rule:5:Rule.js:1004> Rule#rule-ktrefqfy._evaluate() constraints state true
                            [latest-21281]2021-10-08T20:38:07.818Z <Rule:5:Rule.js:1013> Rule#rule-ktrefqfy rule state now false, changed no
                            [latest-21281]2021-10-08T20:38:19.635Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
                            [latest-21281]2021-10-08T20:38:19.636Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:38:19.636Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:38:28.614Z <wsapi:WARN> wsapi: timed out waiting for ping reply (pong) from client "172.17.0.1#4"
                            [latest-21281]2021-10-08T20:38:28.615Z <wsapi:INFO> client "172.17.0.1#4" closed, code=1006, reason=
                            [latest-21281]2021-10-08T20:38:49.688Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
                            [latest-21281]2021-10-08T20:38:49.688Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
                            [latest-21281]2021-10-08T20:38:49.688Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
                            [latest-21281]2021-10-08T20:38:54.226Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1
                            [latest-21281]2021-10-08T20:39:14.695Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
                            [latest-21281]2021-10-08T20:39:14.695Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:39:14.696Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:39:44.747Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
                            [latest-21281]2021-10-08T20:39:44.747Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
                            [latest-21281]2021-10-08T20:39:44.748Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
                            [latest-21281]2021-10-08T20:40:14.758Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
                            [latest-21281]2021-10-08T20:40:14.758Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:40:14.759Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:40:44.809Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
                            [latest-21281]2021-10-08T20:40:44.810Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
                            [latest-21281]2021-10-08T20:40:44.810Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
                            [latest-21281]2021-10-08T20:41:19.824Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
                            [latest-21281]2021-10-08T20:41:19.824Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:41:19.825Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:41:39.101Z <wsapi:WARN> wsapi: timed out waiting for ping reply (pong) from client "172.17.0.1#5"
                            [latest-21281]2021-10-08T20:41:39.102Z <wsapi:INFO> client "172.17.0.1#5" closed, code=1006, reason=
                            [latest-21281]2021-10-08T20:41:49.876Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
                            [latest-21281]2021-10-08T20:41:49.876Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
                            [latest-21281]2021-10-08T20:41:49.876Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
                            [latest-21281]2021-10-08T20:42:29.878Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
                            [latest-21281]2021-10-08T20:42:29.879Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:42:29.879Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:42:59.931Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
                            [latest-21281]2021-10-08T20:42:59.931Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
                            [latest-21281]2021-10-08T20:42:59.931Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
                            [latest-21281]2021-10-08T20:43:44.942Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
                            [latest-21281]2021-10-08T20:43:44.942Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:43:44.943Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:44:14.994Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
                            [latest-21281]2021-10-08T20:44:14.994Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
                            [latest-21281]2021-10-08T20:44:14.994Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
                            [latest-21281]2021-10-08T20:44:33.693Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1
                            [latest-21281]2021-10-08T20:44:35.025Z <wsapi:INFO> client "172.17.0.1#6" closed, code=1001, reason=
                            [latest-21281]2021-10-08T20:44:54.281Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1
                            [latest-21281]2021-10-08T20:45:04.999Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
                            [latest-21281]2021-10-08T20:45:04.999Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:45:05.000Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:45:35.050Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
                            [latest-21281]2021-10-08T20:45:35.051Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
                            [latest-21281]2021-10-08T20:45:35.051Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
                            [latest-21281]2021-10-08T20:46:30.052Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
                            [latest-21281]2021-10-08T20:46:30.052Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:46:30.053Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:46:34.315Z <wsapi:WARN> wsapi: timed out waiting for ping reply (pong) from client "172.17.0.1#7"
                            [latest-21281]2021-10-08T20:46:34.316Z <wsapi:INFO> client "172.17.0.1#7" closed, code=1006, reason=
                            [latest-21281]2021-10-08T20:46:46.206Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1
                            [latest-21281]2021-10-08T20:47:00.103Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
                            [latest-21281]2021-10-08T20:47:00.103Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
                            [latest-21281]2021-10-08T20:47:00.104Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
                            [latest-21281]2021-10-08T20:47:11.581Z <wsapi:INFO> client "172.17.0.1#8" closed, code=1005, reason=
                            [latest-21281]2021-10-08T20:47:14.206Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1
                            [latest-21281]2021-10-08T20:48:00.114Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
                            [latest-21281]2021-10-08T20:48:00.115Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:48:00.115Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:48:30.167Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
                            [latest-21281]2021-10-08T20:48:30.167Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
                            [latest-21281]2021-10-08T20:48:30.168Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
                            [latest-21281]2021-10-08T20:49:30.169Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
                            [latest-21281]2021-10-08T20:49:30.169Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:49:30.170Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:50:00.221Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
                            [latest-21281]2021-10-08T20:50:00.221Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
                            [latest-21281]2021-10-08T20:50:00.221Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
                            [latest-21281]2021-10-08T20:50:24.385Z <wsapi:WARN> wsapi: timed out waiting for ping reply (pong) from client "172.17.0.1#9"
                            [latest-21281]2021-10-08T20:50:24.386Z <wsapi:INFO> client "172.17.0.1#9" closed, code=1006, reason=
                            [latest-21281]2021-10-08T20:50:27.211Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1
                            [latest-21281]2021-10-08T20:51:00.225Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
                            [latest-21281]2021-10-08T20:51:00.225Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:51:00.226Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:51:22.359Z <wsapi:INFO> client "172.17.0.1#10" closed, code=1001, reason=
                            [latest-21281]2021-10-08T20:51:22.848Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1
                            [latest-21281]2021-10-08T20:51:30.276Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
                            [latest-21281]2021-10-08T20:51:30.277Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
                            [latest-21281]2021-10-08T20:51:30.277Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
                            [latest-21281]2021-10-08T20:52:30.279Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
                            [latest-21281]2021-10-08T20:52:30.279Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:52:30.280Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:53:00.331Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
                            [latest-21281]2021-10-08T20:53:00.331Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
                            [latest-21281]2021-10-08T20:53:00.331Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
                            [latest-21281]2021-10-08T20:54:00.338Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
                            [latest-21281]2021-10-08T20:54:00.338Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:54:00.339Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
                            [latest-21281]2021-10-08T20:54:30.006Z <Rule:5:Rule.js:763> Rule#rule-ktggia4q dependency notification entity-changed Entity#vera>device_719 from Entity#vera>device_719
                            [latest-21281]2021-10-08T20:54:30.007Z <Rule:5:Rule.js:769> Rule#rule-ktggia4q requesting eval; entity-changed Entity#vera>device_719
                            [latest-21281]2021-10-08T20:54:30.007Z <Rule:5:Rule.js:982> Rule#rule-ktggia4q (vB2 DLT 2 Motion ID) evaluate() acquiring mutex
                            [latest-21281]2021-10-08T20:54:30.008Z <Rule:5:Rule.js:986> Rule#rule-ktggia4q._evaluate() mutex acquired, evaluating
                            [latest-21281]2021-10-08T20:54:30.008Z <Rule:5:Rule.js:990> Rule#rule-ktggia4q update rate is 0/min limit 60/min
                            [latest-21281]2021-10-08T20:54:30.008Z <Rule:5:Rule.js:914> Rule#rule-ktggia4q evaluateExpressions() with 0 expressions
                            [latest-21281]2021-10-08T20:54:30.009Z <Rule:5:Rule.js:1002> Rule#rule-ktggia4q._evaluate() trigger state now false (was false)
                            [latest-21281]2021-10-08T20:54:30.009Z <Rule:5:Rule.js:1004> Rule#rule-ktggia4q._evaluate() constraints state true
                            [latest-21281]2021-10-08T20:54:30.009Z <Rule:5:Rule.js:1013> Rule#rule-ktggia4q rule state now false, changed no
                            [latest-21281]2021-10-08T20:54:30.389Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
                            [latest-21281]2021-10-08T20:54:30.390Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
                            [latest-21281]2021-10-08T20:54:30.390Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
                            
                            

                            -Reactor (Multi-hub) 25082-3c348de6
                            -Docker on Synology NAS
                            -Ezlo firmware version 2.0.59.2471.8
                            -HASS Docker 2025.2.5
                            -ZWaveJSUI 10.1.3
                            -Update 30/03/2025

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

                              No changes to EzloController for several builds now. Mine is working great.

                              What's your install environment?

                              Log snippets need several dozen lines before the error in order to be useful. For controller connection issues, it's also good to capture the entire startup until a bit past the first connection failure.

                              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
                              • N Offline
                                N Offline
                                noelab
                                wrote on last edited by toggledbits
                                #18

                                It's Docker on Synology

                                [latest-21281]2021-10-08T21:17:51.677Z <app:null> Reactor latest-21281-c4807c0 starting on v14.17.3
                                [latest-21281]2021-10-08T21:17:51.678Z <app:INFO> Process ID 1; platform linux/x64 #41890 SMP Thu Jul 15 03:37:40 CST 2021; locale (undefined)
                                [latest-21281]2021-10-08T21:17:51.678Z <app:INFO> Basedir /opt/reactor; data in /var/reactor/storage
                                [latest-21281]2021-10-08T21:17:51.679Z <app:INFO> NODE_PATH /opt/reactor
                                [latest-21281]2021-10-08T21:17:51.691Z <app:INFO> Configured locale (undefined); selected locale(s) en-US.UTF-8
                                [latest-21281]2021-10-08T21:17:51.746Z <app:INFO> Loaded locale en-US
                                [latest-21281]2021-10-08T21:17:51.880Z <Plugin:null> Module Plugin v21173
                                [latest-21281]2021-10-08T21:17:51.888Z <default:INFO> Module Entity v21260
                                [latest-21281]2021-10-08T21:17:51.891Z <Controller:null> Module Controller v21278
                                [latest-21281]2021-10-08T21:17:51.891Z <default:null> Module Structure v21270
                                [latest-21281]2021-10-08T21:17:51.900Z <default:null> Module Ruleset v21096
                                [latest-21281]2021-10-08T21:17:51.900Z <default:null> Module Rulesets v21096
                                [latest-21281]2021-10-08T21:17:51.922Z <default:null> Module Rule v21278
                                [latest-21281]2021-10-08T21:17:51.978Z <default:null> Module Engine v21277
                                [latest-21281]2021-10-08T21:17:51.978Z <default:null> Module httpapi v21278
                                [latest-21281]2021-10-08T21:17:51.987Z <default:null> Module httpproxy v21054
                                [latest-21281]2021-10-08T21:17:52.004Z <default:null> Module wsapi v21274
                                [latest-21281]2021-10-08T21:17:52.075Z <app:NOTICE> Starting Structure...
                                [latest-21281]2021-10-08T21:17:52.079Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping
                                [latest-21281]2021-10-08T21:17:52.081Z <Structure:INFO> Structure#1 starting controller interface vera (VeraController)
                                [latest-21281]2021-10-08T21:17:52.085Z <Structure:INFO> Structure#1 starting controller interface ezlo (EzloController)
                                [latest-21281]2021-10-08T21:17:52.086Z <Structure:INFO> Structure#1 starting controller interface weather (OWMWeatherController)
                                [latest-21281]2021-10-08T21:17:52.087Z <Structure:INFO> Structure#1 starting controller interface reactor_system (SystemController)
                                [latest-21281]2021-10-08T21:17:52.173Z <default:null> Module VeraController v21271
                                [latest-21281]2021-10-08T21:17:52.180Z <default:null> Module EzloController v21274
                                [latest-21281]2021-10-08T21:17:52.183Z <default:null> Module OWMWeatherController v21278
                                [latest-21281]2021-10-08T21:17:52.184Z <default:null> Module SystemController v21102
                                [latest-21281]2021-10-08T21:17:52.192Z <VeraController:NOTICE> VeraController#vera starting
                                [latest-21281]2021-10-08T21:17:52.246Z <VeraController:INFO> VeraController#vera loaded mapping ver 21274 rev 1 format 1 notice 
                                [latest-21281]2021-10-08T21:17:52.247Z <VeraController:INFO> VeraController: deviceclass vera_system_object capability sys_system does not provide attribute state
                                [latest-21281]2021-10-08T21:17:52.295Z <EzloController:null> EzloController#ezlo created, config { "source": "wss://10.0.4.119:17000", "serial": "XXXXXXXXXX" }
                                [latest-21281]2021-10-08T21:17:52.295Z <EzloController:null> EzloController#ezlo instance log level (null) (4)
                                [latest-21281]2021-10-08T21:17:52.314Z <Controller:INFO> EzloController#ezlo device mapping data loaded; checking...
                                [latest-21281]2021-10-08T21:17:52.316Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
                                [latest-21281]2021-10-08T21:17:52.346Z <Controller:NOTICE> Controller SystemController#reactor_system is now online.
                                [latest-21281]2021-10-08T21:17:52.374Z <Controller:INFO> EzloController#ezlo opening hub connection to "XXXXXXXXXX" at wss://10.0.4.119:17000
                                [latest-21281]2021-10-08T21:17:52.376Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
                                [latest-21281]2021-10-08T21:17:52.381Z <app:INFO> Structure running; pausing for controllers' initial ready
                                [latest-21281]2021-10-08T21:17:52.632Z <OWMWeatherController:INFO> OWMWeatherController#weather done; 1 locations, 0 failed
                                [latest-21281]2021-10-08T21:17:52.634Z <OWMWeatherController:NOTICE> Controller OWMWeatherController#weather is now online.
                                [latest-21281]2021-10-08T21:17:53.307Z <VeraController:NOTICE> Controller VeraController#vera is now online.
                                [latest-21281]2021-10-08T21:18:22.427Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
                                [latest-21281]2021-10-08T21:18:22.428Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
                                [latest-21281]2021-10-08T21:18:22.429Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
                                [latest-21281]2021-10-08T21:18:27.433Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
                                [latest-21281]2021-10-08T21:18:27.433Z <Controller:INFO> EzloController#ezlo opening hub connection to "XXXXXXXXXX" at wss://10.0.4.119:17000
                                [latest-21281]2021-10-08T21:18:27.434Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
                                [latest-21281]2021-10-08T21:18:52.386Z <app:NOTICE> Starting HTTP server and API...
                                [latest-21281]2021-10-08T21:18:52.392Z <app:NOTICE> Starting Reaction Engine...
                                [latest-21281]2021-10-08T21:18:52.393Z <Engine:INFO> Reaction Engine starting
                                [latest-21281]2021-10-08T21:18:52.393Z <Engine:INFO> Checking rule sets...
                                [latest-21281]2021-10-08T21:18:52.445Z <Engine:INFO> Checking rules...
                                [latest-21281]2021-10-08T21:18:52.446Z <Engine:INFO> Data check complete; no corrections.
                                [latest-21281]2021-10-08T21:18:52.485Z <Engine:5:Engine.js:1350> _process_reaction_queue() entry 630
                                [latest-21281]2021-10-08T21:18:52.500Z <Rule:5:Rule.js:623> Rule#rule-kuhickgs cleaning loaded condition states
                                [latest-21281]2021-10-08T21:18:52.501Z <Engine:5:Engine.js:886> Engine: new rule rule-kuhickgs ((undefined)), creating!
                                [latest-21281]2021-10-08T21:18:52.522Z <Rule:5:Rule.js:623> Rule#rule-ku1myjlz cleaning loaded condition states
                                [latest-21281]2021-10-08T21:18:52.522Z <Engine:5:Engine.js:886> Engine: new rule rule-ku1myjlz ((undefined)), creating!
                                [latest-21281]2021-10-08T21:18:52.534Z <Rule:5:Rule.js:623> Rule#rule-ks5pci0k cleaning loaded condition states
                                [latest-21281]2021-10-08T21:18:52.534Z <Engine:5:Engine.js:886> Engine: new rule rule-ks5pci0k ((undefined)), creating!
                                [latest-21281]2021-10-08T21:18:52.536Z <Rule:5:Rule.js:623> Rule#rule-ks5pdqcs cleaning loaded condition states
                                [latest-21281]2021-10-08T21:18:52.536Z <Engine:5:Engine.js:886> Engine: new rule rule-ks5pdqcs ((undefined)), creating!
                                [latest-21281]2021-10-08T21:18:52.537Z <Rule:5:Rule.js:623> Rule#rule-ks5pbeg9 cleaning loaded condition states
                                [latest-21281]2021-10-08T21:18:52.538Z <Engine:5:Engine.js:886> Engine: new rule rule-ks5pbeg9 ((undefined)), creating!
                                [latest-21281]2021-10-08T21:18:52.539Z <Rule:5:Rule.js:623> Rule#rule-ks5p8t6m cleaning loaded condition states
                                [latest-21281]2021-10-08T21:18:52.539Z <Engine:5:Engine.js:886> Engine: new rule rule-ks5p8t6m ((undefined)), creating!
                                [latest-21281]2021-10-08T21:18:52.540Z <Rule:5:Rule.js:623> Rule#rule-ks3j24qn cleaning loaded condition states
                                [latest-21281]2021-10-08T21:18:52.541Z <Engine:5:Engine.js:886> Engine: new rule rule-ks3j24qn ((undefined)), creating!
                                [latest-21281]2021-10-08T21:18:52.549Z <Rule:5:Rule.js:623> Rule#rule-ktrlog1t cleaning loaded condition states
                                [latest-21281]2021-10-08T21:18:52.549Z <Engine:5:Engine.js:886> Engine: new rule rule-ktrlog1t ((undefined)), creating!
                                [latest-21281]2021-10-08T21:18:52.550Z <Rule:5:Rule.js:623> Rule#rule-ktrlox2g cleaning loaded condition states
                                [latest-21281]2021-10-08T21:18:52.550Z <Engine:5:Engine.js:886> Engine: new rule rule-ktrlox2g ((undefined)), creating!
                                [latest-21281]2021-10-08T21:18:52.551Z <Rule:5:Rule.js:623> Rule#rule-ktrlp04x cleaning loaded condition states
                                [latest-21281]2021-10-08T21:18:52.552Z <Engine:5:Engine.js:886> Engine: new rule rule-ktrlp04x ((undefined)), creating!
                                [latest-21281]2021-10-08T21:18:52.553Z <Rule:5:Rule.js:623> Rule#rule-ktrlp2cn cleaning loaded condition states
                                [latest-21281]2021-10-08T21:18:52.553Z <Engine:5:Engine.js:886> Engine: new rule rule-ktrlp2cn ((undefined)), creating!
                                [latest-21281]2021-10-08T21:18:52.554Z <Rule:5:Rule.js:623> Rule#rule-ktrlp4il cleaning loaded condition states
                                [latest-21281]2021-10-08T21:18:52.555Z <Engine:5:Engine.js:886> Engine: new rule rule-ktrlp4il ((undefined)), creating!
                                [latest-21281]2021-10-08T21:18:52.556Z <Rule:5:Rule.js:623> Rule#rule-ktrlp6j9 cleaning loaded condition states
                                [latest-21281]2021-10-08T21:18:52.556Z <Engine:5:Engine.js:886> Engine: new rule rule-ktrlp6j9 ((undefined)), creating!
                                [latest-21281]2021-10-08T21:18:52.557Z <Rule:5:Rule.js:623> Rule#rule-ktrlp8v2 cleaning loaded condition states
                                [latest-21281]2021-10-08T21:18:52.557Z <Engine:5:Engine.js:886> Engine: new rule rule-ktrlp8v2 ((undefined)), creating!
                                [latest-21281]2021-10-08T21:18:52.558Z <Rule:5:Rule.js:623> Rule#rule-ktrlpbmt cleaning loaded condition states
                                [latest-21281]2021-10-08T21:18:52.558Z <Engine:5:Engine.js:886> Engine: new rule rule-ktrlpbmt ((undefined)), creating!
                                [latest-21281]2021-10-08T21:18:52.559Z <Rule:5:Rule.js:623> Rule#rule-ktrlpdzf cleaning loaded condition states
                                

                                -Reactor (Multi-hub) 25082-3c348de6
                                -Docker on Synology NAS
                                -Ezlo firmware version 2.0.59.2471.8
                                -HASS Docker 2025.2.5
                                -ZWaveJSUI 10.1.3
                                -Update 30/03/2025

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

                                  Huh. Docker container also working just fine for me, with authenticated access, with anonymous access, and with anonymous insecure access. What version of firmware is your hub? Have you tried to reboot the hub?

                                  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
                                  • N Offline
                                    N Offline
                                    noelab
                                    wrote on last edited by
                                    #20

                                    Now it's working again after I powered off/on ezlo controller and restarted Reactor. The log is too long, no privileges to upload it. It's not the first time it happens upgrating the container.
                                    ezloplus Firmware: 2.0.19.1714.2
                                    Thanks anyway.

                                    [latest-21281]2021-10-08T21:55:33.176Z <Controller:INFO> EzloController#ezlo hub inventory complete/successful; 837ms
                                    [latest-21281]2021-10-08T21:55:33.179Z <Controller:NOTICE> Controller EzloController#ezlo is now online.
                                    

                                    -Reactor (Multi-hub) 25082-3c348de6
                                    -Docker on Synology NAS
                                    -Ezlo firmware version 2.0.59.2471.8
                                    -HASS Docker 2025.2.5
                                    -ZWaveJSUI 10.1.3
                                    -Update 30/03/2025

                                    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

                                    • Local expression in Rule does not evaluate as they used to do
                                      toggledbitsT
                                      toggledbits
                                      0
                                      4
                                      39

                                    • Reactor (Multi-System/Multi-Hub) Announcements
                                      toggledbitsT
                                      toggledbits
                                      5
                                      130
                                      73.7k

                                    • Home Assistant 2025.11.2 and latest-25315
                                      G
                                      gwp1
                                      0
                                      6
                                      83

                                    • Notice to Docker + ARM Users (RPi 3/4/5 and others)
                                      toggledbitsT
                                      toggledbits
                                      1
                                      1
                                      49

                                    • Requesting a proper ARM64/aarch64 Docker image (Pi 5 support)
                                      M
                                      mgvra
                                      1
                                      3
                                      123

                                    • Script action and custom timers
                                      toggledbitsT
                                      toggledbits
                                      0
                                      4
                                      143

                                    • Help resolve change in behaviour post update
                                      CatmanV2C
                                      CatmanV2
                                      0
                                      12
                                      390

                                    • There is an alternative to homebridge-mqttthing
                                      akbooerA
                                      akbooer
                                      1
                                      2
                                      115

                                    • Reactor w/HA 2025.11 error on set_datetime service call setting only time
                                      CrilleC
                                      Crille
                                      0
                                      6
                                      162

                                    • Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
                                      toggledbitsT
                                      toggledbits
                                      0
                                      17
                                      476

                                    • Shelly Wall Display XL
                                      akbooerA
                                      akbooer
                                      2
                                      9
                                      796

                                    • [Solved] alarm() in global expression throws error in log.
                                      toggledbitsT
                                      toggledbits
                                      0
                                      26
                                      847
                                    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