Michel Kohanim Posted November 27, 2012 Author Share Posted November 27, 2012 Hi Andy, Thank you. Doesn't the screen scroll up/down? MAC has been nothing but a nightmare lately. johncrab, Thanks so very much for the update! With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
andyf0 Posted November 27, 2012 Share Posted November 27, 2012 Hi Andy, Thank you. Doesn't the screen scroll up/down? MAC has been nothing but a nightmare lately. johncrab, Thanks so very much for the update! With kind regards, Michel It has been this way for some time. I remember posting about it previously somewhere. It's hard to do a screen grab while doing a drag and drop since you've got the button held down while dragging. Maybe there's a key sequence that will work. I'll post later if I can get it. Edit: AGAIN, fooled by the box that is drawn by dragging and dropping. I am hovering over the scene/folder to drop in to with the box instead of the arrow. You really should do something about that. Sorry for the alarm! Quote Link to comment Share on other sites More sharing options...
johnnyt Posted November 28, 2012 Share Posted November 28, 2012 I upgraded to 3.3.4 RC1 and my IOlincs started getting changed to momentary A from latching. It started (that I noticed) with the addition of a new 2 week old IOLinc, which showed latching but behaved in a momentary fashion. It wasn't until I queried the options that momentary A showed up. I changed it to latching and all was fine after. But then one of my other older IOLinc's began behaving as though it was configured momentary ON. It had been operating in latching mode for about 2 years until now. It also showed latching until I did a query and it changed to momentary A. I changed it no problem and decided to check all my other IO Lincs and sure enough the same thing happened - showed latching, queried, showed momentary A, changed it, all seems to be fine now. A bug? A known issue? What's the risk this will happen again? Have attached the relevant section of my event viewer log output set to level 3. Lots of new xml-type stuff I've not seen in event viewer before... (ignore the variables being set along the way - they stream in from some temp sensors via an Autelis RS232-to-ISY converter but it's too hard to go through what comes out as a single line txt file in Notepad to find and delete them out) ISY-Events-Log.v3.3.4__Wed 2012.11.28 03.50.48 PM.rar Quote Link to comment Share on other sites More sharing options...
LeeG Posted November 28, 2012 Share Posted November 28, 2012 johnnyt You will find the event log much easier to read when using WordPad rather than NotePad. Quote Link to comment Share on other sites More sharing options...
johnnyt Posted November 30, 2012 Share Posted November 30, 2012 Good to know about using Wordpad. What about the IO Linc's changing from latching to momentary? Sent from my iPod touch using Tapatalk Quote Link to comment Share on other sites More sharing options...
LeeG Posted November 30, 2012 Share Posted November 30, 2012 I don't remember other reports like that. However, 3.2.6 was not processing the Set Options correctly for I2CS I/O Lincs. The 3.3.4 release (or maybe 3.3.3) corrected that problem. It is possible that the ISY had one of the Momentary mode indicators stored from 3.2.6 that was not reflective of the actual settings. I checked my I2CS I/O Linc which indicates Latching Mode and is operating in Latching Mode but that may be from my testing of the fix when it became available. Quote Link to comment Share on other sites More sharing options...
johnnyt Posted November 30, 2012 Share Posted November 30, 2012 I checked all nine of my IO Lincs this morning (all used in latching mode) and one of them changed to momentary after I queried it. I don't know whether or not it was behaving in latching or momentary mode before - I just thought I would query it. It's an older one (not i2CS). I'll keep checking periodically. Quote Link to comment Share on other sites More sharing options...
LeeG Posted November 30, 2012 Share Posted November 30, 2012 Was this a Query request or a Set Options request? Quote Link to comment Share on other sites More sharing options...
johnnyt Posted November 30, 2012 Share Posted November 30, 2012 set options Quote Link to comment Share on other sites More sharing options...
LeeG Posted November 30, 2012 Share Posted November 30, 2012 I just ran an Event trace while doing a Set Options | Query on an older non-I2CS I/O Linc. Nothing was written back to the I/O Linc. Are any commands issued to the I/O Linc through the ISY plugin? Quote Link to comment Share on other sites More sharing options...
thedishking Posted November 30, 2012 Share Posted November 30, 2012 Hello, I just upgraded to 3.3.4 a few days ago, and my unit locked up last night. I had been running official release 3.2.6 since it was released, and did not have to reboot once. Should I post my error logs? Or should I email them to Michel? Thanks! Travis Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted November 30, 2012 Author Share Posted November 30, 2012 Hi Travis, I am so very sorry to hear. We did have one other report of this issue which, apparently, had to do with some device/program interactions. Still unsure as to the exact reason but it's now fixed. Questions: 1. Do you have any devices to which you cannot communicate (i.e. red ! marks next to them)? 2. If you look at your logs, do you see a lot of X10 activity (if any) right prior to the hang? 3. Is your router Linksys Exxx series? If so, are you certain that you have the latest firmware on it? 4. If you have DirecTV, has anything changed on your setup? With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
thedishking Posted November 30, 2012 Share Posted November 30, 2012 Hi Michel, I will answer below in blue 1. Do you have any devices to which you cannot communicate (i.e. red ! marks next to them)? No, everything looks good. I do have some scenes that fail diagnostic test, but they appear to work. I have added a few programs lately, trying to migrate everything to ISY from HomeSeer. 2. If you look at your logs, do you see a lot of X10 activity (if any) right prior to the hang? Not that I can see. I don't have any X10 in my home. 3. Is your router Linksys Exxx series? If so, are you certain that you have the latest firmware on it? Nope, Netgear R6300. To be perfectly clear, I do have a Linksys E3000 running purely as an AP (DHCP turned off, running only with LAN port enabled), with DD-WRT Firmware. The Linksys stock firmware crashes too much for me. 4. If you have DirecTV, has anything changed on your setup? Nothing has changed. Only the occasional reboot of the HR34 IRD. ISY Error Log.v3.3.4__Fri 2012.11.30 04.21.06 PM.zip Quote Link to comment Share on other sites More sharing options...
thedishking Posted November 30, 2012 Share Posted November 30, 2012 I don't know if it is helpful, but the unit locked up around 7 or so last night. I rebooted (power cycle) unit around 10 or so last night. Travis Quote Link to comment Share on other sites More sharing options...
Michel Kohanim Posted November 30, 2012 Author Share Posted November 30, 2012 Hi Travis, Bad answers: not what I was hoping to hear!!! At the moment, what I recommend is this: 1. Clear your Error Log so that we can start fresh 2. Reboot your Linksys Router (not the NetGear one) even though it does not have Linksys firmware 3. Let's wait for it to happen again 4. Send me the Error Log directly (support@universal-devices.com) With kind regards, Michel Quote Link to comment Share on other sites More sharing options...
johnnyt Posted December 1, 2012 Share Posted December 1, 2012 I just ran an Event trace while doing a Set Options | Query on an older non-I2CS I/O Linc. Nothing was written back to the I/O Linc. Are any commands issued to the I/O Linc through the ISY plugin? if you mean my homeseer plug-in, I don't do anything to my iolincs with HS. They are used exclusively with ISY. Can you glean anything from the event log I attached earlier (post 53) as to whether or not the options I set were reported as successful? Sent from my iPod touch using Tapatalk Quote Link to comment Share on other sites More sharing options...
LeeG Posted December 1, 2012 Share Posted December 1, 2012 johnnyt The only I/O Linc commands setting options are for Key Beep Off and Latching Mode Quote Link to comment Share on other sites More sharing options...
klundy Posted December 1, 2012 Share Posted December 1, 2012 I upgraded to 3.3.4 last weekend. I thought I was seeing some strange intermittent behavior of devices coming on. I found it is not intermittent. I have programs that change the LED backlight on KPLs in bedrooms. Anytime the program ran to adust the backlights, the load comes on. Brighten or dim, doesn't matter. It also occurs if I try to manually adjust the backlights via the admin console. Interestingly, the backlights do not change anymore. Just the load comes on. KPL Dimmer v.36 KPL Relay v.36 KPL Relay v.98 all exhibit this behavior. A KPL Dimmer v.2D does NOT turn the load on, but the backlights do not adjust. Kevin Quote Link to comment Share on other sites More sharing options...
LeeG Posted December 1, 2012 Share Posted December 1, 2012 Pick one of the KPLs (not the 2D version as that and 2A firmware have issues), right click and select Diagnostics | Query Insteon Engine. Try the Backlight adjustment. Quote Link to comment Share on other sites More sharing options...
klundy Posted December 1, 2012 Share Posted December 1, 2012 Pick one of the KPLs (not the 2D version as that and 2A firmware have issues), right click and select Diagnostics | Query Insteon Engine. Try the Backlight adjustment. That fixed it. At least for a single test. Care to educate me on that? Thanks!! Kevin Quote Link to comment Share on other sites More sharing options...
LeeG Posted December 1, 2012 Share Posted December 1, 2012 The 3.3.x images depend on the Insteon Engine information being correct because of all the new I2CS support. The Insteon Engine information might not be correct coming from older firmware. Did not bother older firmware without all the new I2CS logic the ISY images now contain. Quote Link to comment Share on other sites More sharing options...
GuitarBuilder Posted December 1, 2012 Share Posted December 1, 2012 I installed 3.3.4 because I wanted to add an LED Insteon bulb and have nothing but problems since then. I had a very stable system before with no issues. Now, I get repeated warnings that various devices are not communicating properly; the onset of these coincides exactly with the upgrade to 3.3.4. In addition, the very reason I upgraded was to add the bulb and it refuses to recognize it! Back to the drawing board, guys! I would greatly appreciate being able to get back to my old stable state. Quote Link to comment Share on other sites More sharing options...
jdickens Posted December 1, 2012 Share Posted December 1, 2012 After upgrading from 3.3.2 to 3.3.4 any and all scene tests fail. Everything else works fine. When I downgrade to 3.3.2 they work. Very repeatable when I upgrade and then downgrade. I have cleared the cache and under "about" it shows the correct version after each firmware change. Any suggestions would be appreciated. I have looked for other posts, but none similar, so it must be something I am overlooking. Quote Link to comment Share on other sites More sharing options...
LeeG Posted December 1, 2012 Share Posted December 1, 2012 The Scene Test fail messages are false. Glitch in 3.3.4. The response from each device in the Scene Test has to be examined to determine if the test was actually successful. Quote Link to comment Share on other sites More sharing options...
golfleep Posted December 2, 2012 Share Posted December 2, 2012 I've upgraded to 3.3.4 without any major issues, except that I've occasionally had trouble adding devices to the ISY. One I've been having trouble with is a dual band on/off KPL (2487S). I can add the device successfully, except that is is always added as an "unsupported device:2.44" I can control the KPL, but none of the other 4 buttons are added to the device list. I'd appreciate any help, I've attached a portion of the event viewer log in case it's helpful: Sat 12/01/2012 08:33:41 PM : [20 41 d5 ] Added to list of devices to link to ISY Sat 12/01/2012 08:33:41 PM : [iNST-TX-I1 ] 02 62 20 41 D5 0F 0D 00 Sat 12/01/2012 08:33:41 PM : [iNST-ACK ] 02 62 20.41.D5 0F 0D 00 06 (00) Sat 12/01/2012 08:33:42 PM : [iNST-SRX ] 02 50 20.41.D5 12.9E.54 27 0D 02 (02) Sat 12/01/2012 08:33:42 PM : [std-Direct Ack] 20.41.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Sat 12/01/2012 08:33:42 PM : [iNST-TX-I1 ] 02 62 20 41 D5 0F 10 00 Sat 12/01/2012 08:33:42 PM : [iNST-ACK ] 02 62 20.41.D5 0F 10 00 06 ID-REQ (00) Sat 12/01/2012 08:33:42 PM : [iNST-SRX ] 02 50 20.41.D5 12.9E.54 23 10 00 ID-REQ (00) Sat 12/01/2012 08:33:42 PM : [std-Direct Ack] 20.41.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Sat 12/01/2012 08:33:51 PM : [iNST-TX-I1 ] 02 62 20 41 D5 0F 10 00 Sat 12/01/2012 08:33:51 PM : [iNST-ACK ] 02 62 20.41.D5 0F 10 00 06 ID-REQ (00) Sat 12/01/2012 08:33:52 PM : [iNST-SRX ] 02 50 20.41.D5 12.9E.54 23 10 00 ID-REQ (00) Sat 12/01/2012 08:33:52 PM : [std-Direct Ack] 20.41.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Sat 12/01/2012 08:33:52 PM : [iNST-SRX ] 02 50 20.41.D5 02.2C.41 87 01 00 (00) Sat 12/01/2012 08:33:52 PM : [std-Broadcast] 20.41.D5-->02.2C.41, Max Hops=3, Hops Left=1 Sat 12/01/2012 08:33:52 PM : [20 41 D5 0 ] Calibrating engine version Sat 12/01/2012 08:33:52 PM : [iNST-TX-I2CS] 02 62 20 41 D5 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Sat 12/01/2012 08:33:52 PM : [iNST-ACK ] 02 62 20.41.D5 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Sat 12/01/2012 08:33:52 PM : [iNST-SRX ] 02 50 20.41.D5 12.9E.54 27 2F 00 (00) Sat 12/01/2012 08:33:52 PM : [std-Direct Ack] 20.41.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Sat 12/01/2012 08:33:53 PM : [iNST-ERX ] 02 51 20 41 D5 12 9E 54 12 2F 00 00 01 0F FF 20 A2 00 12 9E 54 FF 1F 01 DD Sat 12/01/2012 08:33:53 PM : [Ext-Direct ] 20.41.D5-->ISY/PLM Group=0, Max Hops=2, Hops Left=0 Sat 12/01/2012 08:33:53 PM : [20 41 D5 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8) Sat 12/01/2012 08:33:54 PM : [20 41 D5 1 ] Start : Adding device to ISY Sat 12/01/2012 08:33:54 PM : [20 41 D5 1 ] Finish : Adding device to ISY was Successful Quote Link to comment Share on other sites More sharing options...
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.