forum

Application Status or Application Busy is a Command Class that allows the device to inform the sender (controller) that it is busy. It's ID is 0x22 (you should find it in the NIF). You can check Online Manual (https://github.com/Z-Wave-Me/Z-Way-Manual/blob/master/zwayDev.pdf) chapter 8.51 What means...

This is "by design" - according to the Z-Wave standard for multichannel devices there is a mapping of first channel to the "root device". This lead to one more device on the screen. Please check http://z-uno.z-wave.me/Reference/Z-Wave/#Channels for more info. It explains that the...

Please update to the latest stable (go in Maintainance -> Firmware upgrade)

Please send us the log of inclusion

You can use AutoOff. It already does what you need. To still help you with your code: 1. You should not do devTimerSwitch.on inside the handler. Do it outside. Otherwise you subscribe many times. 2. Unsubscribe from it only on module stop. 3. Also unsubscribe on stop from the binding of Z-Way object...

You need to use standard TRIAC modules like with Arduino. we have such h a module

In brief you should trap zero cross interrupt, wait a bit depending on the dim level, turn on the TRIAC control PIN and the turn it off

ghrayfahx wrote: ↑

24 Jul 2017 05:37

Also, what is required for S2? I have a My Cloud and the UZB for it. I have a lock that isn’t learning in properly and I’m hoping some updates fix that.

Your lock is 100% not S2 yet, so nothing will change here. What kind of lock do you have and what problems?

brianaker wrote: ↑

24 Jul 2017 04:00

Does V3 work with S2 at this time?
I do have a raspberry attached to z-wave bridge controller but it is joined as an S2 device.

Yes, it does work as S2 primary controller and S2 seconddary. But we have not made enough tests yet. Use it on your own risk

Yes. RaZberry and WD usually comes one after another. v2.3.5 will be released soon.

As for v3.0.0, it will be availble only RaZberry only unless people really want to test it on other platforms. For this you need to have S2 devices.

Please clean notifications.json.