[SOLVED] New iblind and zwaveJScontroller/MSR not communicating
-
@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.
@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
reactionsas well for the very same reason: single place to edit. I know @toggledbits will cringe but my "Open ALL" , "Tilt ALL", and "Close ALL" arereactionsthat contain the other room-specificreactionsand are called byrulesets.I've increased my
delaysagain 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. -
@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
node8-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 of50
cover.close= iblind moves to position of50<---expected result, position0
position.set= iblind moves to position of80As this
Reactionwas 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.
@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.refreshaction) 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. -
@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.refreshaction) 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.@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. -
T toggledbits locked this topic on
