These is just a sample of what's there. I started looking at this file because a couple of my programs to turn off devices at a particular time do not appear to be running since 2 nights ago despite IoX showing them enabled at start-up. The 'turn-on' at sunset programs works but the 'turn-offs' at 10:45pm do not seem to run. So I was curious what would be in this file. Since it is an "error" file I would generally expect this file to be empty - things are running fine.

I also wasn't sure when someone would want to run the "Restore PLM" option in IoX, as if would running that fix all of these random errors? I did not want to try since that requires all battery devices be turned on and to gather them all would be a hassle. In the end I just want my "turn-off" programs to run (which do not involve any battery powered devices) and am very curious why there is so much content in the error file.

Also curious why the filename is called ISY Error Log and not EISY Error Log

 

at 2024/12/07 04:26:40 AM    0    -170001    <s:Envelope><s:Body><u:GetISYConfig xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetISYConfig></s:Body></s:Envelope>
Sat 2024/12/07 04:26:46 AM    0    -170001    Authenticate
Sat 2024/12/07 04:26:47 AM    0    -170001    <s:Envelope><s:Body><u:GetStartupTime xmlns:u="urn:udi-com:service:X_IoX_Service:1"></u:GetStartupTime></s:Body></s:Envelope>
Sat 2024/12/07 04:26:47 AM    0    -170001    <s:Envelope><s:Body><u:GetSysConf xmlns:u="urn:udi-com:service:X_IoX_Service:1"><name>/CONF/INTEGER.VAR</name></u:GetSysConf></s:Body></s:Envelope>
Sat 2024/12/07 04:26:48 AM    0    -170001    <s:Envelope><s:Body><u:GetSysConf xmlns:u="urn:udi-com:service:X_IoX_Service:1"><name>/CONF/STATE.VAR</name></u:GetSysConf></s:Body></s:Envelope>
Sat 2024/12/07 04:26:48 AM    0    -170001    <s:Envelope><s:Body><u:GetVariables xmlns:u="urn:udi-com:service:X_IoX_Service:1"><type>1</type></u:GetVariables></s:Body></s:Envelope>
Sat 2024/12/07 04:26:48 AM    0    -170001    <s:Envelope><s:Body><u:GetVariables xmlns:u="urn:udi-com:service:X_IoX_Service:1"><type>2</type></u:GetVariables></s:Body></s:Envelope>

If I recall correctly, 170001 messages are informational and can be ignored.

ISY is still the base of UD's platform. eisy is the hardware that runs the ISY system.

If some programs are not running correctly, try rebooting eisy and see if it makes a difference.

2 hours ago, raymondjiii said:

but the 'turn-offs' at 10:45pm do not seem to run

Did you just migrate to eisy? If yes, there is a know quirk with the first run programs that use time of day... leaving it as is and letting it run for a day or 2 will permanently resolve it

I've had the Eisy for about a year maybe - every thing was fine until 2 nights ago. When I saw that things were not working I did a hard reset, restored from backup and waited to see. The next night things still did not turn off. The thing is other "turn off at" programs are running fine. Just not the outdoor one, there are about 10 devices in that program. From the days of X10 I would always make a second one to run in case the furnace was on when the first one ran (runs like 15 minutes later). Oddly, that one did not shut things off either. Then I wondered, it's cold out - but they do respond to the turn-on program. But, one of the 10 devices is inside (a switch that powers an outside receptacle) and that one did not turn off either. So I am ruling out the cold weather, which I found hard to believe since it was all devices. I'll see what happens tonight and tomorrow night to see if that quirk resolves (but the other turn-off time of days programs are working fine).

I believe the firmware was updated to .4 on that hard-reset, but then again the one turn-off program stopped working at .3. The only thing I can think of is too many devices in the program (which was never a problem before).

Edited December 7, 2024Dec 7 by raymondjiii

If a load turns on but not off then it could be the load, when on, that's creating noise on the powerline. I doubt that the issue is with the eisy itself.

3 hours ago, Techman said:

If a load turns on but not off then it could be the load, when on, that's creating noise on the powerline. I doubt that the issue is with the eisy itself.

Maybe....but it's been same load since I owned an Isy994 and now and Eisy.

Loads can go bad. What do you have plugged in to the device, i.e. led bulbs have a electronic driver circuit. 

7 low voltage (12V AC) transformers and two strings of LED lights - each item is plugged into it's own outlet (the Insteon dual controlled outlets top and bottom). They all couldn't have gone bad at once. But I can try to unplug one every night and see if that makes a difference.

The low voltage transformers are capable of creating noise on the power line. All you need is for one to go bad. Best to try process of elimination as you suggested.

35 minutes ago, Techman said:

The low voltage transformers are capable of creating noise on the power line. All you need is for one to go bad. Best to try process of elimination as you suggested.

Wait a minute....I woke up at 4am, all of the outdoor lights were on. I opened UD Mobile, went to Favorites and hit the Outside lights button and that was it - done. It could be intermittent thing I guess.