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. [SOLVED] New iblind and zwaveJScontroller/MSR not communicating
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

[SOLVED] New iblind and zwaveJScontroller/MSR not communicating

Scheduled Pinned Locked Moved Multi-System Reactor
solved
44 Posts 3 Posters 5.3k 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 toggledbits

    Yeah, logs confirm everything going out as expected, ZWJS acknowledging the request, and also sending a notification for a value change asynchronously. ZWaveJSController appears to be doing the right things. ZWaveJS appears to be doing its part as well.

    G Offline
    G Offline
    gwp1
    wrote on last edited by gwp1
    #34

    @toggledbits I'm conducting an experiment.

    DR2 blind (22-0) is configured as [Default] direction and using MSRs ZWJSController. I have set the three Reactions to:

    DR OPEN: cover.open
    DR CLOSE: cover.close
    DR @25: position.set = .75 (resulting in the blind being tilted open 25%, "top inside").

    All other iblinds are using HA's ZWJSC plugin and all ran flawlessly for the past 24 hours. I'm wondering if this issue is somehow load-induced. If this single blind remains solid I will add a second and so on.

    UPDATE: as my patience level on any given day runs the gamut between saint and toddler I've added KITCHEN (18-0) to this test with the same settings as above excepting .80 instead of .75. Both of these iblinds were the most impacted in being unresponsive.

    *Hubitat C-7 2.4.1.177
    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

    *HASS 2025.6.0
    w/ ZST10-700 fw 7.18.3

    *Prod MSR in docker/portainer
    MSR: latest-25139-fbd67abc
    MQTTController: 25139
    ZWave Controller: 25139

    G 1 Reply Last reply
    0
    • G gwp1

      @toggledbits I'm conducting an experiment.

      DR2 blind (22-0) is configured as [Default] direction and using MSRs ZWJSController. I have set the three Reactions to:

      DR OPEN: cover.open
      DR CLOSE: cover.close
      DR @25: position.set = .75 (resulting in the blind being tilted open 25%, "top inside").

      All other iblinds are using HA's ZWJSC plugin and all ran flawlessly for the past 24 hours. I'm wondering if this issue is somehow load-induced. If this single blind remains solid I will add a second and so on.

      UPDATE: as my patience level on any given day runs the gamut between saint and toddler I've added KITCHEN (18-0) to this test with the same settings as above excepting .80 instead of .75. Both of these iblinds were the most impacted in being unresponsive.

      G Offline
      G Offline
      gwp1
      wrote on last edited by gwp1
      #35

      @toggledbits we have fail!

      Added two more iblinds to the test. They failed to respond so I isolated one of them and did the following tests on node 8-0:

      LR Left OPEN: cover.open
      LR Left CLOSE: cover.close
      LR Left @20: position.set = .80 (resulting in the blind being tilted open 20%, "top inside").

      Results:
      cover.open = iblind opens, position of 50
      cover.close = iblind moves to position of 50 <---expected result, position 0
      position.set = iblind moves to position of 80

      As this Reaction was to run BOTH left and right blinds I removed the right blind and ran the left solo as the kitchen and DR are (both still working fine, btw). For reference, Kitchen was existing unit and was re-interviewed to be current, DR is a brand new unit. LR's are existing units re-interviewed.

      Log forthcoming.

      *Hubitat C-7 2.4.1.177
      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

      *HASS 2025.6.0
      w/ ZST10-700 fw 7.18.3

      *Prod MSR in docker/portainer
      MSR: latest-25139-fbd67abc
      MQTTController: 25139
      ZWave Controller: 25139

      toggledbitsT 1 Reply Last reply
      0
      • T Offline
        T Offline
        tamorgen
        wrote on last edited by tamorgen
        #36

        @gwp1, I just replaced 6 of my ib2 motors with ib3.1, and they are working just fine (12 of 14 are v3.1). I can control them from MSR with ZWJSController without issue.

        My only issue is actually Home Assistant itself. I've had to go to great lengths to get a somewhat working card for each of the blinds in my home, and I'm still not completely there yet. I'm hoping either the ZWaveJS devlopers or the HA developers figure out whats going on with the 'state' value for each of these, as they all return 'unknown', so none of the cards work out of the box.

        G 1 Reply Last reply
        0
        • T tamorgen

          @gwp1, I just replaced 6 of my ib2 motors with ib3.1, and they are working just fine (12 of 14 are v3.1). I can control them from MSR with ZWJSController without issue.

          My only issue is actually Home Assistant itself. I've had to go to great lengths to get a somewhat working card for each of the blinds in my home, and I'm still not completely there yet. I'm hoping either the ZWaveJS devlopers or the HA developers figure out whats going on with the 'state' value for each of these, as they all return 'unknown', so none of the cards work out of the box.

          G Offline
          G Offline
          gwp1
          wrote on last edited by
          #37

          @tamorgen said in [SOLVED-ish] New iblind and zwaveJScontroller/MSR not communicating:

          they are working just fine (12 of 14 are v3.1). I can control them from MSR with ZWJSController without issue.

          It's more helpful if, instead of generalized statements, you provide settings/configurations you're using whilst having this success for comparison sake.

          I ran into an issue this morning wherein, after completing the weekly zwave_device.set_config, the iblinds finish in a closed position but reporting back in all systems (HA, both ZWJSC's, and MSR) as 50 or open. I've created a workaround wherein, after completing the config, they wait a few seconds then tilt 20% and then set back to open.

          *Hubitat C-7 2.4.1.177
          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

          *HASS 2025.6.0
          w/ ZST10-700 fw 7.18.3

          *Prod MSR in docker/portainer
          MSR: latest-25139-fbd67abc
          MQTTController: 25139
          ZWave Controller: 25139

          T 1 Reply Last reply
          0
          • G gwp1

            @tamorgen said in [SOLVED-ish] New iblind and zwaveJScontroller/MSR not communicating:

            they are working just fine (12 of 14 are v3.1). I can control them from MSR with ZWJSController without issue.

            It's more helpful if, instead of generalized statements, you provide settings/configurations you're using whilst having this success for comparison sake.

            I ran into an issue this morning wherein, after completing the weekly zwave_device.set_config, the iblinds finish in a closed position but reporting back in all systems (HA, both ZWJSC's, and MSR) as 50 or open. I've created a workaround wherein, after completing the config, they wait a few seconds then tilt 20% and then set back to open.

            T Offline
            T Offline
            tamorgen
            wrote on last edited by tamorgen
            #38

            @gwp1 said in [SOLVED-ish] New iblind and zwaveJScontroller/MSR not communicating:

            It's more helpful if, instead of generalized statements, you provide settings/configurations you're using whilst having this success for comparison sake.

            All of mine are like this, cover.close, cover.open.

            Perform cover.close on Office Blind Left (zwavejs>30-0)
            Delay for 5 seconds
            Perform cover.close on Office Blind Right (zwavejs>31-0)
            Delay for 5 seconds
            Perform zwave_device.refresh on Office Blind Left (zwavejs>30-0)
            Perform zwave_device.refresh on Office Blind Right (zwavejs>31-0)
            

            I'm not even sure the zwave.device.refresh is needed anymore. This was more of an issue when trying to force the old device class to refresh on both the binary switch and the multi-level switch, as they weren't directly connected and didn't update each other. It was one of the reasons that the folks at iBlinds were pushing to get the window device class implemented.

            G 1 Reply Last reply
            0
            • T tamorgen

              @gwp1 said in [SOLVED-ish] New iblind and zwaveJScontroller/MSR not communicating:

              It's more helpful if, instead of generalized statements, you provide settings/configurations you're using whilst having this success for comparison sake.

              All of mine are like this, cover.close, cover.open.

              Perform cover.close on Office Blind Left (zwavejs>30-0)
              Delay for 5 seconds
              Perform cover.close on Office Blind Right (zwavejs>31-0)
              Delay for 5 seconds
              Perform zwave_device.refresh on Office Blind Left (zwavejs>30-0)
              Perform zwave_device.refresh on Office Blind Right (zwavejs>31-0)
              

              I'm not even sure the zwave.device.refresh is needed anymore. This was more of an issue when trying to force the old device class to refresh on both the binary switch and the multi-level switch, as they weren't directly connected and didn't update each other. It was one of the reasons that the folks at iBlinds were pushing to get the window device class implemented.

              G Offline
              G Offline
              gwp1
              wrote on last edited by
              #39

              @tamorgen I see you doing the delay as I do. How do you do a weekly config? (The blinds will "drift" if not config'd weekly or bi-weekly.

              I have removed the zwave_device.refresh to see how that goes.

              Question: you have a great number of blinds in your fleet as do I - how many blinds do you group together? I see you grouped two for your office blinds, do you have more than two at a time grouped in a single reaction? Or are you skipping reactions and adding each entity in each ruleset?

              *Hubitat C-7 2.4.1.177
              *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

              *HASS 2025.6.0
              w/ ZST10-700 fw 7.18.3

              *Prod MSR in docker/portainer
              MSR: latest-25139-fbd67abc
              MQTTController: 25139
              ZWave Controller: 25139

              T 1 Reply Last reply
              0
              • G gwp1

                @tamorgen I see you doing the delay as I do. How do you do a weekly config? (The blinds will "drift" if not config'd weekly or bi-weekly.

                I have removed the zwave_device.refresh to see how that goes.

                Question: you have a great number of blinds in your fleet as do I - how many blinds do you group together? I see you grouped two for your office blinds, do you have more than two at a time grouped in a single reaction? Or are you skipping reactions and adding each entity in each ruleset?

                T Offline
                T Offline
                tamorgen
                wrote on last edited by tamorgen
                #40

                @gwp1 ,

                I really don't have any sort of weekly config on mine. I haven't noticed mine drifting at all, but a weekly recalibrate wouldn't be a bad idea.

                I have rules for hourly refreshing the the cover, position, and switch positions that are now pretty much legacy of the old device class. I only have two of the IB2 devices left, and they're in non critical rooms ( guest bedroom and mudroom). I'll replace those later this year. Once those are gone, I'll be able to remove those three hourly rules.

                I have reactions set up for each set of windows in a room. Most rooms only have two windows, so I group those. The lone exception is my family room, where I have four windows, but on different walls. I have those set up on two separate reactions, which allows me to separately set the blinds to a partial open position when the sun is shining directly in. The largest events with the blinds are at sunrise, sunset, and when the house is vacant or someone arrives, when I'll set the reactions from the rule, and I have "Wait for completion" enabled after each call for a reaction. It takes a couple of minutes for all my blinds to open/close when it's called. I initially didn't do this, but iBlinds recommended not calling them all at once (thus the pause in between each call for a blind to open/close). For the most part, this has helped tremendously with the IB2 motors, although they still had their fair share of problems, which is why I've been replacing them all this year.

                I call the reactions from rulesets, so I don't have to reinvent the wheel each time I want to perform an action on a window. It also allows me to make an adjustment once and not 10 different times in different rules.

                G 1 Reply Last reply
                0
                • T tamorgen

                  @gwp1 ,

                  I really don't have any sort of weekly config on mine. I haven't noticed mine drifting at all, but a weekly recalibrate wouldn't be a bad idea.

                  I have rules for hourly refreshing the the cover, position, and switch positions that are now pretty much legacy of the old device class. I only have two of the IB2 devices left, and they're in non critical rooms ( guest bedroom and mudroom). I'll replace those later this year. Once those are gone, I'll be able to remove those three hourly rules.

                  I have reactions set up for each set of windows in a room. Most rooms only have two windows, so I group those. The lone exception is my family room, where I have four windows, but on different walls. I have those set up on two separate reactions, which allows me to separately set the blinds to a partial open position when the sun is shining directly in. The largest events with the blinds are at sunrise, sunset, and when the house is vacant or someone arrives, when I'll set the reactions from the rule, and I have "Wait for completion" enabled after each call for a reaction. It takes a couple of minutes for all my blinds to open/close when it's called. I initially didn't do this, but iBlinds recommended not calling them all at once (thus the pause in between each call for a blind to open/close). For the most part, this has helped tremendously with the IB2 motors, although they still had their fair share of problems, which is why I've been replacing them all this year.

                  I call the reactions from rulesets, so I don't have to reinvent the wheel each time I want to perform an action on a window. It also allows me to make an adjustment once and not 10 different times in different rules.

                  G Offline
                  G Offline
                  gwp1
                  wrote on last edited by
                  #41

                  @tamorgen we are very much aligned in our approach.

                  • My office has four windows, one front-facing and three smaller side-facing. I group the three together.
                  • My main room covers the single kitchen, single dining room, and two paired living room blinds.
                  • My master bedroom has two paired together, the master bath a single that I do not group with the bedroom.
                  • Guest rooms are single independents.

                  I, too, do reactions for:

                  • open (Day)
                  • close (Evening/Night)
                  • tilt (this is used for Away for all, also for "sun defer" as the sun moves around the house)

                  I do reactions as well for the very same reason: single place to edit. I know @toggledbits will cringe but my "Open ALL" , "Tilt ALL", and "Close ALL" are reactions that contain the other room-specific reactions and are called by rulesets.

                  I've increased my delays again back to 00:00:05 (was down to 00:00:02) just to see if that may help the initial issue that spawned this topic. I don't need to have all blinds close at once (sure, it would be cool) - it's still fun for guests when the actions start in the office at the front of the house and just file their way around until all are completed.

                  *Hubitat C-7 2.4.1.177
                  *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                  *HASS 2025.6.0
                  w/ ZST10-700 fw 7.18.3

                  *Prod MSR in docker/portainer
                  MSR: latest-25139-fbd67abc
                  MQTTController: 25139
                  ZWave Controller: 25139

                  1 Reply Last reply
                  0
                  • G gwp1

                    @toggledbits we have fail!

                    Added two more iblinds to the test. They failed to respond so I isolated one of them and did the following tests on node 8-0:

                    LR Left OPEN: cover.open
                    LR Left CLOSE: cover.close
                    LR Left @20: position.set = .80 (resulting in the blind being tilted open 20%, "top inside").

                    Results:
                    cover.open = iblind opens, position of 50
                    cover.close = iblind moves to position of 50 <---expected result, position 0
                    position.set = iblind moves to position of 80

                    As this Reaction was to run BOTH left and right blinds I removed the right blind and ran the left solo as the kitchen and DR are (both still working fine, btw). For reference, Kitchen was existing unit and was re-interviewed to be current, DR is a brand new unit. LR's are existing units re-interviewed.

                    Log forthcoming.

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

                    @gwp1 said in [SOLVED-ish] New iblind and zwaveJScontroller/MSR not communicating:

                    Log forthcoming.

                    Looked at the log. ZWaveJSController is consistently, correctly issuing the right commands and values for all actions in every case. ZWaveJS is responding with a successful acknowledgement of the command, and later passing an update notification with the node's position having a value consistent with the command previously given in every case. It appears that ZWaveJS understands what MSR is asking it to do, sending that to the device, and the device is sending back updates indicating it has done what has been asked. If that's not what the device actually does, then I assert it's firmware or hardware issue with the device.

                    The log contains errors for an attempt to refresh (using the zwave_device.refresh action) non-existent node 7 (that is, ZWaveJS reports that the node doesn't exist; the entity may still exist as a zombie). That has no effect operationally, just bringing to your attention that after excluding/including devices, you may have missed a now-dead entity.

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

                    G 1 Reply Last reply
                    0
                    • toggledbitsT toggledbits

                      @gwp1 said in [SOLVED-ish] New iblind and zwaveJScontroller/MSR not communicating:

                      Log forthcoming.

                      Looked at the log. ZWaveJSController is consistently, correctly issuing the right commands and values for all actions in every case. ZWaveJS is responding with a successful acknowledgement of the command, and later passing an update notification with the node's position having a value consistent with the command previously given in every case. It appears that ZWaveJS understands what MSR is asking it to do, sending that to the device, and the device is sending back updates indicating it has done what has been asked. If that's not what the device actually does, then I assert it's firmware or hardware issue with the device.

                      The log contains errors for an attempt to refresh (using the zwave_device.refresh action) non-existent node 7 (that is, ZWaveJS reports that the node doesn't exist; the entity may still exist as a zombie). That has no effect operationally, just bringing to your attention that after excluding/including devices, you may have missed a now-dead entity.

                      G Offline
                      G Offline
                      gwp1
                      wrote on last edited by gwp1
                      #43

                      @toggledbits Node 7-0 has cleaned itself up in MSR (it was cleared out in HA's ZWJSC). I got the same from the logs, was hoping you would see something I missed.

                      The firmware is on the latest. I'll doublecheck the firmware on the ZWave Stick that runs these from HA. Thanks @toggledbits, as usual.

                      Updating this thread to [SOLVED] as whatever the issue may be it's not MSR's.

                      *Hubitat C-7 2.4.1.177
                      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                      *HASS 2025.6.0
                      w/ ZST10-700 fw 7.18.3

                      *Prod MSR in docker/portainer
                      MSR: latest-25139-fbd67abc
                      MQTTController: 25139
                      ZWave Controller: 25139

                      1 Reply Last reply
                      0
                      • G Offline
                        G Offline
                        gwp1
                        wrote on last edited by
                        #44

                        A final update here... adding in a minimum of 00:00:05 delays has resolved the issues.

                        *Hubitat C-7 2.4.1.177
                        *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                        *HASS 2025.6.0
                        w/ ZST10-700 fw 7.18.3

                        *Prod MSR in docker/portainer
                        MSR: latest-25139-fbd67abc
                        MQTTController: 25139
                        ZWave Controller: 25139

                        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

                        • Gradually turn on lights.
                          G
                          gwp1
                          0
                          4
                          132

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

                        • Error After Upgrade
                          G
                          gwp1
                          0
                          4
                          103

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

                        • 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