paulbates

Open a ticket to get help https://www.universal-devices.com/my-tickets/

Some eisys are having problems upgrading but UDI is quick to help fix. Submit a ticket and UDI will get you running https://www.universal-devices.com/my-tickets/

Would this be the first time you tried that particular combo, it may have been "broken" in migration? In my experience with insteon & plms on several different HA systems, links can break: From migrations from one controller/plm to another Sometimes powerline fluctuations and/or age of device can cause a controller to forget some of its scene programming. For me it was mostly keypads, but it happened with other devices too

To reference the right variable, here's how to interpret the 2 parameters after /rest/vars/set/ above: the first is whether the variable is an integer or state variable: 1=integer, 2=state the second is the number identification of the variable. You find this by looking in iox at variables and on the left side of the list for the number in front of the row of the variable you want to affect. In the example provided above, /rest/vars/set/1/60/.... the 1 means it's an integer variable and 60 means is the variable identification 60 in the iox integer variable list. The ${sys.node....... is the z wave node identifier.

I think the electrician meant 600 watts. Having said that, there are the actual watts an LED consumes vs effective watts, which is how it compares to an incandescent. You need to know which the 600 is. 600 watts for a garage sounds like a lot so I'd assume that's effective, but don't know. It will say it on the fixture/bulb box. Electrician will know. If you are using a dimmer, I'd suggest using an on/off instead, not sure ambiance of a dimmer matters in a garage. If that doesn't solve the heat from the switch, split up how the lights are wired so they are on separate switches, and create a scene between the switches so that they act as one and all the lights go on/off at the same time

That's a great suggestion.. in pg3x and also as an iox node/device that can be changed via drop down: Local only Cloud only Auto as suggested by Panda88-Cloud if connected, local if disconnected.

Ok thanks. let's break it into pieces First, do you have a way to tell if the camect system is able to detect the USPS truck on it's own, like with an app? Another test is to see if the mail notification is working a expected. In iox, right click on the program and pick Run Then. This will force the other to run and see if the mail notification configuration is working. Try those 2 things and let us know how it went

We'll need more info to help. Can you say how you've tried to approach it? Can you copy your programs and paste them in a post here so we can ask better questions?

I got the paid for notification plug-in and have it send notifications to the pushover app on my Android phone and iPad. I also have my router and other fw upgrade notices sent there, works well and timely

It's been a while since sending things through gmail... but my recollection is that individual relay devices have to be authenticated, one time for this kind of use. Since the eisy is new, that may not have happened https://medium.com/@josewebdev/gmail-email-service-setup-for-code-based-email-sending-8b77d7c0a3c0

I'd suggest biting the bullet and moving to the paid for notification plug-in with the pushover app vs texts. The problem is the mobile carriers not wanting the traffic, not the iox method of trying to get it there

I looked this morning. It's in stock and can be added to the shopping cart.

The only insteon outdoor module I'm aware of is a relay based on/off module... This one: 2634-222

If the load of the lights, in watts, is higher than the switch rating, the switch likely won't last

Hmmm. Are you hearing a little click sound when it switches? If no, it's still a dimmer. When you change the setting to relay in iox, you have to push the button to the left of the setting for it to take.

Yes, and you remove the triac dimmer from the equation It's worth a try and easy to do.

I'd still try the lamp module test. Can't hurt

It probably depends if you have a 'legacy' 6/8 button keypad or a new 4 button

Is the separate building on the same electrical service? A test is to take a lamp module and lamp, put it out there and see what's what

Insteon announced it's single band device and competitor trade-up program https://www.insteon.com/tradeup-program

i3 devices have extra features and UDI added them to a flags node. Yhey aren't typically needed after setup. In IoX, I put them all in their own folder, I don't see them in udm

If it's connected via wifi, there's a chance that they picked Public vs Private network under the wifi settings. That could explain the symptoms

I've found that sometimes I have to rebuild a scene; remove the responder(s) and rebuild.. even with new Insteon products. i had a lamp module for Christmas lights in a bedroom at the far end of the house and spent time trying to resolve traffic issues, when doing the above solved it right away. If that doesn't do it, factory reset it and restore device

Chances are your ISY 99 has a local ip address subnet that is different than your new router. Example some use 192.168.0.x and some use 10.10.1.x etc. Do you have the old router still and able to turn it on and attach to it to see what IP subnet it uses? Many router/modems allow you to pick what subnet you use. An alternative is to: Power off the ISY-99. Press and hold the "Reset" button (usually near the power input) for 10 seconds while powering it on. This should reset the network settings and allow you to reconfigure the connection. But it might also rest the ISY, do you have a backup handy?

I had problems connecting to my PLM when I first set my eisy up. I had to unplug/replug the PLM, wait 10 seconds, and then unplug/replug the eisy a couple of times. Then it connected and it has been fine since