Release 3.3.6 (RC3) Is Now Available

foxcob · December 16, 2012

LeeG,

I went back to 3.3.6 like you requested and deleted the troublesome KPL from the ISY. I then re-linked it and wiped all existing links from the device. Just in case I had also hard reset the KPL before re-linking. After the ISY had added the KPL, the first thing I attempted to do was set the led brightness. Nothing seems to happen on the KPL. I attached a screenshot of the following levels being set: 0/5, 2/10, and 7/15.

Jacob

foxcob · December 16, 2012

This was supposed to be attached to my last post...

LeeG · December 17, 2012

My 3.3.6 Admin Console is using a different option in the 2E command when setting LED Brightness on my v.36 KPL.

What does Help | About show for the Firmware and UI level.

Is it correct the progress bar is now completing?

LeeG · December 17, 2012

The command issued on my system is using 07 as the 2E variant. The command in your post shows the 03 variant. Since both are v.36 KPLs I would expect both commands to use the same variant. The 7/15 (7F) is setting the same brightness level

Sun 12/16/2012 03:26:42 PM : [iNST-TX-I2 ] 02 62 16 7D 60 1F 2E 00 00 03 7F 00 00 00 00 00 00 00 00 00 50

Sun 12/16/2012 07:20:41 PM : [iNST-TX-I2 ] 02 62 15 9A F9 1F 2E 00 01 07 7F 00 00 00 00 00 00 00 00 00 00 4B

foxcob · December 17, 2012

Both the UI and firmware report version 3.3.6 with the exact same date code after them. The progress bar does seem to complete now. BTW, I tried setting a different KPL backlight and it worked. I noticed the commands were different preceding the brightness HEX value when talking to the other KPL. Obviously the address was different, but the commands looked different too. Could the ISY be retaining some config for this KPL after deleting it? This is just weird. When I tried the upgrade again BTW, all the KPLs exhibited the problem again. Restoring from my last 3.3.5 backup which have all but the one KPL working restored the other KPLs to a working status. So something is going wrong during the upgrade of my configuration I would think.

Jacob

LeeG · December 17, 2012

One thing for sure, stop playing with various backups. Restore the 3.3.6 backup. Nothing from a previous device definition should carry forward after deleting and adding the device back from scratch. Is the v.36 KPL a Relay or a Dimmer.

The progress bar situation is resolved with everything at 3.3.6. Letâ€™s stick with that and find the answer to the command variation question.

foxcob · December 17, 2012

So I looked up the command in the insteon command table and found that the command decodes as so:

02 62 16 7D 60 1F 2E 00 00 03 05 00 00 00 00 00 00 00 00 00 00 CA

02 - STX

62 - Extended Message

16 7D 60 - Address

2E 00 - Extended Get/Set

00 - Button/Group number 0

03 - Set LED-Off mask for button

05 - Mask (if bit = 0, LED not affected, if bit = 1, LED turns off when button pressed)

Rest ignored

This makes some sense since after issuing this command the keypad LED's misbehave, but the link table is corrupted as well which I don't understand.

The 07 in place of the 03 would set the Global LED brightness.

Jacob

foxcob · December 17, 2012

The KPL is a dimmer.

LeeG · December 17, 2012

You have access to internal documentation that I do not. The wrong 2E variant is being used for a LED Brightness change. I will leave it up to UDI to clear this up. Suggest opening a ticket with UDI tech support.

foxcob · December 17, 2012

In case you're wondering, I got the command documentation by searching for "insteon commands table" in google. Top item listed was a PDF from insteon.net.

LeeG · December 17, 2012

That document is from 2007. Much has changed since 2007.

Tunaman · December 17, 2012

Installed 3.3.6.

Seems to be fully functional, but looks like there might be an issue with the admin interface.

If the gui isn't maximized. it seems to have trouble painting the ELK security status/buttons.

Screenshot attached.

I do have the elk module.

Michel Kohanim · December 17, 2012

Jacob,

As LeeG suggested, it's VERY important not to go back and forth between backup/firmware releases. when upgrading to 3.3.6, all database files are upgraded. We might have an issue with the upgrade process. This said, going back to firmware 3.2.6 will only exacerbate issues. Again, as LeeG suggested, please:

1. Restore a backup from 3.2.6

2. Remove the KPL in question

3. Add it back in

Let me know if you have the same issues with other KPLs as you have with the one in question.

Hi tunaman,

What operating system and Java version?

With kind regards,

Michel

oskarw · December 17, 2012

I also have Elk module. Win 7 64 bit. Java ver 7 update 9. and the Elk area gets messed up as the previous screen capture. What I noticed is that it gets drawn correctly, and only when the mouse cursor is moved over individual buttons (without clicking) that the buttons get copied over as if they were tool tip and copied to where the mouse was dragged.

Michel Kohanim · December 17, 2012

Hi oskarw,

Thanks so very much for the feedback. Would you be kind enough to let me know the UI version for the Admin Console? Also, if possible, can you try http://www.universal-devices.com/99i/3.3.5 instead and let me know if you still have the same problem?

With kind regards,

Michel

john3morton · December 17, 2012

I am having an issue with alerts.

Any NEW or MODIFIED alerts since installing the 3.3.x series will not be sent via teXt message.

Existing alerts are sent just fine, for any program.

Luckily I have 2 "general" alerts which still function, but the new alerts I have created with specific information about the alert are not working.

I tried creating new alerts after installing 3.3.6 and the problem persists.

Any ideas????

UPDATE:

Sending NEW or MODIFIED alerts via email works just fine. Only sending as a text is not working which makes no sense as the isy sends an email either way...????

As I said, existing alerts are working fine as texts.

~John

(BTW: love my ISY!)

oskarw · December 18, 2012

Michel,

I've tested the link to 3.3.5 and it all works correctly. I then went back to 3.3.6 and it works correctly as well. I've tested in both normal and maximized windows and I can't replicate the error. I then erased all of the Java cache and downloaded new 3.3.6 and it works correctly. I'll report if the problem repeats itself.

oskarw · December 18, 2012

Michel,

Everything, including Elk Module with secure port seems to work but I just took a peak at the Error Log and here is the copy from the last few minutes.

My ISY is on .160 and my laptop where I'm accessing the admin console is .31 Where should I start to troubleshoot why there is such a flood of socket errors and these GET /desc requests?

Mon 2012/12/17 18:54:41 System -170001 [HTTP] 192.168.44.31:49597->80

Mon 2012/12/17 19:06:44 System -170001 [HTTP] 192.168.44.31:49790->80

Mon 2012/12/17 19:06:44 System -170001 [HTTP] 192.168.44.31:49791->80

Mon 2012/12/17 19:06:44 System -170001 [HTTP] 192.168.44.31:49792->80

Mon 2012/12/17 19:06:44 System -170001 [HTTP] 192.168.44.31:49793->80

Mon 2012/12/17 19:06:44 System -170001 [HTTP] 192.168.44.31:49794->80

Mon 2012/12/17 19:06:44 System -170001 [HTTP] 192.168.44.31:49795->80

Mon 2012/12/17 19:06:45 System -170001 [HTTP] 192.168.44.31:49796->80

Mon 2012/12/17 19:06:45 System -170001 [HTTP] 192.168.44.31:49797->80

Mon 2012/12/17 19:06:45 System -170001 [HTTP] 192.168.44.31:49800->80

Mon 2012/12/17 19:07:13 System -170001 [HTTP] 192.168.44.31:49803->80

Mon 2012/12/17 19:07:13 System -170001 [HTTP] 192.168.44.31:49806->80

Mon 2012/12/17 19:07:13 System -170001 [HTTP] 192.168.44.31:49809->80

Mon 2012/12/17 19:07:15 System -170001 [HTTP] 192.168.44.160:2480->80

Mon 2012/12/17 19:07:15 System -170001 0: GET-->/desc

Mon 2012/12/17 19:07:15 System -170001 [HTTP] 192.168.44.160:2481->80

Mon 2012/12/17 19:07:15 System -170001 0: GET-->/desc

Mon 2012/12/17 19:07:15 System -170001 [HTTP] Socket not active#2 26

Mon 2012/12/17 19:07:15 System -170001 [HTTP] 192.168.44.160:2482->80

Mon 2012/12/17 19:07:15 System -170001 0: GET-->/desc

Mon 2012/12/17 19:07:15 System -170001 [HTTP] Socket not active#2 32

Mon 2012/12/17 19:07:15 System -170001 [HTTP] 192.168.44.160:2483->80

Mon 2012/12/17 19:07:15 System -170001 0: GET-->/desc

Mon 2012/12/17 19:07:15 System -170001 [HTTP] Invalid socket 26

Mon 2012/12/17 19:07:15 System -170001 [HTTP] 192.168.44.160:2488->80

Mon 2012/12/17 19:07:15 System -170001 0: GET-->/desc

Mon 2012/12/17 19:07:15 System -170001 [HTTP] Socket not active#2 26

Mon 2012/12/17 19:07:15 System -170001 [HTTP] 192.168.44.160:2489->80

Mon 2012/12/17 19:07:15 System -170001 0: GET-->/desc

Mon 2012/12/17 19:07:15 System -170001 [HTTP] 192.168.44.160:2490->80

Mon 2012/12/17 19:07:15 System -170001 0: GET-->/desc

Mon 2012/12/17 19:07:15 System -170001 [HTTP] Socket not active#2 32

Mon 2012/12/17 19:07:15 System -170001 [HTTP] 192.168.44.160:2491->80

Mon 2012/12/17 19:07:15 System -170001 0: GET-->/desc

Mon 2012/12/17 19:07:15 System -170001 [HTTP] Invalid socket 26

Mon 2012/12/17 19:07:15 System -170001 [HTTP] 192.168.44.160:2497->80

Mon 2012/12/17 19:07:15 System -170001 0: GET-->/desc

Mon 2012/12/17 19:07:16 System -170001 [HTTP] 192.168.44.160:2498->80