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. TILT-ZWAVE2.5-ECO tilt_sensor.state (primary) = NULL
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
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

TILT-ZWAVE2.5-ECO tilt_sensor.state (primary) = NULL

Scheduled Pinned Locked Moved Multi-System Reactor
14 Posts 2 Posters 1.1k 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.
  • SnowmanS Offline
    SnowmanS Offline
    Snowman
    wrote on last edited by
    #1

    @togglebits I am curious as to why the tilt_sensor.state (primary) = NULL. I believe it should show true or false. I have to use binary_sensor.state instead in my rules.

    Again, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes of the tilt sensor in hopes it can help.

    Thanks in advance.

    Reactor version 23302
    ZWaveJSController version 23254
    Z-Wave JS UI version 9.3.0.724519f
    zwave-js version 12.2.3

    battery_power.level=0.99
    battery_power.since=1699401727360
    binary_sensor.state=false
    tamper.state=true
    tilt_sensor.state=null
    x_debug.dt={"entity_class":"Binary Sensor","match":"deviceClass.generic.key=7","description":"Z-Wave Plus Tilt Sensor","default_name":"Tilt Sensor","model":"TILTZWAVE2.5-ECO","capabilities":["tilt_sensor"],"primary_attribute":"tilt_sensor.state","values":[{"valueId":"32:currentValue:","capabilities":{"tilt_sensor":{"attributes":{"state":{}}}}}],"manufacturerId":330,"productType":4,"productId":3}
    x_zwave_values.Battery_isLow=false
    x_zwave_values.Battery_level=99
    x_zwave_values.Binary_Sensor_Any=false
    x_zwave_values.Configuration_Basic_Sets_for_Association_Group_2=0
    x_zwave_values.Configuration_Send_Reports=0
    x_zwave_values.Manufacturer_Specific_manufacturerId=330
    x_zwave_values.Manufacturer_Specific_productId=3
    x_zwave_values.Manufacturer_Specific_productType=4
    x_zwave_values.Notification_Access_Control_Door_state=23
    x_zwave_values.Notification_Access_Control_Door_state_simple=23
    x_zwave_values.Notification_Home_Security_Cover_status=3
    x_zwave_values.Notification_Power_Management_Battery_maintenance_status=0
    x_zwave_values.Notification_UNKNOWN_0x46=23
    x_zwave_values.Notification_alarmLevel=0
    x_zwave_values.Notification_alarmType=0
    x_zwave_values.Version_firmwareVersions=["10.1"]
    x_zwave_values.Version_hardwareVersion=2
    x_zwave_values.Version_libraryType=6
    x_zwave_values.Version_protocolVersion="4.5"
    x_zwave_values.Wake_Up_controllerNodeId=1
    x_zwave_values.Wake_Up_wakeUpInterval=14400
    zwave_device.capabilities=[48,112,113,114,128,132,134]
    zwave_device.endpoint=0
    zwave_device.failed=false
    zwave_device.generic_class="Notification Sensor"
    zwave_device.impl_sig="23305:1:22057:1"
    zwave_device.is_beaming=false
    zwave_device.is_listening=false
    zwave_device.is_routing=true
    zwave_device.is_secure=false
    zwave_device.last_wakeup=1699563172708
    zwave_device.manufacturer_info=[330,4,3]
    zwave_device.max_data_rate=null
    zwave_device.node_id=24
    zwave_device.specific_class="Notification Sensor"
    zwave_device.status=1
    zwave_device.status_text="asleep"
    zwave_device.version_info=[null,"10.1"]
    zwave_device.wakeup_interval=14400
    

    Synology NAS, Docker, Zooz Z-Wave Stick 700, Z-Wave JS-UI, Reactor, Home Assistant, Grafana, and InfluxDB.

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

      Try downloading the latest zwavejs_data.zip from the download server, and place the ZIP file in your config directory and restart Reactor.

      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
      • SnowmanS Offline
        SnowmanS Offline
        Snowman
        wrote on last edited by
        #3

        Working now. I no longer see binary_sensor.state for the tilt sensor which was erratic at times showing the garage door was open while it was actually closed. I can now use the tilt_sensor.state (primary) = true/false

        Thanks again. Much appreciated.

        Synology NAS, Docker, Zooz Z-Wave Stick 700, Z-Wave JS-UI, Reactor, Home Assistant, Grafana, and InfluxDB.

        1 Reply Last reply
        0
        • SnowmanS Offline
          SnowmanS Offline
          Snowman
          wrote on last edited by
          #4

          @toggledbits I just noticed that the tilt_sensor.state = false now and no longer can be used in my rule. I have to use door_sensor.state instead.

          I cannot tell when the issue started and not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes of the tilt sensor in hopes it can help.

          Thanks in advance.

          Reactor version 24190
          ZWaveJSController version 23326
          Z-Wave JS UI version 9.14.5
          zwave-js version 12.12.3

          battery_maintenance.charging=null
          battery_maintenance.rechargeable=false
          battery_maintenance.replace=false
          battery_maintenance.state=null
          battery_power.level=1
          battery_power.since=1720636775292
          door_sensor.state=true
          power_source.source=null
          tamper.state=true
          tilt_sensor.state=false
          x_debug.dt={"entity_class":"Binary Sensor","match":"deviceClass.generic.key=7","description":"Z-Wave Plus Tilt Sensor","default_name":"Tilt Sensor","model":"TILTZWAVE2.5-ECO","capabilities":["tilt_sensor"],"primary_attribute":"tilt_sensor.state","values":[{"valueId":"32:currentValue:","capabilities":{"tilt_sensor":{"attributes":{"state":{}}}}},{"match":{"endpoint":0,"commandClass":48,"metadata.ccSpecific.sensorType":255},"capabilities":{"tilt_sensor":{"attributes":{"state":{}}}}}],"manufacturerId":330,"productType":4,"productId":3}
          x_zwave_values.Battery_isLow=false
          x_zwave_values.Battery_level=100
          x_zwave_values.Binary_Sensor_Any=false
          x_zwave_values.Binary_Sensor_Door_Window=true
          x_zwave_values.Configuration_Basic_Sets_for_Association_Group_2=0
          x_zwave_values.Configuration_Send_Reports=0
          x_zwave_values.Manufacturer_Specific_manufacturerId=330
          x_zwave_values.Manufacturer_Specific_productId=3
          x_zwave_values.Manufacturer_Specific_productType=4
          x_zwave_values.Notification_Access_Control_Door_state=22
          x_zwave_values.Notification_Access_Control_Door_state_simple=22
          x_zwave_values.Notification_Home_Security_Cover_status=3
          x_zwave_values.Notification_Power_Management_Battery_maintenance_status=0
          x_zwave_values.Notification_UNKNOWN_0x46=23
          x_zwave_values.Notification_alarmLevel=0
          x_zwave_values.Notification_alarmType=0
          x_zwave_values.Version_firmwareVersions=["10.1"]
          x_zwave_values.Version_hardwareVersion=2
          x_zwave_values.Version_libraryType=6
          x_zwave_values.Version_protocolVersion="4.5"
          x_zwave_values.Wake_Up_controllerNodeId=1
          x_zwave_values.Wake_Up_wakeUpInterval=14400
          zwave_device.capabilities=[48,112,113,114,128,132,134]
          zwave_device.endpoint=0
          zwave_device.failed=false
          zwave_device.generic_class="Notification Sensor"
          zwave_device.impl_sig="23326:1:23318:2"
          zwave_device.is_beaming=false
          zwave_device.is_listening=false
          zwave_device.is_routing=true
          zwave_device.is_secure=false
          zwave_device.last_wakeup=1720636775220
          zwave_device.manufacturer_info=[330,4,3]
          zwave_device.max_data_rate=null
          zwave_device.node_id=24
          zwave_device.specific_class="Notification Sensor"
          zwave_device.status=1
          zwave_device.status_text="asleep"
          zwave_device.version_info=[null,"10.1"]
          zwave_device.wakeup_interval=14400

          Synology NAS, Docker, Zooz Z-Wave Stick 700, Z-Wave JS-UI, Reactor, Home Assistant, Grafana, and InfluxDB.

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

            Looks like this is the result of a change introduced in ZWaveJS version 12.12.0 (see change #6958 linked there).

            Let's see if we can deal with this the easy way first. I've updated the device definition data. You can download it (ZIP archive zwavejs_data.zip) from the Reactor download server and put the ZIP archive into your config directory (do not unzip it); restart Reactor. Let's see if that brings tilt_sensor back.

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

            SnowmanS 1 Reply Last reply
            0
            • toggledbitsT toggledbits

              Looks like this is the result of a change introduced in ZWaveJS version 12.12.0 (see change #6958 linked there).

              Let's see if we can deal with this the easy way first. I've updated the device definition data. You can download it (ZIP archive zwavejs_data.zip) from the Reactor download server and put the ZIP archive into your config directory (do not unzip it); restart Reactor. Let's see if that brings tilt_sensor back.

              SnowmanS Offline
              SnowmanS Offline
              Snowman
              wrote on last edited by
              #6

              @toggledbits That fixed it. Thank you sir.

              battery_maintenance.charging=null
              battery_maintenance.rechargeable=false
              battery_maintenance.replace=false
              battery_maintenance.state="normal"
              battery_power.level=1
              battery_power.since=1720778246637
              door_sensor.state=true
              power_source.source=null
              tamper.state=true
              tilt_sensor.state=true

              Synology NAS, Docker, Zooz Z-Wave Stick 700, Z-Wave JS-UI, Reactor, Home Assistant, Grafana, and InfluxDB.

              SnowmanS 1 Reply Last reply
              1
              • SnowmanS Snowman

                @toggledbits That fixed it. Thank you sir.

                battery_maintenance.charging=null
                battery_maintenance.rechargeable=false
                battery_maintenance.replace=false
                battery_maintenance.state="normal"
                battery_power.level=1
                battery_power.since=1720778246637
                door_sensor.state=true
                power_source.source=null
                tamper.state=true
                tilt_sensor.state=true

                SnowmanS Offline
                SnowmanS Offline
                Snowman
                wrote on last edited by
                #7

                @toggledbits I appears the tilt_sensor.state = false is back again after I upgraded both Reactor and ZWaveJSController to version 24257. It was working fine with ZWaveJSController version 24242.

                I can certainly stop using this entity and use the door_sensor.state instead.

                I did check the latest changes for zwave-js 13.2.0 and did not see any thing that may have been introduced causing this.

                I have copied, below, the attributes of the tilt sensor in hopes it can help.

                Thanks in advance.

                Reactor version 24257
                ZWaveJSController version 24257
                Z-Wave JS UI version 9.18.1
                zwave-js version 13.2.0

                battery_maintenance.charging=0
                battery_maintenance.rechargeable=0
                battery_maintenance.replace=false
                battery_maintenance.state="normal"
                battery_power.level=1
                battery_power.since=null
                door_sensor.state=true
                tamper.state=true
                tilt_sensor.state=false
                x_debug.dt={"entity_class":"Binary Sensor","match":"deviceClass.generic.key=7","description":"Z-Wave Plus Tilt Sensor","default_name":"Tilt Sensor","model":"TILTZWAVE2.5-ECO","capabilities":["tilt_sensor"],"primary_attribute":"tilt_sensor.state","values":[{"valueId":"32:currentValue:","capabilities":{"tilt_sensor":{"attributes":{"state":{}}}}},{"match":{"endpoint":0,"commandClass":48,"metadata.ccSpecific.sensorType":255},"capabilities":{"tilt_sensor":{"attributes":{"state":{}}}}},{"match":{"endpoint":0,"commandClass":113,"metadata.ccSpecific.notificationType":6},"capabilities":{"tilt_sensor":{"attributes":{"state":{"expr":"value === 22"}}}}}],"manufacturerId":330,"productType":4,"productId":3}
                x_zwave_values.Battery_isLow=false
                x_zwave_values.Battery_level=100
                x_zwave_values.Binary_Sensor_Any=false
                x_zwave_values.Binary_Sensor_Door_Window=true
                x_zwave_values.Configuration_Basic_Sets_for_Association_Group_2=0
                x_zwave_values.Configuration_Send_Reports=0
                x_zwave_values.Manufacturer_Specific_manufacturerId=330
                x_zwave_values.Manufacturer_Specific_productId=3
                x_zwave_values.Manufacturer_Specific_productType=4
                x_zwave_values.Notification_Access_Control_Door_state=22
                x_zwave_values.Notification_Access_Control_Door_state_simple=22
                x_zwave_values.Notification_Home_Security_Cover_status=3
                x_zwave_values.Notification_Power_Management_Battery_maintenance_status=0
                x_zwave_values.Notification_UNKNOWN_0x46=23
                x_zwave_values.Notification_alarmLevel=0
                x_zwave_values.Notification_alarmType=0
                x_zwave_values.Version_firmwareVersions=["10.1"]
                x_zwave_values.Version_hardwareVersion=2
                x_zwave_values.Version_libraryType=6
                x_zwave_values.Version_protocolVersion="4.5"
                x_zwave_values.Wake_Up_controllerNodeId=1
                x_zwave_values.Wake_Up_wakeUpInterval=14400
                zwave_device.capabilities=[48,112,113,114,128,132,134]
                zwave_device.endpoint=0
                zwave_device.failed=false
                zwave_device.generic_class="Notification Sensor"
                zwave_device.impl_sig="24256:1:24192:1"
                zwave_device.is_beaming=true
                zwave_device.is_listening=false
                zwave_device.is_routing=true
                zwave_device.is_secure=false
                zwave_device.last_wakeup=1726513928400
                zwave_device.manufacturer_info=[330,4,3]
                zwave_device.max_data_rate=100000
                zwave_device.node_id=24
                zwave_device.specific_class="Notification Sensor"
                zwave_device.status=1
                zwave_device.status_text="asleep"
                zwave_device.version_info=[4,"10.1"]
                zwave_device.wakeup_interval=14400
                

                Synology NAS, Docker, Zooz Z-Wave Stick 700, Z-Wave JS-UI, Reactor, Home Assistant, Grafana, and InfluxDB.

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

                  Have you opened and closed the door since updating? Because it's a notification sensor, Reactor won't have the right values until it gets notifications from the device.

                  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
                  • SnowmanS Snowman

                    @togglebits I am curious as to why the tilt_sensor.state (primary) = NULL. I believe it should show true or false. I have to use binary_sensor.state instead in my rules.

                    Again, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes of the tilt sensor in hopes it can help.

                    Thanks in advance.

                    Reactor version 23302
                    ZWaveJSController version 23254
                    Z-Wave JS UI version 9.3.0.724519f
                    zwave-js version 12.2.3

                    battery_power.level=0.99
                    battery_power.since=1699401727360
                    binary_sensor.state=false
                    tamper.state=true
                    tilt_sensor.state=null
                    x_debug.dt={"entity_class":"Binary Sensor","match":"deviceClass.generic.key=7","description":"Z-Wave Plus Tilt Sensor","default_name":"Tilt Sensor","model":"TILTZWAVE2.5-ECO","capabilities":["tilt_sensor"],"primary_attribute":"tilt_sensor.state","values":[{"valueId":"32:currentValue:","capabilities":{"tilt_sensor":{"attributes":{"state":{}}}}}],"manufacturerId":330,"productType":4,"productId":3}
                    x_zwave_values.Battery_isLow=false
                    x_zwave_values.Battery_level=99
                    x_zwave_values.Binary_Sensor_Any=false
                    x_zwave_values.Configuration_Basic_Sets_for_Association_Group_2=0
                    x_zwave_values.Configuration_Send_Reports=0
                    x_zwave_values.Manufacturer_Specific_manufacturerId=330
                    x_zwave_values.Manufacturer_Specific_productId=3
                    x_zwave_values.Manufacturer_Specific_productType=4
                    x_zwave_values.Notification_Access_Control_Door_state=23
                    x_zwave_values.Notification_Access_Control_Door_state_simple=23
                    x_zwave_values.Notification_Home_Security_Cover_status=3
                    x_zwave_values.Notification_Power_Management_Battery_maintenance_status=0
                    x_zwave_values.Notification_UNKNOWN_0x46=23
                    x_zwave_values.Notification_alarmLevel=0
                    x_zwave_values.Notification_alarmType=0
                    x_zwave_values.Version_firmwareVersions=["10.1"]
                    x_zwave_values.Version_hardwareVersion=2
                    x_zwave_values.Version_libraryType=6
                    x_zwave_values.Version_protocolVersion="4.5"
                    x_zwave_values.Wake_Up_controllerNodeId=1
                    x_zwave_values.Wake_Up_wakeUpInterval=14400
                    zwave_device.capabilities=[48,112,113,114,128,132,134]
                    zwave_device.endpoint=0
                    zwave_device.failed=false
                    zwave_device.generic_class="Notification Sensor"
                    zwave_device.impl_sig="23305:1:22057:1"
                    zwave_device.is_beaming=false
                    zwave_device.is_listening=false
                    zwave_device.is_routing=true
                    zwave_device.is_secure=false
                    zwave_device.last_wakeup=1699563172708
                    zwave_device.manufacturer_info=[330,4,3]
                    zwave_device.max_data_rate=null
                    zwave_device.node_id=24
                    zwave_device.specific_class="Notification Sensor"
                    zwave_device.status=1
                    zwave_device.status_text="asleep"
                    zwave_device.version_info=[null,"10.1"]
                    zwave_device.wakeup_interval=14400
                    
                    SnowmanS Offline
                    SnowmanS Offline
                    Snowman
                    wrote on last edited by
                    #9

                    I did open and close the garage door after updating Reactor. More than once. I even removed the battery to see if it would make a difference.

                    I am looking at the Notification values under ZWaveJS UI ans can see that the Window/door state do toggle between TRUE/FALSE when the door opens and closes. Nothing unusual here.

                    Looking at Binary Sensor values, I am seing this though. Makes sense?

                    When the garage door Opens
                    1de1d60d-615b-4d3d-b400-b9e101c8daac-image.png

                    When the garage door Closes
                    69844462-27a1-482c-bd1e-59419f09d348-image.png

                    Synology NAS, Docker, Zooz Z-Wave Stick 700, Z-Wave JS-UI, Reactor, Home Assistant, Grafana, and InfluxDB.

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

                      The Z-Wave JS UI doesn't show notifications here, only states. All of those are states. Notifications are class number 113.

                      At this point, I'll need to see logs for what happens when you open and close this thing. Here's what you need to do:

                      1. In your ZWaveJSController config in reactor.yaml, add the following line:

                             config:  # don't add this line, included for indenting reference only
                               monitor_nodes: [24]  # add this line
                        
                      2. Restart Reactor.

                      3. Open and close the door two or three times.

                      4. Remove or comment out the line you added in step 1 and restart Reactor again.

                      5. Post the logs/zwavejs_24_monitor.json file to the URL I am going to DM to you in chat.

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

                      SnowmanS 1 Reply Last reply
                      0
                      • toggledbitsT toggledbits

                        The Z-Wave JS UI doesn't show notifications here, only states. All of those are states. Notifications are class number 113.

                        At this point, I'll need to see logs for what happens when you open and close this thing. Here's what you need to do:

                        1. In your ZWaveJSController config in reactor.yaml, add the following line:

                               config:  # don't add this line, included for indenting reference only
                                 monitor_nodes: [24]  # add this line
                          
                        2. Restart Reactor.

                        3. Open and close the door two or three times.

                        4. Remove or comment out the line you added in step 1 and restart Reactor again.

                        5. Post the logs/zwavejs_24_monitor.json file to the URL I am going to DM to you in chat.

                        SnowmanS Offline
                        SnowmanS Offline
                        Snowman
                        wrote on last edited by
                        #11

                        @toggledbits I now have the requested log file.

                        Synology NAS, Docker, Zooz Z-Wave Stick 700, Z-Wave JS-UI, Reactor, Home Assistant, Grafana, and InfluxDB.

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

                          OK. Pull the zwavejs_data.zip update file from the server and put it into your config directory. The stop Reactor (not restart), clear out storage/entities/zwavejs, and start Reactor again.

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

                          SnowmanS 1 Reply Last reply
                          0
                          • toggledbitsT toggledbits

                            OK. Pull the zwavejs_data.zip update file from the server and put it into your config directory. The stop Reactor (not restart), clear out storage/entities/zwavejs, and start Reactor again.

                            SnowmanS Offline
                            SnowmanS Offline
                            Snowman
                            wrote on last edited by
                            #13

                            @toggledbits The ZIP file fixed the issue. The tilt_sensor.state working as expected. Thanks

                            door_sensor.state=true
                            tamper.state=true
                            tilt_sensor.state=true
                            

                            Synology NAS, Docker, Zooz Z-Wave Stick 700, Z-Wave JS-UI, Reactor, Home Assistant, Grafana, and InfluxDB.

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

                              Perfect. Thanks for sending the log. Don't forget to remove or comment out the monitor_nodes line if you haven't already... it will consume disk space to exhaustion if you don't disable it.

                              Edit: the issue, by the way, was the new device data had handling dependent on which version of Z-Wave JS was running, because the device is reported differently on earlier versions (as you pointed out earlier), but the test in the new data file was broken. Easy fix.

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

                              1 Reply Last reply
                              0
                              • toggledbitsT toggledbits unlocked this topic on
                              • toggledbitsT toggledbits locked this topic on
                              Reply
                              • Reply as topic
                              Log in to reply
                              • Oldest to Newest
                              • Newest to Oldest
                              • Most Votes


                              Recent Topics

                              • Gradually turn on lights.
                                G
                                gwp1
                                0
                                4
                                132

                              • Stop the MSR by an external switch on Hubitat.
                                wmarcolinW
                                wmarcolin
                                0
                                1
                                31

                              • Error After Upgrade
                                G
                                gwp1
                                0
                                4
                                103

                              • Reset attribute value of entity in event handler
                                R
                                RHCPNG
                                0
                                5
                                202

                              • Need help figuring out how to delay a reset on reaction
                                G
                                gwp1
                                0
                                22
                                925

                              • Way to search for rules (rule state) in other rules
                                T
                                tamorgen
                                0
                                3
                                99

                              • Links to MSR from HA
                                Tom_DT
                                Tom_D
                                0
                                1
                                90

                              • Set Reaction > Script Action
                                wmarcolinW
                                wmarcolin
                                0
                                11
                                433

                              • Wiring Samotech SM308-S into light fitting
                                akbooerA
                                akbooer
                                0
                                2
                                146

                              • Errors after updating to MQTTController build 25139
                                toggledbitsT
                                toggledbits
                                0
                                6
                                236

                              • 🎉 My very first MSR controller: OpenSprinkler
                                therealdbT
                                therealdb
                                5
                                13
                                918

                              • Advice reqeusted to migrate MSR from Bare Metal to Container
                                T
                                tamorgen
                                0
                                5
                                260
                              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