larryllix

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?

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

I am the opposite. GH always had better sound but the Gen 3 Alexa's have good sound for music also now. However the Alexa Gen 3 Dots are hard to understand, unlike the Dot Gen 1 and 2 that were very clear. I have both but Alexa won out, due to GH making assumptions and turning things on/off that I didn't ask for. Alexa will ask for clarification before turning on random appliances. When asked to turn the bedroom light GH would issue 9 different commands each time, attempting to turn off red, green, blue, yellow, ..... RGBW LED strips. Alexa would only turn exactly what was defined and not make guesses. For look-up purposes GH yoost to be much better, but this has been improved in Alexa boxes now, and I think it surpasses GH usefulness. The race is constant like INtel and AMD. However GH will answer some fun but questionable phrase definitions that Alexa will refuse to answer.

@glsmith777 I smell one big problem with depending on any type of Ethernet package, to reset a problem router, that depends on your router working properly.

I have found with ASUS routers (I have three, 2 different models) that a reboot won't correct some of the problems. It takes a power cycle to make some things be forgotten. Insteon and ISY994 does it well. YMMV

Perhaps ISY has a bug in it's software that causes a program to trigger upon an IO/Linc status update without change in status. It wouldn't be the first time this has happened. This happened in a previous version update with state variables from Rest i/f updates and UDI fixed it. I suspect the query every hour, is to compensate for a bad comm already. It should never be necessary.

If you enjoy tinkering, you need to program the system yourself. It's fun and rewarding. Every time you think of something new, and you will forever..., you will have to call this guy, or somebody else, that will tell you it wasn't done right in the first place, and pay bucks out, or just not have your idea realised. When somebody else sets up your system, you will not get the basic techniques down and have a hard time progressing with your abilities. We have seen many newbies here that didn't know their ankle from a hole in the ground. There is lots of help here and people are glad to help with hunts or write complete programs for you at times. Don't make me come over there!

If your device query triggers a program to run then ISY thinks the status changed. This happens when you have a bad comm nd ISY hasn't been updated to the latest status of the IO/Linc. GDO are notorious for disturbing Insteon comms. I solved mine with two Insteon FilterLincs. They are easy and have two receptacles. One for the GDO (filtered) and one for the I/OLinc (raw). My Chamberlain MyQ GDO (with battery backup) crippled my Insteon system and made it easy to find. Then I realised my older Chamberlain GDO (straight AC motor) may be causing problems also. Unplugged it after five years and found 99.9% of the rest of any Insteon comm problems. Note: GDOs do not have to be running the mechanism to make Insteon problems. They contain bad power supply filtering.

This is a problem with using the io/linc status reversal with GDOs also. You need to program around it without using the reversal of the status or it should happen every query of the io/linc. If the status indicates Gate_closed, then remove the reversal option and call the status Gate_open.

Scenes are preset values and each device can hold about 250 different scenes. When you send an On, level = xxx% you are not triggering a scene in the device. To cause the scene/preset to become effective you must turn on that scene and every device containing that scene ID/Link will respond to it's preset values.

I have been doing it for years on most of my devices. It's not a problem for modern memories with wear and tear management.