Release 2.8.6 RC2 is now available

[Michel Kohanim]

Hello all,

 

Thanks so very much for the feedback. Found/fixed an intermittent bug in our SMTP code. The side effect is that notifications should be a little faster in 2.8.7.

 

I am waiting to hear back from SmartHome vis-a-vis 2477D LED brightness. If I do not hear back by tomorrow afternoon, we'll go ahead with 2.8.7.

 

 

With kind regards,

Michel

[polexian]

My 2476D switch when using the LED brightness, if set to 0 it is on, any other number 1-254 it turns off also.

 

Mon 11/29/2010 06:33:48 PM : [          IR]     034A Press

Mon 11/29/2010 06:33:57 PM : [          IR]     0085 Press

Mon 11/29/2010 06:34:02 PM : [16 10 5D 1  ] Memory : Write dbAddr=0x0264 [01]

Mon 11/29/2010 06:34:02 PM : [iNST-ACK    ] 02 62 16.10.5D 1F 2E 00 01 03 01 00 00 00 00 00 00 00 00 00 00 00 06        (00)

Mon 11/29/2010 06:34:02 PM : [iNST-SRX    ] 02 50 16.10.5D 13.21.FF 27 2E 00           (00)

Mon 11/29/2010 06:34:02 PM : [standard-Direct Ack][16.10.5D-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

Mon 11/29/2010 06:34:03 PM : [          IR]     0151 Press

Mon 11/29/2010 06:34:14 PM : [16 10 5D 1  ] Memory : Write dbAddr=0x0264 [00]

Mon 11/29/2010 06:34:14 PM : [iNST-ACK    ] 02 62 16.10.5D 1F 2E 00 01 03 00 00 00 00 00 00 00 00 00 00 00 00 06        (00)

Mon 11/29/2010 06:34:15 PM : [iNST-SRX    ] 02 50 16.10.5D 13.21.FF 27 2E 00           (00)

Mon 11/29/2010 06:34:15 PM : [standard-Direct Ack][16.10.5D-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

 

I set it to 1 first, then to 0.

[Michel Kohanim]

Hello polexian,

 

Thanks so very much for the update. I am still waiting for SmartHome to respond. I think that perhaps the command for 2477D is different than the command for 2476D.

 

After initial success, I have not been able to do anything with my 2477D. This is quite odd!

 

With kind regards,

Michel

[kaplansa]

Hello all,

 

Thanks so very much for the feedback. Found/fixed an intermittent bug in our SMTP code. The side effect is that notifications should be a little faster in 2.8.7.

 

I am waiting to hear back from SmartHome vis-a-vis 2477D LED brightness. If I do not hear back by tomorrow afternoon, we'll go ahead with 2.8.7.

 

You think you're gonna have 2.8.7 out this week? Just asking because I use SMTP alerts for security and I'm obviously running blind with the SMTP problem in 2.8.6. I could downgrade if you think that's a better idea (to which version?) rather than holding out for 2.8.7 in the next couple of days. Thoughts?

 

Cheers

[Michel Kohanim]

Hi Kaplansa,

 

Yes, for sure ... we are waiting for SmartHome vis-a-vis the SWL backlight issue and in the meantime, implementing customized notifications.

 

With kind regards,

Michel

[polexian]

Michael,

As of now, the only way to really get what you need out of the insteon devices with the elk is to buy a KPL. My question is, can you program in a KPL in the devices virtualy? Then we could set it with Mobilinc or by using a remote control for all of us with IR?

 

This way we don't have to spend the money on a KPL!

[Michel Kohanim]

Hello polexian,

 

Unfortunatley we do not but virtual devices have been on our list for a while!

 

In the meantime, we are working on the ELK module which is going to solve this specific issue you are trying to deal with.

 

With kind regards,

Michel

[polexian]

I am aware of the elk module, but with a virtual device it would help other people also, not just us elk users.

 

Just a thought.

[gfridland]

This morning, I noticed that I received a few notifications from the ISY...I am still running 2.8.6 and waiting for 2.8.7 which should address the notification issue.

 

What is strange is that performing the test in the notifications screen returns errors, but on occasion, the notification is sent.

 

Any update to when 2.8.7 will be released? If not imminent, I will downgrade to 2.8.5...

 

Thank for all your efforts!

[kaplansa]

This morning, I noticed that I received a few notifications from the ISY...I am still running 2.8.6 and waiting for 2.8.7 which should address the notification issue.

 

What is strange is that performing the test in the notifications screen returns errors, but on occasion, the notification is sent.

 

Any update to when 2.8.7 will be released? If not imminent, I will downgrade to 2.8.5...

 

Thank for all your efforts!

 

That's funny. Exact same thing for me too. All my notifications stopped a couple of days ago when I installed 2.8.6 and upon "testing" I got that same password error everyone else got. And this morning I opened my garage and I got a notification out of the blue. I'm scared to touch anything for fear that I'll stop getting them again, and like you, waiting for 2.8.7 which I hope will be out any day now. Michel and crew are probably just busy working the holidays, my guess

[polexian]

Last I heard, they are waiting for smarthome to return their message to try and fix the dimming issue with the insteon switches.

[Michel Kohanim]

Hi guys,

 

I am so very sorry for the inconvenience. I just didn't want to have too many releases in a span of a few days. Still waiting for SmartHome on the backlight but in the meantime we are now testing custom notifications. We should have a drop by tomorrow in either case.

 

With kind regards,

Michel

[polexian]

Is it possible to be able to query the thermostat:

 

If thermostat main is off

 

and

 

temperature is 4 degrees less than heat set point

 

then turn on heat mode.

[Michel Kohanim]

Hello polexian,

 

You can always query thermostats but the conditional you are referring to requires variables which we do not yet support.

 

With kind regards,

Michel

[junkycosmos]

Hi Guys,

 

I upgraded today to 2.8.6 from 2.8.2 in order to pick up MorningLinc support. Am very pleased to report the MorningLinc is working great (only wish the silly lock was a two way device ) so large thanks to Team on picking up MorningLinc!

 

Does look that since upgrading I too noticed very few email notifications have come through (maybe 2 of 20?) where they were rock solid before. As noted here looks to be same issue for me of gmail credentials (smtp.gmail.com: 587 TLS).

 

Also noticed something weird on my Thermostat t1900 (2441v rev2.0) that the Humidity reading displayed in the ISY99 is jumping around a bit when I query it. Cannot honestly say if this is a 2.8.6 issue or it may have been there for a while as I've never query'ed it back to back before. Doing so just last few minutes readings have been: 47, 174, 41, 37, 37, 35, 36. Checking the physical screen of the TStat its currently measuring 36%; set to call for 40%.

 

 

Looking forward to 2.8.7 as you noted very soon emails notices are pretty high on our list.

 

Thanks again and a very Happy Holiday to you all.

[Michel Kohanim]

Hello all,

 

I just wanted to give you a quick update: custom notifications took a little longer in testing/regression and thus we will have to push back the release date to this Sunday (12/05/2010). I do apologize for the inconvenience.

 

With kind regards,

Michel

[junkycosmos]

Thanks for the update. Will check in Sun/Mon. If impatience gets the better of me I can always down rev1. Would rather wait for some internal testing than anything rush

 

Other observation in going from 2.8.2 to 2.8.6 is that MobiLinc needed a "Download All" (settings>> tap to sync with ISY) for remote program control/behavior to display correctly. Not sure if other upgrades in past have needed same and no big deal.

 

Also (and clearly not related to 2.8.6) I found one of my motion sensors 2420M v1.1 has gone crazy...as if the sensor is seeing motion after every 30 second time out period. Took it down from the wall and tested found testing with new battery in a dark drawer its bad behavior continue.

On ISY consul status would show "on" for 30 seconds then blink "off" then return to "on". Thousands of lines in log ...

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:33:53 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:34:23 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:34:23 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:34:52 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:34:53 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:35:22 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:35:23 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:35:52 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:35:53 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:36:22 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:36:22 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:36:54 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:36:54 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:37:23 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:37:24 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:37:53 PM

 

Have pulled the battery and will let it sit for a while then retry.

[Candide]

I had the same thing happen. I tried a bunch of things, contacted Smarthome, they tried a few things and eventually replaced the 2420M. I also had the low battery warning on continuously.

 

Sorry for your troubles, but glad to see that it isn't only me

 

 

Thanks for the update. Will check in Sun/Mon. If impatience gets the better of me I can always down rev1. Would rather wait for some internal testing than anything rush

 

Other observation in going from 2.8.2 to 2.8.6 is that MobiLinc needed a "Download All" (settings>> tap to sync with ISY) for remote program control/behavior to display correctly. Not sure if other upgrades in past have needed same and no big deal.

 

Also (and clearly not related to 2.8.6) I found one of my motion sensors 2420M v1.1 has gone crazy...as if the sensor is seeing motion after every 30 second time out period. Took it down from the wall and tested found testing with new battery in a dark drawer its bad behavior continue.

On ISY consul status would show "on" for 30 seconds then blink "off" then return to "on". Thousands of lines in log ...

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:33:53 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:34:23 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:34:23 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:34:52 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:34:53 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:35:22 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:35:23 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:35:52 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:35:53 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:36:22 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:36:22 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:36:54 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:36:54 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:37:23 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:37:24 PM

Sensors / DwnMotion-Sensor Status Fri 2010/12/03 03:37:53 PM

 

Have pulled the battery and will let it sit for a while then retry.

[robandcathy1]

I was setting up my christmas lights the other day and used 2 lamp lincs and one appliance linc using ver. 8.4 Now in fall all of these worked, so now that pool is closed I decide to use them for christmas lights, I rename them and plug them in there new locations get a no comm error. so I delete them completly from ISY and from their current locations (3 different places in the house) I manage to link them into the ISY again no problem, but if I try to control them I get a comm error, being somewhat smart I decide to remove them once again from the isy and now plug the four together back to back, 3 moduals and the plm directly connected, should rule out every possible comm error, but still get that error. No matter where they are in the house it willl linc and write updates but as soon as a command is sent get a no comm error, even if the PLM is plugged directly into the other 3 devices, and yes all 3 behave the same, but the 30+ switches in my houst are trouble free, seems to only be the add on moduals. I upgraded to 8.6 and still have same issue. Any thoughts???

Edit: if i do a query it will show normal as soon as I send a commandit will display a red exclamation by the device and the error.

[LeeG]

robandcathy

 

First, immediately unstack the units. They cannot dissipate heat buildup when that many units are back to back. You will cook the one in the middle. Okay to stack two total although that is not recommended by Smarthome.

 

Plug in the PLM, then piggyback one unit into the PLM, Run Event Viewer with Change level 3 - Device Communications Events. Run a Query and then an On/Off sequence and post results.

 

Lee

[Michel Kohanim]

Hi robandcathy,

 

First, please do as LeeG suggests.

 

Secondly, on newer version of LampLincs and ApplianceLincs, if you do not have a load attached, you will get comm errors when you try to turn things on/off.

 

With kind regards,

Michel

[robandcathy1]

2456S3 :

 

Sun 12/05/2010 12:47:16 PM : [iNST-ACK ] 02 62 0A.90.AA 0F 19 00 06 LTSREQ (LIGHT)

 

Sun 12/05/2010 12:47:17 PM : [iNST-SRX ] 02 50 0A.90.AA 0F.9F.4E 27 00 FF (FF)

 

Sun 12/05/2010 12:47:17 PM : [standard-Direct Ack][0A.90.AA-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

 

Sun 12/05/2010 12:47:17 PM : [ A 90 AA 1] ST 255

 

Sun 12/05/2010 12:47:17 PM : [ A 90 AA 1] OL 255

 

Sun 12/05/2010 12:47:17 PM : [ A 90 AA 1] RR 31

 

Sun 12/05/2010 12:47:26 PM : [iNST-ACK ] 02 62 0A.90.AA 0F 14 00 06 LTOFF-F(00)

 

Sun 12/05/2010 12:47:34 PM : [iNST-ACK ] 02 62 0A.90.AA 0F 12 00 06 LTON-F (00)

 

Sun 12/05/2010 12:47:34 PM : [iNST-SRX ] 02 50 0A.90.AA 0F.9F.4E A7 12 FE LTON-F (FE)

 

Sun 12/05/2010 12:47:34 PM : [standard-Direct Nack][0A.90.AA-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

 

Sun 12/05/2010 12:47:39 PM : [iNST-ACK ] 02 62 0A.90.AA 0F 14 00 06 LTOFF-F(00)

 

Sun 12/05/2010 12:47:40 PM : [iNST-SRX ] 02 50 0A.90.AA 0F.9F.4E A7 14 FE LTOFF-F(FE)

 

Sun 12/05/2010 12:47:40 PM : [standard-Direct Nack][0A.90.AA-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

 

Sun 12/05/2010 12:47:53 PM : [iNST-ACK ] 02 62 0A.90.AA 0F 12 00 06 LTON-F (00)

 

-------------------------------------------------------------------------------------

 

2456D :

 

Sun 12/05/2010 12:51:55 PM : [iNST-ACK ] 02 62 0A.A8.B5 0F 19 00 06 LTSREQ (LIGHT)

 

Sun 12/05/2010 12:51:56 PM : [iNST-SRX ] 02 50 0A.A8.B5 0F.9F.4E 27 00 FF (FF)

 

Sun 12/05/2010 12:51:56 PM : [standard-Direct Ack][0A.A8.B5-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

 

Sun 12/05/2010 12:51:56 PM : [ A A8 B5 1] ST 255

 

Sun 12/05/2010 12:51:56 PM : [ A A8 B5 1] OL 255

 

Sun 12/05/2010 12:51:56 PM : [ A A8 B5 1] RR 31

 

Sun 12/05/2010 12:52:10 PM : [iNST-ACK ] 02 62 0A.A8.B5 0F 14 00 06 LTOFF-F(00)

 

Sun 12/05/2010 12:52:21 PM : [iNST-ACK ] 02 62 0A.A8.B5 0F 14 00 06 LTOFF-F(00)

 

Sun 12/05/2010 12:52:21 PM : [iNST-ACK ] 02 62 0A.A8.B5 0F 14 00 06 LTOFF-F(00): Process ACK: duplicate ignored

 

Sun 12/05/2010 12:52:21 PM : [iNST-SRX ] 02 50 0A.A8.B5 0F.9F.4E 23 14 00 LTOFF-F(00)

 

Sun 12/05/2010 12:52:21 PM : [standard-Direct Ack][0A.A8.B5-->ISY/PLM Group=0] Max Hops=3, Hops Left=0

 

Sun 12/05/2010 12:52:21 PM : [ A A8 B5 1] ST 0

 

Sun 12/05/2010 12:52:25 PM : [iNST-ACK ] 02 62 0A.A8.B5 0F 12 00 06 LTON-F (00)

 

Sun 12/05/2010 12:52:27 PM : [iNST-SRX ] 02 50 0A.A8.B5 0F.9F.4E A7 12 FE

-----------------------------------------------------------------------------------

 

2456D :

 

Sun 12/05/2010 12:54:19 PM : [iNST-ACK ] 02 62 0A.8C.E7 0F 19 00 06 LTSREQ (LIGHT)

 

Sun 12/05/2010 12:54:20 PM : [iNST-SRX ] 02 50 0A.8C.E7 0F.9F.4E 2B 00 00 (00)

 

Sun 12/05/2010 12:54:20 PM : [standard-Direct Ack][0A.8C.E7-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Sun 12/05/2010 12:54:20 PM : [ A 8C E7 1] ST 0

 

Sun 12/05/2010 12:54:20 PM : [ A 8C E7 1] OL 255

 

Sun 12/05/2010 12:54:20 PM : [ A 8C E7 1] RR 31

 

Sun 12/05/2010 12:54:26 PM : [iNST-ACK ] 02 62 0A.8C.E7 0F 12 00 06 LTON-F (00)

 

Sun 12/05/2010 12:54:27 PM : [iNST-SRX ] 02 50 0A.8C.E7 0F.9F.4E A7 12 FE LTON-F (FE)

 

Sun 12/05/2010 12:54:27 PM : [standard-Direct Nack][0A.8C.E7-->ISY/PLM Group=0] Max Hops=3, Hops Left=1

 

Sun 12/05/2010 12:54:30 PM : [iNST-ACK ] 02 62 0A.8C.E7 0F 14 00 06 LTOFF-F(00)

 

Sun 12/05/2010 12:54:31 PM : [iNST-SRX ] 02 50 0A.8C.E7 0F.9F.4E A3 14 FE LTOFF-F(FE)

 

Sun 12/05/2010 12:54:31 PM : [standard-Direct Nack][0A.8C.E7-->ISY/PLM Group=0] Max Hops=3, Hops Left=0

 

-------------------------------------------------------------------------------------

Not sure what version numbers these are because the tags cam off

[robandcathy1]

ok think I figured it out but it was strange, using the plm directly, plugging each one in at a time, I still received the comm error, but being stuborne and lazy not wanting to plug christmas lights in by hand, I was playing around and tried them in the wall one at a time, surprise the lamp lincs worked but the app linc still was giving me a comm error, If I plugged all three into different outlets around the house none of them would work, but I have 4 more that worked fine in the back yard not to mention the 30 switches I have on my walls. Seems the appliance linc would only affect the other two and nothing else. I was sure to put one on the other phase of the house to see if it was a phase issue but, still acted the same way. Looking at the logs do you see any problems?

[LeeG]

robandcathy

 

Taking one at a time the 2456S3 at the top of the post answered the Query correctly. The Fast On and Fast Off received a NAK. Did you try Michel's suggestion and plug a load into the 2456S3. Michel indicated some of the devices respond with a NAK if there is no load connected. This does not look like a general powerline communication problem.

 

Lee

[robandcathy1]

Yes I plugged one strand of lights in it, they stay on all the time. I try to turn it off via the button and Isy still no luck, I know it worked fine till last day of season, but like all electronic things, eventually they brake, just curious as to why it would only affect, specifically 2 of the 8 moduals I have, and none of the switches? as soon as I plug it into the wall the other two moduals act up. For now I think its time to look for a replacement. but thanks Lee for another problem solved, thats not the ISY . I have no problems linking it, queering it or anything else, just as soon as a on or off command is sent it gives me that error. I even did a restore , error free.