Topology generation errors, possibly related to new devices not broadcasting RF commands?

[shunsader]

I've recently been having problems adding sensors (4 leak, and today, a motion sensor) that can be added to the ISY, but when testing to see if a signal is generated when triggering (looking at the Error Log, level 3), nothing happens, for the last 4 devices added.

I decided to see if perhaps maximum memory, programs, etc. were the limitation, so as mentioned, tried generating a topology, and when doing so, immediately got HUNDREDS of errors like this "[FileOpen    ] Open failed for [/CONF/410.PRP] (r)". Attached is the Logfile during this process, with intermittent motion sensor commands (women baking in kitchen).

Additional Info: I installed a Z-Wave module somewhere around the time that I was adding these new devices, but do NOT have Z-Wave hardware installed. UNLIKELY that this could be the culprit, but trying hard to isolate the issues...thus, removed module and rebooted, with no new news.

1. Any chance these 2 issues are related? Why can device be added (written to) without any issue, but when it comes time for the sensor to fire/trigger, NOTHING crosses the event log?

2. I've read in another thread that it might be a memory card issue. Why would the memory card only have issues with new devices, then fail when trying to read everything else...when trying to generate a topology report?

I'm at a loss as to where to go from here. FEELS like some type of limitation issue, but need help evaluating by the experts. 

See attached for the LogFile.

- Steve

GeneratingTopologyReportERRORS.txt

[Geddy]

Do you make notes on devices? Right click "Notes"? Seems that I see comments that *.prp files are just notes files. You might have empty notes and thus making zero file sizes that can't be closed or opened properly and topology is having issue with them.

I've seen comments to remove them via telnet, but I can't tell you how. I would suggest opening at ticket with support to get assistance with the removal process. 

They can also help you evaluate if it might be a sd card going bad.  (Please note that the ISY994 takes a Micro SD and can accept up to 32GB. Make sure that it is a newer brand name with A1 rating. Only if you end up needing to replace the card, but I don't think that's the case just yet.)

Submit a Ticket:       https://www.universal-devices.com/my-tickets
Email:                           support@universal-devices.com

 

[MrBill]

The best method to count resources used is the PG2 Node server called ISY Inventory.  (there is also pg3 version, but at its price I can't recommend it, its quite pricey for what it does-- especially since what it counts the ISY should provide natively.)

[shunsader]

@Geddy, I've opened a ticket per your advice, and following that, realized that since I have a 2nd ISY, I should put it to use. Here's my follow up post to the ticket:

I have installed a 2nd ISY994 PRO with another PLM, and installed one of the motion sensors I was having trouble with on the 'production' ISY. It installs and works as expected. I can touch the set button and get On and Off commands broadcasting across the Event Viewer (Level 3), without issue. Because of this, I expect that the problems are associated with my production ISY.

I DID run a PLM Link report, and is just shy of 1000.... 991 links. There is 1728 Mb of free memory (System Status).

Summary of issue: Production ISY can register devices, (as shown in menu, can talk to them, change settings), but when a sensor is triggered, NOTHING comes across the Event Log (Level 3). This started when working with a Leak Sensor....able to get Wet/Dry, but no Heartbeat. Adding additional Leak Sensors...NOTHING across Event Log when pressing Set, or getting wet, although I can see the LED flash when it should be sending data. - Steve