TriLife

Hi Asbril; So, I have deleted the Home App from her phone and reinstalled it. With that, UD disappears from list of the "works with google" items. Although her phone, or her voice should defer to what Google Home has on my account. Bottom line though, once reinstalled and signed on, her Home app immediately sees our household, but continues to say " can't reach Universal Devices". Neither from her phone, not with my voice or hers. Not on the Google Display or other Minis. There is something else fouled up! Im thinking of disassociating my Google account from UD. How do I do this? From within the ISY Portal or from within Google Home? or Both? I know how to disociate it from within Google Home, but not from within UD. Thanks

This is a repeat question, the first time i only got snide remarks! I have an ISY994 and Polisy Pro controlling 100+ SonOff switches by voice. I have scenes, programs and switches. My wife's is a member of the Google household. All was working well until November, when upgraded my Pixel 3a to a 5a. All of a sudden, when my wife asks for a program to be executed, like "hey Google, open sesame" (a program in ISY) the Home Display answers "Sorry, I can't reach universal devices right now"... She can turn on/off lights just fine. When I say the same thing, it works ok. This behavior repeats itself on all Minis and her own phone. I rebooted ISY, Polisy, I added/removed UD to WorksWithGoogle, added/removed the same routine on her phone, retrained Assistant with her voice... Nothing seems to work. All devices in the home have voice recognition enabled. And it was working before. Occasionally, even Strangers can say "open sesame" and the wine cellar opens... Any ideas where to look? cheers

Greetings, Its been a while since I had problems with the Policy/ISY set up. Both me wife and I recently upgraded from older version Pixels to 5a's, Android 12. My integration came after hers (Google Home is registered under me and she's "family" by invite), as before. It used to be that if she or I said Hey Google, good morning", the system would respond "Hi Sweetie" and then play my selection of news, starting with BBC.l (which I chose) Now, when I say it it still does that, but when my wife says it, it says "Hi Heather" and plays Fox News( which she didn't chose)!!!! What makes matters worse, when I say "hey Google, open sesame" on any of the several Google minis and screens and my phone, the wine cellar opens. When my wife tries the same on her phone or any Google Device, it says " can't reach universal devices right now"... This is a major problem, since she is accusing me of restricting her access to the booze!!!!!! She can control all the lights, but can't execute any programs/routines. I dis-invited and re-invited her to the household, and tried to set up the routines on her phone. No dice. The wine cellar is newly one of those open/close items, but the fact that Google Home chooses "Hi Heather" and Fox News instead of my "Hi Sweetie" and BBC, is an indication that it is not the open/close functionality that's causing the problem. All the lights on Policy/ISY show up on her phone's Home Assistant and when I try to add a routine like open sesame on her phone the various programs show up as well. But they don't execute (although on the phone it says "done"). Any ideas? Thanks.

Yup, and getting lots of Oohs and Aahs too. Cheers.

Thanks Geddy, I was heading in that direction, but decided to try an another approach (see above), which fixed the problem...

Thanks MrBill. The hangup seems to occur at GH. It didn't understand "Turn Off Sesame"... I have the solution now, albeit a bit cumbersome. It would be great though, if @bmercier could explain how to use the new OPEN/CLOSE syntax... Will ping him at UD

Here is the solution: 1- Write 2 separate programs in ISY, one for OPEN SESAME, the other for CLOSE SESAME 2- In the ISY PORTAL/GOOGLE HOME, add PROGRAMs OPEN SESAME and CLOSE SESAME as SCENES. Refresh and Upload to GH... 3- In your GH app, add a Routine, responding to "Open Sesame" Starter and as an Action, pick ADJUST SCENES (Open Sesame shows in the drop down). This, instead of TRY ADDING YOUR OWN ("Turn off Sesame")... Repeat for "Close Sesame". This fixed the problem. Thanks for everyone's quick response here.

Thanks Mr. Bill. I already tried that. It seems that it only refuses to do the Shut/Close command (TURN OFF Sesame) that refer to PROGRAMS in ISY. It has no problem executing a TURN OFF Garage Light. Also, when in the Portal, I change the GH Category from SCENE to DEVICE WITH OPEN/CLOSE SYNTAX, Open Sesame command fails to respond as well...

Both RUN IF and RUN ELSE execute properly from within the Console

Thanks! Yes, the ISY is running 5.3.0. I upgraded it from 5.0.16C and did a bunch of work to get it all running again. Including opening and closing Sesame... In order to delete old verbal commands, you hit the red X inside the Google home portion of the ISY Portal. Indeed, it seems to be sufficient to do the Refresh in the ISY Portal to pass console updates to the portal. Hasn't fixed my Close Sesame problem yet though... Thanks

5.3.0

Greetings; I have this really nice cirdular wine cellar with a glass top, which responds to the Google Command, wait for it... "Open Sesame!" and it used to also respond to "Close Sesame". Well, a few days/weeks ago, while it continues to let me get my wine, it refuses to close... ("sorry I don't understand" says google, even from the Home app, sans voice). The glass trap door is driven by an DC linear actuator, which requires me to toggle +/-. I have a Plus Cellar and a Minus Cellar switch, from a Sonoff QUAD (the other two drive light and circulation fan). And, I have a Program in ISY, called SESAME, which has no IFS. In the THEN section flips the switches to open the trap, waits 30secs and turns the switches off - and in the ELSE section closes the trap, waits a 30 secs and tursn the switches off (30 secs to give the actuator time to do its job). (it also turns the fan off and the lights on and vice versa) I then have Google Home routines, OPEN SESAME, which issues the command TURN ON SESAME and the reciprocal CLOSE SESAME, which issues the command TURN OFF SESAME. This CLOSE SESAME IS NOW BROKEN! It opens, but doesn't close. When I have the google routing turn off a switch to the same CLOSE SESAME, it works. I tried renaming and deleting the program in ISY. No cigar. I tried refresh in the Portal, multiple Push to Googles, no dice. It seems to be related to the fact that Im trying to control a program with Google Home, instead of a switch. As I was playing with the SESAME program in the ISY Portal (Select Tool/Connectivity/Google Home), I noticed DEVICE WITH OPEN/CLOSE SYNTAX... This lead me to: The timing on this post and the failure of my system is close enough that I'm thinking this new functionality might be the cause of my torment. Can you please shed some light on this new feature and maybe give me a hint on how I can reconfigure my program to work with this new OPE/CLOSE sytanx thingy? Cheers; Oh, and BTW, if I make a change in the ISY admin console, How do I push it to the ISY Protal, without logging off and logging on again? Thanks

I think the issue is with ISY 5.3.0 not supporting Security 2 yet, as indicated in the pop up window for Z-wave (see attached. In any case, as mentioned by many others and just confirmed in my installation, connecting the AeoTec MS in non-secure mode significantly speeds up the response time and seems to strengthen the meshing. Unless you have a very strong case for encryption, I'd skip it. Cheers.

Good morning! Where are we with the ISY to Polisy migration? Do we have a Z-wave solution yet? Custom Dongle vs, off the shelf? Also, I read in a previous post in this thread that ELK support is already available as a Nodeserver. Can I move this easily from ISY to Polisy without too much trouble? Any how-to-move documents available? Thanks

Awesome! Thanks G. This is exactly what I was looking for all this time. I did a complete reset of my ISY and started from scratch, but as luck would have it, the 5th and node didn't sync up correctly and I had to redo it, assigning node21 the second time around. I will delete 21 and follow your instructions on repopulate node5. Made my day!

Thanks Michel; Since I don't know what SIS is, I proceeded as explained in the post above. All seems to work now. And faster too, since I paired without Security... Cheers

Hello Broyd; Wow, lots of work. Thanks for that. I ended up bringing the ISY out of the IT closet and next to my desk, reset the Z-Wave dongle and added the new set of MultiSensors in one go. Then swapped the newly assigned ones with the ones in the ceiling. After that, I upgraded the firmware of the MS's to V1.14 and continued adding them to the ISY. These will go to the new locations. That way I only had to climb and move the ladder once... To answer your question: I was able to reset ISY's Zwave dongle only, by Z-Wave->Advanced->Factory Reset Z-Wave Dongle. It reset all the node numbers, deleted the references in the various programs and replaced them with relevant Notes, so you can recreate the conditional statements with the new node numbers. Cheers;

Good afternoon. So, I recently upgraded to the newest Z-wave Dongle in the ISY and updated the ISY to 5.3.0. Since I'm adding a lot of AeoTec MultiSensors and they latest rev is V1.14, I figured I'll upgrade the existing ones too and do a reset of the Z-wave Dongle. ISY at present doesn't allow OTA firmware upgrades to Z-wave, so I have to use the Z-wave Stick by AeoTec for this. @lilyoyo1 suggested that I add the AeoTec stick as a secondary controller to the ISY dongle, so I don't have to repeat the remove/add process on the ISY after doing it on the Stick. According to AeoTec this secondary controller process should be controlled by ISY I cannot find anything relating to adding or shifting to primary/secondary controller in the Z-wave menus of the ISY. The ISY manual shows them on the first drop down menu, but they're not in 5.3.0. Can anyone help me with this, please? I don't want to do a reset, just to find out that this is not an option. Thanks

Thanks. did they also remove the ability to add/move Secondary controllers?

Greetings; So, it appears that ISY Z-Wave doesn't support S2 Security, which is probably why when trying to add a multi-sensor with V1.14 firmware in Secure mode it gives an error... I now have to remove all 10 units and add them again, in non-secure mode (seems like this will speed the response a bit, and I haven't installed them in the ceilings yet). But I now have even bigger gaps and I'm thinking of doing Dongle reset... I'd also like to add the AeoTec Dongle as a secondary controller as you suggest, but the Z-wave menu in my 5.3.0 with Z-wave 6.82.01 doesn't include any option for shifting control as indicated it the manual https://wiki.universal-devices.com/index.php?title=ISY_Z-Wave_GenII_-_Instructions. I also noticed that options like Heal- Z-Wave Network and Repair links have disappeared. I have a rather large home which is more linear in layout. The Z-waves are all USB powered so they can mesh together. This Heal network function was rather useful... I hope I didn't just shoot myself in the foot by upgrading to the new 500 dongle... Cheers;

Thanks @lilyoyo1. not that important as to resetting the board, no. Any idea on #1, firmware update without losing my spot on the ISY? Cheers

Thanks for that bit of info. I'll give that a try. Any input the other questions? Cheers.

I do have a follow up questions: I pulled one of the multi-sensor units, which was paired with the ISY down from the ceiling. They are all paired in "secure" (blue light when activated) I then "added" it to the AeoTec Z-Wave dongle to upgrade it from V1.13 to 1.14. Upon upgrade, and after power cycle, the light came up green, indicating a non-secure mode. It also wouldn't connect to the ISY anymore. I had to "remove" and then "add" again in "secure". Obviously the programs now all need to be updated with the new ZWxx ID. And, non-critical, but irritating to an anal retentive person like me, there are now gaps in the numbering, since the old ZWbb is now defunct and the new ZWxx was added at the end of the units (now at ZW45). I deleted ZWbb from the list in MAIN, but when I do a ZWAVE->Synchronize-ALL, they all show back up again, including some stuff that is eons old... So: 1- Is there a way to upgrade the firmware without the multi-sensor losing its pairing with the ISY? (or re-assign a new pairing to an existing one) 2- Is there a way of permanently deleting defunct pairing records, so they don't show up again? 3- Is there a way to re-number or otherwise "clean up" the ZWxx numbering? Mind you, I have added my own pre-fixes to the units "ZW13 Multilevel Sensor" is now "Guest Suite ZW13 Multilevel"... Thanks

Rats, Don't want to clib to 20' ceilings with a recently operated knee. I guess they'll stay on 1.13 until a) OTA is available or b) my knee feels up to it... Thanks anyway lilyoyo1

Hello all; I get the same error, with AeoTec MultiSensor 6 devices on V1.14, ISY on 5.3.0 and the device less than 10" away. It doesn't matter, if I reset the sensor. I always have to Exclude before Add. It gives the error, but adds the device. I don't want to install them in their location, 20' in the air... Any ideas? cheers