tjkintz Posted September 23, 2017 Posted September 23, 2017 My device is v.39. The documentation for this device says: 8 Scene Non-Toggle Mode (Always On) Each button will control all its scene members as follows: Tap: Turn scene on Press and hold: Brighten until release Double-tap: Instant full-on However, if you hold the key down when the key state is on, it will actually lower the key state and if you hold it long enough, it will actually change the state to off. I think the first time you hold it down, nothing happens but if you hold it down again then it lowers the state. While lowering, the LED is red instead of the normal green for on. This quirk presents some programming challenges so I have reverted to toggle mode which is easier to program for.
Techman Posted September 23, 2017 Posted September 23, 2017 My device is v.39. The documentation for this device says: 8 Scene Non-Toggle Mode (Always On) Each button will control all its scene members as follows: Tap: Turn scene on Press and hold: Brighten until release Double-tap: Instant full-on However, if you hold the key down when the key state is on, it will actually lower the key state and if you hold it long enough, it will actually change the state to off. I think the first time you hold it down, nothing happens but if you hold it down again then it lowers the state. While lowering, the LED is red instead of the normal green for on. This quirk presents some programming challenges so I have reverted to toggle mode which is easier to program for. What exactly are your programming challenges?
tjkintz Posted September 23, 2017 Author Posted September 23, 2017 I use the remote keys as toggles for devices and scenes that may have multiple controllers. In my situation, they happen to always be on/off devices, not dimmable devices. I just want to detect a key press and switch the state of the device. I have found that using a control test presents too many things to test for; on, off, dim, brighten, etc. So I have been using toggle mode and testing for status off or not off. That way, each key press is a status change, that simple test will always be true and I can take the appropriate action in the Then clause. Today I decided to experiment with the non-toggle mode. First, the test for a status of off or not off would not work because the status is always on (ignoring the quirk I had mentioned) so there was no status change and the program did not get run. That implies I had to use a control test for 9 possibilities to catch all the possibilities. I tried on or not on and that works for a normal key press but holding the key down, which actually causes it to lower the status as mentioned, the program did not run. I switched back to toggle mode.
Techman Posted September 23, 2017 Posted September 23, 2017 I use the remote keys as toggles for devices and scenes that may have multiple controllers. I Are all the buttons used to control scenes or are some being used to control individual devices that are not part of a scene? Are any of the buttons used to control a program? Can you give me an example of whatever you're having a problem with.
stusviews Posted September 23, 2017 Posted September 23, 2017 The Mini RemoteLinc buttons behave as do KPL buttons when linked to a dimmer responder even when set to Non-toggle On. Tap the button to reverse the last send (If On, then send off, if Off, send on), hold the button to reverse the last send (If On, then send Dim, if Off, then send Brighten).
tjkintz Posted September 23, 2017 Author Posted September 23, 2017 Some control scenes and some control devices but always through programs. No button controls a scene or device directly. I am not really having a problem that I haven't resolved but just ran into mini-remote behavior that is in conflict with the documentation and complicates programming so I thought I would let people know about it. If you are curious about an actual application, I just installed a snow melt system under my driveway. It has 6 heating zones, each controlled by a 2677SA 220V load controller. I also installed a snow sensor which turns on a load when it detects snow. However, it cannot handle the amperage of the heating cables and I want finer control over which zones turn on and for how long. So I attached the load from that sensor to 2443 x22 micro on-off module which signals the ISY that the snow sensor has turned on or off. Eventually I will figure out what to turn on and for how long and program it accordingly but I saw the need to manually turn some zones on and off. I had an extra mini-remote so programmed 6 keys to toggle those zones, one key to turn on all the zones and one key to turn off all the zones. I also programmed a fail-safe program to make sure a zone doesn't stay on longer than 3 hours. So the zones can be turned on due to the snow sensor or with one of the remote keys. They can be turned off due to the snow sensor saying it stopped snowing, the fail-safe program or one of the remote keys. It is a little complicated.
tjkintz Posted September 23, 2017 Author Posted September 23, 2017 stusviews, that isn't what I observed. When set in non-toggle mode, simply clicking a key will always send an on. Holding the key made it dim. I didn't try holding the key again to see if it would brighten but just clicking the key always sent an on.
stusviews Posted September 23, 2017 Posted September 23, 2017 You are correct. I struck-out the erroneous part pertaining to non-Toggle On (see below). Tapping the button will always send an On. Holding the buttons causes the response you are seeing. The Mini RemoteLinc buttons behave as do KPL buttons when linked to a dimmer responder even when set to Non-toggle On. Tap the button to reverse the last send (If On, then send off, if Off, send on), hold the button to reverse the last send (If On, then send Dim, if Off, then send Brighten).
Techman Posted September 23, 2017 Posted September 23, 2017 Some control scenes and some control devices but always through programs. No button controls a scene or device directly. I am not really having a problem that I haven't resolved but just ran into mini-remote behavior that is in conflict with the documentation and complicates programming so I thought I would let people know about it. If you are curious about an actual application, I just installed a snow melt system under my driveway. It has 6 heating zones, each controlled by a 2677SA 220V load controller. I also installed a snow sensor which turns on a load when it detects snow. However, it cannot handle the amperage of the heating cables and I want finer control over which zones turn on and for how long. So I attached the load from that sensor to 2443 x22 micro on-off module which signals the ISY that the snow sensor has turned on. Eventually I will figure out what to turn on and for how long and program it accordingly but I saw the need to manually turn some zones on and off. I had an extra mini-remote so programmed 6 keys to toggle those zones, one key to turn on all the zones and one key to turn off all the zones. I also programmed a fail-safe program to make sure a zone doesn't stay on longer than 3 hours. So the zones can be turned on due to the snow sensor or with one of the remote keys. They can be turned off due to the snow sensor saying it stopped snowing, the fail-safe program or one of the remote keys. It is a little complicated. If you use an 8 button KPL rather than the wireless remote you would be able to see what zones are on or off as indicated by the lit buttons on the KPL. This would protect you from accidentally turning on a zone in the event you touched the wrong button on the remote
lilyoyo1 Posted September 23, 2017 Posted September 23, 2017 The instructions are correct they just didn't spell out step by step what happens. They simply covered turning on a device with the assumption a person would realize the opposite when trying to turn off a device.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.