Release 2.8.2 Beta is now available

[Illusion]

I removed and added back my INSTEON 220V / 240V 30 AMP Load Controller Normally Closed Relay (Dual-Band) Item# 2477SA2. I also believe this device should have 2 nodes. One for the relay and one for the load sensing active function.

 

Please note, this 2 node request would not apply to the Normally Open version of the same type as it does not support load active detection.

[Illusion]

Mac running Snow Leopard v 10.6.4 accessing the Admin Console via Java application:

 

I login and about 38s later the authentication window pops up again (already populated with username and password) and I have to hit okay again to continue working in the admin console.

 

Edit: Seems to be related to accepting terms and conditions. This last time it happened it opened my browser and took me to the UD Terms and conditions page. That is the third time it has asked me to accept the terms and conditions out of the 15 or so times it has just asked me to authenticate again.

[Illusion]

Notification titles are cut a little too short for my taste. Regardless of whether I have compact notifications enable or not, the title of the program sending the notification is now only 20 characters long. I have a series of alert programs sharing the prefix 'Setback Failure - XXXX' where XXXX is the specific setback failure. This important info is now lost in both the subject line and text of the emailed notification.

[LeeG]

Have you tried 'XXXX- SetBack Failure'

[Illusion]

Thanks for the suggestion, Lee. I am just making a comment that I did not used to have this issue, and now all my program names need to change. Of course I will implement your suggestion, but personally I would like the notification to allow more than 20 characters again.

 

Actually, I was not even going to mention this issue, but the UD guys seem to care so much what their users think I felt obligated to take the time to post my concern. Clearly this is not a huge deal to me, but it is a change from previous versions that I do not care for.

 

PS. Thanks so much for the help on the KPL comm issue. It cleared up so many problems for me I cannot tell you. I was at my whits end

[Michel Kohanim]

Hello Illusion,

 

Thanks so very much for the suggestion. Are you saying that the title of notifications used to be longer and now they are truncated?

 

As far as terms and conditions, we will look into it ... I do have Snow Leopard myself and I have not been able to reproduce it but we'll continue digging in.

 

With kind regards,

Michel

[Illusion]

I do believe in earlier versions the program name text was longer and now it is truncated.

 

As far as terms and conditions, the second request for authentication is 100% of the time I open the admin console via Java Application. The additional request to agree to terms and conditions is happening about 1 in 10 log ins.

 

EDIT: Second log in issue does not seem to exist when accessing the Admin Console via applet (from safari).

[Michel Kohanim]

Hi Illusion,

 

Thanks. I did check the code and we have not truncated the subject line at all. The only change has been the addition of Sent timestamp (the actual time the email was sent from ISY) and I do not think that would impact the subject line truncation.

 

We'll check into the terms and conditions issue.

 

With kind regards,

Michel

[fitzpatri8]

Since making some system changes today (adding and deleting scenes, adding new IRLinc Transmitter scenes), I can no longer see the device tree on my ISY after I log in. Programs are still running and I can see and edit programs and use other interface features, but whenever I return to the Main tab I get a blank screen with a System Busy message at the bottom. I've power cycled both the ISY and the PLM with no change, cleared the java cache, tried bringing up the admin console using the app and the online link, all with the same result.

 

Any other ideas?

 

Thanks,

 

Tom

[Michel Kohanim]

Hi Tom,

 

Apologies for the inconvenience.

 

There used to be a bug with null names which caused the symptoms you are experiencing. Please try:

http://www.universal-devices.com/99i/2.8.2/admin.jnlp

 

If that does not work, please send your backup to Rand (support@universal-devices.com) ... he's a master of fixing it!

 

With kind regards,

Michel

[andrewm]

I don't know if something's changed in 2.8.2 wrt linking or whether I've not done it for a while, but either way the usability of the UI when you add a new device is poor.

 

The New Insteon Device Dialog requires you to enter info in both the NAME field and ADDRESS field. If you leave the NAME field blank and press OK, then the dialog closes and nothing happens. I thought it used to default the NAME to the ADDRESS and continue with the linking, and that I had a problem with 2.8.2

 

The way the dialog should work is those two fields should be reversed. The first field to be entered should be the ADDRESS (because that cannot be inferred/defaulted), and once entered that should become the default value for the NAME field. At which point the user should be able to optionally overwrite the default with another name if they so choose. The OK button should be disabled until both fields have valid entries.

[Michel Kohanim]

Hi Andrew,

 

What URL are you using? I tested this and it works fine (just providing the address).

 

With kind regards,

Michel

[andrewm]

I used the usual http://your.isy.ip.address/admin form.

 

OK, I thought that was the way it used to work (though I still think from a usability perspective the dialog should operate as I describe above). This wasn't a one-off... I tried multiple times, even rebooting, re-clearing Java cache, regenerating new self-signed certificate, always trusting the UDI certificate... I was getting quite frustrated because it was very late and I didn't want to have to revert.

 

One observation (take with grain of salt, especially as I'm not connected to the ISY right now) is that it looks like your code-signing certificate has changed, as I had to re-add the certificate to my list of trusted certificates. Iirc, there was also some warning about the certificate validity. I confused this with the comment in your release notes about self-signed certificates, which is why I regenerated a new self-signed certificate for myself, to see if that would fix my device-add issue.

[Michel Kohanim]

Hi Andrew,

 

I do apologize. "I" was using the wrong URL to test. This is indeed broken in 2.8.2 and above because we tried to fix the issue with null names.

 

We'll fix it in the next release.

 

With kind regards,

Michel

[andrewm]

I just noticed an issue - it could be classified as a bug or feature request.

 

The RemoteLinc product has ALL ON / OFF buttons which according to the docs can be linked to additional Insteon devices. However this functionality is not possibe from the ISY that I can see.

 

In my case I'd use it to perform additional cleanup (eg turning off status lights on my keypads), either through scenes or through an event trigger

[andrewm]

And another issue - this condition I've seen several times, but never reported.

 

I just logged in to the ISY, but the device status info is all incorrect (eg seeing on levels of zero, and maximum ramp rates). Additionally trying to query a device doesn't do anything (no progress bar is displayed).

 

Looking at the error log gives me the following for the time period concerned:

Sun 2010/10/10 01:07:58 AM	System	-5012	-	
Sun 2010/10/10 01:07:58 AM	System	-5012	-	
Sun 2010/10/10 01:07:58 AM	System	-5012	-	
Sun 2010/10/10 01:07:58 AM	System	-5011	uuid:00:03:f4:02:b0:0e,29	
Sun 2010/10/10 01:07:58 AM	System	-5011	uuid:00:03:f4:02:b0:0e,29	
Sun 2010/10/10 01:07:58 AM	System	-5011	uuid:00:03:f4:02:b0:0e,29	

The last line repeats multiple times.

I have to think the errors are related, but the info displayed is not helpful to me!

[Brian H]

Unless something has been updated in the RemoteLincs firmware. The All On/Off buttons can not be linked to any additional devices and only control devices linked to the six individual button sets.

 

Both the on line Users Manual and the Quick Start Guide. Have no mention of the All buttons linked to added Insteon devices. The feature chart also only covers how they act with devices linked to the six individual buttons.

 

That said. The sales page does indeed say the All Buttons can control extra devices linked directly to them.

 

10/11/2010: I took a factory reset RemoteLinc and a LampLinc. So no buttons where linked to anything. Held the ALL ON button for ten seconds and it went into the linking mode. Linked it to the LampLinc. The ALL ON and ALL OFF buttons then controlled the LampLinc. This is an older Date Code 2707 Rev 1.0 RemoteLinc.

[bocaray]

Michel,

As you enhance the firmware, "Have you ever considered an 'IF Condition' for the reset?" Something that can be used to run a program should a RESET occur? This would be very useful for establishing 'boot-up' scenes and help with troubleshooting. Something to consider???

 

If you know a method for doing this already, pleaase share.

Thanks

[Michel Kohanim]

Hello Andrew,

 

5011/12 means that ISY could not communicate with the Admin Console. That explains why your statuses are blank or invalid. This is usually caused by firewall software on your machine blocking ISY. If you have firewall software, you MUST put ISY in the trusted zone or white list.

 

Hello bocaray,

 

You can already do this by using "Run at Startup" flag for any program you desire. This can be set in Program Summary tab. In effect, the program flagged as such runs at reboot no matter what.

 

With kind regards,

Michel

[andrewm]

Both the on line Users Manual and the Quick Start Guide. Have no mention of the All buttons linked to added Insteon devices. The feature chart also only covers how they act with devices linked to the six individual buttons.

 

That said. The sales page does indeed say the All Buttons can control extra devices linked directly to them.

 

Yeah you're right - must be an older version of one of those I was reading - that RL I just installed had been sitting in a box for a long time. Nice how SmartHome move the goalposts!

 

However, given that the ALL ON / ALL OFF command just uses the predefined group 255, ISY should still be able to setup other devices to respond to those ALL ON/OFF buttons, shouldn't it? And I see the event code on the ISY diagnostics log, so ISY programs should be able to be triggered from those button pushes.

[andrewm]

5011/12 means that ISY could not communicate with the Admin Console. That explains why your statuses are blank or invalid. This is usually caused by firewall software on your machine blocking ISY. If you have firewall software, you MUST put ISY in the trusted zone or white list.

The only firewall running is Windows Firewall. I'd made no changes to my network since using ISY successfully earlier in the day. I don't remember when I last made changes to Windows Firewall - a long time ago. Attempting to access ISY now (my PC hasn't rebooted), and I get in first go. Go figure... maybe a timing issue.

 

But there are really two issues here. First is a problem accessing the ISY - no biggie, s**t happens and hiccups can be tolerated. But the second is another usability issue in that I don't get an explicit indication telling me I have the first problem; I have to work it out for myself by eventually realizing things aren't working as I'd expect, then spotting the telltale 9-minute ramp time (which is a learned behavior requiring familiarity with ISY).

[Michel Kohanim]

Hi Andrew,

 

I do understand the usability issue. At the moment, there's basically no way around it unless we make the Admin Console keep polling ISY and thus cause other problems.

 

As it stands now, when you lose connection with ISY, based on the advertised max-age information provided by ISY during authentication, Admin Console "assumes" the subscription is alive until either:

1. the keep-alive/max age duration is passed without an event

2. there's socket connection exception

 

For the percentage of the time this is indeed an issue (not to mention that the system is usually left alone once configured), the workaround (keep polling ISY) is completely and utterly a very ugly solution.

 

With kind regards,

Michel

[bocaray]

Michel,

Duh? I guess I didn't see the 'Run at Startup'. Thanks!