dakall

You are absolutely correct. It has been more than a year since I originally set it up; I forgot about the numzones parameter. I had gotten a replacement eisy about a month ago. The PG3 backup I had was old and didn't have this node server. I had to set it up again, and obviously failed to read all the instructions. That's my bad. Thanks.

Let me start by saying that this was working perfectly. I'm not sure exactly when this stopped, but I noticed today that the plug-in is only seeing Zones 1-8 and not 9-16. When I look at the Nodes on the PG3 page 9-16 are not listed or included. It used to show 1-16. Obviously they are not showing up in the IoX Admin Console either. I deleted the plug in and installed into a different slot and got the same results. On the PG3 page, it is showing 10 nodes: Node1 = Alarm Panel Node2 = partition 1 Node3 - Node10 = Zone 1 to Zone 8 But yet when I log directly into the EvisaLink I see 16 zones and it tells me if open or how long closed. I have not changed any of the settings since I got it working several months ago. Could a recent PG3 or IoX update be the culprit?

Updated and rebooted. All seems fine. Great work, as always.

UPDATE: I started a ticket, and after a few back-and-forth messages with Michel, he decided that a remote session was needed. After about 20 minutes of poking around in the eisy, he showed me there were 2 directories that were showing 49GB in size. He said not only should there nothing that size, he was also unable to open those directories. He said that was signs of the harddrive failing. I had also experienced 3 or 4 strange glitches in the past month, but I was able to reboot and go on as normal. I now wonder if this was the early signs of the drive failure. UD is sending me a replacement eisy, and hopefully in a couple of days I can have things back to normal. I cannot say enough good things about the service and support I received. A big thank you to Michel and the UD staff.

Thanks. I did try the button presses, but no luck. I also cannot load the sysconfig.txt file. I will start a support ticket.

I awoke to a notification that PG3 had stopped during the night. Made sense since none of the early morning routines didn't run. I tried to reboot it via the app. I got a notification that the eisy went offline, and then crickets. I waited about 20 minutes but could not access it via the app or the AC. I could, however, ping it on my network, but could not establish an ssh connection. I then unplugged it for 15 minutes and reapplied power. It's been 25 minutes now and still no response. I do have the blue light though. Is there some button combination I can do? Fortunately, I did back it up 2 days ago, so if I end up wiping it, hopefully I can easily restore everything. Any help is greatly appreciated.

Regardless of DST, solar noon is 6 hours after sunrise in your examples. DST does not increase the times between sunrise and sunset. We as humans just offset our clocks from those times.

How are you getting those sunrise/sunset numbers? Are you converting the times somehow?

That's exactly what I'm trying to do. Open up the east side shades, wait an hour and close the west side shades. I currently have the program run at 11:45 am, but I have to change to 12:45 pm when DST kicks in.

Does anyone know of an easy way to compute the time of day for Solar Noon? (midpoint between sunrise and sunset) I know there are variables for sunrise and sunset, but I can't average them together successfully. Or is there a node server that does that? I use the Timedata NS which has lots of info, but not solar noon.

That's exactly what I was thinking. I have 2 other dedicated circuit outlets in that closet. I can try shuffling things around if need be. I'm hoping this was a one-time event.

None that I noticed. The PLM is plugged into a dedicated circuit outlet in the AV closet. The only other thing plugged into that outlet is a small UPS unit for my router.

Of course the one thing I didn't do fixes it. Thanks Interesting thing is that right after I plugged it back in, all the LEDs returned to their "daytime" levels. I didn't need to do anything.

PLM is less than 6 months old. I will try this.....

I can no longer control the backlight LED brightness from the AC or UD Mobile app. I run a program in the evening that sets the switches/dimmers backlight in the bedrooms to 0%, and then back to 30% in the morning. Last night, only some of them dimmed. This morning the ones that dimmed did not brighten. Like I said, I currently cannot change the backlight setting from both the AC or the app. Things I have tried: Reboot eisy (multiple times) Retore most recent backup form AC Restore devices from AC I did get a notification on the app last night (which would have been prior to the dimming program executing) that said "PG3 stopped working." I ignored it since everything seemed to be working fine and all the "bedtime" programs ran normally with the exception of the LED dimming. I don't believe it's a PLM issue since I can still control everything from the AC and the app, so communications seem to be fine. I should add that I'm running PG3x 3.2.17 and IoX 5.8.0