CH491

UPDATE: Close issue as I restore a backup to my IoP and it is back up and running. That was weird like the remove (z-wave device) must have somehow corrupted my IoP. When I came back on-line I sync'd ALL Z-wave devices with the dongle, and the two devices I was trying to delete where no longer on the dongle but still in IoP. But in sync now and looks okay.

I was having problem so removed a device and now the Z-wave dongle is not responding after multiple reboots. IoP 5.4.4 with Zooz Dongle

I have also confirmed that the change_on_pon is not working in PG3 - LiFX Node server. The logs appear to not show the detection and turning on of the feature. In PG2 the log shows this by logging LOGGER.debug('Change of color won\'t power bulbs on') this is not being executed under PG3 so I will have to check with devs if the parameter readings in PG3 differ or if there is a bug from the port into PG3.

I am aware of your post but not sure what I can do to help. Mine is still working fine with the setup above but I have not upgraded to 5.3.0 yet. I will have to look but this would be an issue for the ISY team. I am just a user

Sorry for the delay. I have upgrades to v5.0.16C(RC1) and Z-wave Firmware at v4.55. The Doorbell is added and installed correctly now. :) There are 8 'sound switches' detailed in the manual for separate purposes. (Sound Switch 3 is Door Button 1) you can set the volume and default tone from the manual there are 30 preloaded tones. Once installed you can use the doorbell as a responder to scenes so you can use the speaker as a output device for your events and programs. (i.e. play a tone when a door scenes open, or siren in an emergency, trust me 100% volume is LOUD my dog hates me). Of course, the main use would be for the Door Button to set off a chime (normal doorbell operation). That works no problem. However here is where you might not like it. You currently cannot use it as a scene controller (Trigger a scene when pushed). That being said, you can write a program that checks the value of "current tone". (by matching the tone number number 1-30). So I have my doorbell button 1 set to tone 4. I then have a program that says if sound switch #3's (Button1's) current tone = 4 (meaning it is playing the sound) then run the program 'then' code and when the tone is done (quick play) it will run the 'else' I added a wait in the else so it waits 30 second before running the command. So you can use the button as a "trigger". Now here is a weird part. When push the button right away ISY reports (Main Tab - Sound Switch #3) Default Tone = 4 is playing. But the program with the if clause takes 6-8 seconds to start the program. I am not sure why the delay. So that is what I have for you or anyone the wants to use the AeoTech Doorbell 6 with an ISY ISY944i ZW+ Please comment if you have any information regarding the delay please let me know.

I noticed that (after you mentioned it - TY). I was previously testing on 5.0.15 so this weekend will be a upgrade and test.

I had put it (Aeotec Doorbell 6) away and waited for an update. If you have read about it in a new release I will try it out again this week and will let you know.

I was excited to purchase the 2nd gen Aeotec Doorbell 6. However, when I went to add it to my Z-Wave network it did not correctly identify and setup the device on my ISY944i ZW+. I reached out to Aeotec about when to expect support. They were amazingly quick to reply. In hopes to find out about ISY Support I am posting their reply. "You will need to reach out to ISY support to determine if they plan to further support Doorbell 6 into their Z-Wave gateway. The commands needed to be supported to maximum controls are Multichannel Command Class with Sound Switch Command Class." Do we know if and when these new ZWave objects will be added to the ISY Code? NOTE: I did upgrade to 5.0.15A in hopes for support but still not there. Please Advise, Chad