apostolakisl

Perhaps. I have all of my wirieless tags on usb power so that isn't an issue. I have on occasion had issues where I had to reset the wireless tags for whatever reason which was annoying. I haven't had one of those issues in quite a while, though, so perhaps they fixed something in the firrmware. EDIT: I have the wireless tags set to 30 second updates which with it on usb power is no issue. I really like having the 30 second updates as I use these to monitor walkin fridges and freezers and having that smooth non-skipping temp graph has been very helpful in diagnosing issues. Will yo-link do resolution like that? And if so, will that kill the battery? I see they use 2x aa or aaa which is 3v. So I can't just plug them into the USB POE adapters I'm using for them now. I guess I could stop using POE and just plug 3v into the cat6 wire at the source and run that 3v directly into the battery terminals inside the units, but that is a lot of jury rigging. I also really like the wireless tag graphing they do on their app and website. Does Yo-link have all the features for zooming in/out changing scale and whatnot like wireless tag?

Seems to have fixed it, but I had to clear my browser cache. Initially I was getting a 404 error.

I can see my programs, but like the others, node status is all empty.

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?