I added the 2 lines and it reports brightness level of 0 after I press RF Off for the Lamp Modules.

JLdomains wrote:I added the 2 lines and it reports brightness level of 0 after I press RF Off for the Lamp Modules.

So, what happens when you press on after that? Can you send the log?

Nick,

After I send RF Off and I send RF On it goes to 100% instead of 26%. The ceiling light via an X10 switch works as wanted RF on after a RF off turns it to the dim level of 15 and not 100%.

I am using your virtual X10 script with the 2 added lines from your previous post and the following x10DeviceMap.

property x10DeviceMap : {¬
{"D9", "Gym Ceiling", 15}, ¬
{"D10", "Gym Bedside Lamp JL", 26}, ¬
{"D11", "Gym Bedside Lamp 2", 26} ¬
}

Here is the log for the lamp module:
Received X10 "Gym Bedside Lamp JL" off
VirtualX10 Adr: D10 Cmd: «constant ****xF03» Dim: Pre: xDa: xCm:
VirtualX10 address D10 maps to Gym Bedside Lamp JL
VirtualX10 turn off Gym Bedside Lamp JL
Script Gym Bedside Lamp JL is at 0 after turn off
Sent X10 "Gym Bedside Lamp JL" off
Received X10 "Gym Bedside Lamp JL" on
VirtualX10 Adr: D10 Cmd: «constant ****xF02» Dim: Pre: xDa: xCm:
VirtualX10 address D10 maps to Gym Bedside Lamp JL
VirtualX10 Gym Bedside Lamp JL is at 26; default bright is 26; brighten to 100
Sent X10 "Gym Bedside Lamp JL" extended dim to 100
Received X10 "Gym Bedside Lamp JL" on
VirtualX10 Adr: D10 Cmd: «constant ****xF02» Dim: Pre: xDa: xCm:
VirtualX10 address D10 maps to Gym Bedside Lamp JL
VirtualX10 Gym Bedside Lamp JL is at 100; default bright is 26; brighten to 26
Sent X10 "Gym Bedside Lamp JL" extended dim to 26
Received X10 "Gym Bedside Lamp JL" off
VirtualX10 Adr: D10 Cmd: «constant ****xF03» Dim: Pre: xDa: xCm:
VirtualX10 address D10 maps to Gym Bedside Lamp JL
VirtualX10 turn off Gym Bedside Lamp JL
Script Gym Bedside Lamp JL is at 0 after turn off
Sent X10 "Gym Bedside Lamp JL" off
Received X10 "Gym Bedside Lamp JL" on
VirtualX10 Adr: D10 Cmd: «constant ****xF02» Dim: Pre: xDa: xCm:
VirtualX10 address D10 maps to Gym Bedside Lamp JL
VirtualX10 Gym Bedside Lamp JL is at 26; default bright is 26; brighten to 100
Sent X10 "Gym Bedside Lamp JL" extended dim to 100

I setup an X10 device to be similar to your setup and while I am not seeing the exact same issue, it is bizarre behavior.

The short story is that I think what is happening is overlapping commands generated by the remote, the script and Indigo.

The rub is that the script assumes that the defined X10 addresses are not real devices (hence the name "Virtual X10"). So when you have a real device with the same address as a virtual device you've defined in the script, things can get confusing.

The easiest way to resolve this is to use different addresses for the devices and the remote X10 buttons. For example, a different housecode; remote button E10 controls the device with an address of D10, etc.

Macpro wrote:Not at all. I'm using it in a X10 only installation, as Insteon is still not available in Europe.
The script works without any problems.

Macpro, are you seeing the same behavior as jldomains?

No, I'm seeing normal behaviour.
But I don't have any Leviton modules, only Marmitek.

What might be happening is that the Leviton module is set to hold the last brightness level as start value. Then, when you do a status request, the module reports that start value instead of the actual value. So you get 26 and not the expected 0.

This is just a wild guess, but you can verify it by changing the options for the Leviton module. Maybe that wil help.

Macpro, are your remote addresses the same as your device addresses? Do you have the "retransmit" option selected for the RF interface?

nsosnicki wrote:Macpro, are your remote addresses the same as your device addresses?

Not always. For most devices, the remote address is different than the device address. I have 1 or 2 devices that need to respond real fast to the remote control. Has something to do with WAF.

nsosnicki wrote:Do you have the "retransmit" option selected for the RF interface?

For one housecode, retransmit is enabled because devices are directly mapped to the remote. For two other housecodes, retransmit is not enabled.

Now here's something funny...

I'm having trouble with the Virtual X10 script when using Marmitek LWM1 modules.

I start with the light off.
Indigo shows the light in the device list with status off.

I press the "on" button on the remote.
The virtual X10 script does it magic and sets the light to a 60% value.
Indigo shows this value in the device list.
The log shows that Indigo sends a X10 extended dim to 60 command.

Next I press the brightness button on the remote.
The light gets turned off and then it's set to a dim value of 8%?!?!?!?

If I manualy tell Indigo to perform a status request on the device, the brightness button works as it should. Thus dimming to 68% instead of 8%.

Based upon the manual test, I've changed the AppleScript code from

Code: Select all

turn on device deviceAddress

to

Code: Select all

turn on device deviceAddress
status request device deviceAddress

and from

Code: Select all

brighten device deviceAddress to targetBright

to

Code: Select all

brighten device deviceAddress to targetBright
status request device deviceAddress

This solved my problem.

[edit] I made an error when debugging this issue and that gave some weird results. Posted that story here first, so you might have read that via the RSS feed. Sorry for that. [/edit]

Hi,

I just started using this script as i'm transitioning from Heyu to Indigo.

+Can you update the code in the original post to fix the copy and paste error:

Code: Select all

if currentBright is greater than or equal to defaultBright and currentBright < 100 then

+I am seeing an error in the logs that continue is deprecated:

Code: Select all

 Error               delete "continue receive x10 event ..." line from attachment script (call has been deprecated)

Thanks, I've updated the original script to fix both problems.

I have a situation with this script where I am running both Heyu and Indigo while I transition to Indigo, so for now all my Insteon devices also have X10 addresses assigned to them and I would like to keep it that way for now.

In this case, I have a motion sensor (MS10a X10 security) that when senses motion when it's dark, and the light controlled by a switchlinc was not already on (light is off) then brighten the light to level 6 and set a timer to 1 minute. (the rest of the scripts below is to handle the case of the switch being used locally to cancel to timer):

Code: Select all

SCRIPT upstairs_hall_light on rcvi :: @clrflag 2; @settimer 11 0
SCRIPT sec_motion_upstairs alert night notflag2 notarmed rcva :: (($x10_upstairs_hall_light & $isOff)) && heyu "bright upstairs_hall_light 6; settimer 11 1:00; setflag 2"
SCRIPT -timeout timer11 flag2 :: @clrflag 2; @settimer 11 0; heyu off upstairs_hall_light


Anyway, what I see in the Indigo logs is something like:

Code: Select all

2011-05-10 23:51:35     Received X10    C6 brighten by 5
2011-05-10 23:51:35     Received X10    C6 brighten by 5
2011-05-10 23:51:36     Received X10    C6 brighten by 5
2011-05-10 23:51:36     Sent INSTEON    "Upstairs Hall" on to 5
2011-05-10 23:51:36     Trigger Action  Upstairs Hall Multi-Link
2011-05-10 23:51:36     Sent INSTEON    "Upstairs Hall" on to 10
2011-05-10 23:51:36     Trigger Action  Upstairs Hall Multi-Link
2011-05-10 23:51:37     Sent INSTEON    "Upstairs Hall" on to 15
2011-05-10 23:51:37     Trigger Action  Upstairs Hall Multi-Link
2011-05-10 23:51:37     Sent INSTEON    "Upstairs Hall Slave" on to 5
2011-05-10 23:51:37     Sent INSTEON    "Upstairs Hall Slave" on to 10
2011-05-10 23:51:38     Sent INSTEON    "Upstairs Hall Slave" on to 15


C6 is the X10 address for both Upstairs Hall and Upstairs Hall Slave (a 3-way)
C6 brighten by 5 is being received 3 times, so it brightens
Then once the insteon signals start being sent, it flashes off and then brightens again to the same level

The obvious solution here is to remove the X10 addresses from the insteon devices, but am I ready for that yet I don't know. I am just hoping there is an easy solution for this in Indigo since I'm not too familiar with it yet. The easiest solution to the flashing light may be to be able to change a device state without actually sending the powerline commands?

Thanks,
Brandt

I think the quickest way to solve all of this is to drop the X10 addresses. It probably won't be as bad of a transition as you are expecting, and you'll appreciate how fast everything is once you stop throwing around X10 commands so much.

support wrote:I think the quickest way to solve all of this is to drop the X10 addresses. It probably won't be as bad of a transition as you are expecting, and you'll appreciate how fast everything is once you stop throwing around X10 commands so much.

Very well, I'll give it a shot. I was just hoping to have everything (all my heyu scripts) set up just the way it was before on Indigo before switching over completely. One of the major things is figuring out how to handle the MS10a's and DS10a's in Indigo before physically switching over my w800usb to the Mac Mini.