Status of local device action back to ISY

[riceman]

Hi all--

 

Just got my ISY unpacked and running last night. I've been trying to figure out if there is an easy way to have the ISY immediately see a local switchlinc action (somebody turning the switch on or off). Right now, it appears the only way is to manually query or to set up a schedule to periodically query. However, neither is an option if I want to set up an immediate trigger in response to a local state change at the switch.

 

Is this part of the enhanced trigger functionality in 2.5? I can think of many scenarios where having ISY immediately see the state change of a local action would be extremely useful. Will I have the same issue with using X10 motion sensors to trigger events (when X10 support is incorporated)?

 

Other than that, everything else with the inital setup has been really smooth! Great product...

 

Thanks

Dave

[Michel Kohanim]

Hello Dave,

 

If you have SwitchLinc versions above 2.4, you should immediately see the feedback (when you do anything on the switch). For SwitchLinc version below 2.4, you will never get the status back and thus you would have to manaully query. Unfortunately, at this point, the only thing I can suggest is to get an upgrade for your SwitchLics.

 

Thanks and with kind regards,

Michel

 

Hi all--

 

Just got my ISY unpacked and running last night. I've been trying to figure out if there is an easy way to have the ISY immediately see a local switchlinc action (somebody turning the switch on or off). Right now, it appears the only way is to manually query or to set up a schedule to periodically query. However, neither is an option if I want to set up an immediate trigger in response to a local state change at the switch.

 

Is this part of the enhanced trigger functionality in 2.5? I can think of many scenarios where having ISY immediately see the state change of a local action would be extremely useful. Will I have the same issue with using X10 motion sensors to trigger events (when X10 support is incorporated)?

 

Other than that, everything else with the inital setup has been really smooth! Great product...

 

Thanks

Dave

[Sub-Routine]

The first thing I did after reading your question Dave, was to try a switch. It did as yours, no notice to the ISY. Then I spent 15 minutes trying all my switches to conclude that all my switches, except one, do show an instant change in the ISY. I deduced that the one 2.4 SL I own was the only one that doesn't function properly.

 

So I return to report that, and Michel has beaten me to it! I knew I should just wait for the great customer support that UDI has, but it was worth it to test all my switches, as many are not used often.

 

Thank you Michel.

 

Welcome to the forum Dave. The ISY is a great device, you will find a lot of good information here.

 

Thank you,

Rand

[MikeB]

Curious - what is it about the pre-2.5 switches that don't allow the ISY-26 to read the status?

 

Also, I believe those revision remarks apply ONLY to the dimmers. I have v2.2 Relays that report the status fine.

 

I believe, as far as time of release goes:

 

v2.2 relay = v2.5 dimmer

v2.3 relay = v3.1 dimmer

 

My initial purchase of v2.2 relays and v2.5 dimmers had the super-bright LEDs.

 

My second purchase of v2.3 relays and v3.1 dimmers were a more pleasing LED brightness.

[riceman]

Well I went and tried several switches, all to no avail. I specifically tried every possible variation on linking a switchlinc dimmer I just bought from smarthome a couple days ago and the label says V 3.1. Almost all my switchlincs are less than a couple months old. The oldest is maybe 6 or 8 months. How long has the version 2.4 and above been out?

 

Any other ideas on what I might be doing wrong? I've restored the device via the ISY, I've reset it via the physical reset on the switchlinc... Everything is fine when I turn the switch on or off from the ISY console page -- I just cannot get updated switch status whenever the switch is turned on or off at the switch itself, unless I manually issue the query command..

 

Frustrated in Florida

[riceman]

Stop the presses, I tried one last thing -- I performed a restore on the PLM and viola! --all local actions at all my switchlincs are now reporting instantly to the ISY -- no manual query needed!! Phew, I thought I was stuck with a bunch of old switchlincs!

 

Thanks for the help in getting this solved.

 

Dave

[Sub-Routine]

Stop the presses, I tried one last thing -- I performed a restore on the PLM and viola! --all local actions at all my switchlincs are now reporting instantly to the ISY -- no manual query needed!! Phew, I thought I was stuck with a bunch of old switchlincs!

 

Thanks for the help in getting this solved.

 

Dave

 

That seems odd and unwarranted, but since it worked it's a Good Thing. There must have been something stuck in the PLM. It's odd that no one else thought of that.

 

You have discovered something new! Another thread for the How Tos section. I knew you were going to be helpful from the moment you joined us

 

Rand

[Mark Sanctuary]

Yeah I experienced this too that a restore seems to fix the devices that don't show the status on the ISY. The ISY should have a single link to each device so it gets its confirmation message back when the switch is used. Might be the link the ISY has with the device is somehow messed up. And some of my dimmers (I think it’s mostly the keypadlinc loads) still just report on/off and not the level percentage.

 

I must have some really old devices; most of mine report v.27, v.28, v.29 or are you guys adding decimal points in between digits? Or are you reading a sticker on the back of the device?

[Sub-Routine]

Yes, we are adding a decimal point so it matches the sticker. You should be fine since your devices are above v.2.4.

 

That's odd with the KPLs, especially since a KPL Relay is probably one of the most requested devices never built. I have only one KPL and it has no load, so it's difficult for me to help you with that. KPLs do have different hardware/firmware than SwitchLincs. You may want to mention this in the Bugs forum.

 

Rand

[MikeB]

I must have some really old devices; most of mine report v.27, v.28, v.29 or are you guys adding decimal points in between digits? Or are you reading a sticker on the back of the device?

 

Actually, I'm talking about the sticker on the front of the device.

 

My ISY-26 shows most of my dimmers at v.27, and most of my relays as v.28.

[Michel Kohanim]

Hello All,

 

Apologies for the long silence as we've been heads down with the 2.5.

 

Rand,

 

Thanks so very much for your quick responses. As usual, you've been instrumental in making ISY a better product.

 

MikeB,

 

I am not sure why previous releases of SL do not have any feedback.

 

riceman and marksanctuary,

 

Thank you so very much for reporting this issue. This must be a bug which we are going to analyze and find the root-cause + resolution. At the moment, it seems to me that you have a defective PLM ... as such, please do be kind enough to report any other anomalies. In the meantime, we are going to test all new releases of SL + KPL.

 

Again, thanks so very much to all for reporting this issue and apologies for the inconvenience.

 

With kind regards,

Michel

[riceman]

Michel --

 

Well, since you requested that I report any other anomalies, I am witnessing a consistent problem: When I do an "ALL OFF" from the ISY console page, not all my devices are responding. The status goes to "OFF" for all devices, but about half of my 10 switchlincs remain on and the two icon dimmer switches do not respond. My Lamplincs respond fine. Furthermore, the same switches also do not respond when I issue an "ALL ON" from the ISY console. I also get the same result when I create a schedule to set all devices under "My Lighting" to OFF.

 

However, all switches do respond as they should when I use the On/Off controls on the individual device control page. And I am no longer witnessing the previous issue I reported where the local device action is not being reported on the ISY console page (but the status is incorrect now for the non-responding devices to the ALL ON or ALL OFF).

 

Has anybody else witnessed this? I tried a PLM restore as well as device restores, all to no avail. It seems that the device and PLM are working properly since the devices always respond to the commands from the individual device page. What would cause some devices to not respond to ALL ON / ALL OFF from the network view page?

 

I really would like to be able to utilize the ALL OFF as part of a scheduled command to make sure all lights / devices are turned off at the end of the night, so I'm hoping this can be figured out.

 

Thanks,

Dave

[Michel Kohanim]

Hello Dave,

 

Thanks so very much for the update. May I humbly ask a few questions:

1. Did you import existing links from a previous installation?

2. Did you do a File->Restore Devices (not individual Restore Device)?

 

As far as your question, here's the only reason why an INSTEON device would respond to on/off from the device page but not from All On/All Off:

When you are on the device page, ISY is sending a direct command (through the PLM) to the device. This does not require any linkages to be set in the device and, thus, it works.

 

When you send an All On/All Off command or when you send a group command (from the scene page in ISY), then the following conditions should be met:

1. The PLM should have an existing link for that device

2. The device should have a slave link for the PLM (device is acting as a slave)

 

So, if any of the above conditions are not met, then the device will not respond to All On/All off.

 

Now, here are more questions:

1. Would you be kind enough to inventory the list of devices that do not respond to the All On/All Off command?

2. For all those devices, would you please let me know if they already belong to a scene (you can check that out by looking at the device page and to your right you have another tree which shows whether or not this device belongs to any groups)

 

After receiving your input, I'd be in a better position to recommend a corrective measure. I believe the issue is due to some existing links which cause a conflict with the PLM.

 

Again, thanks so very much for the feedback,

With kind regards,

Michel

 

 

Michel --

 

Well, since you requested that I report any other anomalies, I am witnessing a consistent problem: When I do an "ALL OFF" from the ISY console page, not all my devices are responding. The status goes to "OFF" for all devices, but about half of my 10 switchlincs remain on and the two icon dimmer switches do not respond. My Lamplincs respond fine. Furthermore, the same switches also do not respond when I issue an "ALL ON" from the ISY console. I also get the same result when I create a schedule to set all devices under "My Lighting" to OFF.

 

However, all switches do respond as they should when I use the On/Off controls on the individual device control page. And I am no longer witnessing the previous issue I reported where the local device action is not being reported on the ISY console page (but the status is incorrect now for the non-responding devices to the ALL ON or ALL OFF).

 

Has anybody else witnessed this? I tried a PLM restore as well as device restores, all to no avail. It seems that the device and PLM are working properly since the devices always respond to the commands from the individual device page. What would cause some devices to not respond to ALL ON / ALL OFF from the network view page?

 

I really would like to be able to utilize the ALL OFF as part of a scheduled command to make sure all lights / devices are turned off at the end of the night, so I'm hoping this can be figured out.

 

Thanks,

Dave

[riceman]

Michel --

 

I will try to provide answers to the rest of your questions tonight when I get home, but in the meantime:

 

1. I did not import the existing links (as far as I know). This is a new install--I may have created some links in devices when I was playing around, but I am not trying to preserve those when I add a device to the ISY.

2. I just did a individual restore against the device that was not responding to the ALL OFF / ALL ON.

3. For the devices that are not responding, none of these belong to a scene (I only have two scenes defined so far, and the devices that are included in it respond fine to the ALL OFF/ALL ON.)

 

Now, when I get home and do more experimenting/troubleshooting, you mention that the device needs to have a "slave link" for the PLM. How is that created? Lately, all I am doing when adding devices is activating the "Start Linking" item in the Link Management pulldown, then going to the device and pressing in the set button (pushing the air gap button in) for about 3 seconds until the light blinks twice (for switchlinc dimmers). I think for the first few devices I added, I did it differently--I pressed the top of the paddle for 10 seconds. I think these ones where I used the top paddle press for 10 seconds are the same ones that are responding to the ALL ON / ALL OFF command from the ISY. Is that just coincidence?? Is there any difference in these two methods of adding? Perhaps I need to brush up on my Switchlinc Insteon manual...

 

Thanks for helping me through the forest.

 

Regards,

Dave

[Michel Kohanim]

Dave,

 

Thanks so very much for the quick feedback. Here's what's going on:

- For devices that may never be controllers such as LampLinc, InlineLinc, and lately OutletLinc, ISY solely depends on the linkages as they are made during the linking session; i.e. ISY does not create a Master link in the device and a Slave link in the PLM. As such, if these devices are not part of any other scenes, therefore they will not respond to All On/Off command issued from the PLM.

- ISY does create master/slave links when a device, regardless of its type, is put inside a scene and, therefore, all the devices that are already part of a scene will respond to All On/Off command.

 

To test this scenario, please create a dummy scene and put one of your non-responding devices inside that scene.

 

Please ldo be kind enough to let me know of the outcome.

 

Again, thanks for your feedback,

With kind regards,

Michel

Michel --

 

I will try to provide answers to the rest of your questions tonight when I get home, but in the meantime:

 

1. I did not import the existing links (as far as I know). This is a new install--I may have created some links in devices when I was playing around, but I am not trying to preserve those when I add a device to the ISY.

2. I just did a individual restore against the device that was not responding to the ALL OFF / ALL ON.

3. For the devices that are not responding, none of these belong to a scene (I only have two scenes defined so far, and the devices that are included in it respond fine to the ALL OFF/ALL ON.)

 

Now, when I get home and do more experimenting/troubleshooting, you mention that the device needs to have a "slave link" for the PLM. How is that created? Lately, all I am doing when adding devices is activating the "Start Linking" item in the Link Management pulldown, then going to the device and pressing in the set button (pushing the air gap button in) for about 3 seconds until the light blinks twice (for switchlinc dimmers). I think for the first few devices I added, I did it differently--I pressed the top of the paddle for 10 seconds. I think these ones where I used the top paddle press for 10 seconds are the same ones that are responding to the ALL ON / ALL OFF command from the ISY. Is that just coincidence?? Is there any difference in these two methods of adding? Perhaps I need to brush up on my Switchlinc Insteon manual...

 

Thanks for helping me through the forest.

 

Regards,

Dave