ZSE50 Cannot control the color of the strobe only function

Built-In Apps and Drivers Built-in Drivers
1

I've been working on this for a while. I finally reached out to Zooz. See my below message to Zooz. Their reply was they could not replicate this on any other hub but can on the Hubitat hub.

It would be great is the team could review this driver and see what can be done to fix this. I am really hopeful this can be sorted out as I have a number of ideas for this device to report things that happen that the whole family can be notified without having to open a screen.

Regards

John

My message to Zooz:

I have a few ZSE50’s and want to use the strobe. I want to control the color of the Strobe when playing no sound.

I have a Hubitat Hub C8

  • I just update the ZSE50 firmware to 1.4

  • I used Hubitat Basic Z-Wave tool to set Parameter to 7

  • I changed the driver to the Hubitat built in drive

  • I pressed “strobe” button. The device flashed Green (not Yellow as parameter 7 suggests)

  • I used Hubitat Basic Z-Wave tool to verify Parameter was still set to 7, it was.

  • When I play a sound, the light does flash yellow as set by parameter.

  • I also noted, Parameter 7 would not accept a value of 170 (blue)

My question:

Is the strobe color controllable or should I just stop trying?

Thanks

2

Don't suppose they told you what command class they used to activate the strobe that worked with the user-chosen color (and maybe how that was set in case it's not the parameter 7 value), since in my testing no combination of things actually made it respect the color... :smiley:

3

No but I will ask. Another thing they didn't mention, using Basic Z-Wave tool, I could not set parameter 7 to 170, it would take 42 but not 170. I did not spend any time finding the limit.

4

I just sent this eMail:

Hi,

Could you ask your technicians what command class they used to control the strobe light? And what command class they used for reporting power?

Thanks

John

5

Yeah, I think this is an artifact of them (or maybe Hubitat, I really don't know what's normal where here) requiring a signed value, not an unsigned value, so you'll need to convert your values using an algorithm like:

if (value > 127) value = value - 256

Don't ask me how long I got stuck wondering if it was working at all before I figured that much out. :slight_smile:

6

Interesting, not good at this, but I would assume a 1 byte value must be positive.

I know you are very capable when it comes the coding, however I wonder is the Hubitat team will comment on this.

7

They did not answer with a specific command class. They only provide this link Command classes

However in the link I found it odd how the parameter portion of the table, the Description is in DEC but the defaults are shown in HEX. I would have thought the driver would understand this and sent the proper code, but I don't really know.

8

The Hubitat driver uses Indicator V3 Indicator Set. I could not find any combination of indicator value properties that respected the parameter 7 color (it's using 0x03/duration, 0x04/cycle count, and 0x05/on-off time and I don't think I saw any others that might work), which is why I was hoping to hear something specific from them. Maybe they're using Sound Switch with no sound or something to make it just the LED? I do feel like they should know what they tested if they did, or at least how the device should work, but maybe I'll try it with Z-Wave JS UI myself sometime or something and see if I can figure something out... :slight_smile:

It's possible that parameter 6 (LED mode) affects this in ways beyond what is apparent from its description, but I'm pretty sure I tried all combinations and couldn't get anything there, either.