New build available

[UniKyrn]

It's still unhappy at the startup of the initization of the thermostat, I won't copy the entire log this time, just from start to the point where it complains about the ACK mode:

10/25/04 9:23:44 PM RCS X10 Thermostat startup Beginning background initialization of thermostats ...
10/25/04 9:23:49 PM RCS X10 Thermostat Info Initializing communications with Living Room Master Thermostat
10/25/04 9:24:10 PM LynX-10 PLC TX: Added an outbound event to the queue: P 4
10/25/04 9:24:10 PM LynX-10 PLC TX: LynX-NET packet = NET 10 NODE 00 SEQ 01 LEN 05
10/25/04 9:24:10 PM LynX-10 PLC TX: X10 PACKET: 29 0F 03 FF 14
10/25/04 9:24:10 PM LynX-10 PLC RX: LynX-NET packet = NET 01 NODE 00 SEQ 01 LEN 00
10/25/04 9:24:10 PM LynX-10 PLC Received an ACK
10/25/04 9:24:11 PM LynX-10 PLC RX: LynX-NET packet = NET 10 NODE 00 SEQ 01 LEN 01
10/25/04 9:24:11 PM LynX-10 PLC Received an ACK
10/25/04 9:24:11 PM LynX-10 PLC RX: LynX-NET packet = NET 01 NODE 00 SEQ 02 LEN 00
10/25/04 9:24:11 PM LynX-10 PLC TX: X10 PACKET: 29 0F 03 FF 14
10/25/04 9:24:11 PM LynX-10 PLC TX: LynX-NET packet = NET 10 NODE 00 SEQ 02 LEN 05
10/25/04 9:24:11 PM LynX-10 PLC TX: Added an outbound event to the queue: P 4
10/25/04 9:24:11 PM LynX-10 PLC RX: X10 PACKET: 01
10/25/04 9:24:11 PM LynX-10 PLC RX: LynX-NET packet = NET 10 NODE 00 SEQ 82 LEN 03
10/25/04 9:24:11 PM LynX-10 PLC TX: Received an X10 command success
10/25/04 9:24:12 PM LynX-10 PLC RX: Received status reply without an address first
10/25/04 9:24:12 PM LynX-10 PLC RX: X10 PACKET: 1D 0F FF
10/25/04 9:24:13 PM LynX-10 PLC RX: Received status reply without an address first
10/25/04 9:24:13 PM LynX-10 PLC RX: LynX-NET packet = NET 10 NODE 00 SEQ 02 LEN 01
10/25/04 9:24:13 PM LynX-10 PLC RX: X10 PACKET: 01
10/25/04 9:24:13 PM LynX-10 PLC TX: Received an X10 command success
10/25/04 9:24:13 PM LynX-10 PLC RX: LynX-NET packet = NET 10 NODE 00 SEQ 83 LEN 03
10/25/04 9:24:13 PM LynX-10 PLC RX: X10 PACKET: 1D 0F FF
10/25/04 9:24:18 PM LynX-10 PLC Received an ACK
10/25/04 9:24:18 PM LynX-10 PLC RX: LynX-NET packet = NET 01 NODE 00 SEQ 03 LEN 00
10/25/04 9:24:18 PM LynX-10 PLC TX: X10 PACKET: 29 0F 03 FF 14
10/25/04 9:24:18 PM LynX-10 PLC TX: Added an outbound event to the queue: P 4
10/25/04 9:24:18 PM LynX-10 PLC TX: LynX-NET packet = NET 10 NODE 00 SEQ 03 LEN 05
10/25/04 9:24:19 PM LynX-10 PLC TX: Received an X10 command success
10/25/04 9:24:19 PM LynX-10 PLC TX: X10 PACKET: 29 0F 03 FF 14
10/25/04 9:24:19 PM LynX-10 PLC TX: Added an outbound event to the queue: P 4
10/25/04 9:24:19 PM LynX-10 PLC RX: LynX-NET packet = NET 10 NODE 00 SEQ 03 LEN 01
10/25/04 9:24:19 PM LynX-10 PLC RX: X10 PACKET: 01
10/25/04 9:24:19 PM LynX-10 PLC TX: LynX-NET packet = NET 10 NODE 00 SEQ 04 LEN 05
10/25/04 9:24:20 PM LynX-10 PLC RX: Received status reply without an address first
10/25/04 9:24:20 PM LynX-10 PLC RX: LynX-NET packet = NET 01 NODE 00 SEQ 04 LEN 00
10/25/04 9:24:20 PM LynX-10 PLC Received an ACK
10/25/04 9:24:20 PM LynX-10 PLC RX: LynX-NET packet = NET 10 NODE 00 SEQ 84 LEN 03
10/25/04 9:24:20 PM LynX-10 PLC RX: X10 PACKET: 1D 0F FF
10/25/04 9:24:21 PM LynX-10 PLC TX: Received an X10 command success
10/25/04 9:24:21 PM LynX-10 PLC RX: Received status reply without an address first
10/25/04 9:24:21 PM LynX-10 PLC RX: LynX-NET packet = NET 10 NODE 00 SEQ 85 LEN 03
10/25/04 9:24:21 PM LynX-10 PLC RX: LynX-NET packet = NET 10 NODE 00 SEQ 04 LEN 01
10/25/04 9:24:21 PM LynX-10 PLC RX: X10 PACKET: 01
10/25/04 9:24:21 PM LynX-10 PLC RX: X10 PACKET: 1D 0F FF
10/25/04 9:24:32 PM LynX-10 PLC Received an ACK
10/25/04 9:24:32 PM LynX-10 PLC TX: Added an outbound event to the queue: P 4
10/25/04 9:24:32 PM LynX-10 PLC TX: LynX-NET packet = NET 10 NODE 00 SEQ 05 LEN 05
10/25/04 9:24:32 PM LynX-10 PLC TX: X10 PACKET: 29 0F 03 FF 14
10/25/04 9:24:32 PM LynX-10 PLC RX: LynX-NET packet = NET 01 NODE 00 SEQ 05 LEN 00
10/25/04 9:24:33 PM LynX-10 PLC TX: Added an outbound event to the queue: P 4
10/25/04 9:24:33 PM LynX-10 PLC TX: Received an X10 command success
10/25/04 9:24:33 PM LynX-10 PLC RX: LynX-NET packet = NET 10 NODE 00 SEQ 05 LEN 01
10/25/04 9:24:33 PM LynX-10 PLC RX: X10 PACKET: 01
10/25/04 9:24:34 PM LynX-10 PLC RX: LynX-NET packet = NET 10 NODE 00 SEQ 86 LEN 02
10/25/04 9:24:34 PM LynX-10 PLC RX: X10 PACKET: 1D 0F FF
10/25/04 9:24:34 PM LynX-10 PLC RX: LynX-NET packet = NET 10 NODE 00 SEQ 87 LEN 03
10/25/04 9:24:34 PM LynX-10 PLC RX: Received status reply without an address first
10/25/04 9:24:34 PM LynX-10 PLC RX: X10 PACKET: 02 11
10/25/04 9:24:34 PM LynX-10 PLC RX: LynX-NET packet = NET 01 NODE 00 SEQ 06 LEN 00
10/25/04 9:24:34 PM LynX-10 PLC TX: X10 PACKET: 29 0F 03 FF 14
10/25/04 9:24:34 PM LynX-10 PLC TX: LynX-NET packet = NET 10 NODE 00 SEQ 06 LEN 05
10/25/04 9:24:34 PM LynX-10 PLC Received an ACK
10/25/04 9:24:34 PM LynX-10 PLC Received an X10 COLLISION
10/25/04 9:24:35 PM LynX-10 PLC RX: LynX-NET packet = NET 10 NODE 00 SEQ 06 LEN 01
10/25/04 9:24:35 PM LynX-10 PLC RX: X10 PACKET: 01
10/25/04 9:24:35 PM LynX-10 PLC TX: Received an X10 command success
10/25/04 9:24:35 PM LynX-10 PLC RX: LynX-NET packet = NET 10 NODE 00 SEQ 88 LEN 03
10/25/04 9:24:35 PM LynX-10 PLC RX: X10 PACKET: 1D 0F FF
10/25/04 9:24:35 PM LynX-10 PLC RX: Received status reply without an address first
10/25/04 9:24:52 PM RCS X10 Thermostat Warning Unable to confirm that Ack Message Mode for Living Room Master Thermostat was set to On
10/25/04 9:24:53 PM LynX-10 PLC RX: LynX-NET packet = NET 01 NODE 00 SEQ 07 LEN 00
10/25/04 9:24:53 PM LynX-10 PLC TX: X10 PACKET: 29 0F 03 FF 16
10/25/04 9:24:53 PM LynX-10 PLC TX: Added an outbound event to the queue: P 4
10/25/04 9:24:53 PM LynX-10 PLC Received an ACK
10/25/04 9:24:53 PM LynX-10 PLC TX: LynX-NET packet = NET 10 NODE 00 SEQ 07 LEN 05
10/25/04 9:24:54 PM LynX-10 PLC RX: LynX-NET packet = NET 01 NODE 00 SEQ 08 LEN 00
10/25/04 9:24:54 PM LynX-10 PLC RX: X10 PACKET: 08 0F 09 FF
10/25/04 9:24:54 PM LynX-10 PLC RX: LynX-NET packet = NET 10 NODE 00 SEQ 8A LEN 04
10/25/04 9:24:54 PM LynX-10 PLC Received an X10 COLLISION
10/25/04 9:24:54 PM LynX-10 PLC RX: X10 PACKET: 02 11
10/25/04 9:24:54 PM LynX-10 PLC RX: LynX-NET packet = NET 10 NODE 00 SEQ 89 LEN 02
10/25/04 9:24:54 PM LynX-10 PLC Received an ACK
10/25/04 9:24:54 PM LynX-10 PLC TX: X10 PACKET: 29 0F 03 FF 16
10/25/04 9:24:54 PM LynX-10 PLC TX: LynX-NET packet = NET 10 NODE 00 SEQ 08 LEN 05
10/25/04 9:24:54 PM LynX-10 PLC TX: Received an X10 command success
10/25/04 9:24:54 PM LynX-10 PLC RX: X10 PACKET: 01
10/25/04 9:24:54 PM LynX-10 PLC RX: LynX-NET packet = NET 10 NODE 00 SEQ 07 LEN 01
10/25/04 9:24:54 PM LynX-10 PLC TX: Added an outbound event to the queue: P 4

[firtha]

More stuff I have learned...

<UL TYPE=SQUARE><LI>When you define a device to be controlled in an event, then change the device, you have to go back to the event and redefine what you want the device to do. (At least in certain circumstances). For example, I had several X10 lamp modules defined for testing, setting them in an event to a certain dim level, with bright first. I then changed them to Leviton 'modules' (or switches). The event kept sending the old X10 dim, but did not sent the bright first. (Some devices did nothing at all!) When I opened the 'device action' menu in the script, the 'bright first' box was greyed out, but checked. Clicking on one of the radio buttons (absolute or relative), fixed the 'bright first'. Then when the script is executed, it sends the proper Leviton (extended) dim commands. I haven't investigated the interactions fully, as you can see, but suffice it to say that when you change the type of a device, weird things can happen in an event.

<LI>The log events from Ultra Log are (of course) sorted by time, but events happening at the same time are in random order! (Makes sense when you think about it... same thing happens at work with SQL to Oracle). Hence my confusion with Brian's logs. Maybe we can all make a mental note to send log snippets from ah.log instead...

<LI>When multiple Leviton devices are dimmed with Smart Group turned on, HS does indeed send extended dims with multiple unit codes. The lynx10 can only do extended commands for one address at a time, hence the errors reported by the Lynx-10 with Brian's event and devices. (The original plugin the Michael wrote must have taken care of this, and I accidentally messed it up; that's the only explanation I have as to why this didn't show up as a problem before). I've fixed this in the next Rev of the plugin.[/list]

I'm still looking at the thermostat problems... when I add 'ACK MODE' to my thermostat script, the plugin behaves OK except that it sets the setpoint to 5 degrees (C). Without the ACK MODE, it works OK for me. So, I can't duplicate Brian's problem exactly, but at least I have something to work on...

[UniKyrn]

The thermostat problem appears timing related to some extent since I don't get the error when logging is enabled. My HS machine is an old 450Mhz K6 box, and it's doing other things also.

Personally, I'm just happy we're finally getting some progress towards fixing the bugs in this thing. Thanks for your efforts.