tjkintz

The router will make a static DHCP assignment based on the mac address. There are two mac addresses, wired and wireless. Once you have gotten an ip address via wireless, make that assignment static in the router.

I have moved my eisy from a wired connection and trying to set up a wifi connection. I am running into the same issue and error message and I too have tried many times. Looking at other related threads, I never see eisi broadcasting an SSID and looking at my router, I never see any attempt by eisy to associate with an AP. I am using a Mikrotik AX access point with WPA2 only. In one thread Michael said to double click the power button twice. Everything else says double click it once. I've tried both.

Regarding zigbee frequencies, they differ from country to country but I configured the module for Portugal which is where I am. Having said that, I see no way to know or configure what frequency the switch uses.

All, thanks for the responses. My initial installation was really a test setting for zigbee and to see if my led lights were dimmable. They aren't! The distance from the eisy to the switches is less than 10' so it isn't the mesh network, and eisy finds the switches, just cannot do anything useful with them. Moes says a Tuya or their gateway is needed but I wanted them to work with eisy so haven't gotten one of those. I'll submit a support ticket but it will probably end up being a failed experiment.

I am new to zigbee but trying to setup smart lighting in Europe where Insteon does not work easily. As a test I bought a Moes zigbee dimmer switch. Eisy finds it and interviews it but the only command eisy shows is Query. Moes expects me to be using their gateway but I hoped any zigbee gateway would work. Any ideas how to make the switch do something useful? Any better zigbee options for europe?

I had exactly the same issues with the same solution, reboot the router. The PG3 log had the same failure trying to access an IPv6 address. Admin console ran fine but PG3 and any node servers were completely hosed.

You were close. I couldn't stop the NS because it wasn't running. I couldn't start it without a license. The NS store said my Polisy was not registered with Portal, even though Portal said it was connected. I could not buy another license or activate a trial. Within PG3, I restarted PG3 and all problems went away. I could then reinstall the NS and update it to the new version.

Update. Following your experience, I gave the Polisy a rest. After powering it back on, I had a valid UUID again and the Portal said it was online. It still could not talk to the PLM and said its status was offline. I then did a "Restart IoX" in the Configuration-System tab. It then started talking to the PLM. One would think that all the Polsy reboots and power cycles I did would have restarted IoX. After all that, I now have YoLink NS issues in that it says I do not have a license. Sigh!

I just have a pure Polisy with no additional boards or z-anything. I would have stuck to the ISY, but I acquired some YoLink devices and needed the YoLink node server. For now, I have lost YoLink.

I am sort of in the same boat. Last evening, according to the last log entries, IoP just stopped working. I can get in via AC but there is no status for any nodes. It goes into the "system busy" loop, sometimes endlessly. It also shows a UUID of 0...1. ISY Portal shows it offline. I have power cycled, updated packages, rebooted, but I am still dead in the water. The PLM doesn't show any activity while the system is busy, but it does show activity from manual Insteon activity. I do not have a backup PLM, but I reinstalled my old ISY and it talks to the PLM fine. From what I can tell, it is IoX 5.4.5 on a Polisy.

I had a similar problem after moving to Polisy/IoP but do not know if the move was the cause. All I can say is that I never had the problem with my old iSY. All my audio and network equipment is in a homerun wired closet. I noticed I was getting flooded with X10 traffic, even though I have no X10 devices. I was able to isolate most of the problems to my audio amplifier. If I unplugged it, most of the problems went away. Luckily, I was able to relocate the Polisy and PLM to a closet far away. All my X10 messages went away. All I can guess is the Polisy is very susceptible to electrical noise.

A bit off topic but actually, the two are quite similar in that the router update is a complete software replacement for the router, fixing bugs and adding new features, etc. The change log is frequently pages long. All that is retained is the configuration, firewall rules, scripts, etc. They do have three update trees to choose from: beta, stable and legacy. And yes, things have gone sideways when I updated from the beta tree so now I automatically update from the stable tree. Because they have a scripting language, I have written scripts to make me aware the router was updated.

Re: "If something isn't clear about that, please let me know what you think would make it better." The problem for me is that I only look at the forum when I am trying to solve a problem. In other words, I rarely look at the forum. As a result, I have no way of knowing there is an update or how to install it. Polisy (PG3 and IoP) is the only device or software I own that doesn't have an easy way of being notified of an available update, along with a script-like upgrade procedure. I regularly run Admin Console, so every time I log in, it would be nice to be notified of new system software, along with some sort of "Click here" button to automatically install the update. Taking it a further step, having a configurable option to automatically look for and apply updates would make it even better. The closest analogy to Polisy is my router in that they do not require regular human interaction, so it is challenging to keep them up to date. With my router, I can manually tell it to look for updates, but it supports a scripting language so every day it automatically looks for updates and applies them if available. That is the type of thing that would really help Polisy, a simple way to manually look for and apply updates, and an automatic way to do it without human intervention.

Bob, The following are two snips from the PG3 purchases screen. The first shows I have a license and the second is what I see when I click (Re)install.

I got things working! The reason you saw one thing and I saw another is the way we went about it. You seem to have gone to the production store and clicked on left YoLInk button. I am pretty sure that was not a live button for me. I somehow got into a state where IoP could not communicate with any Insteon devices. I updated Java, cleared the cache, power cycled the Polisy and PLM. IoP could then communicate with the devices, but the NS still didn't work. I went back to the production store and noticed the live YoLInk button, clicked and then saw what you saw. I was then able to install into slot 1 and everything worked. Whatever method I was using, I could no longer find it. It is impossible to tell which of the things I tried were the key. The purchases section still says I don't have a valid license.