grtaylor

I'm on 4.7.3.

I didn't read it as that, or rather, I doubt that's my issue as my motion sensor variable already has a wait of 31 seconds. A factory reset of ISY to solve this sounds a bit ....

Mine looks just the same. I re-opened the device page, and it shows no motion since I was playing with this earlier today. It only reports that has detected motion when the app is running and ISY sets the variable. It was just triggered, it just updated. Makes me wonder though - If you don't have the Alexa app running, something triggers your variable, and then you re-open the Alex app - is the 'Inactive since' correct? When I open the app it only reports the last time there was motion zand when the Alexa app was open, not the last time there was motion, if you get what I mean?

I just checked, and I built a 31 second delay into mine in ISY. When the Elk motion sensor is violated set variable Alexa to 1. This is the variable that Alexa sees as a motion device. Then I have another program - if Alexa variable = 1 wait 31 seconds and then set back to 0.

I have followed that article to the best of my abilities and think I have done it correctly. I ultimately want to use an ISY variable, triggered by a program, not an Elk motion sensor, I'm just using that to test and make it easier so I don't have to keep triggering a program. So right now, an Elk motion triggers an ISY program, which sets the variable. That variable is set up as a motion sensor in Alexa. I have confirmed/done everything listed on the FAQ page under "I can create a routine, but it does not get triggered" So yes, I see the device change in the Alexa app, and the device has been both a motion sensor and a contact sensor. Both show as triggering when the variable changes. But neither cause the Alex routine to fire.

Sadly, I don't think either apply. I'm triggering the variable/motion no more than once a minute (it's an Elk motion sensor in this case actually tripping, and I think they have a built in 30-60 sec reset period). The routine is pretty darn simple - and if I hit 'Play Routine' it works perfectly. The action (turn on a light using ISY) works immediately.

Similar for me Michel. I see the variable change in ISY, Alexa sees the motion sensor device change when the Alexa app is viewing that device, but it does not trigger an Alexa routine.

I just used Alexa Test or something like that.

Sorry if my earlier reply wasn't clearer - I did all those things as you described. No change.

I checked the status of the routine, disabled and re-enabled the skill, and even tried using a contact versus a motion sensor. No changes.

Good to know it's not just me, but not that they seem to care so little. Is there any diff between creating the device as a motion or a contact sensor I wonder?

No change. It seems the only time Alexa recognizes the motion sensor as 'triggered' is when I have the app open at the device page. That shows as motion detected (it's actually an Elk motion, connected to ISY, setting a variable doing all this). This seems simple - but Alexa just isn't triggering. When motion is detected - turn on a light.

The routine is enabled. an ISY program sets a state variable which Alexa sees as a motion device. the Alexa routine is set to trigger when the motion device is activated. But it does not. But if I observe the motion device itself in Alexa, it gets set just fine.

Yup, state variable. I see the motion device in Alexa trigger when the variable is set to 1. Yet the routine doesn’t t fire.

Actually this is a test. The end flow will be HomeSeer to set a variable in ISY, slow I can trigger a routine to control a device that I can only control with Alexa. I haven’t found a way to create virtual devices in Alexa using HomeSeer. the ISY program works perfectly. If i am in the Alexa app and the program sets the variable Alexa sees the motion.

I'm using ISY Optimized for SmartHome V3, have set up ISY Portal, created a state variable and it shows up in Alexa app as a motion device. If I am viewing the Devices page in the Alexa App (iOS) and set the variable, I see Motion Detected. ISY waits 31 secs before resetting the variable. I then created a routine based on motion being detected and set the action as turning a light on using the HomeSeer skill. If I test the routine, works perfectly. HomeSeer gets the action. But the routine isn't triggered when ISY sets the motion variable. Any pointers? I've read the FAQ and recreated the routine, but apart from disabling then re-enabling the skill (and which, ISY or HomeSeer?) I can't see what else I can do.

I'm 100% certain the flashing I see is Insteon traffic. I press a keypadlinc button, and as each device reacts I get flashing like mad, then it dies down. I trigger a program from ISY to do something, flashing begins again. Task ends, flashing stops. I'm going to go rent a Honda inverter generator I think, hook that up and power off the main breaker. And then compare. If that solves it, I need a new gen..

Thinking outside the small black ISY box for a moment.... So could I run two ISY's with two PLM's? Or, as I also have HomeSeer but haven't really used it yet (going to build touchscreen for Elk/ISY/Sonos and more) could I add an Insteon PLM to HomeSeer and put some devices on that....? Wasn't there a hint once at UDI producing a PLM? or did I dream that?

Mmm. Bummer. So a large scene in ISY with say, 50 devices takes up 50 records? Or just one, for the scene?

Finally got a consistent count. Had to remove power from the thermostat and take the batteries out of two hidden door sensors. 954. So that's a lot. How close to blowing up am I? Do SH have any plans to increase the capacity does anyone know? Paul - not sure how I can consolidate large scenes as you suggested. If the scene is large, it's large. Are you asking if I have more than one large scene with the same devices, and if so, get rid of one, that sort of thing? or something else? I have LED scenes, a good number, to keep my keypad buttons in sync. So keypad buttons stay in sync with lights that are changed via a scene triggered elsewhere.

I just counted the scenes in my ISY. 130. Add that to the 14 8 button and 4 6 button keypads, and the 15 Switchlincs... and kaboom. I think I'm gonna need a bigger boat.

Hmm. Well even with ballpark guesses that has me at over 800 links. The numbers that come back from a PLM link count are all over the place, 300 something through to 900 something. And the last count just ended - 817. Trying again. This time it'll be 300...

@ Stu - Great, thanks. Is there a way to see how many links the ISY thinks the PLM should have? to be able to see if it has them all? And if traffic coming to the PLM messes up the count, is there a way to filter that out, export the Log, look for dupes and so on?

Stu, would that work when changing the PLM too? I've got programs like that for some handheld 8 button switchlincs so they get updates, but would that work for a PLM change too? PLM reset seems to have done the trick. That 8 button I started seeing issues with now works. I'm trying to make sure everything else does too. There was some heartbeat traffic and thermostat updates during the Restore PLM, It's really hard to get a clean run with no other traffic with any number of wireless devices in play, I'm trying to do a PLM count now to see what number I end up with. Hopefully will start to see a number come out, but I've always recalled that any other traffic seen during the count seems to mess things up. Is that still the case?

Thanks for the confirmation on the plan. I have a bunch of leak sensors and other stuff in hard to reach places. The idea of resetting all of them to a new PLM... urgh...