JCBond Posted December 30, 2012 Posted December 30, 2012 I have a network of about 40 Insteon devices. I recenly 'upgraded' 5 KPLs to the latest version and they were working fine with any software version prior to 3.3.6. I even had a program to change the LED levels twice a day. When I installed v3.3.6 they all went crazy. I would press a button on the KPL and many other buttons would turnon at the same time. Since I installed 3.3.7 I removed them all from the software. Manually reset them. Re-added them to the system and added them to their respective scenes. All the scenes are working, and the KPLs seem to work. EXCEPT I can NOT get the LED levels to change using the ISY. They are stuck in the default level. I have tried the recomended Query insteon engine, and no change. I even moved the ISY so that it's PLM was on the same cicuit as the KPLs ALL 5 units are behaving the same way. They all worked before v3.3.6, they all went crazy with 3.3.6 and now none of them work on the LED levels Here is a log of an attempt to change the level: Sun 12/30/2012 10:01:34 AM : [iNST-TX-I2CS] 02 62 1D F5 6B 1F 2E 00 00 03 7F 00 00 00 00 00 00 00 00 00 00 50 Sun 12/30/2012 10:01:34 AM : [iNST-ACK ] 02 62 1D.F5.6B 1F 2E 00 00 03 7F 00 00 00 00 00 00 00 00 00 00 50 06 (00) Sun 12/30/2012 10:01:35 AM : [iNST-SRX ] 02 50 1D.F5.6B 13.26.DF 27 2E 00 (00) Sun 12/30/2012 10:01:35 AM : [std-Direct Ack] 1D.F5.6B-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Sun 12/30/2012 10:02:03 AM : [iNST-TX-I2CS] 02 62 1D F5 6B 1F 2E 00 00 03 09 00 00 00 00 00 00 00 00 00 00 C6 Sun 12/30/2012 10:02:03 AM : [iNST-ACK ] 02 62 1D.F5.6B 1F 2E 00 00 03 09 00 00 00 00 00 00 00 00 00 00 C6 06 (00) Sun 12/30/2012 10:02:03 AM : [iNST-SRX ] 02 50 1D.F5.6B 13.26.DF 23 2E 00 (00) Sun 12/30/2012 10:02:03 AM : [std-Direct Ack] 1D.F5.6B-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Sun 12/30/2012 10:02:07 AM : [iNST-TX-I2CS] 02 62 1D F5 6B 1F 2E 00 00 03 09 00 00 00 00 00 00 00 00 00 00 C6 Sun 12/30/2012 10:02:07 AM : [iNST-ACK ] 02 62 1D.F5.6B 1F 2E 00 00 03 09 00 00 00 00 00 00 00 00 00 00 C6 06 (00) Sun 12/30/2012 10:02:08 AM : [iNST-SRX ] 02 50 1D.F5.6B 13.26.DF 27 2E 00 (00) Sun 12/30/2012 10:02:08 AM : [std-Direct Ack] 1D.F5.6B-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Quote
foxcob Posted December 30, 2012 Posted December 30, 2012 JCBond, I have experienced the same thing as you. For now I have returned my system to 3.2.6 and restored from my backup when I was at 3.2.6. Everything went back to normal after I restored my KPLs from there. I cannot get them to work right from 3.3.x. Unfortunately I cannot beta test in this state since my KPL's all stop working and my wife's patience would be much shorter than mine with these conditions. I hope they figure this out soon. Jacob Quote
IndyMike Posted December 30, 2012 Posted December 30, 2012 Michel, I concur with foxcob and JCbond. After upgrading from 3.3.5 to 3.3.7 I can no longer control backlight on KPL's (mine are I2). Backlight on my I2CS SWL works fine. Below are the event viewer results for the respective firmware revisions. Neither generates errors. 3.3.5 adjusts KPL lighting, 3.3.7 does not. Let me know if you need additional information V3.3.5 KPL Backlight Sun 12/30/2012 15:50:33 : [iNST-TX-I2 ] 02 62 19 46 CE 1F 2E 00 01 07 7F 00 00 00 00 00 00 00 00 00 00 4B Sun 12/30/2012 15:50:33 : [iNST-ACK ] 02 62 19.46.CE 1F 2E 00 01 07 7F 00 00 00 00 00 00 00 00 00 00 4B 06 (00) Sun 12/30/2012 15:50:33 : [iNST-SRX ] 02 50 19.46.CE 0C.A8.B4 2B 2E 00 (00) Sun 12/30/2012 15:50:33 : [std-Direct Ack] 19.46.CE-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 V3.3.7 KPL Backlight Sun 12/30/2012 16:03:26 : [iNST-TX-I2 ] 02 62 19 46 CE 1F 2E 00 00 03 7F 00 00 00 00 00 00 00 00 00 00 50 Sun 12/30/2012 16:03:26 : [iNST-ACK ] 02 62 19.46.CE 1F 2E 00 00 03 7F 00 00 00 00 00 00 00 00 00 00 50 06 (00) Sun 12/30/2012 16:03:26 : [iNST-SRX ] 02 50 19.46.CE 0C.A8.B4 2B 2E 00 (00) Sun 12/30/2012 16:03:26 : [std-Direct Ack] 19.46.CE-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Quote
Xathros Posted December 31, 2012 Posted December 31, 2012 FWIW, I have 2 8 Button I2 KPL's that are working perfectly with 3.3.7 with regard to backlight changes. I had one event in 3.3.6 where the load on one of them turned on to 6% when the LED's were supposed to dim but that only happened once and it's been perfect since 3.3.7. My KPL's are FW V.36 and V.40. It was the v.40 that turned the load on instead of a backlight change once. I have 2 Fanlincs. One of those had the LED's turn back on with 3.3.6 and I could not turn them back off until 3.3.7. Once I installed 3.3.7 and did a Query Insteon Engine on that Fanlinc, I was able to turn the LEDs back off. Both Fanlincs are v.41 but only one had this problem and again, both are now fine with 3.3.7 -Xathros Quote
Michel Kohanim Posted December 31, 2012 Author Posted December 31, 2012 Hello all, Thanks so very much for all the feedback and certainly a good timing since we are still in Beta! We are looking into everything here right now and hopefully we'll find a resolution soon. Thanks again and HAPPY NEW YEAR to all. With kind regards, Michel Quote
rahnee Posted December 31, 2012 Posted December 31, 2012 I too have 3 8 Button KPL v40 that do not work properly since 3.3.6. When pressing the "H" button I get other buttons that also light. Additionally scene changes that are supposed to update the buttons do not work consistently anymore. Each KPL is different...nothing is exactly the same...but none of them work correctly. All my 6 button KPL's seem to be working properly...however some of my scenes are "inconsistent" with regards to updating the button status. It is hit or miss....very frustrating. Also as reported by others, I cannot get the backlighting to adjust. Quote
Michel Kohanim Posted December 31, 2012 Author Posted December 31, 2012 Hi rahnee, Backlight not working is a command that's sent from ISY. What you are describing is a device configuration (i.e. multiple buttons turning on/off) ... furthermore, scenes not working has nothing to do with firmware: it's the programming within the device. Did you change anything with these devices after the upgrade? With kind regards, Michel Quote
foxcob Posted December 31, 2012 Posted December 31, 2012 Michel, I know you posted the question to rahnee, but I experienced the same thing. My KPLs worked correctly until I attempted to set the backlight brightness. After that, my button configurations seemed to be all messed up. Specifically, I noticed that button H on one of my 8 button KPLs was acting completely differently than it had before causing other buttons to light up and triggering other scenes. Don't know if this helps. Jacob Quote
IndyMike Posted January 1, 2013 Posted January 1, 2013 foxcob and JCBond, I have not seen the button issue on my V.39 KPL. The KPL does exhibit the backlight issue. Since the button action is controlled by the link table, would you mind performing a "device link scan" and compare? Please post the results if you see compare differences. Quote
foxcob Posted January 1, 2013 Posted January 1, 2013 IndyMike, I'll have to look and see if I still have a screencap of my table comparison around. I do remember off hand that it had a mis-compare on the very last entry of the offending KPL. Jacob Quote
Michel Kohanim Posted January 1, 2013 Author Posted January 1, 2013 Thank you all ... we are looking into it as we speak. With kind regards, Michel Quote
foxcob Posted January 1, 2013 Posted January 1, 2013 Got it, You can see the last record is incorrect. This happens after attempting to set the KPL backlight brightness. Jacob Quote
LeeG Posted January 1, 2013 Posted January 1, 2013 foxcob The last record that is labeled mismatch is not an error. In the device it has the first byte as 00 which marks the End Of List. The remainder of the data (7 bytes) have no meaning in the End Of List record. It is labeled a mismatch because the ISY Links Table display shows a dummy End Of List record which is all 00's. The ISY does not store an actual End Of List record in the ISY data as it would take up 8 bytes unnecessarily. That looks like a Show Device Links display from something earlier than 3.3.7 as the End Of List record is now annotated with ignored/mismatch rather than just mismatch. So long as the active records are identical the actual device link database is correct. Quote
IndyMike Posted January 1, 2013 Posted January 1, 2013 Initial upgrade from 3.3.5 to 3.3.7: Don't remember the ISY performing a Query at restart. This normally requires quite a bit of time on my system. The lack of a query could explain the inability to control ramp rates, etc. Reboot: ISY does perform a query on reboot. Curiously, my 2 AM shutdown program evaluates to "true" and runs. Local time is after 10 AM. I have a similar program set to turn off the basement at 11:20 - it does not run. Program is set NOT to run at startup. Thought this might be an error with the grace period. Set the grace period to 0 with the same effect. If Time is 2:00:00AM Then Set Scene '1st Floor / SC 1st Floor Off' Off Wait 1 minute Set Scene 'Basement / SC BSMT' Off Else - No Actions - (To add one, press 'Action') Link Table Reads: Can't read the last record (511) from device EEprom anymore (range restricted to 510 by ISY). This was very handy for determining X10 addresses, etc. Can we get this back? I can read the 127th record from my Icon units with the reduced memory. Icon Config info: 127 : 0C00 : 50 10 39.00.00 00 00 00 Downgraded to 3.3.5: 1) 2 AM program still runs on re-boots. Disabling "Catch up Schedules at Re-start" prevents the program from running. 2) Link table read range restricted in 3.3.5 as well. Not sure when this was implemented. Quote
Michel Kohanim Posted January 1, 2013 Author Posted January 1, 2013 Hi IM, Thanks so very much. Query at startup has always been there and the function for which has never changed. We're looking into all other issues. With kind regards, Michel Quote
Michel Kohanim Posted January 2, 2013 Author Posted January 2, 2013 Hello All, Just wanted to let everyone know that we found the bug with KPL backlight issue and it's fixed. And, I want to thank every one for providing us with feedback and diagnostics information. We should have another RC (hopefully the last one) by the end of the week. With kind regards, Michel Quote
foxcob Posted January 2, 2013 Posted January 2, 2013 Michel, Thanks for your work on this and thanks to any others who are behind the scenes! Looking forward to trying the next beta now. Jacob Quote
elvisimprsntr Posted January 2, 2013 Posted January 2, 2013 BACKGROUND I have been getting NTP retry errors and USSockets errors (which incidentally is not listed on the error codes wiki). Not sure what beta release these started showing up, but they were not present with the last official release. I can manually sync time without a problem. I am using "us.pool.ntp.org" as the NTP server. Tue 2013/01/01 00:00:01 System -140005 Net Module Rule: 25 Tue 2013/01/01 00:00:01 System -140005 Net Module Rule: 28 Tue 2013/01/01 00:00:02 System -140005 Net Module Rule: 30 Tue 2013/01/01 00:00:03 System -140005 Net Module Rule: 36 Tue 2013/01/01 00:00:03 System -140005 Net Module Rule: 39 Tue 2013/01/01 00:00:04 System -140005 Net Module Rule: 41 Tue 2013/01/01 00:46:17 System -60006 Stopping retries/next cycle Tue 2013/01/01 05:00:00 System -140005 Net Module Rule: 24 Tue 2013/01/01 05:00:01 System -140005 Net Module Rule: 23 Tue 2013/01/01 05:00:01 System -140005 Net Module Rule: 30 Tue 2013/01/01 05:00:02 System -140005 Net Module Rule: 35 Tue 2013/01/01 05:00:02 System -140005 Net Module Rule: 34 Tue 2013/01/01 05:00:03 System -140005 Net Module Rule: 41 Tue 2013/01/01 14:59:31 System -170001 [uDSockets] RSub:44 error:6 Tue 2013/01/01 14:59:36 System -170001 [uDSockets] RSub:44 error:6 Tue 2013/01/01 14:59:41 System -170001 [uDSockets] RSub:44 error:6 Tue 2013/01/01 14:59:46 System -5012 30 Tue 2013/01/01 18:00:01 System -140005 Net Module Rule: 23 Tue 2013/01/01 18:00:01 System -140005 Net Module Rule: 23 Tue 2013/01/01 18:00:02 System -140005 Net Module Rule: 30 Tue 2013/01/01 18:47:01 System -60006 Stopping retries/next cycle Wed 2013/01/02 00:00:01 System -140005 Net Module Rule: 25 Wed 2013/01/02 00:00:01 System -140005 Net Module Rule: 28 Wed 2013/01/02 00:00:02 System -140005 Net Module Rule: 30 Wed 2013/01/02 00:00:03 System -140005 Net Module Rule: 36 Wed 2013/01/02 00:00:03 System -140005 Net Module Rule: 39 Wed 2013/01/02 00:00:03 System -140005 Net Module Rule: 41 Wed 2013/01/02 05:00:00 System -140005 Net Module Rule: 24 Wed 2013/01/02 05:00:01 System -140005 Net Module Rule: 23 Wed 2013/01/02 05:00:01 System -140005 Net Module Rule: 30 Wed 2013/01/02 05:00:02 System -140005 Net Module Rule: 35 Wed 2013/01/02 05:00:03 System -140005 Net Module Rule: 34 Quote
Michel Kohanim Posted January 2, 2013 Author Posted January 2, 2013 Hello elvisimprsntr, It seems that at the same time you had problems communicating with network resources (not receiving a response from the resource). Do you always get those (i.e. the resource never responds)? Also, please note that we have had a lot of trouble with pool.ntp.org especially if you have other devices on the network using pool.ntp.org. I have found NIST's time servers to be the most responsive: http://tf.nist.gov/tf-cgi/servers.cgi Would you please try one of these and let me know whether or not you are still having these errors? With kind regards, Michel Quote
rahnee Posted January 2, 2013 Posted January 2, 2013 Thanks for the update Michel. All the issues I experienced with the backlighting started at the same time as the buttons (aka scenes) not updating properly. The system has been in place for 6 months with none of these issues before the updated firmware. (I updated for IO Linc control). Hopefully it all come (back)together after the next release. Quote
arw01 Posted January 3, 2013 Posted January 3, 2013 Also, please note that we have had a lot of trouble with pool.ntp.org especially if you have other devices on the network using pool.ntp.org. I have found NIST's time servers to be the most responsive: http://tf.nist.gov/tf-cgi/servers.cgi Do we just cut and past that whole url in place of the pool.ntp.org, or need to put something else in there? Quote
steelman58 Posted January 3, 2013 Posted January 3, 2013 arw01, You insert: time.nist.gov Gerard Quote
arw01 Posted January 8, 2013 Posted January 8, 2013 Thank you. Michael, I would like to see a message that tells me the clock was set (maybe the difference in time) when I manually do the sync. Also, how about showing on the configuration screen the last time it synced the time please. Thanks Alan Quote
Michel Kohanim Posted January 8, 2013 Author Posted January 8, 2013 Hi Alan, My pleasure and all great ideas which have been added to our requirements list. With kind regards, Michel Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.