11-16-2017, 07:23 PM
11-16-2017, 07:47 PM
[user=1]slychiu[/user] wrote:
Hi Slychui,
Apologies, Im slow to learn and quick to forget :-)
So, my understanding is
1) When velbus status changes, comfort updates the value of the counter.2) When the counter value changes, then it triggers a response.3) Then you are saying that the response should set the counter value again ?
Do I also not need to add a \"IF counter value =255, then set counter to 0 ?
Quote:If counter 59=0
Then set counter 59=255
Hi Slychui,
Apologies, Im slow to learn and quick to forget :-)
So, my understanding is
1) When velbus status changes, comfort updates the value of the counter.2) When the counter value changes, then it triggers a response.3) Then you are saying that the response should set the counter value again ?
Do I also not need to add a \"IF counter value =255, then set counter to 0 ?
11-16-2017, 07:57 PM
Sorry ignore my last post
You have to set a threshold with hystetesis
Eg
If counter 59 < 50 then lights on
If counter 59 > 80 then lights off
You have to set a threshold with hystetesis
Eg
If counter 59 < 50 then lights on
If counter 59 > 80 then lights off
11-16-2017, 08:08 PM
Thanks again,
But can you explain how this doesnt trigger a loop, as when I turn on the lights, then the counter value will change and trigger the same response again ?
But can you explain how this doesnt trigger a loop, as when I turn on the lights, then the counter value will change and trigger the same response again ?
11-16-2017, 08:34 PM
[user=1]slychiu[/user] wrote:
Sorry, I\'m still not getting it, here is what I have done
Set counter 59 to trigger response \"corridoor lights\"
Respoinse corridoor lights is as follows
If counter 59<60, then do response corridor light on
else,
if counter 59>80, then do response corridoor light off
I update comfort with this, and then as first test I go and manually turn on the light at the wall. The result is disco city, the light goes into a continious toggle, and I have to disconnect my velbus before I can talk to comfort again and remove it.
So, I am completely failing to understand how to prevent the toggle loop ?
Quote:Sorry ignore my last post
You have to set a threshold with hystetesis
Eg
If counter 59 < 50 then lights on
If counter 59 > 80 then lights off
Sorry, I\'m still not getting it, here is what I have done
Set counter 59 to trigger response \"corridoor lights\"
Respoinse corridoor lights is as follows
If counter 59<60, then do response corridor light on
else,
if counter 59>80, then do response corridoor light off
I update comfort with this, and then as first test I go and manually turn on the light at the wall. The result is disco city, the light goes into a continious toggle, and I have to disconnect my velbus before I can talk to comfort again and remove it.
So, I am completely failing to understand how to prevent the toggle loop ?
11-17-2017, 07:36 AM
If you just want to turn on the Lights if it is dark then
If Counter 59 < x then do lights on
Why do you need to turn off the lights?
If Counter 59 < x then do lights on
Why do you need to turn off the lights?
11-17-2017, 12:41 PM
[user=1]slychiu[/user] wrote:
Quote:If you just want to turn on the Lights if it is dark thenI am issueing a voice command, so I need to be able to trurn it in and turn it off
If Counter 59 < x then do lights on
Why do you need to turn off the lights?
11-17-2017, 12:58 PM
I understand that your counter 59 is the light level for automatic switch on of the lights.
It should not be used as general on/off control of the light, as this is why you are having the disco problem
If your voice command triggers responses then on and off commands can be linked to individual responses
I dont know if on and off words can map to values that are sewnt to the counter
eg On sets counter X to 255, Off sets counter X to 0. If so then your counyter response cam switch on or off the lights based on the value. Note that this should not be the same as counter 59 which is the light level
It should not be used as general on/off control of the light, as this is why you are having the disco problem
If your voice command triggers responses then on and off commands can be linked to individual responses
I dont know if on and off words can map to values that are sewnt to the counter
eg On sets counter X to 255, Off sets counter X to 0. If so then your counyter response cam switch on or off the lights based on the value. Note that this should not be the same as counter 59 which is the light level
11-17-2017, 01:06 PM
[user=1]slychiu[/user] wrote:
Hi slychui,
The objective was to use the counter as the device in St, so counter 59 is the actual light and the status in St is based on the counter value. The control piece is st adusting the counter value to 0 or 255, I don\'t think the st can adjust two different counters ?
Quote:I understand that your counter 59 is the light level for automatic switch on of the lights.
It should not be used as general on/off control of the light, as this is why you are having the disco problem
If your voice command triggers responses then on and off commands can be linked to individual responses
I dont know if on and off words can map to values that are sewnt to the counter
eg On sets counter X to 255, Off sets counter X to 0. If so then your counyter response cam switch on or off the lights based on the value. Note that this should not be the same as counter 59 which is the light level
Hi slychui,
The objective was to use the counter as the device in St, so counter 59 is the actual light and the status in St is based on the counter value. The control piece is st adusting the counter value to 0 or 255, I don\'t think the st can adjust two different counters ?
11-17-2017, 01:29 PM
Perhaps Matt will have a solution to this
Control needs to be separate from status
Control needs to be separate from status