What's in release 2.4

[Michel Kohanim]

Hello all,

 

Release 2.4 is all about enhanced triggers.

 

Enhancements

More triggers. Status: being implemented

Triggering schedules/scheduling triggers. Status: being implemented

GUI Facelift for triggers/schedules. Status: being implemented

 

 

 

With regards

[sfhutchi]

Since you mentioned GUI, please consider making the difference between a controller and a responder a bit more obvious. Possibly a different color for the controller? The italic lettering is a bit too subtle.

[Michel Kohanim]

Since you mentioned GUI, please consider making the difference between a controller and a responder a bit more obvious. Possibly a different color for the controller? The italic lettering is a bit too subtle.

 

sfhutchi,

 

Consider it done ...

 

With regards,

Michel

[sfhutchi]

Excellent. Thanks.

[Mark Sanctuary]

Do you have an update on the time and details of the 2.3 release?

[Michel Kohanim]

Do you have an update on the time and details of the 2.3 release?

 

Hello Mark,

 

In short, at the moment, we are running a little late on the new triggers/scheduling functionality mostly due to our desire to add as many new requested functions (almost on a daily basis) as possible before the release.

 

At the same time, release 2.3 has a lot to offer including expanded support for Linksys and Buffalo routers, multi-select drag/drop, many firmware enhancements and bug fixes, etc. As such, I think we'll be releasing 2.3 without the new triggers/scheduling by the end of the week.

 

Thanks and with kind regards,

Michel

[Mark Sanctuary]

That’s great news on the 2.3 release coming soon.

 

I personally would like to get the triggers/scheduling soon, so do you think we should do a poll of everyone on if all new feature requests (except new bugs requests) should come after 2.4 so you guys can get the triggers/scheduling done in 2.4?

[Michel Kohanim]

That’s great news on the 2.3 release coming soon.

 

I personally would like to get the triggers/scheduling soon, so do you think we should do a poll of everyone on if all new feature requests (except new bugs requests) should come after 2.4 so you guys can get the triggers/scheduling done in 2.4?

 

Hello Mark,

 

Thanks so very much for the offer but I think that we don't have enough time to collect enough votes. In all likelihood, we will have a 2.3 release before the triggers release.

 

Thanks so very much,

Regards,

Michel

[Mark Sanctuary]

What I really mean is that you lock 2.4 as the triggers/scheduling release only. No other new features until 2.5 release because I think we all are waiting more for this than anything else.

[Michel Kohanim]

What I really mean is that you lock 2.4 as the triggers/scheduling release only. No other new features until 2.5 release because I think we all are waiting more for this than anything else.

 

Mark,

 

Yes, you are right. We should lock 2.4 for triggers/schedules with no other new functionality. But, I am still not sure if this requires a vote. Do you?

 

With regards,

Michel

[sfhutchi]

I vote for 'no vote'.

I believe that Michel and the team are truly aware of everyone's requests and are rolling these out as quickly as they can. This product has improved quicker than any other Insteon device that I have dealt with.

[Mark Sanctuary]

Ok no vote needed. If 2.4 can be the triggers/scheduling magic number then so be it. Thanks for all your hard work guys!

[Michel Kohanim]

Hello all,

 

We have decided to release version 2.3 by no later than 07.09.2007 and dedicate version 2.4 solely for triggers/scheduler. Version 2.3 is packed with some bug fixes but many functional and cosmetic enhancements:

 

Bug Fixes:

XML Parse Error with certain firewall software

Fixed Lat/Long for Alberta, Canada

ISY hang after DHCP renew

Dynamic-DNS addresses would not get resolved when accessing ISY remotely

Extra html tags on the AutoUpdate dialog

 

 

Functional Enhancements:

Multi selection of devices to be moved into a scene

Support for KPL Toggle Mode

Support for KPL Synchronized Buttons ... a workaround to link KPL to itself

Support for Linksys Routers WRT54GS and DLink DIR-655

Performance improvements in system startup

Performance improvements in adding devices

 

Cosmetic Enhancements:

Changed the color to RED for a controller within a scene; everything else is blue

Left Nav bar widened to support long names

Changed the "Cancel" label to "Done" in certain dialogs

Added UDI Forum menu option to the Help menu

Progress bar:

- No longer Always on Top

- More accurate when clearing configuration before a Restore ISY

- More accurate after linking/adding/removing devices and scenes

 

Thanks so very much for all your support and help,

With regards,

Michel

[Mark Sanctuary]

WOW! You have been busy! Good job guys!

[Michel Kohanim]

Hello All,

 

Here's a high level list of what to expect in Release 2.4:

 

Bug Fixes

Right mouse click on MAC/OSX does not work: Done

File dialog on MAC/OSX does not allow filename entry: Done

Regression: adding a KPL/SWL manually (using the address) caused ISY to hang: Done

Regression: removing devices left residue: Done

The cross reference tree view did not reflect both Manages and Is Managed By relationships: Done

 

 

Enhancements

Show default backup filename: Done

All on/off on My Lighting and Network icons: Done

All on/off from controllers such as ControLinc: Done

Full support for RemoteLinc: Done

The window opens maximized: Done

The state of the window is now persisted between sessions: Done

The state of the tree is now persisted between sessions: Done

EZRain timer support: Testing

All On/Off workaround: Testing

 

80% likelihood to be included

Replace Device: Testing

Keep existing links: Testing

Merge existing links: Testing

 

40% likelihood to be included

Enchanced Triggers/Schedules: Testing

 

With kind regards,

Michel

[Sub-Routine]

Thank you for the update, it sounds great!

 

Thank you,

Rand

[Michel Kohanim]

Rand,

 

My pleasure. And, thank you so very much for your continued feedback and guidance on the forum. I sincerely appreciate it.

 

With kind regards,

Michel

 

Thank you for the update, it sounds great!

 

Thank you,

Rand

[sfhutchi]

Thanks for the update on v.2.4.

Based on the latest update, it looks like enhanced triggers/scheduling will in all likelihood be pushed to a future release. I hate to ask, but what is the ETA for 2.5? I know that many of us are anxious for this.

[Kib]

Just a quick note to thank the crew on the schedule screen fix on 2.3, so far it appears to have cleared up the problem.

 

Still hoping I'll see the "security random time" feature I'd mentioned to Michel sometime soon.

 

BTW - Without sounding too much like a suck-up, you folks should be very proud of what you've accomplished. This is my fifth HA installation, and by far it's working the best and I have the highest confidence level that stuff is going to do what it's supposed to do, when it's supposed to do it then any other system I've previously used...

 

Thanks again !

[Michel Kohanim]

sfhutchi,

 

Long time no see!

 

We are working very hard to put at least some of the trigger functionality into release 2.4. Due to a complete redesign, this process has taken us longer than anticipated. Please be assured that we recognize the importance of the this new enhacement and will do our utmost to support it as soon as possible. If triggers don't make it in release 2.4, the next release would be in approximately a month.

 

In release 2.4, we have added a work-around for All Off/On which alleviates at least some of the needs for complex triggers.

 

With sincere apologies and with thanks for your patience.

Regards,

Michel

 

 

Thanks for the update on v.2.4.

Based on the latest update, it looks like enhanced triggers/scheduling will in all likelihood be pushed to a future release. I hate to ask, but what is the ETA for 2.5? I know that many of us are anxious for this.

[Michel Kohanim]

Kib,

 

Thanks so very much for the update, the compliments, and your business. We are indeed very proud of our little box but none of it would've been possible without the feedback and suggestions of our clients.

 

Security random timer/schedule is for a fact in our trigger/scheduler release which, as you may already know, could slip yet again. I truly apologize.

 

Thanks again and please don't hesitate to contact us in case you have any questions/suggestions/comments.

 

With kind regards,

Michel

 

Just a quick note to thank the crew on the schedule screen fix on 2.3, so far it appears to have cleared up the problem.

 

Still hoping I'll see the "security random time" feature I'd mentioned to Michel sometime soon.

 

BTW - Without sounding too much like a suck-up, you folks should be very proud of what you've accomplished. This is my fifth HA installation, and by far it's working the best and I have the highest confidence level that stuff is going to do what it's supposed to do, when it's supposed to do it then any other system I've previously used...

 

Thanks again !

[sfhutchi]

Thanks for the update. I can be patient. I believe that I have a fairly stable configuration now and am ready to move all trigger / timer functionality to the ISY. Currently, I still rely on Houselinc Desktop for some of this.

[Michel Kohanim]

sfhutchi,

 

Thanks for your patience ... would you be kind enough to let me know for what aspects you use HouseLinc? There might be some simple fixes/enhancements that we can include to alleviate those scenarios.

 

Thanks and with kind regards,

Michel

Thanks for the update. I can be patient. I believe that I have a fairly stable configuration now and am ready to move all trigger / timer functionality to the ISY. Currently, I still rely on Houselinc Desktop for some of this.

[sfhutchi]

Specifically the timed triggers. For example, with Houselinc I have some triggers that look for an 'on' press (at an exhaust fan for example).. the exhaust fan turns on, then I wait 10 minutes, then send an off command to that fan. I have some other scenarios ready for morning scenes and things like this, but I need some timed elements added to the triggers. I don't have a problem being patient though. If some of this is added soon, great... if I have to wait, I have work-arounds for now.

[Michel Kohanim]

sfhutchi,

 

Thanks so very much for the detailed explanation. We are going to do our utmost to get this out in our next release.

 

With kind regards,

Michel

Specifically the timed triggers. For example, with

Houselinc I have some triggers that look for an 'on' press (at an exhaust fan for example).. the exhaust fan turns on, then I wait 10 minutes, then send an off command to that fan. I have some other scenarios ready for morning scenes and things like this, but I need some timed elements added to the triggers. I don't have a problem being patient though. If some of this is added soon, great... if I have to wait, I have work-arounds for now.