First impressions of the ISY-26 - review

[MikeB]

Here are some of my initial impressions on the ISY-26, after playing with it for almost a day.

 

I received my unit a week or so ago, but haven't had the time to open and play until yesterday.

 

Installed the latest version of Java, and got right in to the interface using a Vista Business PC (IE7) and a Windows XP Pro machine (IE6) with no issues.

 

Had one issue right away where I was no longer able to login. I left a message at Universal-Devices, and Michel called back right away. Beyond excellent customer support. I'll go into more detail later.

 

I maintain a good spreadsheet of all my devices, so I felt more comfortable typing my devices in by address, adding them one at a time. Unfortunately it had a problem reading in my links using that method, but I didn't mind recreating them.

 

Between yesterday evening and this AM I was able to add all my devices, recreate all my links (scenes), and duplicate 95% of the functions I had before (more on that other 5% later). I still need to do my RemoteLincs, which I hope to tackle today.

 

Once you get a hang of the interface, it's pretty easy to work with. I have 60+ Insteon devices, and 30 or so scenes in the ISY-26. Nothing too too complex (yet).

 

Simple drag and drop worked well for me, but once I added most of my devices I found right-clicking worked better and faster to add devices to scenes.

 

I did have some communication issues programming devices, but usually retrying fixed it for me. The ISY-26 is plugged in to an odd location in my home right now (on a sub-panel), but I'll move it to a more permanent location later, improving my signal reliability.

 

Here are some comments/concerns/requests/questions in no particular order:

 

- Support from Michel was top-notch. Called me back right away. Not only did he help fix my issue, he offered and spent quite a bit of time showing me around the ISY-26 and helping me understand some things I didn't grasp yet. Can't say enough - great guy to deal with.

 

- Not a big fan of the interface colors (at least on my display). The pink was kind of hard to read at times. I understand the need for consistency, so making this user-definable probably isn't an option, but if I were UD I would put a bit of thought into the interface pallette. I think they could make it much more professional looking and pleasing simply by changing some colors around. I would go with a neutral theme for the background, maybe gray), and implement the text in darker colrs - orange, red, blue, green, etc... BUT - I'm obviously nitpicking. Other than the colors, I thought the interface was fine.

 

- I received a Java error a few times when trying to program certain devices. However, the switches seemed to program fine anyway. Not sure what the deal is, but the error was: "Socket open failed: java.nio.channels.ClosedSelectorException"

 

- One of the features I really like about PowerHome is the statistics it keeps for you to help find and troubleshoot switch and signal reliability issues. I don't know if it's feasible, but this would be a REAL nice feature to add.

 

- Is there a way to make a device a controller of 2 scenes? For example, I have a scene called "Floor1Off" that I control from a couple KeypadLincs around my house. I also have a "Floor2Off" scene that I control from a couple KPLs. Finally, I have 1 KPL that has a "Floor 1+2 Off" button. I ended up creating a whole new scene called "Floor1+2Off" and made that the controller. Not sure if it's possible, but it would have been nice to simply add that "Floor1+2Off" KPL button as a controller to both of my existing scenes.

 

- One feature I assumed was included with the ISY-26 was timed events. For example, if I turn my closet light on, I want to make sure it is automatically turned off 10 or 20 mins later - just in case whoever turned it on forgets to turn it off. Same with bathrooms, vents, etc. From what I understand this is being included in a soon-to-be released firmware update. This is one of the features I was using with my old setup, but currently am unable to do with the ISY-26. One thing to keep in mind when implementing this feature - say we have a 10 min timer setup on Closet1. If a user turns Closet1 ON, an event should be triggered that will turn Closet1 OFF 10 mins later. However, if Closet1 is turned off manually, that event should be cancelled. Don't want a situation where a light is turned on, then turned off 8 mins later, then turned back on, and the ISY-26 turns it off 2 mins after that.

 

- It would be nice if the casing of the ISY-26 had a couple keyed holes in the back for wall mounting. I'll probably end up using velcro, but some built-in wall mount method would be nice.

 

- I knew this feature wasn't in the current firmware release, but I did use FAST ON/FAST OFFs to trigger events with my old setup. I think this is an important feature to add.

 

- I also plan to use other software with my Insteon network, which will require me to keep other PLCs/PLMs on the network. This software will require me to keep links from my devices to these other PLCs/PLMs. My understanding is that when I restore a device through the ISY-26, that it will delete those links. If possible, I'd love a way for the ISY-26 to recognize and allow me to create links to these other PLCs/PLMs. If nothing else, I think they ISY-26 should have away to ignore these links and not delete them when I choose 'restore device'.

 

- I did experience a few instances where the PLM stopped sending/receiving commands. The ISY-26 did not give me any errors, but commands simply would not go out. Unplugging/replugging the PLM to cut the power brought it back online. I never needed to cut the power to the ISY-26. My PLM is FIRM52, and I'm running ISY-26 firmware that Michel sent me (2.4.4).

 

- I had a couple instances when programming KPL buttons that the ISY-26 SEEMED to complete the task, but the button was never added to the scene. I'd try again, and same thing - no error, but it wasn't in the scene. I ended up doing a restore device to those buttons, then tried adding them again, and it worked.

 

- One question - what is everyone using the Floor Plan for? Any good uses for it, or is it completely cosmetic?

 

 

 

ANYWAY, sorry for the long post. In summary, I think this device is fantastic, easy to use, and does 95% of what I want. Customer support was above and beyond what could be expected, and it's great to see that UD responds well and relatively quickly to many feature requests posted on this forum. Hopefully with the new firmware update, it will do 99% of what I want.

 

I can't wait to start using this full-time, and for the new firmware update. I also can't wait for any new products UD may have in store for us.

 

I think SmartHome would be wise to push this product more - it could definitely help them sell a lot more Instoen product.

 

I will also be posting this up on TechMall, AccessHA, and Cocoontech.

[Michel Kohanim]

MikeB,

 

Thanks so very much for your thorough feedback.

 

Here are my comments:

1. Color: you are 100% right. Initially, at least, we have changed the pink!

2. Java socket error: ISY is busy and didn't have enough time to respond to a status request. It's being fixed as we speak.

3. Statistics. I guess we can do the same; we already have the log file in Excel (under tools). We could possibly create some Excel macros to extrapolate the number of successful vs. failed communications for the same device. Do you have an example of the statistics you would like to see?

4. A device to be controller for two scenes: unfortunately, early on, we had to make a design decision which precluded this scenario. The reason: less complex code for 95% of the functionality. If we do get a lot of requests, we will surely put the time and effort to implement it

5. Timed events shall be there as you described in 2.5

6. Wall mounting: you are 100% correct. It shall be done

7. KPL button not showing up: this is related to our client (GUI) code suppressing the "same" error for the same "device" within 2 seconds (considers it duplicate) ... we are working on a "predictive" solution

8. Fast on/Fast off triggers ... in 2.5

9. PLM stopping is a known PLM bug especially when confronted with a lot of operations ... working with SmartLabs for a solution

10. Creating links to other PLMs: quite feasilbe; the only problem is that they have no limitation: they can respond to 255 groups and control 255 groups. But, surely doable ... can't guarantee that we'll actually implement this functionality since we prioritize based on the the number of feedback for the same functionality

11. Floorplan: experimental, rather toy-like, and mostly cosmetic; it's slated to be completely removed.

 

 

Thanks again for your feedback,

With kind regards,

Michel

 

Here are some of my initial impressions on the ISY-26, after playing with it for almost a day.

 

I received my unit a week or so ago, but haven't had the time to open and play until yesterday.

 

Installed the latest version of Java, and got right in to the interface using a Vista Business PC (IE7) and a Windows XP Pro machine (IE6) with no issues.

 

Had one issue right away where I was no longer able to login. I left a message at Universal-Devices, and Michel called back right away. Beyond excellent customer support. I'll go into more detail later.

 

I maintain a good spreadsheet of all my devices, so I felt more comfortable typing my devices in by address, adding them one at a time. Unfortunately it had a problem reading in my links using that method, but I didn't mind recreating them.

 

Between yesterday evening and this AM I was able to add all my devices, recreate all my links (scenes), and duplicate 95% of the functions I had before (more on that other 5% later). I still need to do my RemoteLincs, which I hope to tackle today.

 

Once you get a hang of the interface, it's pretty easy to work with. I have 60+ Insteon devices, and 30 or so scenes in the ISY-26. Nothing too too complex (yet).

 

Simple drag and drop worked well for me, but once I added most of my devices I found right-clicking worked better and faster to add devices to scenes.

 

I did have some communication issues programming devices, but usually retrying fixed it for me. The ISY-26 is plugged in to an odd location in my home right now (on a sub-panel), but I'll move it to a more permanent location later, improving my signal reliability.

 

Here are some comments/concerns/requests/questions in no particular order:

 

- Support from Michel was top-notch. Called me back right away. Not only did he help fix my issue, he offered and spent quite a bit of time showing me around the ISY-26 and helping me understand some things I didn't grasp yet. Can't say enough - great guy to deal with.

 

- Not a big fan of the interface colors (at least on my display). The pink was kind of hard to read at times. I understand the need for consistency, so making this user-definable probably isn't an option, but if I were UD I would put a bit of thought into the interface pallette. I think they could make it much more professional looking and pleasing simply by changing some colors around. I would go with a neutral theme for the background, maybe gray), and implement the text in darker colrs - orange, red, blue, green, etc... BUT - I'm obviously nitpicking. Other than the colors, I thought the interface was fine.

 

- I received a Java error a few times when trying to program certain devices. However, the switches seemed to program fine anyway. Not sure what the deal is, but the error was: "Socket open failed: java.nio.channels.ClosedSelectorException"

 

- One of the features I really like about PowerHome is the statistics it keeps for you to help find and troubleshoot switch and signal reliability issues. I don't know if it's feasible, but this would be a REAL nice feature to add.

 

- Is there a way to make a device a controller of 2 scenes? For example, I have a scene called "Floor1Off" that I control from a couple KeypadLincs around my house. I also have a "Floor2Off" scene that I control from a couple KPLs. Finally, I have 1 KPL that has a "Floor 1+2 Off" button. I ended up creating a whole new scene called "Floor1+2Off" and made that the controller. Not sure if it's possible, but it would have been nice to simply add that "Floor1+2Off" KPL button as a controller to both of my existing scenes.

 

- One feature I assumed was included with the ISY-26 was timed events. For example, if I turn my closet light on, I want to make sure it is automatically turned off 10 or 20 mins later - just in case whoever turned it on forgets to turn it off. Same with bathrooms, vents, etc. From what I understand this is being included in a soon-to-be released firmware update. This is one of the features I was using with my old setup, but currently am unable to do with the ISY-26. One thing to keep in mind when implementing this feature - say we have a 10 min timer setup on Closet1. If a user turns Closet1 ON, an event should be triggered that will turn Closet1 OFF 10 mins later. However, if Closet1 is turned off manually, that event should be cancelled. Don't want a situation where a light is turned on, then turned off 8 mins later, then turned back on, and the ISY-26 turns it off 2 mins after that.

 

- It would be nice if the casing of the ISY-26 had a couple keyed holes in the back for wall mounting. I'll probably end up using velcro, but some built-in wall mount method would be nice.

 

- I knew this feature wasn't in the current firmware release, but I did use FAST ON/FAST OFFs to trigger events with my old setup. I think this is an important feature to add.

 

- I also plan to use other software with my Insteon network, which will require me to keep other PLCs/PLMs on the network. This software will require me to keep links from my devices to these other PLCs/PLMs. My understanding is that when I restore a device through the ISY-26, that it will delete those links. If possible, I'd love a way for the ISY-26 to recognize and allow me to create links to these other PLCs/PLMs. If nothing else, I think they ISY-26 should have away to ignore these links and not delete them when I choose 'restore device'.

 

- I did experience a few instances where the PLM stopped sending/receiving commands. The ISY-26 did not give me any errors, but commands simply would not go out. Unplugging/replugging the PLM to cut the power brought it back online. I never needed to cut the power to the ISY-26. My PLM is FIRM52, and I'm running ISY-26 firmware that Michel sent me (2.4.4).

 

- I had a couple instances when programming KPL buttons that the ISY-26 SEEMED to complete the task, but the button was never added to the scene. I'd try again, and same thing - no error, but it wasn't in the scene. I ended up doing a restore device to those buttons, then tried adding them again, and it worked.

 

- One question - what is everyone using the Floor Plan for? Any good uses for it, or is it completely cosmetic?

 

 

 

ANYWAY, sorry for the long post. In summary, I think this device is fantastic, easy to use, and does 95% of what I want. Customer support was above and beyond what could be expected, and it's great to see that UD responds well and relatively quickly to many feature requests posted on this forum. Hopefully with the new firmware update, it will do 99% of what I want.

 

I can't wait to start using this full-time, and for the new firmware update. I also can't wait for any new products UD may have in store for us.

 

I think SmartHome would be wise to push this product more - it could definitely help them sell a lot more Instoen product.

 

I will also be posting this up on TechMall, AccessHA, and Cocoontech.

[MikeB]

Thanks for reading my long-winded post! Here are my comments:

 

3 - Personally, I think ack vs nack is fine. I find it useful if there is a particularly problematic circuit, or switch, or whatever.

Here are some screenshots showing PowerHome:

http://www.mbdatasystems.com/pics/powerhome1.jpg

http://www.mbdatasystems.com/pics/powerhome2.jpg

 

4 - No big deal, just a thought. If it complicates it, I agree - leave it out.

 

10 - It would be ideal if they ISY-26 could program links to other PLMs, but what's most important to me is that the ISY-26 not delete them. I know it may not be common, but there will be others I'm sure who will be using other software and devices with the ISY-26. I don't think it's appropriate for the ISY-26 to delete those links just because it doesn't recognize them.

 

Maybe there could be a field where you can type in Insteon addresses of devices that the ISY-26 will preserve links to? So, any links that the ISY-26 finds to the listed devices when doing a recover device would be left alone, not deleted.

 

Then I could still manually create those links, and not worry about the ISY-26 dropping them.

 

Thanks again Michel!!!

[Michel Kohanim]

Mike,

 

Thank you so very much for the quick reply.

 

Please see my comments below.

 

With kind regards,

Michel

 

Thanks for reading my long-winded post! Here are my comments:

 

3 - Personally, I think ack vs nack is fine. I find it useful if there is a particularly problematic circuit, or switch, or whatever.

Here are some screenshots showing PowerHome:

http://www.mbdatasystems.com/pics/powerhome1.jpg

http://www.mbdatasystems.com/pics/powerhome2.jpg

I would love to check out these links but I wonder how David would feel about this. I will have to get his permission.

 

 

4 - No big deal, just a thought. If it complicates it, I agree - leave it out.

 

10 - It would be ideal if they ISY-26 could program links to other PLMs, but what's most important to me is that the ISY-26 not delete them. I know it may not be common, but there will be others I'm sure who will be using other software and devices with the ISY-26. I don't think it's appropriate for the ISY-26 to delete those links just because it doesn't recognize them.

 

Maybe there could be a field where you can type in Insteon addresses of devices that the ISY-26 will preserve links to? So, any links that the ISY-26 finds to the listed devices when doing a recover device would be left alone, not deleted.

 

Then I could still manually create those links, and not worry about the ISY-26 dropping them.

I had a chat with our CTO and I was wrong: ISY does not delete existing links as long as they were brought in by the crawl function. I know this is too much to ask, but is there anyway for you to verify?

Also, I have added your request vis-a-vis adding links to other PLMs and it will be reviewed in our next requirements meeting.

 

 

Thanks again Michel!!!

[jbev]

I had a chat with our CTO and I was wrong: ISY does not delete existing links as long as they were brought in by the crawl function. I know this is too much to ask, but is there anyway for you to verify?

Also, I have added your request vis-a-vis adding links to other PLMs and it will be reviewed in our next requirements meeting.

 

 

Thanks again Michel!!!

 

I have a bunch oif links left in my system too and restore device seems to not do anything to them. I thought restore device was supposed to resync the device with the current link information in the ISY or did I miss something?

[Sub-Routine]

Thanks for reading my long-winded post! Here are my comments:

 

3 - Personally, I think ack vs nack is fine. I find it useful if there is a particularly problematic circuit, or switch, or whatever.

Here are some screenshots showing PowerHome:

http://www.mbdatasystems.com/pics/powerhome1.jpg

http://www.mbdatasystems.com/pics/powerhome2.jpg

 

PowerHome does polling, the ISY does not, so these figures will probably not be as useful from the ISY. I guess you could do a Query every so often, but...

 

4 - No big deal, just a thought. If it complicates it, I agree - leave it out.

 

Michel has promised a Copy Scene, AFAIR.

 

10 - It would be ideal if they ISY-26 could program links to other PLMs, but what's most important to me is that the ISY-26 not delete them. I know it may not be common, but there will be others I'm sure who will be using other software and devices with the ISY-26. I don't think it's appropriate for the ISY-26 to delete those links just because it doesn't recognize them.

 

Maybe there could be a field where you can type in Insteon addresses of devices that the ISY-26 will preserve links to? So, any links that the ISY-26 finds to the listed devices when doing a recover device would be left alone, not deleted.

 

Then I could still manually create those links, and not worry about the ISY-26 dropping them.

 

Using a PLC and my Group Commander program it was not a problem to create links between another PLC and other devices. The ISY PLM has no problems communicating with the PLM in my EZIO with the limited testing I have done.

 

Thanks again Michel!!!

 

I hope you find the ISY to be as useful as I do to program your Insteon devices, I think it is a fantastic Insteon tool!

 

Thank you,

Rand

[Michel Kohanim]

jbev,

 

Apologies for a tardy reply. Here's the situation:

1. If you bring existing links, then those links are copied unadultered and the "meaningful" ones are used to create scenes/relationships. But, the links remain specifically due to siutations such as those described by MikeB.

2. If you do NOT bring existing links (choosing options 1 and 2 during link), then ISY overwrites existing links and then when you do Restore Devices, all the devices will by in synch with ISY.

 

I hope this answered your question.

 

With kind regards,

Michel

 

I had a chat with our CTO and I was wrong: ISY does not delete existing links as long as they were brought in by the crawl function. I know this is too much to ask, but is there anyway for you to verify?

Also, I have added your request vis-a-vis adding links to other PLMs and it will be reviewed in our next requirements meeting.

 

 

Thanks again Michel!!!

 

I have a bunch oif links left in my system too and restore device seems to not do anything to them. I thought restore device was supposed to resync the device with the current link information in the ISY or did I miss something?

[Michel Kohanim]

Rand,

 

Thanks so very much for the feedback. You are 100% correct, we never do a poll except for the 3:00 AM schedule (which is simply there to make sure we are 100% in synch).

 

As far as analysis, I think you are right. At the same time, we have a history of the number of failed operations per device, I think we can extrapolate some minimally useful information.

 

Thanks again,

With kind regards,

Michel

 

Thanks for reading my long-winded post! Here are my comments:

 

3 - Personally, I think ack vs nack is fine. I find it useful if there is a particularly problematic circuit, or switch, or whatever.

Here are some screenshots showing PowerHome:

http://www.mbdatasystems.com/pics/powerhome1.jpg

http://www.mbdatasystems.com/pics/powerhome2.jpg

 

PowerHome does polling, the ISY does not, so these figures will probably not be as useful from the ISY. I guess you could do a Query every so often, but...

 

4 - No big deal, just a thought. If it complicates it, I agree - leave it out.

 

Michel has promised a Copy Scene, AFAIR.

 

10 - It would be ideal if they ISY-26 could program links to other PLMs, but what's most important to me is that the ISY-26 not delete them. I know it may not be common, but there will be others I'm sure who will be using other software and devices with the ISY-26. I don't think it's appropriate for the ISY-26 to delete those links just because it doesn't recognize them.

 

Maybe there could be a field where you can type in Insteon addresses of devices that the ISY-26 will preserve links to? So, any links that the ISY-26 finds to the listed devices when doing a recover device would be left alone, not deleted.

 

Then I could still manually create those links, and not worry about the ISY-26 dropping them.

 

Using a PLC and my Group Commander program it was not a problem to create links between another PLC and other devices. The ISY PLM has no problems communicating with the PLM in my EZIO with the limited testing I have done.

 

Thanks again Michel!!!

 

I hope you find the ISY to be as useful as I do to program your Insteon devices, I think it is a fantastic Insteon tool!

 

Thank you,

Rand

[jbev]

That's what I was afraid of. So the only way it seems that I am going to be able to clear them now is to go through and do a factory reset on all of them?

 

jbev,

 

Apologies for a tardy reply. Here's the situation:

1. If you bring existing links, then those links are copied unadultered and the "meaningful" ones are used to create scenes/relationships. But, the links remain specifically due to siutations such as those described by MikeB.

2. If you do NOT bring existing links (choosing options 1 and 2 during link), then ISY overwrites existing links and then when you do Restore Devices, all the devices will by in synch with ISY.

 

I hope this answered your question.

 

With kind regards,

Michel

[Michel Kohanim]

jbev,

 

NO. No need to factory reset all of your devices. I just posted a reply to your last posting. Please let me know if it's clear.

 

With kind regards,

Michel

 

That's what I was afraid of. So the only way it seems that I am going to be able to clear them now is to go through and do a factory reset on all of them?

 

jbev,

 

Apologies for a tardy reply. Here's the situation:

1. If you bring existing links, then those links are copied unadultered and the "meaningful" ones are used to create scenes/relationships. But, the links remain specifically due to siutations such as those described by MikeB.

2. If you do NOT bring existing links (choosing options 1 and 2 during link), then ISY overwrites existing links and then when you do Restore Devices, all the devices will by in synch with ISY.

 

I hope this answered your question.

 

With kind regards,

Michel

[MikeB]

Just a follow-up to this mini review.

 

I've been using my ISY-26 full-time since this original post, and have moved it to a more permanent location in my basement, mounted on my equipment panel.

 

I'm now running firmware release 2.4.9. This is currently beta, but very solid so I'm sure we'll be seeing 2.5.0 soon.

 

With this new firmware, far more advanced triggers and events are possible. I've added:

 

- Timers turn off my closet lights after 10 mins in case they are accidentally left on.

 

- Timers to turn off my bathroom vents & lights after 30/60 mins in case they are accidentally left on.

 

- Fast On triggers that will turn on an entire room or area when needed.

 

- Fast Off triggers that will turn off an entire room or area when needed.

 

 

 

My uses are actually pretty basic. Far more sophisticated things are possible. For example, groups of triggers that only run when you are home/away/on vacation etc., triggered by maybe a KeypadLinc button. MANY more sophisticated triggers & events are possible.

 

I have also purchased an Elk M1, which the ISY-26 integrates with. I'm hoping to install my M1 sometime in the next few weeks. I'll be sure to report back when I do.

 

Above and beyond additional features, the firmware updates since my original post have fixed certain issues/annoyances.

 

- RemoteLincs are programmed more efficiently

- Interface colors have been improved

- Haven't seen any Java errors

- No PLM lockups during normal use

 

 

Overall, the device has been fantastic. Absolutely no complaints about this device.

 

What impresses me most about Universal Devices is that they continue to perfect the ISY-26. Instead of leaving it as a very good product and moving on to their next project, they seem to strive for perfection by continuing to make the ISY-26 better and better.

[MikeB]

More praise for the ISY-26.

 

 

I had given up on X10 with my system a while back. Powerline signals were weak, and I didn't want to spend money on boosters for something I hoped to eventually replace with Insteon anyway (once Insteon-compatible equivelants are available).

 

I had tried adding X10 back into my system, but was bouncing around between different automation software packages at the time. Some supported it better than others, some were a hassle, some wouldn't allow the control of KeypadLinc secondary buttons (without odd workarounds), etc...

 

The latest firmware on the ISY-26 adds basic X10 functionality. At first I wasn't interested, but then figured I'd give it a shot. I've decided to limit myself to RF devices (which is pretty much all I need anyway), to avoid powerline issues.

 

I had a WGL V572A kicking around (as pictured in this package: http://www.smarthome.com/1135k.html ). I plugged it in to an outlet very close (on the same circuit) to the ISY-26/PLM, and created some triggers.

 

I've been testing it for a while now with -

 

- an X10 IR bridge (powerline, but just for testing)

- an X10 PalmPad remote

- an X10 SlimFire keychain remote

 

... and it's been working great. Flawlessly, actually.

 

I now have the ability to use my old X10 keychain remotes to turn on my outdoor lights (front door, driveway, etc.) from my car. I was using my RemoteLinc, but the X10 keychain remote is much more convenient in the car. I get almost 300 feet of range with the standard whip antenna from the V572A mounted up in my attic. 300 feet is pretty much the end of my driveway, no obstructions (other than the attic roof).

 

I'm able to trigger either specific Insteon devices, or entire scenes (for example my driveway lights, which include a bunch of KeypadLinc secondary buttons).

 

I also plan on experimenting with some X10 motion sensors, but I don't currently own any.