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. Ezlo Plus - Philips Hue devices duplicates in MSR
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor
[Solved] Runtime error when exiting global reaction that contains a group
S
I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved. The Runtime Error is different in the two browsers Safari v18.3 @http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Google Chrome 133.0.6943.142 TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Steps to reproduce: Click the pencil to edit a global reaction with a group. Click the Exit button. Runtime error appears. or Click Create Reaction Click Add Action Select Group Add Condition such as Entity Attribute. Add an Action. Click Save Click Exit Runtime error appears. I don’t know how long the error has been there as I haven’t edited the global reaction in a long time. Reactor (Multi-hub) latest-25060-f32eaa46 Docker Mac OS: 15.3.1 Thanks
Multi-System Reactor
Cannot delete Global Expressions
SnowmanS
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons. I have not created a global expression for some times and just noticed this while doing some clean-up. I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success. Here's what the log shows. [latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } Reactor latest-25067-62e21a2d Docker on Synology NAS
Multi-System Reactor
Local notification methods?
CatmanV2C
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method. This was prompted by yesterday's fun and games with my ISP. I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone) I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions? TIA C
Multi-System Reactor

Ezlo Plus - Philips Hue devices duplicates in MSR

Scheduled Pinned Locked Moved Multi-System Reactor
14 Posts 2 Posters 475 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • cw-kidC Offline
    cw-kidC Offline
    cw-kid
    wrote on last edited by cw-kid
    #1

    Just noticed I have two devices in the Entities list with the same name coming from the same controller (Ezlo Plus) and I am not sure why this is ?

    The device in question is called "Cabinet Light Strip (Hue)"

    Using the Ezlo online API tool I did a hub.devices.list query and searching the output I can only find one device called "Cabinet Light Strip (Hue)"

    This is the entry for ir, from the API Tool.

    {
            "_id": "6300d20b123e4318ec576f13",
            "batteryPowered": false,
            "category": "dimmable_light",
            "deviceTypeId": "ezlo.philips_hue_lamp",
            "gatewayId": "6300d1d5123e4318ec576e99",
            "info": {
              "id": "1",
              "parent_device_id": "6300d1fb123e4318ec576e9a"
            },
            "name": "Cabinet Light Strip (Hue)",
            "parentDeviceId": "",
            "persistent": false,
            "reachable": true,
            "ready": true,
            "roomId": "62bec965123e43124ea13972",
            "security": "no",
            "status": "idle",
            "subcategory": "dimmable_bulb",
            "type": "light.controller"
        
    

    This is what I see in the Entities list in MSR

    58497342-faf4-4e8e-b70e-c8cf96fa5673-image.png

    Entry #1 -

    color_temperature.value=null
    dimming.level=0.64
    dimming.step=0.1
    power_switch.state=false
    rgb_color.blue=125
    rgb_color.green=141
    rgb_color.red=129
    x_ezlo_device.battery_powered=false
    x_ezlo_device.category="dimmable_light"
    x_ezlo_device.manufacturer=null
    x_ezlo_device.model=null
    x_ezlo_device.parent="62baddaf123e4347bb149fec"
    x_ezlo_device.reachable=true
    x_ezlo_device.ready=true
    x_ezlo_device.room="62bec965123e43124ea13972"
    x_ezlo_device.status="idle"
    x_ezlo_device.subcategory="dimmable_bulb"
    x_ezlo_device.type_id="ezlo.philips_hue_lamp"
    x_ezlo_item.alert="select"
    x_ezlo_item.dimmer=64
    x_ezlo_item.dimmer_down=0
    x_ezlo_item.dimmer_stop=0
    x_ezlo_item.dimmer_up=0
    x_ezlo_item.effect="none"
    x_ezlo_item.hue=37777
    x_ezlo_item.rgbcolor={"blue":125,"green":141,"red":129}
    x_ezlo_item.rgbcolor_down=0
    x_ezlo_item.rgbcolor_stop=0
    x_ezlo_item.rgbcolor_up=0
    x_ezlo_item.saturation=107
    x_ezlo_item.switch=false
    x_ezlo_object.id="62bade0a123e4347bb14a040"
    Capabilities: color_temperature, dimming, power_switch, rgb_color, x_ezlo_device, x_ezlo_item, x_ezlo_object
    Actions: color_temperature.set, dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, rgb_color.set, rgb_color.set_rgb, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check
    
    

    Enrty #2 -

    color_temperature.value=null
    dimming.level=0
    dimming.step=0.1
    power_switch.state=false
    rgb_color.blue=0
    rgb_color.green=0
    rgb_color.red=0
    x_ezlo_device.battery_powered=false
    x_ezlo_device.category="dimmable_light"
    x_ezlo_device.manufacturer=null
    x_ezlo_device.model=null
    x_ezlo_device.parent=""
    x_ezlo_device.reachable=true
    x_ezlo_device.ready=true
    x_ezlo_device.room="62bec965123e43124ea13972"
    x_ezlo_device.status="idle"
    x_ezlo_device.subcategory="dimmable_bulb"
    x_ezlo_device.type_id="ezlo.philips_hue_lamp"
    x_ezlo_item.alert="lselect"
    x_ezlo_item.dimmer=0
    x_ezlo_item.dimmer_down=0
    x_ezlo_item.dimmer_stop=0
    x_ezlo_item.dimmer_up=0
    x_ezlo_item.effect="none"
    x_ezlo_item.hue=61509
    x_ezlo_item.rgbcolor={"blue":0,"green":0,"red":0}
    x_ezlo_item.rgbcolor_down=0
    x_ezlo_item.rgbcolor_stop=0
    x_ezlo_item.rgbcolor_up=0
    x_ezlo_item.saturation=227
    x_ezlo_item.switch=false
    x_ezlo_object.id="6300d20b123e4318ec576f13"
    Capabilities: color_temperature, dimming, power_switch, rgb_color, x_ezlo_device, x_ezlo_item, x_ezlo_object
    Actions: color_temperature.set, dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, rgb_color.set, rgb_color.set_rgb, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check
    

    x_ezlo_object.id="62bade0a123e4347bb14a040"

    and

    x_ezlo_object.id="6300d20b123e4318ec576f13"

    The one ending in 6f13 is the one I see listed in the Ezlo Online API Tool output.

    If I search the output for "62bade0a123e4347bb14a040" its not found at all.

    So I don't know what this other duplicated device is or where its come from.

    These are newish Philips Hue plugin devices from Ezlo's own Hue plugin.

    So then I searched the Entities list for another "Hue" device called "TV Backlight (Hue)" and I have two of those listed also.

    b19b7716-d5d7-40c0-bffc-450bcf2f12dd-image.png

    x_ezlo_object.id="62bade08123e4347bb14a031"

    and

    x_ezlo_object.id="6300d20d123e4318ec576f21"

    Searching again the data output from the Ezlo API tool for these two device ID's I only see one of them. The one ending in 6f21.

    {
            "_id": "6300d20d123e4318ec576f21",
            "batteryPowered": false,
            "category": "dimmable_light",
            "deviceTypeId": "ezlo.philips_hue_lamp",
            "gatewayId": "6300d1d5123e4318ec576e99",
            "info": {
              "id": "2",
              "parent_device_id": "6300d1fb123e4318ec576e9a"
            },
            "name": "TV Backlight (Hue)",
            "parentDeviceId": "",
            "persistent": false,
            "reachable": true,
            "ready": true,
            "roomId": "62bec965123e43124ea13972",
            "security": "no",
            "status": "idle",
            "subcategory": "dimmable_bulb",
            "type": "light.controller"
    

    Maybe their new Philips Hue plugin is doing something funky? But I cannot see these duplicated device ID's listed in the hub.device.list API query and I do not see two of these Hue devices in their web GUI with the same names either.

    So bit confused now as to what is happening.

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

      Since they have different IDs, it stands to reason that 62baddaf123e4347bb149fec existed at some point. Since EzloController doesn't yet do deadmarking (that's coming in this weekend's build as I said in your other thread), it would not yet be marked as a missing entity. Why the ID changed is up to Ezlo's firmware and/or your actions. Reactor just acts on what it gets.

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

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

        Yeah like you say the other ID / device must of existing at one point or MSR would not of imported it.

        Actually thinking about it more now, I remember I had to install and setup their Hue plugin twice, as they have no plugin upgrade process in place yet, for newer version numbers of the same plugin, they need to sort that out !

        So the first version of the Hue plugin I had to remove and this deleted all the imported Hue devices off the Ezlo controller.

        I then had to install their newer version of their Hue plugin and pair it with the bridge again, thus importing all the devices again with new ID's presumably.

        So I think that is probably why I now have duplicated Ezlo Hue plugin devices in MSR.

        OK looking forward to your new build with dead marking.

        Thanks

        1 Reply Last reply
        0
        • toggledbitsT toggledbits

          Since they have different IDs, it stands to reason that 62baddaf123e4347bb149fec existed at some point. Since EzloController doesn't yet do deadmarking (that's coming in this weekend's build as I said in your other thread), it would not yet be marked as a missing entity. Why the ID changed is up to Ezlo's firmware and/or your actions. Reactor just acts on what it gets.

          cw-kidC Offline
          cw-kidC Offline
          cw-kid
          wrote on last edited by cw-kid
          #4

          @toggledbits

          Patrick may I ask another question here please?

          On the Ezlo Hue Plugin devices in their own rules engine "Meshbots" there is an "alert" option that makes the lights blink.

          c264f354-1d56-4acc-bb97-f3633d35fa79-image.png

          I don't see this "alerts" option in an MSR rules action however.

          f95f8374-35c0-4fe4-aac2-b0e3b64da1e7-image.png

          I guess its similar to the Vera controller plugins? Where sometimes you had to add support for that particular plugins functions is that correct?

          When I select a Hue Plugin device in their Meshbot Action these are the options I see:

          14160176-b17a-43ed-a40c-3724f066c34a-image.png 3a4fb5a2-d061-44f8-a2f2-304ddd776111-image.png

          Thanks.

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

            I PM'd you a like to upload your ezlo_inventory.json file (in logs). I can see there if anything is published that would lead to that action, or if it's "special knowledge" (i.e. kludge) in Ezlo's Reactor clone.

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

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

              OK thanks I uploaded the requested file. All my rules are still in MSR so could be handy if I could use this blink feature on the Hue lights, but not mission critical.

              I did look under the AltHue plugin on the Vera Plus but could not find "alert" and a forum post I read suggested it was never added by that dev.

              1 Reply Last reply
              0
              • toggledbitsT toggledbits

                I PM'd you a like to upload your ezlo_inventory.json file (in logs). I can see there if anything is published that would lead to that action, or if it's "special knowledge" (i.e. kludge) in Ezlo's Reactor clone.

                cw-kidC Offline
                cw-kidC Offline
                cw-kid
                wrote on last edited by cw-kid
                #7

                @toggledbits

                Damn looks like I won't be able to upgrade MSR anytime soon. I can no longer login to the Debian box MSR runs on for some reason. Not sure what happened and went wrong.

                https://smarthome.community/topic/1015/help-please-cannot-login-to-debian-msr-box

                EDIT: I've managed to fix my login problems now.

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

                  Couple of nice updates there for me !

                  VeraController: Ensure x_vera_device.failed and .configured are null if Vera fails to provide state for these values.
                  EzloController: Dead-marking and automatic removal (after delay) of entities for Ezlo devices/rooms/scenes that no longer exist (functional parity with other hub Controller objects).

                  I am going to update MSR now.

                  Thanks

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

                    Seems to be working and detecting dead devices now from the Ezlo Plus controller.

                    So after 24 hours it would auto remove them from MSR right.

                    Or I can just manually remove them now.

                    Cheers

                    c139cc58-c95b-4ff5-a164-8f6ab53a2cd5-image.png

                    toggledbitsT 1 Reply Last reply
                    0
                    • cw-kidC cw-kid

                      Seems to be working and detecting dead devices now from the Ezlo Plus controller.

                      So after 24 hours it would auto remove them from MSR right.

                      Or I can just manually remove them now.

                      Cheers

                      c139cc58-c95b-4ff5-a164-8f6ab53a2cd5-image.png

                      toggledbitsT Offline
                      toggledbitsT Offline
                      toggledbits
                      wrote on last edited by
                      #10

                      @cw-kid said in Ezlo Plus - Philips Hue devices duplicates in MSR:

                      So after 24 hours it would auto remove them from MSR right.
                      Or I can just manually remove them now.

                      Yes.

                      For the alert, use the x_ezlo_device.set_item_value action with the item name and desired value:

                      04b747b3-40fa-4b56-aabc-7c11a0899aa4-image.png

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

                      cw-kidC 1 Reply Last reply
                      1
                      • toggledbitsT toggledbits

                        @cw-kid said in Ezlo Plus - Philips Hue devices duplicates in MSR:

                        So after 24 hours it would auto remove them from MSR right.
                        Or I can just manually remove them now.

                        Yes.

                        For the alert, use the x_ezlo_device.set_item_value action with the item name and desired value:

                        04b747b3-40fa-4b56-aabc-7c11a0899aa4-image.png

                        cw-kidC Offline
                        cw-kidC Offline
                        cw-kid
                        wrote on last edited by
                        #11

                        @toggledbits

                        Even better thanks. I will give the alert a try.

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

                          The "alert" works I just tested it.

                          Thanks.

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

                            A bit of background here. Unlike Vera, which had actions separate from values (state variables) to make things happen, the Ezlo firmware uses the Z-Wave approach of modifying values as a way of stimulating action. It's not surprising they would use this model, as Z-Wave is the philosophical core of their system. There is therefore no need for separate actions, which on Vera was the byproduct of attempting to implement UPnP (and didn't quite get there).

                            Since actions on Ezlo are actually just item value changes, using x_ezlo_device.set_item_value, you can set the value of any item associated with a device, even if the value isn't mapped to one of Reactor's capabilities or attributes, and whatever action that may stimulate either in the firmware or on the device itself will occur.

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

                            cw-kidC 1 Reply Last reply
                            1
                            • toggledbitsT toggledbits

                              A bit of background here. Unlike Vera, which had actions separate from values (state variables) to make things happen, the Ezlo firmware uses the Z-Wave approach of modifying values as a way of stimulating action. It's not surprising they would use this model, as Z-Wave is the philosophical core of their system. There is therefore no need for separate actions, which on Vera was the byproduct of attempting to implement UPnP (and didn't quite get there).

                              Since actions on Ezlo are actually just item value changes, using x_ezlo_device.set_item_value, you can set the value of any item associated with a device, even if the value isn't mapped to one of Reactor's capabilities or attributes, and whatever action that may stimulate either in the firmware or on the device itself will occur.

                              cw-kidC Offline
                              cw-kidC Offline
                              cw-kid
                              wrote on last edited by
                              #14

                              @toggledbits

                              Thanks for the additional information, that is certainly good to know about.

                              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

                              • Advice reqeusted to migrate MSR from Bare Metal to Container
                                T
                                tamorgen
                                0
                                5
                                33

                              • Reactor (Multi-System/Multi-Hub) Announcements
                                toggledbitsT
                                toggledbits
                                5
                                122
                                35.4k

                              • Z-Wave Future....
                                CatmanV2C
                                CatmanV2
                                0
                                5
                                125

                              • Can´t restart or upgrade/deploy MSR
                                toggledbitsT
                                toggledbits
                                0
                                4
                                83

                              • [Solved] Limit HA Entity in MSR
                                wmarcolinW
                                wmarcolin
                                0
                                7
                                188

                              • Disaster recovery and virtualisation
                                CatmanV2C
                                CatmanV2
                                0
                                5
                                655

                              • Remote access of Zwave stick from Z-wave server
                                CatmanV2C
                                CatmanV2
                                0
                                3
                                380

                              • Organizing/ structuring rule sets and rules
                                G
                                gwp1
                                0
                                5
                                373

                              • Moving MSR from a QNAP container to RP 5 - some issues
                                G
                                gwp1
                                0
                                5
                                343

                              • Widget deletion does not work and landing page (status) is empy
                                G
                                gwp1
                                0
                                4
                                335

                              • Need help reducing false positive notifications
                                T
                                tamorgen
                                0
                                7
                                518
                              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