Another minor flaw I found: since some (most of in my case) of the X10 modules don't send X10 codes when manually activated (Marmitek AW 12 modules) the state of the units represented in the console and consequently in Haiku isn't always right.
But the unit switch in Haiku is just a trigger: it turns it ON if it's OFF and vice-versa. So if I have a unit that is really ON but reports as OFF in the controller I have to click to trigger it to ON and then again to OFF (hope I made my point). Wouldn't it be possible to have 2 separate buttons one to send a ON command and the other for OFF? This way I could change the state regardless of the one that the console actually thinks it is.
For those who may be wondering: it's not very annoying for lights, but I have some modules used for rollers that most of the time are manually half-open but declared OFF (closed). If I want to close them I have to turn them ON, wait for them to open and then again turn them OFF (if i send X10 commands in the middle of the operation I always get weird results). This is indeed a major inconvenience.
But the unit switch in Haiku is just a trigger: it turns it ON if it's OFF and vice-versa. So if I have a unit that is really ON but reports as OFF in the controller I have to click to trigger it to ON and then again to OFF (hope I made my point). Wouldn't it be possible to have 2 separate buttons one to send a ON command and the other for OFF? This way I could change the state regardless of the one that the console actually thinks it is.
For those who may be wondering: it's not very annoying for lights, but I have some modules used for rollers that most of the time are manually half-open but declared OFF (closed). If I want to close them I have to turn them ON, wait for them to open and then again turn them OFF (if i send X10 commands in the middle of the operation I always get weird results). This is indeed a major inconvenience.
