larryllix

Thanks My ISY Portal hasn't changed for a long time and all checks OK. I am running ISY 5.3.0 but fairly sure vocals have functioned since then OK. Perhaps amazon changed IFTT functions? What is the syntax for the Rest GET? All I get is gooble-dee-gook back. eg: "http://192.168.0.161/rest/nodes/garage%20door%20one%20open" 404try { Object.defineProperty(screen, "availTop", { value: 0 }); } catch (e) {} try { Object.defineProperty(screen, "availLeft", { value: 0 }); } catch (e) {} try { Object.defineProperty(screen, "availWidth", { value: 1280 }); } catch (e) {} try { Object.defineProperty(screen, "availHeight", { value: 720 }); } catch (e) {} try { Object.defineProperty(screen, "colorDepth", { value: 24 }); } catch (e) {} try { Object.defineProperty(screen, "pixelDepth", { value: 24 }); } catch (e) {} try { Object.defineProperty(navigator, "hardwareConcurrency", { value: 8 }); } catch (e) {} try { Object.defineProperty(navigator, "appVersion", { value: "5.0 (Windows)" }); } catch (e) {} try { Object.defineProperty(navigator, "doNotTrack", { value: "unspecified" }); } catch (e) {} try { window.screenY = 713 } catch (e) { } try { window.screenTop = 713 } catch (e) { } try { window.top.window.outerHeight = window.screen.height } catch (e) { } try { window.screenX = 1273 } catch (e) { } try { window.screenLeft = 1273 } catch (e) { } try { window.top.window.outerWidth = window.screen.width } catch (e) { } -----------------------------------------------------------------------------------------------------------------------

@bmercier I have just found all my Alexa pseudo MS routines responding to "MS not detected" values instead of "MS detected" values in the state variables. This has been working for several years as "MS detected" but suddenly all 20 routines changed. I have made temporary changes in my critical Alexa routines to detect" NO MOTION" to trigger my routines until this can be stabilised. I strongly suspect this has been a change in the reporting from ISY Portal for pseudo MS devices. Can you please verify the ISY Portal pseudo-MS sending logic to Alexa has not been reversed recently (last week or two) before I open a ticket with amazon? (typically useless anyway) Thanks Benoit!!

To follow oberkc's thinking, try a wait 2 seconds between a few lines to see if it makes a difference when you test run "Then". You should have posted your program via copy to clipboard so people can see if it is enabled and other details.

Correct! They have been working on "detected" for a few years now. Suddenly they are triggering on the "Not detected" or when I release the variable to 0 again. Last two years about 20 routines set up like this: Var = 1 = ISY Portal pseudo MS = Motion = Routine trigger on Detected= say "whatever has happened" Now Var = 1 = ISY Portal pseudo MS = Motion = Routine trigger on Not Detected = say "whatever has happened" I was being fooled by the 30 second Wait timer for var = 0 but wondering why the vocal was being delayed 30 seconds and sometimes not coming through at all for the last few days.

to tag somebody you "quote" them or type an '@' followed by their name. Now you have to select the name from the auto-filled in fall down menu or it doesn;t happen. You will know by the coloured box around the text like this @BOden I have found to trigger a routine you only need a few seconds to hold the trigger flag on but Alexa will not allow faster than 30 second repeats of the action in order to eliminate DOS attacks and nuisance channel crowding. Right now I have just found all my routines triggering after the pseudo MS signal has released (no motion) and my routines stopped functioning without the 30 second delay. This makes my routine trigger arbitration program broken for the time being.

@bmercier I have just found all my Alexa pseudo MS routines responding to "MS not detected" values instead of "MS detected" values in the state variables. This has been working for several years as "MS detected" but suddenly all 20 routines changed. I have made temporary changes in my critical Alexa routines to detect" NO MOTION" to trigger my routines until this can be stabilised. I strongly suspect this has been a change in the reporting from ISY Portal for pseudo MS devices. Can you please verify the ISY portal MS sending logic to Alexa has not been reversed recently (last day or two) before I open a ticket with amazon? (typically useless) Thanks Benoit!!

I read the fix as: too short of a trigger signal On time. 30 seconds fixed it. "My configuration had some issues so I took it all back to factory (I don't know if it was related to the issue here)." You didn't flag @BOden to get his attention.

I just use one program that sets the variable to 1, Wait 30 seconds, set variable to 0. I was thinking of designing a stacking program so that variables would be set to 1 and cleared again in order so that no notification would ever be missed. It would be nice if ISY had indexed variable access or variable numbered access (arrays?) to make this easier.

I use 30 seconds just as a reminder to not ever trigger another notification in less than 30 seconds. Alexa will just ignore any signals it receievs before a 30 second time out. It doesn't have to be the same signal to be ignored....any. The other point is...have you tested your routine to see if it works...like the speaker is in another room or volume turned down or disconnected from your WiFi?

Seems like this could be the basis of a decent and real Insteon system debugger. May even find some bugs in the ISY994 drivers, looking in from the outside. I did a similar thing in the X10 world and found defective devices a few years ago.

That would only save about one drag and drop of each device per scene incarnation. For Alexa controls I just use programs. The devices send a checkback of status, unlike scenes and any increased delay (there should be none) is not noticed for verbal commands.

If you have a router with no port forwarding enabled, you just need a good virus and spyware scanner to eliminate these Trojan Horse style threats. If you were attacked via the ISY Portal, you would need to contact UDI and let them block the attack through the portal, including changing your passwords.

Not the skill... enable the routine inside each routine. They like to turn themselves off when something doesn't jive.

I typically use my fingerprint on my Android phone but after using some solvents it doesn't function again for about a week or so. Longer passwords work just as well but I get tired of looking it up in my password file just to find .... "Mary had a little lamb. It's fleece was white as snow"..but now it doesn't contain any numerals or enough punctuation or whatever the next imaginative code monkey thinks up this week.

I don't use the built in replacement process. Every time I have I done it backwards and made a mess. The manual process is so easy. Link the new device to ISY Name the old device with an added XX to the end of the name. Name the new device to the old device's original name. Use the replace NAME XX with NAME Save the programs. Done. Takes about 45 seconds. No guessing. No getting from to mixed up or remembering a process you only use about every two years.

OMG! Does that mean we will get 'chipped' at birth? I am still waiting for signal wires in the roads so we can get autonomous cars working. Sent using Tapatalk

My son lost about $230K on an app like that, when his Samsung S7 crashed and wiped out the memory. The banks use 2FA security login techniques without using any additional apps or hassles for the users that also introduce more hacking entrances. They detect your account name and password, IP address, browser type and ID number, PC security numbers and absolute enrollment techniques. Adding more apps and software for user portals can create more entrance points for hackers to get access to your accounts. I try to avoid them as much as possible. Of course there is money to be made selling software if you can introduce FUD into the market.

Yeah. and I get the confirmation email on the same device being hacked, that I lost in the park. ? It's mostly not about your security. Its about KYC rules. It's about harvesting your email address or mobile number. Even banking accounts don't use these techniques. They don't need it.

I had a lot of problems with this a few years back. Now I have had problems and been caught several times again with deleting all devices before discovering, in Alexa. That removes all triggers from Alexa Routines every time, but when you rebuild them all again they are all disabled. The switch at the top of every routine shows the status of the Enable/Disable but it appears like a switch to disable them. This shows the current status of each Routine, not the action.. Make sure it reads Enabled.

Not quite. ISY evaluates the From and To only twice at the two times. When another trigger in the If section triggers an evaluation of the If section, a From/To is evaluated and is True between the two times, and False outside of the From/To times. Also From will run Then, and To will run Else sections when used alone. A single time trigger is true only when it is being evaluated because it triggered the evaluation. This means two event triggers will never evaluate to True simultaneously. If ....At time 3:30 PM ....AND .... Switchlinc is switched On can never run Then, as both events can never be true at the same time. While one is being evaluated as a trigger the other condition is always False.

I don't think that was ever implemented. I can't say I am unhappy about that decision. In my opinion every 2FA technique I have ever used has been a joke, a PITA, and may actually lessen security.

The older admin console ISY Finder will be stored in your java cache and needs to be cleared out, and then reinstalled with every new ISY firmware version. When the UI and firmware versions don't match you will have trouble with mismatched features that cause trouble. ISY Launcher loads and installs the correct version each time.

For sure. I have had go'rounds with eBay. I don't trust them anymore for being a vendor....and very little to purchase through them.

Sorry. I didn't include the post I was responding to. I was responding to Bumbleshoot, demonstrating that I have the same latest polisy O/S version, the same as he does. No problem here with my equipment.

I am getting the same: FreeBSD 12.1-RELEASE-p10 r365882 POLISY