Steve Sullivan Posted January 29, 2013 Posted January 29, 2013 Hey all. Long time since i've been on the forum. System has been working pretty good up until a few days ago. I noticed some programs not working. Now none of my motion sensors status are seen at all. I can set options on them and my thermostat works so I think the access points are ok. I've updated to the latest release. Tried cycling power a few times. Any ideas? Frankly I'm stumped. Here's some data from the log. Wed 2013/01/23 11:59:53 PM System -140000 datafeed.weatherbug.com Thu 2013/01/24 12:43:53 AM System -140000 datafeed.weatherbug.com Thu 2013/01/24 01:59:53 AM System -140000 datafeed.weatherbug.com Thu 2013/01/24 02:19:52 AM System -140000 datafeed.weatherbug.com Thu 2013/01/24 02:27:52 AM System -140000 datafeed.weatherbug.com Thu 2013/01/24 02:39:52 AM System -140000 datafeed.weatherbug.com Thu 2013/01/24 03:35:53 AM System -140000 datafeed.weatherbug.com Thu 2013/01/24 03:43:52 AM System -140000 datafeed.weatherbug.com Thu 2013/01/24 04:31:52 AM System -140000 datafeed.weatherbug.com Thu 2013/01/24 04:38:18 AM System -60001 time.nist.gov Thu 2013/01/24 05:38:31 AM System -60001 time.nist.gov Thu 2013/01/24 06:27:53 AM System -140000 datafeed.weatherbug.com Thu 2013/01/24 06:38:52 AM System -60006 n/a Thu 2013/01/24 06:39:52 AM System -140000 datafeed.weatherbug.com Thu 2013/01/24 07:39:02 AM System -60001 time.nist.gov Thu 2013/01/24 09:31:50 AM System -140000 datafeed.weatherbug.com Thu 2013/01/24 09:39:23 AM System -60006 n/a Thu 2013/01/24 09:39:51 AM System -140000 datafeed.weatherbug.com Thu 2013/01/24 10:03:52 AM System -140000 datafeed.weatherbug.com Thu 2013/01/24 10:59:52 AM System -140000 datafeed.weatherbug.com Thu 2013/01/24 12:39:51 PM System -140000 datafeed.weatherbug.com Thu 2013/01/24 01:27:50 PM System -140000 datafeed.weatherbug.com Thu 2013/01/24 01:51:50 PM System -140000 datafeed.weatherbug.com Thu 2013/01/24 01:59:50 PM System -140000 datafeed.weatherbug.com Thu 2013/01/24 02:19:52 PM System -170001 [TCP-Conn] -1/-140002, CLI-WBug Thu 2013/01/24 02:23:50 PM System -140000 datafeed.weatherbug.com Thu 2013/01/24 02:43:51 PM System -140000 datafeed.weatherbug.com Thu 2013/01/24 03:15:54 PM System -140005 CLI-WBug Thu 2013/01/24 03:23:50 PM System -140000 datafeed.weatherbug.com Thu 2013/01/24 03:35:50 PM System -140000 datafeed.weatherbug.com Thu 2013/01/24 04:51:55 PM System -140005 CLI-WBug Thu 2013/01/24 05:33:48 PM System -5012 160 Thu 2013/01/24 05:33:48 PM System -5006 uuid:160 Thu 2013/01/24 06:07:45 PM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 4 Thu 2013/01/24 06:08:02 PM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 4 Thu 2013/01/24 07:23:52 PM System -140005 CLI-WBug Thu 2013/01/24 07:31:56 PM System -140005 CLI-WBug Thu 2013/01/24 08:19:59 PM System -140005 CLI-WBug Thu 2013/01/24 09:31:56 PM System -140005 CLI-WBug Thu 2013/01/24 09:51:55 PM System -140005 CLI-WBug Fri 2013/01/25 01:20:00 AM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 4 Fri 2013/01/25 01:20:01 AM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 39 Fri 2013/01/25 01:20:01 AM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 54 Fri 2013/01/25 07:22:01 AM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 4 Fri 2013/01/25 07:22:02 AM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 4 Fri 2013/01/25 07:22:23 AM System -170001 [TCP-Conn] -6/-140002, Net Module Rule: 4 Fri 2013/01/25 07:41:04 AM System -60006 n/a Fri 2013/01/25 07:41:19 AM System -60006 n/a Fri 2013/01/25 09:41:44 AM System -60006 n/a Fri 2013/01/25 01:42:17 PM System -60006 n/a Fri 2013/01/25 02:42:36 PM System -60006 n/a Fri 2013/01/25 05:43:03 PM System -60006 n/a Sat 2013/01/26 04:44:10 AM System -60006 n/a Sat 2013/01/26 07:44:41 AM System -60006 n/a Sat 2013/01/26 01:15:45 PM System -140000 datafeed.weatherbug.com Sat 2013/01/26 11:45:53 PM System -60006 n/a Sun 2013/01/27 01:50:00 AM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 4 Sun 2013/01/27 01:50:01 AM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 39 Sun 2013/01/27 01:50:02 AM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 54 Sun 2013/01/27 08:03:41 AM System -5012 169 Sun 2013/01/27 08:03:41 AM System -5006 uuid:169 Sun 2013/01/27 08:19:43 AM System -170001 [TCP-Conn] -1/-140002, CLI-WBug Sun 2013/01/27 11:46:58 AM System -60006 n/a Sun 2013/01/27 11:47:13 AM System -60006 n/a Sun 2013/01/27 02:47:40 PM System -60006 n/a Sun 2013/01/27 06:48:09 PM System -60006 n/a Sun 2013/01/27 06:48:24 PM System -60006 n/a Mon 2013/01/28 12:49:03 AM System -60006 n/a Mon 2013/01/28 01:20:01 AM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 4 Mon 2013/01/28 01:20:01 AM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 39 Mon 2013/01/28 01:20:02 AM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 54 Mon 2013/01/28 01:50:01 AM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 4 Mon 2013/01/28 01:50:01 AM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 39 Mon 2013/01/28 01:50:02 AM System -170001 [TCP-Conn] -1/-140002, Net Module Rule: 54 Mon 2013/01/28 02:49:27 AM System -60006 n/a Mon 2013/01/28 03:49:49 AM System -60006 n/a Mon 2013/01/28 04:50:08 AM System -60006 n/a Mon 2013/01/28 09:09:44 AM System -5 Start Mon 2013/01/28 09:10:02 AM System -170001 [Network] Established Mon 2013/01/28 09:10:13 AM System -60006 n/a Mon 2013/01/28 01:10:05 PM System -60006 n/a Mon 2013/01/28 05:26:56 PM System -5 Start Mon 2013/01/28 05:27:14 PM System -170001 [Network] Established Mon 2013/01/28 05:49:35 PM System -5012 26 Mon 2013/01/28 06:00:35 PM System -170001 [uDSockets] HTTP:33 error:6 Mon 2013/01/28 06:00:40 PM System -170001 [uDSockets] HTTP:33 error:6 Mon 2013/01/28 06:00:45 PM System -170001 [uDSockets] HTTP:33 error:6 Mon 2013/01/28 06:00:50 PM System -170001 [uDSockets] HTTP:33 error:6 Mon 2013/01/28 06:00:55 PM System -170001 [uDSockets] HTTP:30 error:6 Mon 2013/01/28 06:00:55 PM System -170001 [uDSockets] HTTP:31 error:6 Mon 2013/01/28 06:00:55 PM System -170001 [uDSockets] HTTP:33 error:6 Mon 2013/01/28 06:01:00 PM System -170001 [uDSockets] HTTP:30 error:6 Mon 2013/01/28 06:01:00 PM System -170001 [uDSockets] HTTP:31 error:6 Mon 2013/01/28 06:01:00 PM System -170001 [uDSockets] HTTP:33 error:6 Mon 2013/01/28 06:01:05 PM System -170001 [uDSockets] HTTP:31 error:6 Mon 2013/01/28 06:41:27 PM System -5 Start
Steve Sullivan Posted January 29, 2013 Author Posted January 29, 2013 OK so I just restored one of them and it's working. I guess I'll continue on that path. Any ideas what could have caused all of them to stop working?? Thx
LeeG Posted January 29, 2013 Posted January 29, 2013 Since Motion Sensors sleep and they all stopped working the most likely cause is the PLM lost some its link records so the Motion messages were not passed to the ISY. However, it is odd that it would only be the Motion Sensor link records
Steve Sullivan Posted January 29, 2013 Author Posted January 29, 2013 Thanks for the quick reply. that makes sense, there were some other programs not working as well. I've restored the PLM and that seems to be a fix. I haven't had this issue before, any idea what would cause it, or if it's a sign of the PLM going bad??
LeeG Posted January 29, 2013 Posted January 29, 2013 Could be a PLM that is beginning to fail or maybe a very short power outage resulted in the PLM firmware doing something unintended. PLMs accumulate duplicate and unneeded link records over time which can prevent new link records from being written because the PLM link database becomes full. That does not seem likely in this case since these were older link records. A link record could have become corrupted making the PLM link record search stop prematurely. It is something to watch. If it happens frequently then a new PLM would be a good idea.
Steve Sullivan Posted June 5, 2013 Author Posted June 5, 2013 So it's been a while since this last post. Lot's of issues still though. I had suspected a bad PLM. Got a new one and replaced it. Also restored certain devices that were not communicating well. Things seemed ok. Then after a short time (1 day) certain programs stopped running and some devices stopped communicating. Most of these were motion based with timers. Then others were just basic programs with scenes. Seemed like some devices just forgot their settings, like ramp rates and etc. After another restore on the new PLM and devices things again seemed to work for a short time but stopped. I got annoyed and unplugged my ISY and PLM altogether, told the family to shut off the lights and went un-automated. HORRIBLE - after years of the lights shutting off by themselves my family has been way too conditioned to remember shut them off manually. Might be a good topic for another thread. So. I feel I have some bad switches(noise), maybe a bad ISY99, maybe bad new PLM (doubtful), maybe bad access points. Since the ISY99 has been shunned I bought a new 994IR, new access points, a few switches, another PLM. Just received the parts today. Any thoughts on how to proceed replacing all of this? I'd like to replace the suspected bad devices, backup from there, replace the ISY, then restore the PLM. Though I'm not sure if maybe there's some corruption going on and I should start over from scratch. I have lots of programs, most pre-variable and ugly so it would be nice to clean up.... but that seems like a huge undertaking.
oberkc Posted June 5, 2013 Posted June 5, 2013 I have not knowingly experienced a once-good PLM loose (or otherwise become corrputed) link records. I have had a PLM failure, but it was a global failure...not limited to a single device or type of device. On the other hand, I am very suspicious that a marginal communication environment can introduce errors into the link creation process (scene creation). I suspect you have yet to get to the root cause of your problems. And, I would definitely take this opportunity to start fresh. Given your history, I would not start from a backup. My thoughts: a) narrow down your troubleshooting a bit. Is your motion sensor programs not responding because the ISY is not seeing the status change of the motion sensors, because the motion sensors are not working as expected, or because the program not responding as you expect? This can be done by watching the event viewer while someone triggers the sensor. make sure you have the latest firmware for the ISY-994 c) reconfirm your access points are communicating and on opposite legs of your electrical system d) when you start adding devices, pay attention to the speed at which they add. I find that you can quickly get a sense for how quickly device react to a linking process, and that a device that tends to take a little longer to add is a foreteller of communication issues. If you have some of these...stop and solve.
LeeG Posted June 5, 2013 Posted June 5, 2013 I would second oberkc recommendation to start over. It is a pain to think about adding all the devices again but it insures they are all clean to start with. Some things to think about from the beginning. 1 ISY should be on 4.0.5 RC2. Verify with Help | About that both Firmware and UI show 4.0.5. 2 insure all UPS and other electronics at PLM plug point are on a FilterLinc 3 Access Points should be positioned for good phase coupling. It is okay to position them for RF device communication as well but phase coupling is primary function. Run 4 tap set button test starting with the PLM to verify the Access Points are in reliable range of the PLM. Run 4 tap set button test first from one Access Point and then the other to insure they are in reliable RF range of each other and on opposite phases. Establishing good phase coupling should be done before adding any devices. 4 Factory reset each device before adding to the ISY. Add with ‘erase existing links’ option which should be redundant but insures no links are carried forward in case the factory reset was not successful. 5 start with devices closest to the PLM and work outward. Insure each device is working well before proceeding to the next device. Run Tools | Diagnostics | Event viewer at LEVEL 3. Turn the device On and Off several times from the Admin Console watching the event trace for Hops Left=x count. Devices near the PLM would be expected to have a Hops Left=2. If that is not the case stop and find the issue before adding the next device. 6 spot check existing devices as a new device is added to insure the load being controlled by the new device is not adversely affecting existing devices. I am sure this seems like a lot of work and perhaps overkill. It is much easier to find and fix problems as they are discovered rather than add all the devices and find the same old problems are still there.
Steve Sullivan Posted June 5, 2013 Author Posted June 5, 2013 Thank you both. I will be replacing upgrading the isy to the new 994 so I'll make sure it's on the latest firmware. I'll follow your advice, and I certainly would like to figure out what "went wrong/bad" as this install is over 4 years old. Adding devices and linking is going to be a bit of work but not nearly as much as re-doing all of my scenes and programs. Do you guys know of a way to "export" my current programs? So I could have a reference while rebuilding? I'm not currently home and cannot log in remotely for some reason but I can't remember a way to do this. Thank you for your help
oberkc Posted June 5, 2013 Posted June 5, 2013 Do you guys know of a way to "export" my current programs? No...not programs only. The only way I know to "export" stuff is via backup. Unfortunately, this could potentially be also restoring your problems, which I am sure you are hoping to avoid. I'm not currently home and cannot log in remotely for some reason but I can't remember a way to do this. Or, perhaps, your IP address has changed? (This can happen from time to time.)
Steve Sullivan Posted June 5, 2013 Author Posted June 5, 2013 Something has changed with my dns, I can't access anything at the house at the moment. I'll have to figure out something to reference the old programs. Probably just set up the old Isy on another network/computer...
Steve Sullivan Posted June 5, 2013 Author Posted June 5, 2013 That would work but it would be a lot of them:) More I am thinking of this whole parts swap / start from scratch thing, the more I think I'm going to try and isolate the current issues before changing much around. Think I'll replace any suspected bad switches/ motion sensors/ access points first and take it from there. Maybe cleanup old programs, see how things go and then hopefully getting the new ISY and PLM working from a clean 99 backup. If I see any issues I can always wipe and start over.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.