I saw this infoon the setup of the switch. It seems that you should be able to just send Dim or Bright commands to move it in 4% increments. Have you tried sending Bright commands in the the Direct X10 Command property instead of the Dim commands? If you can't get it to move correctly using the Bright;25 (for full down), you can maybe change the Task to send individual Bright commands (no ; and number, just Bright) until you can get it where you need it.
I wonder if you have a bad switch or something. Maybe the powerline noise from the motor is messing up the X10 transmission ??
Ok Scot i hope ur a handsome man as i could kiss ya!!!!!!
Right it didnt quite work the way you said but gave me something to play with.
I added item/action X10 Command OFF
then added item/delay 18500
then added item/action X10 Command Dim;5 (if you remember dim;5 gave me about an inch of drop)
This way instead of dropping 10 secs then going straight back up with ON command it drops 18.5 secs then sends an extra inch....
I now have the drop i NEED :lol: :lol:
Im well chufffed. But this brings me to next Question for you.
Before with It working thru Devices it was linked to Meedio Essentials and i have an all view for lights and screen. I clicked Screen Off which dropped it down (wrongly) and then Screen On again to lift it all the way back.
Glad to hear it's working better for you. No need for kissing though... it's just software
I'm really not familiar at all with the Essentials to HB connector to help you on the interoperability. There should definitely be a way to do what you are looking for.
Since the HouseBot connector is fairly new, you may not be able to find the support you need on the community forums. You might want to consider opening a ticket in the support system (support.meedio.com).
Scottbot, thought id let you know the good news. Finally got this working Through Meedio Essentials yesterday.
As it turned out it was easy as pie (after the help you have been giving me)
We were talking of sending commands as dim;25 etc and wasnt workin, then we said to use task, which did work but essentials looks at the Device section to make changes so the task didnt work.
Not until i discovered the Execute Tasks bit and found an "if this equals this then run task". Found i could add a Button State as a property within devices. So added that and it has the option of Up/Down (which is great for my screen commands). So my what if, is linked to this Device in Essentials and if Button State equals Down it runs the task for screen down. If it equals Up screen goes up.
Excellent :lol: :lol: :lol: .
Cheers dude. If i can get this to work off a hot key in the future i can link it to my remotes control of Essentials too. But for now im happy.
