mango

The tplink AC4000 looks like a beast, wow. I can only assume the new router is doing some sort of blocking of the ISY from LAN to the WAN, as internally on your LAN it appears to be working properly. I would check there, maybe even open up a DMZ to test.

Have you tried setting it to DHCP to test?

Your HTTP and HTTPS ports should be 80 and 443 respectively. Also, change DNS to 8.8.8.8 (although 8.8.4.4 should also work)

Is there anything specific to zwave I need to be attentive to in programming (such as timeouts / retries / redundancy etc.)? My lock has appeared as 6 nodes - the primary for locking / unlocking / setting the codes, and then 5 what appear to be alarm nodes. Are the alarm nodes specific to separate alarm-type programming? I assume they are just state variables if they go off?

Hey Bill, Thanks this is the sort of thing I need. I understand your logic.

Zwave version: 6.82.01

Hi all, I'm a newbie to ISY Zwave and Zwave Schlage locks (moving from a Schlage Sense Bluetooth/IP lock). I am presently installing front and back door BE469s. I have attempted to search here for some inspiration on how to manage the locks. A few months ago I found some valuable resources with examples of programming, but now am unable to find anything. Would anyone have some programming examples to share for their setup? My goal is to have a front door KPL button say 'DOORS LOCKED' - for it to hopefully work as controller and responder - to light up when both doors are locked (door sensors showing doors are closed), and for the button to be able to lock both doors if not locked (sensors closed). Also I would like to use pushover (which I have just setup today) to log door activity. I think I have that one worked out.

Hi, did this ever get resolved? Using UI and Firmware 5.3 with a new BE469. Am unable to get options but lock is working. 6 Nodes showing.

Interesting thread all, thank you. I'm towards the lower end of the intellect here and usually just lurk and 'steal' (borrow / learn) ideas for ISY functionality. For that I thank you all. I am not a coder or programmer and am still fumbling with the basics of conditional logic. As a complete outsider to the Polisy debate I would like to offer my fly-on-wall take: I've been on the scene quite some time, started with X10 and enjoyed using the ISY99 when Insteon was on the up. Now I have two properties both with ISY994s and quite a bit of kit. It is Insteon, not UDI who are the catalyst for this issue. Insteon have failed in so many respects, in pretty much everything they do. A company that used to be a leader in the field has just shriveled up and is (in my view) continuing to slide lower into obscurity. The writing is on the wall. For those of you who have invested heavily into Insteon, keep buying up all the spare stuff you can and run your system(s) for many more years to come, but be understanding that it will come to an end. If UDI is to keep its head above water, it need not attempt to throw precious development time into supporting new Insteon products (I doubt any are coming anyway). It's pure economics. They will support existing kit and assign Insteon functionality to the Polisy. That's pretty much it.

Okay thanks!

Dragging this old thread out of the mud, just to see if there is any new news? I have been away from the scene for quite some time, but was having difficulty purchasing new hardware so came here to see whether the writing is on the wall.

Okay so I had some time to put towards this again and found that it's working once more. Some of my house ISY/Alexa config I left as-is untouched. It's in these zones that the command "Lights X" works again. I can walk to any of these Alexa zones and say "Alexa, Lights on" and she replies "okay" as before and the scene will enable. Strange..... Something definitely was a little buggy Alexa side for a while me thinks. Anyway I'm very glad to have simplistic command control once more, thanks all for the input.

Hi dbuss, Thank you although I don’t think this applies to my issue. I have Alexa viewing my ISY setup as devices already. They are only scenes on the ISY.

HI Larry. Thanks I will try later tonight. It would be a pity if true. It was beautifully simplistic before....

I have to add a #me too to this issue and have only just had time to put towards it. My Alexa/ISY setup had been working fine for many months. Multiple Echos grouped with selected Insteon devices which are ISY Category Scenes to Alexa Category Device/Lights. Depending on your physical location in the building, saying the command "Lights ON" or "Lights OFF" worked to control individual zones matched with location. Not having to know the actual spoken word of the area to control it, but simply using the words "Lights..." is a feature I am trying to make work again for the family. Since the problem started Alexa would respond "Please try again using percent for brightness or degrees for temperature." It seems some logic Amazon had in place to be able to determine that the spoken word "lights" can control each separate Alexa group has been lost. So may question would be, how do I rebuild the structure from ISY to Alexa to be able to use the wildcard word "lights" in different zones?

+1 Very interested in verbal notifications (leak sensor etc.).

Ahh yes I think I understand, thank you. I will ponder this a bit more.

Hi Benoit, Thank you for your help! My specific question is: Does/can ISY differentiate between an Alexa voice triggered action as opposed to any other tradiional action? If so, I would like to build upon this. If I log ISY when performing a voice command, I don't see any difference in/out compared to pressing a switch for the same action. A clunky way to acheive what I want is to create Alexa only driven scenes/programs, but I am loathed to do that because of duplication.

Is there any way to flag an Alexa voice command through ISY? Specifically I would like to sense voice commands and act upon them through ISY programming. I am aware of Smart Home routines and could possibly build something that turns on a fake device in ISY but I am looking for a cleaner more direct way to sense an Alexa voice triggered command within the ISY itself. Possible? I would like to differentiate between voice triggers and keypad button presses / programs etc.

I appreciate you working on a fix, thankyou rabbit1543. Missing heartbeat aside, your code works to discover leaks which is the main thing. Checking heartbeat status can be easily done through the ISY manually for anyone wanting to check in the interim. The faulty code wasn't really a ball breaker in my opinion.

Teken, sorry for the late reply I have been unable to get to the PLM to check the stickers. I think I will put this one to bed and leave as-is. The sensors work as they should with the caveat of requiring manual setup as well as do not report version number through console.

I appreciate your help. I've taken this thread off topic I hope a moderator can split it, my apologies. Can't get to PLM until tonight. My setup is tiny, have not looked at table. The sensors appear to be doing everything they should if setup manually....

Yes tried both ways. Auto does not work. Nothing is discovered. This is why I think it's the PLM(?)

Hmm, tried that and they all re-register as v.00. Latest ISY non-beta firmware. Some time ago I had bumped into a thread here discussing a similar issue and a PLM replacement fixed the problem. I can't seem to locate it....