How to send zwave ALL ON and ALL OFF?

Simple question here… how does one send the zwave ALL ON and ALL OFF commands? (Typically used for alarms or other “oh crap” situations.)

Put all your zwave items in a group called gAll, then do

gAll.send command(ON)

No… That would send ON to all items in the group - it doesn’t use the ZWave SWITCH_ALL class which I think is what is requested.

I’ve not tried this myself since I don’t tend to use this class, but I think you should be able to use command=switch_all on any device since its ultimately a controller method…

Give it a try and let me know if it works.

Chris

I was going to say that’d create one heck of a zwave radio storm! :slight_smile: (big network!)

You’re right, the switch_all class is what I’m after. I’ll give it a go and update.

Well, none of these work…

                sendCommand(LAUNDRY_LIGHT,switch_all)
                sendCommand(LAUNDRY_LIGHT,SWITCH_ALL)
                sendCommand(LAUNDRY_LIGHT,switch_all_on)
                sendCommand(LAUNDRY_LIGHT,SWITCH_ALL_ON)

…any other ideas? :wink:

I would have thought just ON and OFF were valid commands in a rule - as with any switch?

ON and OFF just switch that light on. Looking for how to send switch_all_on and switch_all_off zwave command.

Yes, but the converter should convert the command to the correct command class for the item. You still need to use a valid command :wink:

I’m very lost as to what you’re saying. What are you proposing I send to whom?

Ok - let’s start from the beginning…

  • You need to set up an item, with a configuration string that connects a zwave device with the command class - as I showed earlier. As I said, I’ve not tried it, but I think it should be command=switch_all and it can be attached to device as ultimately it gets linked back to the controller in the converter.
  • You can then connect this item to a sitemap widget, or use it in a rule
  • If you use it in a rule, then it needs to use a valid command type (On/Off, or a number, or Up/Down - whatever). It’s the same with any command you send in OH.
  • If you use it on a sitemap, then you are probably best to use a Switch widget, and this will send the ON/OFF commands the same as the rule.

Does that make sense? If not, maybe my first point above with the item config is wrong…

Ahhhh, that was the part that I wasn’t getting. I decided to set up an item and attach it to the zwave controller itself, just a simple switch…

Switch TEST_SWITCH_6 "Test virtual switch 6" (Group_Test) {zwave="1:0:command=switch_all"}

Flipping that on and off, eventually seems to send the all on (and all off) commands, but it’s definitely upsetting the apple cart…

2016-04-22 18:06:06.040 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 22: Timeout while sending message. Requeueing - 2 attempts left!
2016-04-22 18:06:06.041 [ERROR] [b.z.i.p.s.SendDataMessageClass:158 ]- NODE 22: Got an error while sending data. Resending message.
2016-04-22 18:06:11.070 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 49: Timeout while sending message. Requeueing - 2 attempts left!
2016-04-22 18:06:11.071 [ERROR] [b.z.i.p.s.SendDataMessageClass:158 ]- NODE 49: Got an error while sending data. Resending message.
2016-04-22 18:06:16.102 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 31: Timeout while sending message. Requeueing - 2 attempts left!
2016-04-22 18:06:16.103 [ERROR] [b.z.i.p.s.SendDataMessageClass:158 ]- NODE 31: Got an error while sending data. Resending message.
2016-04-22 18:06:21.170 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 12: Timeout while sending message. Requeueing - 2 attempts left!
2016-04-22 18:06:21.171 [ERROR] [b.z.i.p.s.SendDataMessageClass:158 ]- NODE 12: Got an error while sending data. Resending message.
2016-04-22 18:06:26.234 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 20: Timeout while sending message. Requeueing - 2 attempts left!
2016-04-22 18:06:26.235 [ERROR] [b.z.i.p.s.SendDataMessageClass:158 ]- NODE 20: Got an error while sending data. Resending message.
2016-04-22 18:06:31.264 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 19: Timeout while sending message. Requeueing - 2 attempts left!
2016-04-22 18:06:31.265 [ERROR] [b.z.i.p.s.SendDataMessageClass:158 ]- NODE 19: Got an error while sending data. Resending message.
2016-04-22 18:06:31.303 [ERROR] [eController$ZWaveReceiveThread:1546]- Protocol error (CAN), resending
2016-04-22 18:06:36.405 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 13: Timeout while sending message. Requeueing - 2 attempts left!
2016-04-22 18:06:36.406 [ERROR] [b.z.i.p.s.SendDataMessageClass:158 ]- NODE 13: Got an error while sending data. Resending message.
2016-04-22 18:06:41.437 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 48: Timeout while sending message. Requeueing - 2 attempts left!
2016-04-22 18:06:41.439 [ERROR] [b.z.i.p.s.SendDataMessageClass:158 ]- NODE 48: Got an error while sending data. Resending message.
2016-04-22 18:06:46.561 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 33: Timeout while sending message. Requeueing - 2 attempts left!
2016-04-22 18:06:46.562 [ERROR] [b.z.i.p.s.SendDataMessageClass:158 ]- NODE 33: Got an error while sending data. Resending message.
2016-04-22 18:06:51.592 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 18: Timeout while sending message. Requeueing - 2 attempts left!
2016-04-22 18:06:51.594 [ERROR] [b.z.i.p.s.SendDataMessageClass:158 ]- NODE 18: Got an error while sending data. Resending message.
2016-04-22 18:06:56.623 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 53: Timeout while sending message. Requeueing - 2 attempts left!
2016-04-22 18:06:56.624 [ERROR] [b.z.i.p.s.SendDataMessageClass:158 ]- NODE 53: Got an error while sending data. Resending message.
2016-04-22 18:07:01.654 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 36: Timeout while sending message. Requeueing - 2 attempts left!
2016-04-22 18:07:01.655 [ERROR] [b.z.i.p.s.SendDataMessageClass:141 ]- NODE 36: Node is DEAD. Dropping message.
2016-04-22 18:07:06.658 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 26: Timeout while sending message. Requeueing - 2 attempts left!
2016-04-22 18:07:06.659 [ERROR] [b.z.i.p.s.SendDataMessageClass:158 ]- NODE 26: Got an error while sending data. Resending message.
2016-04-22 18:07:11.690 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 51: Timeout while sending message. Requeueing - 2 attempts left!
2016-04-22 18:07:11.691 [ERROR] [b.z.i.p.s.SendDataMessageClass:158 ]- NODE 51: Got an error while sending data. Resending message.
2016-04-22 18:07:16.847 [ERROR] [WaveController$ZWaveSendThread:1347]- NODE 30: Timeout while sending message. Requeueing - 2 attempts left!
2016-04-22 18:07:16.848 [ERROR] [b.z.i.p.s.SendDataMessageClass:158 ]- NODE 30: Got an error while sending data. Resending message.

Keep in mind these are devices that under normal use never (or nearly never) have communications problems (except node 36 – that’s unplugged right now). Which devices time out are not consistent and change every time. I’m thinking that since I have a large number of devices that send HAILs whenever they change state that despite using one command to switch them all on/off I’m creating a radio typhoon switching them all on/off. i.e. “nice idea, but it sucks.” Oh well, had to try! Thanks for the help!

Without seeing the debug log I can’t really say what might be happening. This command though will send separate messages to every node on the network that supports the switch_all command class, so it will result in your ‘radio storm’ in any case.

It might be possible to send it as a broadcast, but broadcasts aren’t routable so it would only work to some devices. Additionally, broadcasts aren’t reliable in that there’s no ack (and thirdly, I’ve not tried it so I’m not completely sure it would work :wink:).

Anyway, if you want to send a debug log Ill take a look and see if there’s anything that can be improved.