Michel Kohanim

@asbril, Are those devices that don't communicate battery devices? With kind regards, Michel

@gdingus, I am so very sorry to hear. Have you tried positioning ISY vertically with LEDs facing down? If the Z-Wave heal completes and if you still have problems, then it seems that the routes are not recreated properly. With kind regards, Michel

Hi @smokegrub, I have asked @bmercier to chime in. With kind regards, Michel

@apostolakisl, can you please let me know what node servers you are running and the size of your log (especially the error log)? Or, better yet, can you please send your error log and log to support@unviersal-devices.com? Thanks and with kind regards, Michel

@drprm1, Ok, thank you. Please keep us posted. With kind regards, Michel

@drprm1, Please check your junk mail. Also, why would you have time outs for sending emails? The bottom line is that it seems that you might have a program running in an infinite loop. If you can login, check your programs. With kind regards, Michel

@asbril, Yes, you can turn query on restart back on . With kind regards, Michel

Hi Teken, Haven't heard back. With kind regards, Michel

Hi smokegrub, Something like this: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration_V3#Instructions_for_using_Multiple_ISYs_with_one_Echo_Accout With kind regards, Michel

Hi Jim, Let me try again: ISY Query != Program.QueryAll ISY Query (right mouse click on node | Query), queries EVERYTHING including properties. Program.QueryAll only queries the status (ST) and NO properties. So, if you do not have Query at boot up enabled, all you get is ST and NO properties (on level). With kind regards, Michel

Nooooo. Query all program only queries status of devices. It does NOT query properties such as on level. With kind regards, Michel

Hi Jim, Correct. Query All only queries status. You need to manually query the device. And it should be enabled at Startup. With kind regards, Michel

Hi Jimbo, 3AM query only queries the status. What are you querying? With kind regards, Michel

@Scott847, yes it is safe. @Atitus713, in that case your old Z-Wave dongle is probably bad. What I suggest is to reboot with the old dongle and then do Z Wave/ Tools / Synchronize nodes / All. If your ISY Z-Wave nodes are removed then your old Z Wave dongle is empty. With kind regards, Michel

@Scott847, Cannot reproduce. It's probably routing related. @Atitus713, did you backup your old Z-Wave dongle? With kind regards, Michel

Hi Jimbo, Please query your device. It might be that the on level is set to 0. With kind regards, Michel

HI @drprm1, I responded to your ticket. With kind regards, Michel

Hi Bill, Have you taken a look at the error log? With kind regards, Michel

Hi firstone, You are 100% correct and that's precisely what I suggested (i.e. without using hints). The only reason for using compliance is because we also have to do solar/storage inverters and EVs (for our CEC project). They have no commands and have nothing to do with Alexa. So, I prefer having a comprehensive portal solution for node servers (including the could polyglot) rather than just a one-off for Alexa. I'll discuss with @bmercier when he's back from his well deserved vacation. With kind regards, Michel

@firstone, Once we agree on the compliance layer, than we'll implement the same in the Portal (without using hints). With kind regards, Michel

Hi @pjjameso, Have you tried to position ISY vertically? Yes we will get those devices and test. With kind regards, Michel

Hello everyone, Thanks for all the feedback. Security must be considered first and foremost in this day and age. There are no excuses for doing anything else. Benoit has already looked into 2FA and we should have it working by YE. With kind regards, Michel

Hi @kevindavis544, Please send your uuid to support@universal-devices.com. With kind regards, Michel

Thank you all. Can you please disable and then enable the skill and then let me know whether or not you see any improvements? Thanks and with kind regards, Michel

Thanks everyone. If it's happening on both firmware version branches, then definitely related to Echo itself. Have you looked at history to see what Echo is hearing? With kind regards, Michel