MrBill

sudo service polyglot stop sudo service udx stop sudo pkg update sudo pkg upgrade sudo service polyglot start sudo service udx start

That's actually exactly how I do it.... I was thinking about suggesting that next round... but wanted to use the moment to teach state vs integer first.

So Specifically the question that I asked is about communication in the direction of the switch TO ISY. It's good to know that the ISY can talk to the switch, and if "If I press the button" means if you turn on the switch the ISY doesn't realize the switch turned on then we've established that communication is bad the other direction. The purpose of the question was to determine if communication is occurring... if we don't have that the program will never work. Given that we have communication from the ISY to the Switch, the first thing that I would try in this case is to Factory Reset the switch. Pull the bottom programming/air gap lever out, wait 10 seconds, push the lever all the way in and HOLD IT IN until the long beep stops. (Don't let up when the beep starts, keep hold the switch in until the beep is done.) Next, in the device tree select the device, right click it and choose Restore Device. After the ISY is done reprograming the switch repeat the test and let us know if it works yet. I'm not looking at the instructions, so I don't know if the words there could be better or if you misinterpreted them. However for the program as written you only need and integer variable. The difference? In an IF statement a State variable will cause the IF to run anytime it changes. You're not relying on that magic property here, instead you are specifically using 'Run Program' anytime you want the program to run. Another way to say this is that a State Variable can be use in an IF statement as either a trigger or a filter. Conversely, an integer variable can only be used as a filter. Triggers can start execution, Filters prevent it. State Variables use more resources, as such it's best to use an Integer Variable unless the magic property of the state variable being able to trigger a program is needed. Another good habit is to make the first character of all variable names either a lower case s or lower case i to indicate it's type. That just makes the programs easier to read and better organizes the variable drop downs in the admin console. Lastly I can't tell if you're carefully typing programs in the forum or if you've figured out how to paste them, but if you haven't figured it out.... click the program name in the program tree and right click and choose Copy to Clipboard. then you can literally ctrl-v paste it into a forum message.

Assuming 'Hall Bath Fan' is the correct device that should work fine. What happens if you switch to the Main tab and hi-lite that device, then go turn the switch on, does the ISY change the state from Off to On? You didn't ask for programming advice beyond the question you asked, but state variables use more resources than integer variables and I'm not certain why you would need a state variable for this application. Also unless it's an adjustable value I'm not even sure I would use a variable.

UDI has amazing customer service thanks to Michel.

For problem number 1 (after you resolve problem#2) I would try the other linking method. Use the Link Management menu at the top of the "Admin Console", select "New Insteon Device". Enter the devices Address, and name and click OK. No need to put the device in linking mode. For problem number 2, I suggest you open a ticket: support@universal-devices.com

The official communication channel with Universal Devices is via support tickets, you should email support@universal-devices.com to open a ticket. While the forum is operated by UDI, and they do occasionally comment, they don't read and track every thread.

It looks like you created that as an "Integer" variable. Because you likely want to use the variable "Away" in the IF statement of a program you likely want to make it a "State" variable instead. Integer variables can be use in IF statements, but they act as Filters, whereas State variable are triggers. Not required, but a good practice due to the way the dropdowns elsewhere in the admin console work is to make the first character of your variable a telltale of its type. Many of us would name this variable "sAway" as a state variable or if it was an integer variable we might call something "iBeanCounter" (and @larryllix will be along shortly to tell you about using c for Constant with some of your integer variables ??)

It's out of stock. It hasn't been discontinued at this time. Discontinued products like "Hidden Door Sensor" aren't listed on the website. It's unknown when it will be back in stock due to the current worldwide semiconductor shortages. Some people repair failed PLMs by replacing capacitors. someone had success swapping parts from a USB model into the serial model. there's another thread where a converter was created so that a USB model could be used. ISY is in the process of moving to Polisy, when it does the USB PLM is an option. Always make backups. I've had a spare 2413s on the shelf since I started reading about failures years ago.

That's one way, and perfectly acceptable. I don't have an ELK, so I can't say if there is an equivalent procedure for that equipment. Let us know if it helps. there are others here with ELK equipment.

I do tinker with my ISY alot... but I make certain to back up regularly. Come to think of it tho, i need to backup polisy that's been awhile.... and my backups go in a directory that gets backed up to cloud space automatically. The best setup of all is Home Assistant, they have an ADD-on that backs up everyday and syncs the backup directory to Google Drive and prunes old backups according to however you configure a batch of robust settings.

There's only two choices for Z-wave, 300 and 500. the 300 board reports z-wave version 4.55.00 and has a Blue LED to the right of Port A. The 500 series reports z-wave version 6.81.00 and has no LED. Series 300 boards are only compatible thru and including 5.0.16C As far as your ghost chasing just delete the DB file, not sure the path on Pi and let Polyglot recreate it. I had to go thru the pain of ISY SD card failure earlier this year and I became alot smarter during the process. lol Is that the original SD card in your ISY? If so it lasted a long long time...

Yeah, you'll need 5.0.16C... The other way you can spot the 300 board is to look at the Back of the ISY next to right of Port A there is a blue LED (it doesn't look like a blue LED unlit-- you can see that it is if you shine your phones flashlight on it).

Using Search I don't find that version either. Which may mean it shouldn't be installed because it had a major flaw. Does your system have a z-wave menu at the top of the admin console? If so what z-wave version shows there? if its 4.55.00 then go to 5.0.16C which is as far as you can go until the z-wave board is swapped out (there is an upgrade deal here). If you don't have a z-wave menu, or the answer to the version question is 6.81.00 then it should be fine to load 5.3.4 and restore a 5.0.14 backup... I'm no expert on that tho, I don't think there were major changes between 5.0.14 and 5.3.4 that would effect loading an older backup, you might want to confirm with support@univerasal-devices.

Hi @JNaccarato Have you tried restarting the ISY?

I would load the same version of Firmware that the backup was made with onto the ISY, after the backup is restored then proceed to upgrade to the latest firmware. That might not be needed if the backup was made with say 5.3.0 and you're moving up to 5.3.4, for that tiny step I would load the backup onto newer firmware. Since you're running polyglot on a pi you must already be on v5, so if you're aren't too far back in 5.x versions it might be just great to restore a backup made with older firmware onto newer firmware. 5.0.8 might be a breaking point.. I don't know if there are others. Before you buy a new ISY at this point I'd try a new SD card.. look for the A1 designation... 16gb or 32gb will work with the ISY. If the SD card will get you by for now then order a Polisy and move your nodeservers over, and then you'll be ready to go when ISY migrates to Polisy.

That looks like a newer 2413s. date codes are miserably hard to read because they have changed the format many times, but that one might be the 47th week of 2018... what does @Teken think of the datecode?

On restoring backup... what version was the back up and what version was the default firmware on the new ISY? You may need to upgrade/downgrade the ISY firmware to match. On portal: Add the new ISY to the portal and accept the connection in the admin panel. At this point the new ISY will be using a free 30 day trial subscription. Next email support@universal-devices.com giving them both the old and new UUID's, as well as your portal login name, and ask them to transfer the subscription from old to new ISY.

lets tag @MrWorf

if the Portal tab says Online and registered, and the portal says offline since February something is quite odd. First verify the the UUID found on the Help > About dialog box in the admin console matches the UUID you're finding in your portal account. Also did you click the Refresh button on the portal tab in the admin console? does it still say online? and the portal itself doesn't show the online button lit? Does the Tools > Error log in the admin console give any clues? If you've checked all that and your ISY is still showing offline in portal you should probably open a ticket: support@universal-devices.com Include the UUID of your ISY from Help > About in the admin console and also include the portal account username that are logging into.

Is your portal subscription active and not expired? on the portal "Select Tool" > "Information" > "ISY Portal Access License" Then in the Admin Console, select the "Configuration" tab and the "portals" sub tab? Do you see anything besides "Online" and "Registered" there? Also on the "System" tab UPnP can be unchecked. the Portal integration makes an outbound connection from the ISY to the Portal and keeps it open, there is no need for UPnP or open ports.

These like PLM's apparently have capacitors that fail, make sure they all still work. Also if you have AP's you obviously have older Insteon and everything might not be dual band. the newer dual band products are better and more reliable, and don't require access points.

in addition to @lilyoyo1's questions... did you set level 3 in the event viewer? do you see any 1101 green or grey icons to the left of device names anywhere in your device tree? do you have wireless devices?