State settings not working properly.

[quixote]

I have been noticing that when using state settings that they are sometimes unreliable. In certain instances I need to hit the button twice to execute the first command, then if I hit it a third time it fires the second command. The logger shows that the trigger is,in fact, registering, but the command simply does not occur. Am I missing something?

[Promixis]

I don't use states so... hopefully somebody knows!

[mhund]

Hi,

I know a similar situation and maybe its the same.
States are working for each command itself and have no relation to other commands in the same multigroup. Sofar, if you execute a single command in a multigroup (for testing), only this state changes and not the states of other commands in this group. This leads to undefined situations, which should be handeld with the "reset All states". And there is the problem. "reset All states" does not reset all states to 1, but all states to begin state. This leads to mailfunction of Multigroups which have been thought for alternating commands.

Understand? Its a little bit hard to explain ...
To answer your question: Unreliable state changes did not occur as long as I am using girder. But Problems with the mentioned situation.

mhund

[quixote]

Thank you Mike C and Mhund.
So I guess the solution would be to use LUA? Mike, how did you go about it? I'm thinking that I could just set variables for the different modes and states ie.- mode=light light_mode=on, etc.

[Promixis]

if you want to track x10 status, I would do it in lua using tables...

On = 1
Off = 0

Kitchen = "A1"
Bathroom = "D1"

X10Status = {}

X10Status.A1 = On

print (X10Status.A1)
print (X10Status ["A1"])
print (X10Status [Kitchen])

X10Status [Kitchen] = Off

print (X10Status.A1)
print (X10Status ["A1"])
print (X10Status [Kitchen])


Lets start a new thread on this...