paulbates

I use the TimeData Nodeserver which has strikingly the same syntax. FWIW, in TimeData, that program would execute on Feb 7th every year right at midnight. Another question, are you sure about the "Resource 'Send a flower' statement working? To validate that, right-click on the program in iox and select run then to force run the program and see if that works as expected.

Is the plug-in running, what does it's pg3x page show? Can you post the program you're having problems with

The links probably hung around in the devices and the ISY doesn't know. If you re-read my post above, you should pick the device that exhibits the most problems and factory reset it. Then right click on it in the admin console and pick Restore device.

Modbus JSON is a standard, you need to define the file based on your modbus network so that eisy plugin can consume the data and read/write modbus devices. UDI, I believe, wants to integrate with it but not create modbus tools. You can web search tools either GitHub python or excel macros for a solution, or maybe the file already exists for you installation? My guess is once you've created the correctly named file and stored it in the correct location, the plugin will load that data and have related nodes for you to work with it

Here's where I define my pushover "applications"

Those values come from pushover to integrate with it. The user key points pushover to your account. The application key is what pushover uses for each group, which you define. Here's how I use mine. Operation Log, Battery Alerts, House notices and House Alerts on the left are what pushover calls Applications. Each organizes the notifications you place into them and each has a unique key when you create it on pushover. To use each in a program, it looks like this. This one is a House alert. (I know it doesn't show up in my graphic above, but there would be one if there was a house alert message. The center, where it says 'Set' is the node you create for each pushover 'application' It's not super straightforward but once you go through and complete one you'll see.

You'll need to say where you are on the journey to set up pushover on the notification plugin You have the paid for version of the notification plugin? That's required There's setup steps for the notification plugin on the pg3 page for the plugin, have you done that? Here's what mine looks Iike when I setup a pushover node under custom typed config

Another thought is that keypads are the most complicated of insteon devices. I've had to factory reset the 6/8 buttons from time to time to get rid of quirky behavior similar to what you're describing. Out of the i3 devices discussed in the forums, the keypad has had the most quirks, even out of the box. In some cases insteon support is contacted and the device replaced. I'd try factory resetting the keypads + restore device, one at a time, starting with the non-i3s first.

What i saw in the announcement was that the latest update provided the ground work for it, get the software foundation in place on eisy

No. Version of PM won't matter. I see 2 possibilities: New plm is bad .. less likely There's a significant noise problem on your powerline. More likely. Look up the "4 tap" test and run it on your insteon devices and note the results. The 4 tap test will eliminate the plm as the problem as well as highlight problems

I don't know about the Alexa part, but the program is generally like this: If Status 'Garage door open' = On (however you detect it) then Repeat every 10 minutes (Statement that send the alert) When the garage door closes, the program will cancel

Here's an example I use to keep data for my sump pump. You' ll always need two variable statements, one to assign the value, and one to tell the isy to remember it even if it reboots. If 'TimeData' Day of Month is 1 days And Time is 11:59:55PM Then $Sump_Pump_Maximum_daily_Gallons = $Sump_Pump_Gallons_Daily $Sump_Pump_Maximum_daily_Gallons Init To $Sump_Pump_Maximum_daily_Gallons

There is a way. Right after you set the variable, put an 'init to' as the next program statement with the same value. It will survive the reboot.

Do the links in iox / admin console look right? Post a pic if you're not sure. I'd factory reset the on/off switch, and right click on it in iox and pick "Restore Device". If that works repeat with the keypad

I had it to and I think it updated from 1.2.2 on its own. Once I clicked the X on the side of the message, its not come back, even after closing and logging back in

The eisy currently comes with 2 environments.. iox = the ISY that we know and love pg3x = plugins = node servers = the way for additional integrations to use The pg3x environment is on iox under the plugins menu. It will launch a browser to the pg3x instance on your eisy. It also has the plugins store and allows you to install the individual plugins to pg3x and connect them to iox There's a 3rd environment on the way... eisy will host the web version of iox java client that is used currently. Parts of that were installed in the recent upgrade but it hasn't been launched yet

It's the switch that's responding inappropriately, so an unwanted link to repsond to the remote is likely there. Factory reset the switch and perform a restore device

A possible shortcut is to pick "Admin Console (Cloud)" when you click on your ISY in the launcher. That will download the AC for your 5.9.1 firmware

Polisy is still supported AFAIK. I've seen posts in the recent upgrade threads that it took some people multiple boots. Here's one that is thorough and prescriptive on things to try

DHCP or RA (router advertisement), the address has to be provided from somewhere.

Matter is based on the IPV6 network stack. My understanding is that your internet router needs to provide local IPV6 addressing for Matter devices to work. Many ISPs and many home routers provide IPV6 addressing, IMO the lack of IPV6 is likely not the cause of problems we're seeing here. My router shows that my eisy is assigned a public IPV6 address which means it should have a local one as well. I've seen posts and comments that boarder routers can be IPV4 but not found concrete documentation on how that actually works.

Yes since you have an eisy you can replace the serial with USB version, just use the cable that comes with the new one and follow the replace PLM procedure. The procedure listed is for the ISY994 but you can follow it for eisy except for the Port A step, plug it in to where the current PLM is plugged into eisy The only caveat is if your current serial PLM is located remotely from the eisy, more than 15' and you have a custom serial cable... if "yes" to that special case, you'll need to get the serial version of the PLM. If not, it doesn't matter.

You're welcome. The information is all helpful. It's an older PLM from 2016 that's an older rev. It's somewhere between dying and dead. You'll need to get a new PLM ordered and follow the swap out procedure. The new rev PLMs have had component upgrades so ideally it will last longer

Looks like you have links. A few more questions Do you have Insteon device to device setups like a 3 way where the switches work on their own without the ISY? Do those things work? Can you turn on the event viewer, set it to level 3, pick a few devices and switch them from the device and then also control them from iox, and post the event viewer? A screen shot will be better

Sounds like a dying / dead PLM. Some questions How old is the PLM. There's a sticker with 4 numbers on the back of the PLM, what are they? Unplugging, waiting for 10 seconds and replugging the plm, any change? Restore plm now, any change In iox go to tools/diagnostics/PLM info, what does it say What does the PLM links table show?