Got a rule that upon motion sets a couple dimmers, i.e. turn on at the level specified.... Used to work fine, didn't change anything in the logic, but at some point in the not too distant past (weeks not years) it stopped working. Have done a couple updates without noticing when it stopped working so reverting is challenging. Only thing I can think of is "Dim" is no longer turning on the dimmer as well as setting level... which is what it used to do. Any suggestions?
Tried to duplicate.. using only one dimming device...
app:466 2021-05-24 09:34:34.617 am info Action: END-IF
dev:336 2021-05-24 09:34:34.600 am info pseudoDimmer is Off
app:466 2021-05-24 09:34:34.589 am info Action: Off: pseudoDimmer
app:466 2021-05-24 09:34:34.585 am info Action: ELSE-IF (pseudo Motion inactive(T) [TRUE]) THEN
app:466 2021-05-24 09:34:34.570 am info Action: Dim: pseudoDimmer: 12 (skipped)
app:466 2021-05-24 09:34:34.567 am info Action: IF (pseudo Motion active(F) [FALSE]) THEN (skipping)
app:466 2021-05-24 09:34:34.536 am info BikeSquid Triggered
app:466 2021-05-24 09:34:34.527 am info BikeSquid: pseudo Motion motion inactive
app:466 2021-05-24 09:34:26.856 am info Action: END-IF
app:466 2021-05-24 09:34:26.851 am info Action: Off: pseudoDimmer (skipped)
app:466 2021-05-24 09:34:26.845 am info Action: ELSE-IF (pseudo Motion inactive(F) [FALSE]) THEN (skipping)
dev:336 2021-05-24 09:34:26.820 am info pseudoDimmer set to 12 level
app:466 2021-05-24 09:34:26.807 am info Action: Dim: pseudoDimmer: 12
app:466 2021-05-24 09:34:26.801 am info Action: IF (pseudo Motion active(T) [TRUE]) THEN
app:466 2021-05-24 09:34:26.771 am info BikeSquid Triggered
app:466 2021-05-24 09:34:26.744 am info BikeSquid: pseudo Motion motion active
Ah, well so are mine,... problem I didn't make clear is the lights don't in fact come on....
OK, so new info, one of the two dimmers seems to be lost in the zwave network... i.e. won't respond to repair or refresh.
So I can swap out the switch which should resolve that, but why didn't the working light come on?? I've removed the broke one from the rule, now the remaining light does respond as expected. But shouldn't the rule be able to work around a non-responsive device??
Thanks for the input gentlemen.
Any suggestions short of replacing the unresponsive dimmer (now showing "pending" after attempting a refresh... it 'failed' to be repaired.
Shut down the hub cleanly to red light (settings, shutdown), power off the hub at the mains wall plug (not at the hub micro USB, which is fragile and can break the solder joints to the PC board). After 30 sec, reapply power, let hub boot. This is the only way to power down reset the Z-Wave radio.
If the problem dimmer has an air gap to remove its power, do that so the dimmerās Z-Wave radio will reset.
Then, if the problem dimmer doesnāt respond from its Devices page, exclude it, then factory reset the dimmer (varies from manufacturer to manufacturer), include back.
If it still doesnāt work, then it probably needs replacing.
There's a potential step before that that I've used a few times.. to use ZWave Replace.
On a C-7 in the ZWave Details page, the faulty device should have a replace button. It's designed to do just that.. to replace a dead device with a new, but of course it works just as well for replacing the same device. You do have to reset the device, but without Excluding it. Then the Replace will work. I did this on Friday, for example. I clicked replace and then clicked the device into Include and it worked for me.
Tried both suggestions, no love... @csteele - interesting, but I get yet another error
"Replace is NOT Running.
status: failed"
I tink I be grabbin' a spare dimmer man!
However, I wonder if this highlighted a bug in the C-7 code where an unresponsive device stops a rule from executing on other working devices that share the rule?
Possible, but not likely. It just doesn't sound like a rare event. Anyone with a weak mesh would trip over this and thus I'd expect to "hear more" in this forum.
I've used Replace at least a dozen times... most of those were back when it was first offered. But like I said, as recently as Friday. It worked first time for me Friday and I must admit I was unprepared. I circled back to click Replace a second time and it wasn't there... only then did I realize it had worked. I think that means I'm used to it taking a swing or two.
Well I take plenty of swings but maybe that advice will help someone else. In this case I tried replace from a pc and an android interface. Both resulted in the same outcome,... twice,... on each interface.
In the end I did a forced remove on the device, and just before replacing it, tried and succeeded in re-including it, so I'll call this solved.
I circled back to click Replace a second time and it wasn't there... only then did I realize it had worked. I think that means I'm used to it taking a swing or two.
