AD8BC

It's all good. Thanks IndyMike! The second PLM restore after I restored from my backup went so much better.

That makes sense. I've got a good backup that should work. Should I do a factory reset of the PLM first?

Just looked at my PLM links table. Seems a little light. Yet trying to do another PLM Restore does nothing. What should my next steps be?

Finally had my 8 year old serial PLM completely die. Just received my new one. Followed the instructions to replace and restore the PLM (plug in PLM, boot EISY, etc). Did a restore PLM and manually restored devices that had issues.... I can send commands to individual devices now from the admin console, but it will not receive states from the devices nor can I send commands to groups or scenes. In most cases I can query an individual device but that's about it. What am I missing here? Did the devices' link tables get written but possibly the PLM did not? Thanks y'all! EDIT: Tried rebooting EISY through both power cycle and Reboot command in admin console. Still no luck. EDIT 2: Another weird symptom. Seems like items are missing from the scenes in the admin console (on levels, etc.)

I had this problem in the beginning when I migrated to the EISY. It couldn't reach the time server through my router, but when I plugged it in directly to my Uverse modem it worked. I ended up finding a setting in my router that would enable NTP (I use the Ubiquti Dream Machine router).

I finally got back home from an extended trip and started playing with this again. I ended up putting the EISY right on the AT&T Uverse LAN (before my Ubiquiti router) and the time set. After further troubleshooting, I found some settings in the Ubiquiti router that needed to be enabled and mapped to a timeserver -- it seems like, since the time server isn't settable in the EISY, it's looking for the router to be the NTP server (I think). Of course, since I can't change the time manually, I won't know if this is the final solution or not until perhaps DST goes away again or the internal clock starts to lose time for some reason. Thanks for all of your help, guys!

Yeah I think so. I didn't want to do it on the holiday weekend, I'm heading out on a trip for the next week so I'll open a ticket when I get back home -- things are running well on the old ISY. I did get it talking over the hardwire Ethernet. I connected it right up to the router instead of the unmanaged switch and it's coming up in the finder now. Thanks for your help Techman. I know you've been here for a long time.

Yup. Every time.

Yeah I tried setting up via Ethernet first. UD Mobile didn't see it until I disconnected it, restarted it, and went the wifi route. I evert tried manually setting up UD Mobile with the IP address that the router assigned to it via DHCP.

No dice. Left it disconnected from power for a good hour. Also I've run the package update numerous times.

It's connected by WiFi right now with DHCP. When I connect to the network with the Ethernet port I can see the device from the network (different IP) and ping it but the launcher won't find it. I've cleared the cache, re-downloaded the launcher, rebooted the device, restarted the device, did the hokey pokey, and I'm still a few days and hours ago.

I am in the process of commissioning a new EISY. I have both running on my network right now and can switch the PLM between them since they are running essentially the same system. However, the EISY will not set it's time. The ISY will synchronize with the computer and the NTP server, but the EISY will not. Tried rebooting, tried power cycling, tried pulling the power and turning it back on. I've searched for solutions on the forum but nothing seems to be awry with my router or anything like that. Also tried manually setting time via SSH and FreeBSD commands. Was not allowed. Should mention everything was upgraded and it's running version 5.8 and the UI and firmware match. Using Ubiquiti Dream Machine router on AT&T Uverse. Also, I'll add this to the thread, the IoX finder only works when the EISY is connected by Wi-Fi. When hard wired to Ethernet it isn't found, although I can see it on my router and ping the IP address. And the Admin Console only has settings for one Ethernet device which appears to be the wireless. I would like to hardwire Ethernet this if possible. @Michel Kohanim you're my only hope LOL. Thanks!

I came here to make sure I wasn't alone! Mine is down too.

I want to take a moment here to commend Universal Devices for their outstanding support. I just visited my forum profile here and discovered I joined here nearly 12 years ago. Which means I've been a UDI customer for nearly that long, and I have never - NEVER - had a bad experience. Or even a mediocre one. Every single time I have run into an issue with my ISY I have had almost immediate support. Whether it be on a weekday or on a Sunday evening, I get responses on the forum and the trouble ticket system within hours. I get NOTHING like that at work when I deal with my industrial automation vendors. Michel loves his company and I can tell that he puts his blood, sweat, and tears into it. UDI has a focus on continuous improvement and customer service. And the community here is just as awesome. Thanks, guys, for all of your help.

Brian I just had the same thing happen over the past few months. It literally took a day of being unplugged for it to reset. Sometimes it would work for a few weeks, sometimes just a few hours. I replaced it last month. Seems they only last a few years.

On a similar note, I have a 911 Flash keypad button at the front door that flashes the outside lights if double-tapped (FastOn). It also sends me a text message. The flash program stops when the button is turned off or fastoff. Really, instead of a flash, it uses a "repeat' routine with a large number of repeats. That way it will eventually time out. I did this because one time we had an ambulace come to the house and they couldn't find the place. Now I can tell 911 to look for the flashing lights.

Thanks Michel, I put it in on Saturday. So far it works great compared to .13! -- Bill

Hi Michel, Should I try the .14b to see if it solved my .13b problems?

Gotcha, thanks Michel, I'll wait!

That depends, I'm a little behind the times here... what would constitute i1 only mode? I never ever had problems with the PLM locking up. Maybe this weekend I'll try to reload the .13 firmware and see if I can replicate the problems again.

Sure Michel, it comes up v52.

Well, Michel, version .8 has been running reliably since last Thursday. All statuses seem to be reporting just fine to the ISY (with the exception of the motion sensor, I may have to re-install it into the ISY.

Michel, Unfortunately, with the exception of the one new Icon relay switch, two Icon lamplinks (that have been running fine) and the motion sensor, the rest of the items on my network that I have been having difficulty with are 14-20 months old, unless the new items are somehow corrupting communications with the old ones. This morning everything seems to be running well since I manually ran the "Query All" last night, with the exception that my motion sensor doesn't seem to be reporting to the ISY -- could this be because I went from .13b to .8? I'll play a little more after work this evening. Thanks for your help! Oh, what did you mean by how long more on my 30 day? -- Bill

It has gotten more interesting. I downgraded back to 2.6.8... Same issues. But I did some further poking around... It still did not reliably hear when devices turned ON. But it always heard FAST ON, OFF, FAST OFF. But here's the kicker -- in some cases, on the affected devices that are dimmers, I could not use the ON command from the Administrative Console... If the light was ON at any level, clicking on ON would turn the unit OFF. Then, after doing a REFRESH ALL, everything seems to work again.

Well since I got back home from vacation I have been doing a little playing around. I still have the same issue with my new Icon Relay switch for the bedroom closet. When I turn it on locally, the status does not change in the ISY. However, it always seems to recognize a Fast ON and I think it recognizes an ON after that. Or, the same old Query Device works and then it will also recognize the Local ON after that for a time. I also seem to have an issue with at least three other switches... two SWLs and one KPL. And with these it's not always a local ON that isn't recognized... it's sometimes a remote group ON that will do it. I know I have a problem because I have a group that illuminates a KPL LED when any inside light is on (uses an ISY program). Sometimes when one of these lights is turned ON the progam won't run because it won't get the status. And this all seemed to noticeably happen after upgrading to .13. I loaded the beta after having issues with .11 and my motion sensor... I'm at work now but I'll get rev levels of the devices I am having difficulty with tonight or tomorrow.