paulbates

I'm assuming yes, but not a policy user. Maybe a policy user can respond here.

If your immediate goal is notifications and everything is working currently, I would focus on that and not complicate it with a hardware upgrade. You can get a notification when a sensor opens and closes... it's easy to do with the UDM app natively. My suggestion is to focus on function... ask questions about the notifications and other things you want to accomplish. Nothing wrong with an eisy upgrade, but its extra work on top of what you want to accomplish

The pg3x plugins rely on short and long polling via message queues to communicate with devices/external services. The pg3x elk log looks like normal "respiration" of that activity to me.

A couple of things: When following @Brian H's advice... did you cut power to the outletlinc, either turning the breaker off or carefully uninstalling and uncapping the hot and reconnecting? I've seen this behavior before, where an Insteon device is malfunctioning; it continues to respond to old programmed links, but can no longer be reconfigured... red Xs, beeping when attempting to make changes. In my experience the device can continued to be used "as is" but no new changes can be accepted to the device itself. Since outletlincs are typically responders, potentially you continue using it even though scene changes appear to fail in iox. In particular this happened where I used a large, but in spec, load ... landscape light transformer. The landscape lighting transformer's 6' cord was plugged directly into the outletlinc and line noise from it was too much. I had other outletlincs powering larger, in spec, transformers that worked but there was +20' of extension cord in between. I was able to add an extension cord and that helped. Can you describe the christmas tree load you are controlling, what type of lights, and are you sure it's within the specs of the outletlinc (check the manual)?

What is the device, how old is it? Did you get errors when deleting, factory resetting and re adding to the isy?

By scenes working, do you mean The device activates other insteon devices?... Or.. The device is activated by scenes from the isy? Or both? Posting the event viewer output will help. There are others here better at interpreting that better than me... But without seeing it, this can't progress Turn in the event viewer, set to level three and capture: Single click Double click (fast on) What you do when you say "scenes work" Post that here This thread has revealed that you've tried the normal diagnostics. If the device is older, it's possible that it's failed. I've had older insteon devices that would function as programmed, but then "lose it" when needing to reprogram them, like a new plm or adding a scene member.

Yes, which is why I suggested it. If the event view isn't seeing it, then the device isn't properly updated to the new plm

It sounds to me like the PLM is not recognizing the fast off. Since you changed the PLM recently, that change is still a likely suspect. Under tools/diagnostics; open the event viewer. Set it to level 3. Double click the masterbed off (fast off). Copy the results from the event view and past here

2 other things... Did you replace your PLM when upgrading to eisy? Right-click on the MasterBed device from the admin console/iox and pick restore device and re-test the program You can add those devices to a scene with master bed as the controller. They'll all switch off at the same time and there will be less Insteon traffic. The scene becomes a device that you can turn on and off with the program

I updated to 1.0.8 and the disconnect/failed messages disappeared. I hadn't upgraded to 1.0.7 so it was possibly fixed there. Thank you.

I noticed that my ring doorbell was not running programs I had on my eisy for detecting mtion. I started with unit itself and its app, and it was working. Looked at the ring and eisy log and couldn't find where log entries for motion were coming. I looked around at the ring sub forum and found a similar problem and a recommendation to check the pg3x remote connection. I looked at mine and found this: Remote connection feature available:Yes Remote connection configured:No Remote connection active:No I reconnected and now it's fine. Question/Request: Is there, or can there be a way to get a UDM notification when this drops? This happened around the time of the MQTT changes in pg3X and maybe it's a one time thing. It would be helpful if this connection fails that it Retries x number of time itself Let me know that its not connected or failed to reconnect

Another option is yolink / yosmart. They make a thermostat and security products, and dependable range is their strong suit. There is an actively developed plugin for the eisy that i use for other applications. If I had a quarter mile away outbuilding, I would be giving it a look. They are really responsive to requests about product use pre and post sale.

Udi sells eisy an integrated product / appliance, the code is not open source and not available for compiling or as an image

The ISY's use of the network is very limited (doesn't stream) and only connects at 100mb, so an ET / WIFI bridge should work fine. Like most things network, you'll get what you pay for, eg get a highly rated product vs cheapest. Other ideas: If he has some kind of cable service providing streaming services to his tv vs logging the tv in directly, the boxes providing the streaming to the tv sometimes have ET ports in the back I usually have my previous router hanging around after I upgrade. Some routers can be configured in bridge mode: You log the router into the campus wifi, and plug the ISY in to one of its ET ports.

I would go that route if you're running, and you can live with it the next few days

Wondering if it's a problem with iox on your pc itself. Before going the factory reset route, try clearing the java cache and re-installing iox.

Some migration behavior problems can be expected with programs. Try opening and saving programs that you are having problems with and/or have a yellow icon Also, I would close and restart iox, and if that doesn't help, unplug and replug the eisy, that might help with program migration behavior problems as well

Like Z-Wave, Zigbee will be a journey rather than a destination ... More manufacturers will make more new products continuously ... and do new and unexpected things with the standard. Integrators like UDI will do their best to keep up.

I would pull the plug on the eisy, plug back in

Yes and no... Yes, the eisy is able to support Zigbee. And, no, not every device is necessarily supported. You can do a search just in this thread for the one you're interested in, and you can ask UDI to consider adding support for it if you don't find it Also, add the specifics in your post here, maybe someone has it working already

The event viewer, set to level 3, is different than the log and will show detailed Insteon traffic (or lack of it) to help figure out what's going on. Tools->Diagnostics->Event Viewer ... set to level 3 at the bottom and repeat your tests, post that back here by Saving the Log to File with a description of what part you were doing each test Did you try the "restore device" on one of the problem devices?

Without event viewer info, there is something that might/might not work: One at a time, right click on each Device in iox and select restore device. This possibly could solve one of the things it could be

This is how I do it Ring Battery - [ID 0003][Parent 0038] If 'Lighting Premise / Ring - Front Door' Battery life is 25% Or 'Lighting Premise / Ring - Front Door' Battery life is 20% Or 'Lighting Premise / Ring - Front Door' Battery life is 15% Then Set 'Notifications / Service Pushover Battery' Send Sys Custom With Params Priority=Normal Format=None Sound=Vibrate Only Retry=30 Expire=60 Content 17 Notification ID (ID=17) Else - No Actions - (To add one, press 'Action')

Questions You mention the UDM app, but its also true on iox? You're using the PLM you had on your ISY? I would start with the event viewer in level 3 and repeat steps that fail, like opening the garage and repost.

Insteon makes micromodules, on/off and dimmer, that embed in fixtures and can be remotely controlled like any Insteon switch. Though its for a slightly different purpose, I use one for our kitchen exhaust hood and lights. You'll probably have to take apart part of the hood to install it.