apostolakisl

I have the same thing on a Polisy. Added Sensibo node on pg3x and it shows up 3 times. I deleted and readded the node and same thing. I rebooted polyglot and same thing. It wasn't until I rebooted polisy that the issue corrected.

I would get yourself a spare PLM. The caps aren't the only thing that fails on those older PLM's. Having a spare PLM will prevent delay should your PLM (when your PLM) fails. You wouldn't want to have your PLM fail and discover that the PLM's are on backorder or something.

You aren't so much migrating as you are replacing. You aren't going to have both running as you migrate over from one to the other. This should be thought of as a remove and replace. I don't know anything about the 2413UH. It is the "H" part that is unusual and I'm not sure how that will come to play here. But I would not use it. I would continue to use your same PLM, otherwise you will need to re-write links to your entire network and PLM. Get the cable that converts the rj45 on the plm to usb or If you have the DB9/rj45 that came with the PLM, then I would just get the device I linked from Amazon, it is cheap and comes fast and works exactly as it should. You don't need to do anything to your 994 except back it up. Once it is backed up, you are done with it, no need to change any settings on it. Just unplug it. Your Eisy will be on DHCP by default and actually it doesn't even allow a static IP assignment. I would suggest you use your router's DHCP assignment such that it assigns your Eisy the same IP that your 994 was on. It may not matter, but if you have any other devices that link to ISY by that IP address, you won't have to reconfigure them. Also, with a static DHCP assignment, your Eisy will always be given the same IP making it easy to find on your network should you need to SSH into it or manually enter the IP address for whatever reason. Routers do generally keep giving the same device the same IP even if you don't reserve it, but not for necessarily. If you reserve the IP, it will 100% for sure. Typically, if you only have an Insteon network, it really is just a matter of backing up 994, removing it, booting up Eisy with the same PLM you used on 994, and then restoring the backup. You may need to resave network resources if you have any of those, that was something we had to do after updating the eisy firmware to 6.0, if you start right from 6.0, you may not need to. If you have polyglot running on a rpi, you will need to reboot that and I believe you need to change the port number to 8080. Assuming you told your router to use the same Ip as 994, you can leave that setting. Eisy has PG3x built into it, so you may choose to migrate polyglot to that, but you don't have to. PG2 is no longer supported so eventually as the world changes, you will likely need PG3. Finally, if you use the portal, you will need to add the eisy to your account, and then move your subscription from the 994 to the eisy.

Sorry, you're right. It is polisy that uses the db9.

He must already have the Insteon supplied serial cable with rj45 and db9 with correct pin out. How else would a 2413s connect to a 994? That cable combined with the cable from Amazon works, I am using it right now. And it is same day delivery, at least for my address.

You can use that one or you can use one that converts usb to DB9 and continue to use your current wire. That is what I did. Amazon shipped same day, didn't want to wait.

Just had a frustrating time with Google Home not wanting to connect to UD. It had been connected with my Polisy and when I moved over to Eisy it lost the connection and would not reconnect, often times giving no error, it just closed the login screen as if I had never logged in. The solution was simple, just uninstall and reinstall Google Home. Of note, the settings I had in Google home were not lost doing this. Also of note, I have two ISY's on the account. If you want Google Home (and Alexa) to see both ISY's, go to the far upper right corner of the portal web page under profile and select Use All ISY's for Google Home and Amazon.

My other eisy works with its current configuration already in place (different wireless tag account as well), but it sounds like if I ever lost that and need to reconfigure it, I will lose that as well.

Am I the only one? Has anyone else successfully authenticated wireless tag recently? I tried creating a new username and associated the same tag manager to that username and still get the same errors. Wireless tag shows it is connected and has the correct LAN address of my PG, so it is receiving the correct info from PG authentication, but on the other end, PG is not receiving the correct info or is failing to accept the info despite it being correct. I have tried this on both PG2 and PG3x running on different machines.

I see this also with the virtual device node. I am getting 0/1 for off/on instead of off/on.

I have an Elk alarm that I physically wired the relay into the garage door opener, so if I turn the Elk relay on for 1 second it is like pushing the button for 1 second. An IO linc would work the same. This is how I set it up. I also set the icon to be green when the door is closed. Hitting the button on UD mobile is the same as hitting the button in the house for 1 second. I do not have a "close" and "open" button because they don't work with garage doors that are already in motion. If the door is closing, it will still register as open. I suppose you could put a delay in that waits for however many seconds your garage door takes to close before testing if the door is closed, but then it will delay every time you try to close the door.

What does the program that controlled this look like now?

This has been going on for a while. I have tried installing wireless tag via pg2 and pg3x and it is the same result. I have tried creating a whole new account with wireless tag to see if it was a quirk with the account and it didn't fix it. The wireless tag account says that authorization has been granted. But the nodeserver is not getting access. It gives me an error when I authorize UD to access wireless tag. Despite the error, wireless tag lists UD as having access, but like I said, the nodeserver denies that it has access. This is the error message that comes up after I grant permission. Despite the error, wireless tag lists UD as having access I tried creating a new user account and I get the same result. I have revoked access and regranted it multiple times and each time it is the same. When I try to authorize, I get the following screen. I click to authorize, and then I get that error screen. If I click to deny, I also get the error screen with just one word different. EDIT: Also, this used to work. I had this same wireless tag account linked for years. Something happened and I reinstalled the node and this is the result.

Looks like you are using roughly 3gb out of 50 total. 50 is a bit of a weird number, maybe it is a 64gb drive and they aren't using all of it? But like Guy said, I wouldn't worry about it. I doubt you will ever need more than 50gb. I believe if you follow the guy on the youtube video posted through the zpool list command it will tell you how big your drive is and how much of it is unallocated.

For whatever reason, I logged on this morning and now it is connected. ??? Didn't do anything between then and now.

???

Updated to polisy from 994. Initially 5.9.1. PG3x showed up fine. Updated to 6.0.0 and now pg3x says no IoX discoverable. Of course not only is on the same network but is on the same machine. Under IoX configuration tab it lists no IoX's and trying to manually add it doesn't work either.

I'm not positive on this, but I think those images could probably be loaded on "generic" hardware and UD is trying to keep them under wraps. Whatever the partitioning is before you flash the drive is lost when you flash it using rufus and the images UD supplied. The ssd I flashed to I had already formatted to the full 128GB and after flashing it was only ~3GB of usable space and rest inaccessible. While I am sure all imaging software has its own details, the windows imaging software I use on a very regular basis creates an image with a partition size the same as the source. If you try to restore to a smaller drive, it just won't, and if you restore it to a larger drive, you need to do some partition expansion or it goes unused.

After I flashed polisy to 5.9.1 I only had 3GB on my drive. I didn't know it at the time because I never checked, did think I needed to. I then tried upgrade packages and it bricked it. Then when I put the drive back onto my windows PC I discovered that the partition was only 3GB. I flashed it again, and once again, 3GB. At this point I did the above youtube instruction and it expanded my partition to 120GB. Then I did the "update packages" command, it worked correctly. So my polisy is now on 6.0.0. EDIT: Of note, after it updated to 6.0.0, polisy was using roughly 6GB of drive space, so I suspect your previous update packages would not have had enough room. Surprised it didn't brick like mine.

Yeah, looks like his drive was only partitioned with less than 6GB of space. After the update, I was using a bit over 6GB, so that would definitely not work out.

This worked for me exactly as posted in the video except for subbing in "zudi" for "zroot" starting at 1:06 in the video. The screen shot for the video here is where the creator is typing zroot, you should be using zudi here and on the next line as well.

I installed the 14.1 polisy image and it formatted my drive with only a 3GB partition and left the rest of the drive unformatted. If you do an image restore, I would definitely run the df command to confirm you haven't trapped yourself in a barely big enough partition. I posted a link to a youtube video that shows you how to pretty quickly expand the partition if indeed you need to. The 14.1 image is 5.9.1 and the older bsd version. But after installing that image, fixing the partition size, I was able to update to 6.0.0 and the newer BSD just fine.

This sounds like the same issue as with elk showing a number for the alarm status instead of the word. I see my open weather node shows the name of the day in the admin console, but not on UD mobile. @Jimbo.Automates @bpwwer

Did you try rebooting eisy/polisy? I had issues with other pop-up notifications presenting with every instance of opening the admin console after adding a new insteon device. Every time, it would tell me I had successfully added that device. Rebooting got rid of it. Though for all I know, if I add another insteon device it will happen again. Don't know, haven't added any since then.

I have the same issue. Didn't notice this thread and started my own.