mango

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....

This is great thank you. Setting up and testing now I have 4314rev2.3 sensors and a v72 serial PLM. The sensors have to be setup manually and report as (2852-222) Leak Sensor v.00 through console. Is this a problem or will I still get full functionality? Wet and dry testing works well, I am presently waiting for a heartbeat and will test for heartbeat missed.

Three reds. Fantastic. Meter time.

Remove the ISY and leave/setup basic scenes on the SL and KPLs

Oberkc I am not the op but thanks for the advice!

Can this not all be done with logic? Do not assign the button directly but have it toggle on and off with programming in between doing the reversing.

I have found using the up and down arrows instead of keying in the values seems to work more often than not.

Now all you need is for your other half to be the recipient so they get the mail from the box for you. Fully automated!

Queuing the writes up in batches is a much nicer way to go about things.

The ISY responds to pings. Does yours?

Yes, DHL will sting you.