Hurting2Ride

I ordered a new 2413S on Sunday and it's in my hands today. 😊 😊 😊

Blasphemy!

Thanks.

While the Insteon manual for the 222 does refer to the Insteon hub, it also refers to issues native to the device itself. For example, it explains exactly what the red & green blinking lights mean and how to put the device in & out of linking mode. It's worth looking through.

I'm curious about the answers to this as well. I know there's at least a couple of people active on this forum that have multiple systems, although I don't know how they're being used (production, development, disaster recovery.) Hopefully they can provide some insight. Questions I have 1) do all modules need to be repurchased? a. Does this depend on if the system is to be used only in case of 1st system hardware failure vs used for development or some other live use? b. if not, in the event of 1st system hardware failure, how quickly can modules be moved from the 1st system to the 2nd ? 2) I'm assuming that other than keeping the 2nd system at the same release level as the 1st, there's not much "prep" that can be done to have the system take over from the 1st. I'm assuming this because it seems like the idea of a 2nd PLM on the network with similar link tables would be asking for trouble. But I'd happily be wrong. 3) is there any way to create an automated backup process either via the ISY UI itself or kicked off via command? or an acceptable "hack" that scripts the process? 4) all the other things I'm not thinking of...

This has been stuck in my noggin. I wanted to have a similar function to what you're looking for, without using any 3rd party products to do so. Create an e-mail notification message with the text, including the quotation marks: "http://x.x.x.x:yy/rest/nodes/${sys.node.#.addr}/cmd/DON/255" x.x.x.x. = your ISY ip address yy = your ISY port (if not 80) These must be entered manually into the email subject or body as there is no easy substitution to get the systems address. If you put the above in to a e-mail notification you would be able to click the resulting link and your default browser should take you there. In this case the link would turn on whatever device tripped the notification. As I did not include authorization information in the link you should be prompted for your id/password. Once the command is entered you will receive a result code message from the ISY to let you know if the command succeeded or failed. You could pretty up the link any way you want using standard html code in the email. In my case I created a quick program that looked for an OFF command to this Lamplinc, address 14 52 18. The "Then" command was to Notify and send me an email, using the above substitution, with the resulting link "http://192.168.1.155:82/rest/nodes/14 52 18 1/cmd/DON/255". The basic commands would be On = "http://x.x.x.x:yy/rest/nodes/${sys.node.#.addr}/cmd/DON/255" Off = "http://x.x.x.x:yy/rest/nodes/${sys.node.#.addr}/cmd/DOFF/0"" Set a Variable = "http://x.x.x.x:yy/rest/vars/set/1/88/zz" In this example, 1 = Integer variable (2= State Variables), 88 = Integer Variable Number, zz = set value. zz can only be a decimal numeric. Any chars other than 0-9 will cause the command to fail. Run program = ""http://x.x.x.x:yy/rest/programs/pppp/runThen" pppp=Program # :Options = run, runThen, runElse, stop, enable, disable, enableRunAtStartup, disableRunAtStartup https://wiki.universal-devices.com/index.php?title=ISY_Developers:API:REST_Interface has the complete set of commands available. P.S. Remember to take a backup before you start messing around with the REST (or any) API.

That's great! I have a feeling Javi was referring to Insteon groups but either way glad he brought them up. I hadn't considered them in this case but now it's bouncing around in my brain different ways both Alexa & Insteon groups could be used for this. It sounds like Alexa is issuing the individual commands to each device. Do they appear to turn on or off in sequence rather than simultaneously? or can you see individual commands in the event log?

If I understand what you're looking to do correctly (without IFTTT) you effectively want to use the REST API. That's where you would find the info on how to build http commands that will execute a program, change a variable, etc.

Very possible I'm being dense. I like the idea of the "presets" so you can use similar or the same logic for any scene, but what's the full spoken you use to dim/brighten a scene?

My pleasure. I've been experiencing similar frustrations w/ Alexa integrations so I feel your pain! I've seen a FEW other random posts on the internet machine mentioning that spelling/grammar issues seemed to be a cause of their issues. I'd be very interested if your neighbor routine would work as intended if you spelled it as "neighbor" rather than "neighbour".

...and another thought. Have you tried disabled the ISY skill & re-enabling it? I've had a few scenarios (non-ISY) where doing this "fixed" whatever got hung up in Alexa w/ that skill.

I also meant to ask what happens if you use your same routine but change the action to anything other than a vocalization? If that works, what about leaving that action in place and re-adding the vocalization as a second action?

Any chance this is similar to your issue?

If I may... What's the name of the device on Alexa? What's the name of the ISY variable it's tied to? What does your Alexa routine currently look like?

I don't know if this is in any way related but I spent about 4 excruciating hours of routines & notifications working, then not, then sometimes, then...while troubleshooting a Ring doorbell the other day. Came to find out that Alexa appears to cache certain information about devices and doesn't do a very good job cleaning up it's cache. If you delete & re-add a device with the exact same name it's possible that Alexa updates some of the device info but not all. My problem was "solved" by naming my door bell "Front DoooR". That's all it took for all of my related routines & announcements to work 100% of the time. I then waited a few hours, changed the device name back to "Front Door" & everything continued to work fine after that. P.S. There are also some issues (it seems) with permissions related to Amazon Household. The website thread I followed the other day to finally determine the above issue with devices also referenced the permission. While applicable to my issue, someone might find it does theirs. P.S.S. What values were you setting in Alexa for contact open/close?