paulbates

Thanks Techman, and I had your same experience at my last house, outside MS1's, where phantom Insteon "Ons" happened when the battery died.

I'm about to install an MS in my garage. Does anyone know if the small block iPhone charger will power it s. It's 5 watts. The manual is vague about the actual power requirement - 5 volt micro USB I'm going to try it but wondering if anyone has before, since I have a number of these around.. normally "unglowing" led Christmas lights.

There's no manual way described, but I wonder if a manual way exists... and the i3 keypad manual is not as detailed / technical as the owners manual of previous keypads

It's probably time to open a ticket with UDI. You see the program flip green, and the scene and "run then" work instantly, something else is wrong.

A question... The i3 devices come with 2 device entries each: a device entry to control the switch a "Flags" device entry which is more config info. Did you review the Flags for the Keypad to see if the option is there?

I'll be interested if they do respond. The manuals are a little vacant, no detailed guide just a setup guide. It indicates that the top button is for the load, but then there's this little gem: 5. Device ID *Default is set for dimming. Press and hold to adjust brightness - learn more. The connected fixture can be assigned to a different button via compatible software such as Hub 2 with Director app.

Glad to hear it. I had a couple bumps getting a new eisy and new Insteon PLM going at my new-to-me house.. similar story that the PLM initially appeared to be dead.. but wasn't. And I'm really happy with the news system and the addition of UDM... I do all my new Insteon device adds and scene additions using it

I recently set up a new eisy on a new 2413u and had the same problem. It took several eisy power off / on cycles, including a longer off (~30 secs) for it to work.. and since then its been fine.

It's worth noting that restoring to a new PLM, using Restore PLM, it will take a while. The address of the old PLM is still in every device on your Insteon network, and needs to be replaced.... one a time. If you have battery devices like motion or door sensors, they have to be put in manual linking mode, you have to be ready for that. There's an icon on the admin console that I believe skips battery devices, so you can do all the non battery ones first, and then turn it on afterwards and deal just with battery devices. Its at the very end of the row of icons.

After experimenting with the ecobee occupancy sensors via the plugin, I know they work... and also know that our dog "trips" them. I scrolled through the api and don't see the ecobee app's geofence presented as a data point. I know UDM can do this, but its not practical or necessary to put UDM on my wife's phone; she has & likes the ecobee app. Is it possible to add the ecobee geofence state via the plugin?

It should be possible... Use the "schedule" clauses with AND and the other device conditions. It's hard to be more specific without more info or a sample program you might have started

Here's a more elegant one program version that came up on my drive back home from family Christmas If 'Wireless Tags / Utility Room Sensor' Event State is Detected Movement Then Set 'Basement / Utility Room' On Else Wait 15 minutes Set 'Basement / Utility Room' Off

If the tag turns off before 15 minutes, the program stops running.. is likely the cause. Try putting the actions in a separate program, and change the 'then' of the current program to run the new program. The new program should have no 'if' statement

https://www.theverge.com/23820078/matters-biggest-problem-apple-google-thread-border-router-interoperability This article from this summer gives a detailed description of the state of affairs. UDI is not the bottle neck. They're suffering, like other integrators, from the governing bodies decision to let Apple, Google, Samsung et. al. mutually agree and cooperate on proprietary products & border routers. Going to need to let the dust created from the dust settle😒.

I went back and reviewed the intro thread for system notifications via UDM UDM system notifications work for me and not suggesting removing them from UDM. The question is, is there a way for them to also be provided to the the Notification Plugin? Not a hight priority; but it would be nice to have all notifications in one spot. I can see an "order of events" problem in this request; in that system notifications can't be sent to a plugin that hasn't loaded yet... and which notification plugin to pick when there is more than one iox device.

+1 This is something good to do on your terms, not when the card finally gives up

One more idea.. the common element of the problem is the program - you're sure every thing is good in the program? .. maybe open and resave it

Just to clarify a few things You did "Restore Device" for both, and that ran successfully? A lot gets communicated from the PLM to the devices for that to complete, which suggests the PLM can talk to the devices The eisy PLM is plugged into the same outlet as the ISY? One more thing, easy to try through I'm not sure it works with scenes. I used it at my last house that had problem areas and it helped... adjust the individual device retries: Right click on the device Pick advanced / PLM Communications Bump the Retries up to 2 or 3 and retest

My understanding is you substitute the Group key where you would have used the User Key

My understanding of pushover is that phones are associated with one account. You could put that to the test by going to pushover and trying to add your wife's number to your account to see if that works.... if it does, make a group on pushover with both devices They do offer pushover for teams at a cost which I believe would meet the requirement but seems pricey to me for what it gives for you requirement, Something else to try, a workaround of sorts: Jimbo's plugin defines the User Key and application key for each node.. so you can define similar notifications nodes for each account for the same type notification, and send them back to back in a program.

I believe the program is actually firing when you turn 'Office / OnOff-9.1 On-Off Module' on. The reason you're not seeing any notifications is because your "Then" statements either aren't doing anything, or erroring out. Before writing a program, test the notifications individually to make sure they are working Edit.. to prove this theory right (or wrong) add the following statement in the then Your devices 'Office / OnOff-9.1 On-Off Module' pick "Beep" from the drop down as the action When you turn the device on, it will beep at the device, showing that "Control" is actually working

Based on recent threads, I'm guessing that the notifications are new... have you tested them? What happens if you right-click on the program and select "run then" to force the program to run?

The. I ink for the device direct is different than the links for the scene. I would right click on one of the devices and pick "Restore device" and then retest the scene. This may not be it, but important to eliminate and doesn't take long to do.

If I read the first post right, you should be able to set the on levels for the local switch behaviors (first post) and each/every scene (;ast post) and have those 2 things be different. If there are multiple scenes associated with keypad buttons, you'll have to open each scene and change all of the members, including the second entry on the second graphic - foyerrecessed 1st floor. You can do a lot with variables but my understanding of what you want should be solvable with scenes... just a lot of detail work for every "moving part" in the setup

There are a number of moving parts here. Did you recenlty replace the routers? The router provides the ISY with its IP address which is how it gets out to the portal. It could be as simple as restarting the ISYs Do you have other internet services on the ISYs that are functioning, like notifications? Are you able to access the admin consoles? If you go to the config tab Does the IP config look right vs the subnet the unity's are providing.. the first three octets of the router and iSYs need to match eg 192.168.x, 10.10.1.x, etc Is it set up for DHCP or manual address?... if you have manual addresses, that is likely the problem.. the new routers could be providing a different local subnet and the iSYs can't talk any more. There are other possibilities like firewall but I'd start by looking at those basics