Jump to content

Using a Dimmable Light in a 3way (Master/Slave) setup - Slave turns on set level always to 100%


Roman

Recommended Posts

Finally switched over to LED dimmable lights, wow what a wattage savings.. That said everything is working great but did notice the following issue but only in my 3way (Master/Slave) setup.

Master and Slave (did reset the levels at the insteon switch just in case as well verified through the ISY) set the ON LEVEL to 60%

Test the Master Switch no issues click once ON lights go to 60% Click ON again lights go to 100%. Switch properly reports the level.

Test the Slaver Switch issues click once ON lights go to 100% Click ON again lights stay on 100%. Slave switch y reports the level click 1 ON shows 60% but light is at 100%, Click ON again and level on switch shows 100% but light is always going on 100%. When you look at Master Switch levels on click 1 does show 100%.

So no matter what when using the Slave switch it seems to report correctly on itself but for some reason the Master Switch is always going to 100%, but not the case when operating the Master Switch..

PS.. I should note it ISY also since switching to dimmable LED lights does not seem to report the switch status either ? However that said can control the switch from the ISY and status is reported if commands sent from ISY.. As if the 2 way communication switch to ISY no longer communicating ?

Very weird, and I have 3 setup all do the same of the 3 way situation. Single pole, no issues obviously working as they are suppose to.

Thanks, just a mere inconvenience.

Roman

Link to comment
Share on other sites

3 hours ago, lilyoyo1 said:

Both should be in a scene as controllers and both controllers need to be configured for the responder device to go to 60%.

I suspect you simply updated the device attributes and not what the scene should do

Interesting, you did have me fix, but now the opposite problem.. Now the Slave turns on to say 60% but when I click on the switch again does not go to 100% just stays at 60% though the light switch LEDs do show it to be at 100%.. Interesting.. Master working fine.

Note: Did notice on my MASTER that in the Scene which I do to that switch does not have a "Retry" line ??? Yet other scene Master switches do ?

 

 

1.jpg

2.jpg

3.jpg

Link to comment
Share on other sites

Yes.. Looked at Individual device settings, then the scene setting which all 3 areas of scene are identicle.. Interesting enough I have 3 situations whereby I have a 3way setup.. Always the SLAVE, Master is fine.

Roman

Link to comment
Share on other sites

Okay did some further testing, not the lights themselves... Looks like my slave switches in a 3 way configuration do not communicate with the ISY, and again they the Insteon Switch will turn on and off the light but not change the level. When I push ON or FAST ON on the ISY no action at the light, even OFF does not work when using ISY to send command ?? Anyone have suggestions ? MASTER switch no issues, works at switch level as well from ISY.

So good news is not the new dimmable LED lights.. Something in the setup of ISY and the SLAVE Switch.

 

ISY Firmware v5.3.3

 

Hmm Looks like a "double tap" at the SLAVE solves the issue for full on, unlike the MASTER a single tap.

 

Roman

Link to comment
Share on other sites

8 hours ago, Roman said:

Looks like my slave switches in a 3 way configuration do not communicate with the ISY

If your devices are having trouble communicating with each other, there is little you can do in the settings and configuration to help.  This problem must be solved before you can go much further.

- do you have many Insteon devices?  (There is benefit to a certain number of devices to act as repeaters for the Insteon signals.)

- is your PLM plugged into an outlet or circuit with lots of other electronic devices?  (Power supplies...UPS...printers...computers....all could disrupt communication to the PLM.)

Link to comment
Share on other sites

When there is a scene command, ISY will display all the level of the devices as per the scene settings as ISY has them.  The devices themselves may not actually be at that setting, but ISY will show them that way.  ISY has to assume the devices all heard and responded to the scene command.  The reason is that when a device responds to a scene, it does not send a status report, so ISY must assume it happened.  So this is why you may see devices in ISY that show one status but are in fact a different status.  I assume that devices responding to scenes do not send status reports because there could potentially be a lot of devices all trying to report status simultaneously and that might overwhelm the comm.  This is different from controlling a single device, which will send a status update.

You could also have orphan and bad links.  I have seen ISY get things messed up where it writes links to devices that aren't correct, so even factory resetting and then restoring from ISY just puts the bad links back.  In that case you have to delete the devices from ISY, factory reset, and start over.  When this happens, lots of weird things happen and there is no point in trying to figure out, you can't fix it except to delete and start over.

You also may have a comm problem.  If you can query all the devices and get a quick response, you probably do not have a comm problem.  If you query and the "busy" indicator in the bottom left corner of ISY just flashes on for a second, then you have a strong comm.  If it spins for a while, then you don't.  Obviously if puts a red exclamation, then you don't have comm at all.  Also, if you have lots of problems turning the device off, but not on, then that means the device is causing noise.  A 24v transformer could definitely be causing noise.

Link to comment
Share on other sites

2 hours ago, apostolakisl said:

If you can query all the devices and get a quick response, you probably do not have a comm problem. 

The only amendment I would make to this is that a query could tend to be an indicator of communication problems, but only between the PLM and queried device.  It may not be a good indicator of communication between two devices.

Link to comment
Share on other sites

2 minutes ago, oberkc said:

The only amendment I would make to this is that a query could tend to be an indicator of communication problems, but only between the PLM and queried device.  It may not be a good indicator of communication between two devices.

Hmmm.  I wouldn't expect this.  I do believe that PLM's are repeaters.  So if ISY gets a quick ACK from 2 devices, then at worse the com between those two devices would be device1->plm->device2.  

Link to comment
Share on other sites

1 hour ago, apostolakisl said:

I wouldn't expect this.  I do believe that PLM's are repeaters. 

Perhaps.  Yes, I also understand that PLM's are repeaters.  Upon further reflection, I have experienced where direct links between two devices working, but communication with the PLM has failed.  You are probably correct, however, that the inverse of my experience (PLM>>>device works, but device>>>device does not) may not be assumed.  I may have made too broad an extrapolation.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...