DennisC

That's good for now, thank you.

Javier, You have nested icons that can be used for folders and nodes. Do you have a listing of what icons are available? It takes a while to look through all of them without knowing exactly what is available.

Out of curiosity, does your firmware and UI match? Are you using the ISY Launcher?

That zwave version looks like it is the older version zwave dongle. Newer zwave devices might not report all nodes or might not report them correctly.

See factory reset: https://wiki.universal-devices.com/index.php?title=Resetting_Your_ISY

For starters, are you using a 994i ISY? If you are on a previous version of ISY none of the current stuff is supported, as it is end of life. Do you know what firmware version you are running now? How do you normal access your ISY? Is it from ISY Launcher? If you are using ISY Launcher, then when you click on your ISY it lets you choose to load Dashboard or Admin Console. If you are accessing it from a IP address go to Help - About from the menu. If you are accessing from the portal, go to Select Tools - ISY Web Access then Help - About. Once we know your firmware version, we can give you more instructions. To use UD Mobile app you need to be running v5 firmware. If you are still on v4 firmware, updating to v5 takes a bit of prep time and some verification time after the upgrade. However, there is another app from the same author called Go2ISY which will run on v4 firmware. Also, you should be using the ISY Launcher to access your ISY. The Launcher will select the correct UI so you don't need to worry about updating the admin console part, which really is UI related. To use the Launcher go to the upgrade post for your firmware version and follow instructions to download and install Launcher.

Try right clicking the device and look in the menu for something "neighbors". This will update the association.

When was the last time you did a hard reboot of the device running your nodeserver? If it's been awhile maybe try rebooting it by powering it down.

Sorry, I'm out of suggestions.

Within the last two months I had an issue requiring me to contact UD for help with the error log. I had some 140005 Net Module Rule : x errors and I was told that was referring to my coresponding Network Resource. In my case, the Network Resource was also working, however, maybe it was returning a failed responded before succeeding, or something else. But I did confirm it was coming from the Network Resource. So, I am speculating that the same thing may be happening in this case.

I would suggest disabling that resource for a short period and see if it disappears.

Maybe you should open a support ticket with Wes at Mobilinc to see if he can offer any insights, or at least tag him with @ naming convention.

I think but I am not positive, that Net Module Rule 4 refers to Network Resource #4.

For starters here is a link to the ISY error log: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages

I would suggest using @ notification system to bring UD's attention to your request. You can type "@" symbol,then start typing Michel's name and when it appears, select it from the list. This will notify him to read this post.

Here is some troubleshooting guides from the Wiki, try going done the list: https://wiki.universal-devices.com/index.php?title=Troubleshooting_Help

This is a long shot but, if you right click on the device there should be a synchronize call under one of the menu items. That might relate the association.

Right click the device and look through the various menus. I believe there is something there that I think is called heal or heal network. That should help. If not, try synchronize all.

Try this: Finding ISY's Current IP Address from a Windows Command Console Open a Command Console (DOS Prompt) Window: Go to the Start menu and choose Run. In the Run dialog, enter cmd and click OK. At the command prompt, type the command: arp -a <ENTER> The arp command will display a table containing the IP Address and Physical Address of each of the network-connected devices it discovers. Locate the line on which the Physical Address column contains ISY's MAC address (see the section #Finding ISY's MAC Address). From the table line identified in the previous step, obtain ISY's IP address (Figure 10). Once you have the IP address, download the Launcher and try to access your ISY. Once you get in, I suggest you set up a DHCP reservation with your router. The instructions are in the Wiki.

If you are at the same location as your ISY and you are Not using custom ports, your ISY should be available on the standard port 80. If you want to use port 443, you would need to use https instead of the standard http. Are you using the correct ISY Launcher? To be sure, clear your Jave cache and go to the page for firmware updates and install the Launcher for your firmware. When using the Launcher it will automatically select the correct UI. Also, the Launcher should be able to find your ISY. If it doesn't you can select the add button and enter: http://xxx.xxx.x.xxx Hit enter and wait a moment. If it was the correct IP address, it will be added. If you don't know the IP address look at the ISY and find the Mac address. Then look in your router for the IP associated with that IP.

The 4.55.00 version refers to the zwave firmware for the series 300 dongle, not the dongle series itself. The newer 500 series dongle does not have a light on it, so you can tell just by looking at your ISY. Also, the firmware version is different.

Are you using anELK-M1XEP? Do you have DHCP checked on the ethernet setup screen and have you made a reserved DHCP in your router to assign the same IP address to your Elk each time?

One other thing you could try is "update neighbors". Now that you have several devices added, an update to the mesh might help. I don't remember exactly where it's located, by I think it's a right click on the device. Then you need to look through the choices given.

It is not unusual for this to happen. You can either ignore the phantom nodes or place them in a folder with a name of your choice to remember they are not in use.

I would suggest trying to move the ISY closer to the fan and try adding it then.