Jump to content

2.4.13


maui4marko

Recommended Posts

Posted

I upgraded to 2.4.13 and much to my dismay I lost some things.

 

Here's what happened: yesterday I installed 14 new devices and added multiple scenes for them (under 2.4.12). Today I installed the new release and all that's left of yesterday's work are the raw devices (no names and no scenes).

 

Not sure what I did wrong. I tried backing out the changes, but looks like I'll have to redo from scratch.

Posted
Do you do a backup from before you installed the beta?

 

If so then you can use that to get your stuff back.

 

Yes, I backed up and restored the backup but for some reason its not there... just the device addresses - none of my updates showed up.

Posted

No, actually I didn't know about that link. I have been launching it "normally" and haven't had any issues like this to date.

 

What is different about the link beta link that I should know about?

Posted

maui4marko,

 

Apologies for the inconvenience.

 

You do not have to use that link. What you are doing it correct (going directly to the device's URL).

We might have a bigger problem than the update to 2.4.13 if you've lost your previously created scenes/updates. Would you do me a favor? Please create one scene, call it Test, add a device into it as a Responder, and then reboot ISY. Please let me know if still have the scene and the device after reboot.

 

With kind regards,

Michel

 

No, actually I didn't know about that link. I have been launching it "normally" and haven't had any issues like this to date.

 

What is different about the link beta link that I should know about?

Posted

Ok, did the test and the Test scene is still there. The ones I lost were just created yesterday - I'm guessing that has something to do with it.

 

Here's a screen shot after reboot.

 

isy.jpg[/img]

 

Earlier, I also tried doing a Factory Reset, reloading 2.4.13, and then reloading my saved config and same results.

Posted

Some follow-up info:

 

- ISY could control the devices, but the status always showed as Off

- I had to remove the devices and relink them and then the status showed correctly

- The devices remembered the previous ramp and on levels, but not ISY

- I had to recreate the scenes from scratch

 

After performing the above actions, ISY appears to be functioning normally

Posted

maui4marko,

 

Thanks so very much for the update. The fact that the status of your devices were always off means that the "links" were not written to the PLM. Two cases:

1. The PLM was locked up

2. You have reached the 417 max number of links allowed by the PLM. How many devices do you have?

 

This said, however, I still can't figure out why your would lose your scenes. This, to me, is a much more serious problem which requires more investigation. Please do let me know if you find other strange behavior.

 

With kind regards,

Michel

 

Some follow-up info:

 

- ISY could control the devices, but the status always showed as Off

- I had to remove the devices and relink them and then the status showed correctly

- The devices remembered the previous ramp and on levels, but not ISY

- I had to recreate the scenes from scratch

 

After performing the above actions, ISY appears to be functioning normally

Posted

I've got 39 devices installed and currently 19 scenes. I have the beta PLM which I think I remember supports ~1000 links. Some of my scenes have lots of devices, so is it possible I'm running up against the limit?

 

I've only made a first pass at the scenes, so could probably reduce the number and complexity. Is there any way of telling how many links I have, through memory usage or other means?

 

I do have more devices planned, so it will definitely be worth my time to fully understand where I sit in terms of usage.

 

Thx,

Marko

Posted

A related issue:

 

The 2 KPLs (one in 6 button mode, other in 8 button mode) no longer "take" any scenes assigned to them. After setting it a scene and assigning the KPL as a Controller, it won't respond to button presses. The On/Off lights will activate, but the scene does not come on.

 

ISY can turn on and off the scene, but I'd kinda like my buttons to do it too :?

 

I have tried doing a Factory Reset on the KPLs to no avail. Have also tried Restoring the KPL, as well as the PLM.

 

Could this be related to the PLM being a beta version? It is Firm 56 dated 8/15/07.

 

Any suggestions on how I can get the KPLs functioning again with scenes?

 

mahalo,

Marko

Posted

maui4marko,

 

Ah, I had totally forgotten that you have the Beta PLM. No, I don't think the PLM is the issue. I think something is "seriously" wrong somewhere.

 

The reason that factory reset/restore device does not fix the problem is that the the responders in the scene have to have a slave link pointing to your KPL. It seems that the responders in your scene do not have that link. Would you be kind enough to let me know what happens if you remove of the responders from the scene and then try adding it back?

 

Thanks and with kind regards,

Michel

 

A related issue:

 

The 2 KPLs (one in 6 button mode, other in 8 button mode) no longer "take" any scenes assigned to them. After setting it a scene and assigning the KPL as a Controller, it won't respond to button presses. The On/Off lights will activate, but the scene does not come on.

 

ISY can turn on and off the scene, but I'd kinda like my buttons to do it too :?

 

I have tried doing a Factory Reset on the KPLs to no avail. Have also tried Restoring the KPL, as well as the PLM.

 

Could this be related to the PLM being a beta version? It is Firm 56 dated 8/15/07.

 

Any suggestions on how I can get the KPLs functioning again with scenes?

 

mahalo,

Marko

Posted

Aloha Michel,

 

I removed the responders and added back - no change.

 

I know you said its not the PLM, but its almost as if it is remembering the corrupt links and cannot overcome that.

 

Since the Broncos are totally choking, I spent some time today and did additional testing as follows:

- removed all devices that were "corrupted"

- did factory reset on all corrupted devices

- did an ISY backup

- removed PLM

- factory reset ISY

- power off ISY & PLM

- reload 2.4.13 to ISY

- reload saved settings

- restore PLM

 

My logic was to try to get back to a clean slate in trying to eliminate all traces of the corrupt devices.

 

I then created a new test scene by adding corrupted/reset KPL & a couple corrupted/reset devices.

 

Same behavior as before...KPL will not control scene. I then tried adding a corrupted/reset SL to control the scene to try to isolate if it was just the KPL or if it is all corrupted devices. Same result - SL could not control the scene either.

 

As before, ISY will turn on/off the scene from the GUI but the controller device will not. That is why I'm thinking that the PLM is "remembering" the bad links and no matter what I try, I cannot delete or overwrite those bad links.

 

I also tested whether manual links between the corrupt KPL & corrupt devices work, and they do. The KPL will properly control any of the devices via manual links. It is only when using scenes that it doesn't work properly.

What's my next step?

 

Mahalo,

Marko

Posted

Marko,

 

Thanks so very much for taking the time and going through the trouble of diagnosing the issues. If I understand it correctly, your PLM is reset, your ISY is factory reset, your KPL/SL are reset, and in the first scene you create, the controllers do not control each other but ISY can control both. If this is the case, then the PLM is NOT the culprit simply because ISY can control the scene. Device to device links (i.e. your KPL to SL) do not require PLM to be functional. So, this leads me to believe one or more of the following:

1. We have a bug in ISY ... for which I have already started the root cause analysis

2. Are you sure you are putting both of your devices as "controllers" in the scene?

3. If 2 is "true", then could it be that "one" of your devices (the responder usually) is defective

 

The next step is please allow me to figure out if we have a bug in ISY. This should not take longer than late tonight or early tomorrow morning. If we cannot find a bug/reproduce the probelm, and if the answer to #2 above is "yes", then we have to figure out which one of your devices are causing the problem.

 

Again, please accept my sincere apologies for the troubles you're experiencing.

 

With kind regards,

Michel

 

Aloha Michel,

 

I removed the responders and added back - no change.

 

I know you said its not the PLM, but its almost as if it is remembering the corrupt links and cannot overcome that.

 

Since the Broncos are totally choking, I spent some time today and did additional testing as follows:

- removed all devices that were "corrupted"

- did factory reset on all corrupted devices

- did an ISY backup

- removed PLM

- factory reset ISY

- power off ISY & PLM

- reload 2.4.13 to ISY

- reload saved settings

- restore PLM

 

My logic was to try to get back to a clean slate in trying to eliminate all traces of the corrupt devices.

 

I then created a new test scene by adding corrupted/reset KPL & a couple corrupted/reset devices.

 

Same behavior as before...KPL will not control scene. I then tried adding a corrupted/reset SL to control the scene to try to isolate if it was just the KPL or if it is all corrupted devices. Same result - SL could not control the scene either.

 

As before, ISY will turn on/off the scene from the GUI but the controller device will not. That is why I'm thinking that the PLM is "remembering" the bad links and no matter what I try, I cannot delete or overwrite those bad links.

 

I also tested whether manual links between the corrupt KPL & corrupt devices work, and they do. The KPL will properly control any of the devices via manual links. It is only when using scenes that it doesn't work properly.

What's my next step?

 

Mahalo,

Marko

Posted

Michel,

 

Thank you for being so responsive, especially during non-business hours.

 

I'll post further tomorrow, but just want to clarify that these issues are only related to the devices that were "corrupted" during the original upgrade process. The other devices I have that were not affected are functioning normally both w/ISY and without.

 

I'll do some more testing in the morning and post my specific scenario and setup so as to help with your diagnosis.

 

Thx, Marko

Posted

Hi Marko,

 

We did find a bug in ISY. By any chance, did you add your devices using "Add New Insteon Device"? If so, this feature does NOT overwrite existing links and that's what's causing all your problems.

 

As a work-around for corrupted devices, would you be kind enough to do the following:

1. If you are adding your devices by Address, make sure to follow them up with a Restore Device OR

2. Add your device using the "Start Linking" method

 

Please do be kind enough to let me know how it goes.

 

With kind regards,

Michel

 

Michel,

 

Thank you for being so responsive, especially during non-business hours.

 

I'll post further tomorrow, but just want to clarify that these issues are only related to the devices that were "corrupted" during the original upgrade process. The other devices I have that were not affected are functioning normally both w/ISY and without.

 

I'll do some more testing in the morning and post my specific scenario and setup so as to help with your diagnosis.

 

Thx, Marko

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...