It is possible that your EZSnsRF contains one of the new PLMs. Smarthome introduced a PLM with larger memory to accommodate more links. This pushes the link database start address higher than most other Insteon devices. Links established with the Set button are stored at the higher address by the PLM and retrieved by the PLM from the higher address when a Dakota Alert signal is received. That is why the links work even though outside legacy code cannot display them because that code only knows about the lower link database start address. At least that is the working assumption for your EZSnsRF. I have an EZIO8SA which came with one of the newer PLMs. Once I figured out why I could not display active link records in the new PLM, curiosity drove me to tweak the Utility. You really don’t need to see the link records to establish a working configuration but if you want to see them, and they really are at the higher address, I have a modified version of the SHN Utility that works at the higher link database address. It is a binary .exe file which cannot be attached to these forum entries. If you want to try my modified Utility send me a PM with an email address where I can send the new .exe and instructions on how/where to install it. The original SHN Utility is not lost and can be restored by renaming a file.

SHN is working on the Utility and should have a formal version that works with the higher database address but there is no target date.

EDIT:
As an update, it has been confirmed that this EZSnsRF is using the higher link database address associated with the larger memory size PLMs. The current 1.78 SHN Utility will not display active links in these new devices.

Hang about. Are you saying that the SimpleHomeNet devices are built inside a PLM?

sprior, thanks for the update. It is very useful information. I was not sure what would happen if you did that sequence and was reluctant to ask you to do that because of where it leaves you if it did not work. Until we can find a solution, you will have to use the Set button on the EZSnsRF to create the controller links or use EZSrve Scene Management to create the links which will give you the EZSrve side only and follow up with the modified Utility with the New PLM checked to create the corresponding controller of link records in the EZSnsRF itself. Unless you did a reset on the EZSnsRF, the Virtual Input records should be correct.

Earlier in the evening I opened up a conversation with SHN Support about your situation. At that time I did not know what would happen if you deleted and added the EZSnsRF device after uploading 1.57/1.58. You have filled in that blank which should be very helpful. I’ll pass the information on to SHN support. Thanks.

EDIT: I just reread your last post. If you feel like taking a chance, you can change the MSB value from 0F to 3F. That is the Most Significant Byte value for addressing memory. That is the change I made to the SHN Utility. When the New PLM is checked, the MSB starts out at 3F rather than 0F. Actually hold on that thought. I will try it on my EZIO8SA first and let you know.

sprior, I changed the MSB value to 3F in my EZIO8SA devices3.xml file and did a SYNCH EZSERVE. EZSrve pulled the 5 active link records.

If you have not modified an XML file, do a LIST FILES. Right click on devices3.xml and select “save target as”, storing the file in a simple directory structure somewhere. I stored mine in c:/temp. There have been problems with complex directory structures containing blanks and/or dots. That may be fixed by now but I know c:/temp or something similar works. Edit the devices3.xml file with WordPad or something similar and change the MSB=0F to MSB=3F. Use the UPLOAD FILE to bring the modified devices3.xml file into EZSrve. Once you see the Successful Upload message, Restart (not Reset) EZSrve. Sorry if you already knew all this. Go into Device Management and try the SYNCH EZSERVE again.
The 5 active links in my EZIO8SA showed up in the Link Records: section and watching the Insteon traffic flow that SDM3 was tracing, the data was pulled starting at 3FF8. Let me know how this works for you.