Fair enough. . .and a valid warning. My plan around that is to only have this ever be a off switch with no automation around on. On would only be manual. I was actually checking out some other switches yesterday that seem to have firmware settings you can set that allow that to be enforced at the device level. Not sure what it would take to actually set these options (if ST can do it, and even if so, can I figure it out) so not relying on that.
That may not be foolproof, but if you find a device that can take a setting like that through its firmware that should (probably) prevent random ST cloud problems from flipping the switch on when you didn’t intend it to be.
Assuming you’re talking about a z-wave device, if there’s no setting in the device handler, you could use the z-wave tweaker device handler. You just temporarily change your switch device to use that handler in the IDE, then go to the device’s settings in the mobile app, change the relevant parameter (which should be listed in the device’s manual), save, and then change back to the normal device handler in the IDE.
Edit: even with the use case you describe, keep in mind that the “off” command might fail to send occasionally because of some issue with your mesh, the hub, ST cloud, etc.
1 Like
Definitely not foolproof but my thinking is as long as I keep it off based, it will be an improvement over having no switch at all. With no switch, if they turn on and walk away, it stays on. That being said, with automation, people tend to get lax with those types of things. For that I just nag them when I discover its been left on which has been pretty effective as I rarely have to do it. To combat the cloud flakiness I have several independent triggers that turn it off. Motion based, time from on based, and leaving the house based. Thanks for the suggestion on the Tweaker, will check that out if needed.
1 Like
states to not use on electric heaters
that manual is revised by lawyers to ward off nuisance suits by idiots that point an old heater at something flammable. Anybody can start a fire with an amp of current to a faulty device or unwatched hazard.
1 Like
In the end I chose the Jasco 12719. It met amp rating, is UL listed, has the lock out on firmware setting, and I have found all my GE/Jasco devices (have many wired switches & 1 outdoor) to be rock solid connection wise as long as they don’t die. Have had 2 devices die but not so sure I didn’t cause it. On the upside Jasco warranty support was solid. I wasn’t aware they had a 15 amp outlet so didn’t even think to check for it. They have a zwave plus device now too but didn’t have great ratings yet and figured the cheaper one would be fine. Thanks all for the help!
Where did you see the info re: configuring that parameter? I have one of those switches but I don’t see it in the manual.
I found it on the Jasco site. I ordered from Amazon so maybe I got a different version, but the model number was the same. If you don’t see on the site let me know and I will grab a link. Just not at a computer atm.
Here it is. Wasn’t in the manual but a support page.
http://www.ezzwave.com/advanced-operation/?_ga=2.134101704.797264886.1509048631-166308169.1509048631
Ah I see.
I’m no z-wave expert, but I think that’s referring to a type of group command to turn on/off (ie a group of devices). I don’t think that will cause the device to ignore all on commands from the z-wave controller.
Anyone who knows more about this than me, please feel free to correct me.
Re-reading it I think you are right. Not ignore all On/Off but specifically All On and All Off commands. I took that to mean you could configure to ignore any sent On command not specifically an All On command. Oh well. . .it still has the other positives I was looking for.
1 Like