breischaft

thanks for the reply. Alexa has 4 skills: -local radio stations -Sonos (which are the main devices used for Alexa/these voice commands) -ISY V3 -SiriusXM

example this morning - 7:04 "Alexa, turn outside lights on" Alexa: "OK". no lights. by 7.07, the lights turned on. I wish I had left Admin console and event viewer up on a computer so I could see traffic. Any other thoughts on how to figure out? Thanks!

I have an eisy with over 120 Insteon devices, mostly switches. Also have Amazon Echo or Sonos speakers with Echo built in throughout house, integrated with ISY portal. most of the time, voice commands (Alexa, turn Outside Lights on") work instantly, with alexa replying "ok". Intermittently, Alexa responds "ok" but nothing happens. Within 5 minutes or so, the light does turn on or off. This is across many devices, not just one. It 'feels like' something is asleep and takes time to wake up, then processes a queue. How do I troubleshoot? many times it's not convenient to whip out phone or computer to see eisy - we use switch and move on (mostly with my wife cursing Alexa) Help appreciated. Thanks eisy version 5.8.4

same story.

Maybe I've missed it somewhere, but: can you have multiple admin console's open at same time? I feel like I'd like to have the main tab showing state of devices open at the same time as the programs tab to better follow program states. possible? thanks

As is case many times for me: operator error. I kept reading these forums and needed to remember that the PIN being asked for is written inside the lock, it's not something you get to make up for yourself. having retried the first two locks, they're now communicating properly and showing up in ISY tree. Thanks again to all who contribute here.

similar issue with Schlage locks. I removed all z-wave devices from 994, thinking I could rebuild z-wave network on eisy after transitioning all Insteon stuff over. I could add the 9 or so aerotec sirens that form the main mesh without issue. The first 2 Schlage locks give do not show as nodes in the tree. When I use my Z-wave toolbox, they DO show as being seen by the eisy. (the wave toolbox reads from the eisy what devices are there the table of neighbors. so back to the @Chris Jahncomment on another thread that they ISY node is not created. selecting S0 or S2 security seems to have no change in outcome. same with removing before adding. other thoughts?

ok. Michel connected to my system, the system recognized its master and obeyed. error condition cleared. Root Cause of Operator Error has no permanent solution. Thank you Michel.

logged back into polisy tonight. first time since this post on Tuesday. error has disappeared and I am now back to: ISY was not automatically discovered on your local network. Please configure it in the settings menu now. of course, I do check settings and it's there. not sure if password field is empty or blind for security reasons, but re-enter password and still no change. to answer Michel, uname -a results FreeBSD polisy 12.2-RELEASE-p6 FreeBSD 12.2-RELEASE-p6 r369564 POLISY amd64 I'm not sure what to expect there. also looking at polisy dashboard, I see: Version 2.2.13 Status: ConnectedFrontend Version: 2.2.9-5ISY Version: 5.3.1 The ISY is really on version 5.3.4 So, not sure where to go from here. Thank you for your help

also extremely slow refreshing in safari. don't know if that's related or just lucky

Polisy has not been working for some months now, I've not had time to look at. Started tonight with error that the polisy did not automatically find the isy, re-enter address, etc. In settings, the correct address is there. it is static from the router and I confirmed that it's same on isy. polisy version is 2.2.9-5, with an offer that 2.2.11 is available. tried updating to that. saw in old forum ssh commands to upgrade, stating that the update button doesn't work. tried these: sudo shutdown -r sudo service polyglot stop sudo service udx stop sudo pkg update sudo pkg upgrade sudo service polyglot start sudo service udx start now log in to polisy and get the 'not connected to server' banner. I may have gotten myself into this, but need advice to get back out please. thanks

Toolbox Ordered! Thank you again (I'm sure I'll have more ???'s later too!)

sleeping dogs thing is tough but I get it. I'm trying not to mess too much, but the ANALytical part of me comes back to the two examples in this thread: 1-Mine that shows ISY is NOT a neighbor of the siren 2-Dan's that shows ISY IS a neighbor of the siren lots of discussion in these pages of how zwave needs strong mesh and sometimes excess repeaters. I'm not familiar w zniffer. can you recommend please? And absolutely: Thank you for the response and dialog. Kurt

@simplextech - @Screw Loose Dan beat me to answer and his screen shot (thank you!) shows what I've seen before as well: - Repeater - Node 1 - [This ISY] yet I don't see anything that has ISY as neighbor. Yet all my stuff works (I think). looking again at my screenshot, the last working route WAS direct to ISY. I'm trying to use these details to move the Siren 6's around to get a better mesh. There's lots of overlap with sirens, locks, etc but none that I can see with the ISY itself. This is what I'd think was the most important.

@simplextech Do you have an opinion on this question? Thank you for help you've provided me indirectly in other posts here.