G W Posted December 14, 2017 Posted December 14, 2017 When the module is included, three nodes are created. The parent node: ZW 017 On-Off Power Switch And two child nodes: ZW 017.1 On-Off Power Switch ZW 017.2 On-Off Power Switch When the parent node is turned on, the two child nodes should be turned on. However, when you tell the ISY to turn on the parent node, only child node 1 is turned on yet it does not show on. Child node 1 has to be queried to see that it is on. A hub such as SmartThings has no issues in controlling the child nodes and showing proper status. Best regards, Gary Funk
Chris Jahn Posted December 14, 2017 Posted December 14, 2017 Hi Gary, I don't think turning on the parent node is supposed to turn on both lamps, did you find some documentation for that somewhere or is it just wishful thinking By observation, the root node (ZW 017) appears to just be a non-multichannel version of Node channel 1 (ZW 017.1). The root node also supports a few more command classes. The real issue is: Without custom code for the device, is it possible using the information provided by the device to determine that both the root node and channel 1 node are actually controlling the same on/off switch. I've opened up a bug report for this, and its not clear to me that its possible without custom code.
G W Posted December 14, 2017 Author Posted December 14, 2017 Chris, I added the switch in SmartThings (the same way it's added in ISY) and a Wink and no custom code. Turning on the parent node turns on both outlets. Now, I know ISY isn't SmartThings & Wink and SmartThings & wink aren't ISY. That be accepted, I would expect ISY to operate the same way as SmartThings and Wink as neither use custom code to control the module.
Chris Jahn Posted December 14, 2017 Posted December 14, 2017 Just curious, how do you know they aren't using any custom code?
G W Posted December 14, 2017 Author Posted December 14, 2017 The frimware in the hubs was written before the modules were built. And on SmartThings I haven't added any code to control the module. That being said, I don't know.
Chris Jahn Posted December 14, 2017 Posted December 14, 2017 The Inovelli guys actually did write a custom driver for the device for SmartThings. I don't want to get into a big argument here, but from everything I have read about the device and how others have integrated it, we pretty much need custom code to get the behavior you are requesting.
G W Posted December 14, 2017 Author Posted December 14, 2017 And I'm certainly in no position to argue otherwise.
G W Posted December 14, 2017 Author Posted December 14, 2017 I continue to have discussions with Eric and hopefully one of us will will figure out what I'm doing wrong.
asbril Posted December 14, 2017 Posted December 14, 2017 The good news is that both ISY and Inovelli have excellent customer friendly spirit. This will be worked out eventually.
G W Posted December 14, 2017 Author Posted December 14, 2017 The good news is that both ISY and Inovelli have excellent customer friendly spirit. This will be worked out eventually.I agree. The customer support is great. Eric has been extremely responsive and open. I looking forward to adding many new Z-Wave devices in 2018 and will look to Inovelli first.
G W Posted December 17, 2017 Author Posted December 17, 2017 Michel, Chris, Does ISY support "Switch All?"
asbril Posted December 17, 2017 Posted December 17, 2017 Michel, Chris, Does ISY support "Switch All?" There have been comments in one of the ISY forums that right now the "switch all" does not yet work with ISY. However, the team is working with Inovelli, though most likely this is not a high priority for ISY. I have the switch, like it but I can confirm that the "switch all" is not yet operational.
G W Posted December 17, 2017 Author Posted December 17, 2017 Hi, asbril, That's why I'm asking. I'm working with Eric at Inovelli and that's what we have decided is preventing the parent node from operating properly.
asbril Posted December 18, 2017 Posted December 18, 2017 Hi, asbril, That's why I'm asking. I'm working with Eric at Inovelli and that's what we have decided is preventing the parent node from operating properly. ok
Michel Kohanim Posted December 18, 2017 Posted December 18, 2017 Hi Gary, Don't know what Switch All is. This said, we already exchanged many emails with Eric and his staff. They have custom code for other hubs. That the moment, what we have is what it will be. With kind regards, Michel
G W Posted December 18, 2017 Author Posted December 18, 2017 Hi, Michel, Switch All is a Z-Wave command class and I've found its used by Aeon, Enerwave, Inovelli, SmartThings and Vera, just to name a few. Best regards, Gary Funk
Chris Jahn Posted December 18, 2017 Posted December 18, 2017 HI Gary, Switch All is an obsoleted Z-Wave command class used to switch all devices on or off. New devices are actually forbidden from supporting it. Edit: I just took another look at their script, and they actually do use All On / Off, and then query each of the channels independently. We may be able to support this.
G W Posted December 18, 2017 Author Posted December 18, 2017 Chris, It would be nice if everyone at UDI got on the same page. As for being obsolete, I found nothing in my searches to indicate such. Best regards, Gary Funk
Chris Jahn Posted December 18, 2017 Posted December 18, 2017 Chris, It would be nice if everyone at UDI got on the same page. As for being obsolete, I found nothing in my searches to indicate such. Best regards, Gary Funk 4.1 All Switch Command Class, version 1 [OBSOLETED] THIS COMMAND CLASS HAS BEEN OBSOLETED New implementations MUST NOT support this Command Class. Controlling nodes MUST use S2 Multicast mechanism in order to achieve the All On and All Off functionality
G W Posted December 18, 2017 Author Posted December 18, 2017 4.1 All Switch Command Class, version 1 [OBSOLETED] THIS COMMAND CLASS HAS BEEN OBSOLETED New implementations MUST NOT support this Command Class. Controlling nodes MUST use S2 Multicast mechanism in order to achieve the All On and All Off functionality EDIT: I found it here. http://z-wavepublic.com/sites/default/files/command_class_specs_2017A/SDS13781-4%20Z-Wave%20Application%20Command%20Class%20Specification.pdf However, I didn't find anything that states controllers must not use the command to support hardware built before 6 October 2017. Therefore this is something that ISY should support. Best regards, Gary Funk
Michel Kohanim Posted December 18, 2017 Posted December 18, 2017 Become a member, sign their NDA, sift through the specs, and then you will find it. In the meantime, please let us get back to work instead of all this back and forth. Michel
G W Posted December 18, 2017 Author Posted December 18, 2017 Become a member, sign their NDA, sift through the specs, and then you will find it. In the meantime, please let us get back to work instead of all this back and forth. Michel Hi, Michel There wouldn't be any back and forth of you were just honest and forthcoming with information. By-the-way, your indignation is noted. Best regards, Gary Funk
Recommended Posts
Archived
This topic is now archived and is closed to further replies.