Jump to content

Recommended Posts

Posted

Do you know when you might be also work on the wild card years so an event can be set to run every year without changing it each year.

Posted

Today I was out.  My ISY went into a script that turns on some lights and then sends me a success or error email.  I got hundreds of emails saying error  I tried to log in and could not.  I got home and 1/2 lights were not on.  I noticed clocks were blinking which means power went out.  We did have high winds.  So I unplugged ISY AND POWERLINC because I kept getting emails.  Once I did that the emails stopped and within a minute or two i could log in.  Then I was able to turn on lights manually through ISY.

 

Any idea what happened or do you agree it was the power outage.  Any way to stop this by something like a UPS?

 

Jeff

 

Sent from my iPhone

Posted

It is not set to run at startup. The power went out hours before. I hace had this happen once before when the power goes out for a second and then the unit acts strange. Some devices would respond and some would not. Rebooting worked.

 

This time I think the script was running correctly. It it errors it is set to run again in a minute. This loop continues until it has success. Normally a second run is never needed. Sometimes something does not turn on and it has to run a secOnd time but never before has it had to run 100 times. I could not log into ISY.

 

So I think the lights that were off were not responding at all. Thus it errored. It kept erroring until I rebooted the unit. Then I was able to log in and turn on one of the lights. So then I ran the script and it got success first try.

 

I think we get very light power drops. Some devices stay on and others reboot. I think this is freezing the ISY. This has happened before and I was home. Last time I could log in but a lot of commands would not work. So I rebooted and they all worked.

 

Assuming it is the power can I put the ISY on ups but plug powerlinc into wall.

 

Jeff

Posted

Hi Jeff,

 

What is your PLM version number? Is it dual band or the regular 2412S? If 2412S, this all makes sense as it seems that the PLM had a hard time initializing before ISY tried communicating with it.

 

If you have 2413S, you can always use a power supply with ISY and put the power supply on UPS. ISY should be able to recover from communications errors with the PLM.

 

With kind regards,

Michel

Posted

I have a 2413s. So plug the ISY power adapter into a UPS but the 2413s cant go into a UPS, right?

 

Also yesterday morning a lot of things did not turn off that should have. All I did was unplug each device and plug them back in. Instantly after plugging back in the device turned off (normally it would have remembered the status in the memory). My theory again is that the low voltage we get when the power switches some of them freeze up as does the PLM (we are between two power stations and if one has problems there is an auto-switch to the other. This causes a brief low voltage. Some devices like large TV's might turn off and others might keep playing like a blu-ray.) Unplugging the device unfroze it and it went to the state it was told to be in but too frozen to fix.

 

This is going to be a strange issue I probably just have to deal with. Once I unplug the "frozen" devices they work fine after that until the next power issue which only happens in high wind or ice storms.

Posted

If the modules in question are ApplianceLincs and a hardware revision 4.2.

They default to Off after a power loss. Unlike the earlier revision ones that default to the On or Off state they where in at power loss. Same for the latest Icon Appliance Module

Posted

Actually they are all appliancelincs and icon relays but although they are off they are reporting on. Once I unplug them they are off and report off until the next power issue.

 

Jeff

Posted

If they are Off and you Query them and they report On then that is an issue to discuss with Smarthome.

 

If they were On and the Admin Console shows them On, then power drops and they come up Off as the new devices now do, the ISY and Admin Console will not know they are Off because they do not report status changes at the device. It is necessary to Query the devices to determine if they are On or Off.

 

A Program can be defined that runs at startup to Query those devices if you want the Admin Console and ISY to be aware of status after a power cycle.

Posted

Hi Jeff,

 

There is an option on the Configuration panel to Query at Startup.

ISY-99i/ISY-26_INSTEON:System_Configuration

Unfortunately, if you put the ISY on a UPS it will not be restarted.

 

I have to believe there would be some way to use an IOLinc to be triggered by a minimum voltage which could Wait x seconds and then run the Query All program.

 

I don't know what you could do to reset the devices though. Cycle the breakers somehow?

 

Rand

Posted

Both Insteon controlled thermostats continue to loose connection. I disable them, and then re-enable them. That works until I restart the ISY admin, or until I perform a query of devices.

Posted

upgraded from 2.8.14 without any problems following the very specific instructions. although I have both a mac and windows 7 machine, i always use windows for upgrades.

 

Not sure if the following is specific to 2.8.16 or not, or what forum might be more appropriate, but here it goes...

 

I have two routers using DD-WRT client bridge so i can relocate my IT equipment. when I connected the ISY-99i to the client bridged router, I had all sorts of problems access the ISY-99i admin console. I could log in, but once I clicked on an action to turn a light on the unit would stop communicating on the network which required me to reboot the ISY. All my other IT equipment works fine on the LAN side of the client bridged router. Hopefully it's just some obscure router setting that is causing the problem. Any suggestions would be appreciated.

 

Elvis

Posted

Hello phenneberry,

 

Would you please provide more information? Is it that you lose contact with ALL your devices or just the thermostats? If thermostats, then this is a known issue which SmartHome is working on. If all devices, then more information would be greatly appreciated.

 

Hi Elvis,

 

Do you have any Network Resources and or programs? What would happen if you turned on a device physically? Would the status on Admin Console get updated? Also, have you taken a look at your Error Logs ... if so, can you post anything that you find out of the ordinary?

 

With kind regards,

Michel

Posted

I have a very simple program that turns down the heater every weekday morning at 7:30 (in case everyone leaving forgets to turn it down). This has been one of my most reliable programs. The program is "enabled" and the program summary shows that it should have fired.

 

IF

On Mon,Tue,Wed,Thu,Fri

Time is 7:30:00AM

 

Then

 

Set 'Heating / 14.25.64-Main '60° (Heat Setpoint)

 

Else

 

I've noticed that it is not firing at 7:30 AM since I upgrade to 2.8.16. So far, this is the only program (out of 20+ with schedules) that appears not to be working. The log shows no command being sent out from the ISY.

 

I only noticed it today and my first thought was that it had to do with the M-F type scheduling. I also have a pool program that is M-F (another for weekends) and I thought it might not be working as I remember having to turn on the pool manually last week. However, it fired today as expected so that is not it (my pool pump not responding to ISY commands, while not frequently, does happen).

 

Before someone asks, this does not appear to be related to the RF adapter problem. The t-stat is being fully responsive and the log shows several status updates from the t-stat before and after the 7:30 time but no command to set the setpoint to 60.

Posted

Don't know if this a known issue, but I just installed a Morninglinc RF module, and it would only work by pressing the "set" button and the "start linking" command within the console. Putting in the address of the module directly (like I've done with the 50 or so modules already in the system) would not work. I did the proper "link devices / save links" check box, but something about putting in the address did not work. It went on for an hour or 2, and then gave some kind of error. Pushing the "set" and choosing "start linking" worked immediately, and it works fine.

 

Just an FYI.

Posted

Another minor observation (problem), I sometimes run the Event Viewer for extended timeframes to try and capture strange events (troubleshooting). Normally this works just fine and I typically save and clear its log twice a day (and restart the viewer) if I run it for more than a day.

 

I normally set the Event Viewer to "Device Communications Events" (old level 3). However, since moving to 2.8.16 (from 2.8.12 BTW), the log stops recording anything beyond "Status/Operational Events" (old level 1) sometime in the wee hours of the morning. Yesterday, I started the viewer are 13:36 and it ran fine until 05:37 when it seemed to change its recording level.

 

I am pasting a part of the event log to show the issue. BTW, I have a program that issues a general Query (all devices) at 6:00 AM every morning and I would expect to see that traffic in the event log starting at 06:00.

 

Tue 03/01/2011 05:36:00 AM : [iNST-SRX ] 02 50 14.2B.96 00.00.02 C7 13 02 LTOFFRR(02)

Tue 03/01/2011 05:36:00 AM : [standard-Group][14.2B.96-->Group=2] Max Hops=3, Hops Left=1

Tue 03/01/2011 05:36:00 AM : [ 14 2B 96 2] DOF 2

Tue 03/01/2011 05:36:00 AM : [ 14 2B 96 2] ST 0

Tue 03/01/2011 05:36:00 AM : [iNST-SRX ] 02 50 14.2B.96 00.00.02 C7 13 02 LTOFFRR(02)

Tue 03/01/2011 05:36:00 AM : [standard-Group][14.2B.96-->Group=2] Max Hops=3, Hops Left=1

Tue 03/01/2011 05:36:00 AM : Duplicate: ignored

Tue 03/01/2011 05:36:00 AM : [iNST-SRX ] 02 50 14.2B.96 00.00.02 C7 13 02 LTOFFRR(02): Process Message: failed

Tue 03/01/2011 05:36:00 AM : [standard-Group][14.2B.96-->Group=2] Max Hops=3, Hops Left=1

Tue 03/01/2011 05:36:01 AM : [iNST-SRX ] 02 50 14.2B.96 0F.D4.08 41 13 02 LTOFFRR(02)

Tue 03/01/2011 05:36:01 AM : [standard-Cleanup][14.2B.96-->ISY/PLM Group=2] Max Hops=1, Hops Left=0

Tue 03/01/2011 05:36:08 AM : [iNST-SRX ] 02 50 11.9A.A8 00.00.02 C7 13 02 LTOFFRR(02)

Tue 03/01/2011 05:36:08 AM : [standard-Group][11.9A.A8-->Group=2] Max Hops=3, Hops Left=1

Tue 03/01/2011 05:36:08 AM : [ 11 9A A8 2] DOF 2

Tue 03/01/2011 05:36:08 AM : [ 11 9A A8 2] ST 0

Tue 03/01/2011 05:36:08 AM : [iNST-SRX ] 02 50 11.9A.A8 00.00.02 C7 13 02 LTOFFRR(02)

Tue 03/01/2011 05:36:08 AM : [standard-Group][11.9A.A8-->Group=2] Max Hops=3, Hops Left=1

Tue 03/01/2011 05:36:08 AM : Duplicate: ignored

Tue 03/01/2011 05:36:08 AM : [iNST-SRX ] 02 50 11.9A.A8 00.00.02 C7 13 02 LTOFFRR(02): Process Message: failed

Tue 03/01/2011 05:36:08 AM : [standard-Group][11.9A.A8-->Group=2] Max Hops=3, Hops Left=1

Tue 03/01/2011 05:36:09 AM : [iNST-SRX ] 02 50 11.9A.A8 0F.D4.08 41 13 02 LTOFFRR(02)

Tue 03/01/2011 05:36:09 AM : [standard-Cleanup][11.9A.A8-->ISY/PLM Group=2] Max Hops=1, Hops Left=0

Tue 03/01/2011 05:37:31 AM : [ 14 25 64 1] CLISPH 142

Tue 03/01/2011 05:38:55 AM : [ 14 25 64 1] ST 130

Tue 03/01/2011 05:41:08 AM : [ 14 25 64 1] ST 132

Tue 03/01/2011 05:42:16 AM : [ 14 25 64 1] ST 130

Tue 03/01/2011 05:43:24 AM : [ 14 25 64 1] ST 132

Tue 03/01/2011 05:50:31 AM : [ 14 2B 96 1] DON 1

Tue 03/01/2011 05:50:33 AM : [ 1 2E 1D 1] ST 255

Tue 03/01/2011 05:50:33 AM : [ 14 2B 96 1] ST 255

Tue 03/01/2011 05:50:33 AM : [ 11 9A A8 1] DON 1

Tue 03/01/2011 05:50:33 AM : [ E 9D C7 1] ST 255

Tue 03/01/2011 05:50:46 AM : [ E 9D C7 1] ST 191

Tue 03/01/2011 05:51:01 AM : [ E 9D C7 1] ST 127

Tue 03/01/2011 05:51:16 AM : [ E 9D C7 1] ST 63

Tue 03/01/2011 05:51:31 AM : [ E 9D C7 1] ST 0

Tue 03/01/2011 05:51:33 AM : [ 1 2E 1D 1] ST 0

Tue 03/01/2011 05:52:26 AM : [ 14 2B 96 1] DOF 1

Tue 03/01/2011 05:52:26 AM : [ 14 2B 96 1] ST 0

Tue 03/01/2011 06:00:55 AM : [ 14 25 64 1] ST 134

Tue 03/01/2011 06:04:12 AM : [ 14 25 64 1] ST 132

Tue 03/01/2011 06:05:20 AM : [ 14 25 64 1] ST 134

Tue 03/01/2011 06:23:40 AM : [ 4 96 80 1] ST 0

Tue 03/01/2011 06:25:41 AM : [ 14 25 64 1] ST 136

Tue 03/01/2011 06:26:49 AM : [ 14 25 64 1] ST 134

Tue 03/01/2011 06:29:01 AM : [ 14 25 64 1] ST 136

Tue 03/01/2011 06:32:17 AM : [ 11 6A C6 1] DON 0

Tue 03/01/2011 06:32:17 AM : [ 11 6A C6 1] ST 255

Tue 03/01/2011 06:38:30 AM : [ F C6 18 3] DON 0

Tue 03/01/2011 06:38:30 AM : [ F C6 18 3] ST 255

Tue 03/01/2011 06:38:30 AM : [ E 9D B8 1] ST 255

Tue 03/01/2011 06:38:30 AM : [ F C7 21 1] ST 255

Tue 03/01/2011 06:38:31 AM : [ F C6 18 1] DON 0

Tue 03/01/2011 06:38:31 AM : [ F 48 CB 1] ST 255

Posted

Hello JP,

 

1. Stupid question: are you sure the program is enabled? Also, what is the last runtime for this program?

2. Event log levels are GLOBAL and reset to the lowest when another instance of Admin Console is started

 

Hello telljcl,

 

The only way to link MorningLinc is to use the set button and then use the third option (keep existing links):

http://www.universal-devices.com/mwiki/ ... orningLinc

 

With kind regards,

Michel

Posted

Yes, the program is enabled and the last run time was:

 

Heater Off (daily) Heater Off (daily) On - Idle True Tue Mar 01 07:30:00 PST 2011 Tue Mar 01 07:30:00 PST 2011 Wed Mar 02 07:30:00 PST 2011

 

On the Event log, that would explain it. I have another PC that is starting the Admin Console inadvertently.

Posted

I upgraded from .15 yesterday and it seems I have a problem similar to one I had several revisions back.

 

It seems that after the ISY is running for some period of time, I lose IP connectivity to the ISY. It works after a power off/on but then notice it will stop responding to any requests.

 

What information is needed to help isolate this instead of just powering it off and back on?

 

Thanks.

Posted
Yes, the program is enabled and the last run time was:

 

Heater Off (daily) Heater Off (daily) On - Idle True Tue Mar 01 07:30:00 PST 2011 Tue Mar 01 07:30:00 PST 2011 Wed Mar 02 07:30:00 PST 2011

 

On the Event log, that would explain it. I have another PC that is starting the Admin Console inadvertently.

Hello JP,

 

So according to the summary, the program ran, but no command was sent?

 

Try removing and recreating the setpoint line in THEN, save (and ensure it is enabled), and test.

Posted

I am at a loss. I swear this worked differently before but I am having so many problems maybe since the release candidate a week ago.

 

Anyways, when I use the ISY to control stuff I am fine but if I actually use the insteon switch, the status in the ISY does not update until I do a query of the system. I have one set every night and it takes a few minutes with all my devices.

 

I dont know what to do. My programs are not working because some say something like if light is on then do this. Well if I turn light on from ISY it works fine. Turn it on from switch and nothing happens because the device status in the ISY is still off.

 

I unplugged ISY and PLM multiple times. What can I do?

 

Jeff

Posted

Jeff

 

When the ISY controls the devices and Scenes Ok but manual control at the device(s) is not reflected back to the ISY it means there is a problem with the link records between the device(s) and the ISY PLM. If a single device (or only a few devices) is having an issue then Restore Device (right click on device node in My Lighting tree) will cause the ISY to rewrite the device link database. Best to try this as first solution as it is the fasted of the recovery options. If all the devices have the same issue then likely the PLM was reset along the way and File | Restore Modem (PLM) is needed. This process can be lengthy if a large number of devices are defined.

 

Lee

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...