12th Day of Christmas goodbye HS, unless

[Pete]

I am left wondering if anyone else has ever seen anything like this...

Will check here Mark.

Historically would dim the windows candles using x10 lighting modules and everything else uses appliance modules.

Today using the HS3 CM11A to monitor the X10 powerline stuff more than for trigger Christmas lighting events.

The Omnipro is doing the X10 stuff via the dual phased TW-523 emulator. The homeseer boxes are talking to CM11A's and TW-523's via Ocelot.

Will shift over triggers from the OP2-TW523 stuff over to using HS3 - CM11A stuff to dimming the windows candles numbering around 20 on current schedule.

The candle bulbs are all 4 watt incandescent. (tried using LED warm white bulbs a couple of years back and it was low on the WAF).

[mfisher]

Gordon, I'm glad that v.45 of the X10 plugin appears to be stable and working for you. Is this version also causing HS3 to crawl at 15 to 20 minutes for every command (event)?

I was under the impression that HS3 z-wave was waiting for HS X10 to complete successfully before seending.

I'm really not sure what you mean by this. As I stated in my last post the X10 plugin simply accepts commands from HS3 and processes the transmission/reception of data over the power line in the background. The plugin does not hold-up HS3 or any other plugins while it is handling X10 data transfers, and to my knowledge other plugins do not wait for the X10 plugin to finish processing a command. The Zwave plugin operates completely independent of the X10 plugin and there should be no interaction between them, and in fact I saw Zwave events being triggered in the midst of the X10 details provided in your log (which I removed from the dissection for clarity).



This leads me to ask that you please clarify what you originally said:

Homeseer is taking approx 15 to 20minutes to process commands. Found the problem The X10 plugin, disable it all works instantly. Is there an alternative plugin that can control X10?

Is it really taking 15 to 20 minutes for HS3 to process every command (event)? Is this intermittent or does it happen for every single action HS tries to take? I saw no evidence of this in the log you provided as events other than X10 appeared to be happening on the order of seconds. Since the log snip you provided showed a timespan of only 5 min 28 secs we would not be able to see those delays.

Will you please elaborate on the problem with details of what is supposed to happen, what actually happens and the HS3 events involved?

Also, what is your CPU loading like when the X10 plugin is enabled vs when it is disabled?

[mfisher]

I am left wondering if anyone else has ever seen anything like this...

Will check here Mark.

Historically would dim the windows candles using x10 lighting modules and everything else uses appliance modules.

Today using the HS3 CM11A to monitor the X10 powerline stuff more than for trigger Christmas lighting events.

The Omnipro is doing the X10 stuff via the dual phased TW-523 emulator. The homeseer boxes are talking to CM11A's and TW-523's via Ocelot.

Will shift over triggers from the OP2-TW523 stuff over to using HS3 - CM11A stuff to dimming the windows candles numbering around 20 on current schedule.

The candle bulbs are all 4 watt incandescent. (tried using LED warm white bulbs a couple of years back and it was low on the WAF).

Thank you Pete! If you could just verify that plugin v.45 does not cause HS3 to act any differently like slowing down the event engine, UI, etc. I'd greatly appreciate it.

From Gordon's log the X10 plugin appears to be operating normally, however my updating to VS2017 may have inadvertently changed one of the 'millions' of settings that could affect how the plugin interoperates with HS, or possibly causing it to hog the CPU...

[Gogs]

or possibly causing it to hog the CPU...

That's the words i was looking for

[Gogs]

Gordon, I'm glad that v.45 of the X10 plugin appears to be stable and working for you. Is this version also causing HS3 to crawl at 15 to 20 minutes for every command (event)?

Apparently not, all is working 100% apart from email, not your problem.

This leads me to ask that you please clarify what you originally said: Is it really taking 15 to 20 minutes for HS3 to process every command (event)? Is this intermittent or does it happen for every single action HS tries to take? I saw no evidence of this in the log you provided as events other than X10 appeared to be happening on the order of seconds. Since the log snip you provided showed a timespan of only 5 min 28 secs we would not be able to see those delays.

Will you please elaborate on the problem with details of what is supposed to happen, what actually happens and the HS3 events involved?

Also, what is your CPU loading like when the X10 plugin is enabled vs when it is disabled?

As for CPU let me come back to you. Regarding time delay, yes that was pretty accurate untill I updated X10 plugin, don't deleate this version from your archive, it is very stable.

Do not know if this is significant, BL Backup started doing only partial backup about the same time, no response from Blade yet!

No idea what has changed apart from possibly a HS3 upgrade.

Just to remind you what is what, and thanks for continued support. I will contact Pete soon regarding getting Linux upand running.

Current Date/Time: 29/12/2017 17:34:49
HomeSeer Version: HS3 Pro Edition 3.0.0.368
Operating System: Microsoft Windows XP Professional - Work Station
System Uptime: 0 Days 22 Hours 38 Minutes 23 Seconds
IP Address: XXX.XXX.X.X
Number of Devices: 613
Number of Events: 249
Available Threads: 400

Enabled Plug-Ins
2.0.47.0: BLBackup
2.0.8.0: BLCpuAdvisor
2.0.5.0: BLGarbage
2.0.6.0: BLPlugins
2.0.131.0: BLRadar
2.0.93.0: BLRF
1.0.3.0: BLShutdown
3.0.0.40: EasyTrigger
3.0.0.25: ImperiHome
3.0.1.109: PHLocation
3.3.5.17921: SMS-Gateway
3.0.6542.35207: UltraWeatherWU3
3.0.0.45: X10
3.0.1.173: Z-Wave

[Gogs]

Dec-29 17:21:08
Event Event Trigger "System House Vacant GF Occupancy" Dec-29 17:19:10 ACTIVE ZONE Living Area LR Occupancy has changed to Active Zone Off, Active Zone On (30 mins, 34 secs) Dec-29 17:19:05 Error Unable to connect to POP server(1) Error: Object reference not set to an instance of an object. Dec-29 17:18:07 ACTIVE ZONE Outside CY Occupancy has changed to Active Zone Off, Active Zone On (2 mins, 58 secs) Dec-29 17:16:07 NO ECHO No Echo for Living Area LR TV Sensor, Echo (1 mins, 20 secs) Dec-29 17:16:06 X10 DEBUG CM11A.SendIt(): Success! 0.796 seconds for CM11a to send. Dec-29 17:16:06 X10 DEBUG CM11A.SendIt(): Got ack of: 0x55 Dec-29 17:16:06 X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line). Dec-29 17:16:06 X10 DEBUG CM11A.SendIt(): Received a good checksum: 0xD9 Dec-29 17:16:06 X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a... Dec-29 17:16:06 X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x6 0xD3 Dec-29 17:16:06 X10 DEBUG CM11A.SendIt(): Success! 0.249 seconds for CM11a to send. Dec-29 17:16:06 X10 DEBUG CM11A.SendIt(): Got ack of: 0x55 Dec-29 17:16:05 NO ECHO No Echo for Outside FD Sensor, Echo (58 secs) Dec-29 17:16:05 X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line). Dec-29 17:16:05 X10 DEBUG CM11A.SendIt(): Received a good checksum: 0xD7 Dec-29 17:16:05 X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a... Dec-29 17:16:05 X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x4 0xD3 Dec-29 17:15:10 ACTIVE ZONE Outside CY Occupancy has changed to Active Zone On, Active Zone Off (20 mins, 30 secs) Dec-29 17:15:08 ECHO Echo for Outside FD Sensor, No Echo (22 mins, 29 secs) Dec-29 17:15:08 Z-Wave Device: Ground Living Area Porch Lamp (18) Set to 30 Dec-29 17:15:08 Device Control Device: Ground Living Area Porch Lamp (18) to Dim 30% (30) Dec-29 17:15:08 Event Event Trigger "Living Room Porch Door Closed" Dec-29 17:15:07 X10 DEBUG CM11A.SendIt(): Success! 0.468 seconds for CM11a to send. Dec-29 17:15:07 X10 DEBUG CM11A.SendIt(): Got ack of: 0x55 Dec-29 17:15:06 X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line). Dec-29 17:15:06 X10 DEBUG CM11A.SendIt(): Received a good checksum: 0xD8 Dec-29 17:15:06 X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a... Dec-29 17:15:06 X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x6 0xD2 Dec-29 17:15:06 X10 DEBUG CM11A.SendIt(): Success! 0.937 seconds for CM11a to send. Dec-29 17:15:06 X10 DEBUG CM11A.SendIt(): Got ack of: 0x55 Dec-29 17:15:06 X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line). Dec-29 17:15:06 X10 DEBUG CM11A.SendIt(): Received a good checksum: 0xD7 Dec-29 17:15:06 X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a... Dec-29 17:15:06 X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x4 0xD3 Dec-29 17:15:06 X10 WARNING 2.343 seconds for CM11A to send data. Possible noise or interference on power line. Dec-29 17:15:06 X10 DEBUG CM11A.SendIt(): Got ack of: 0x55 Dec-29 17:15:06 X10 WARNING Still waiting for CM11a to send data... (2.015 sec) Dec-29 17:15:05 X10 WARNING Still waiting for CM11a to send data... (1.015 sec) Dec-29 17:15:03 X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line). Dec-29 17:15:03 X10 DEBUG CM11A.SendIt(): Received a good checksum: 0x42 Dec-29 17:15:03 X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a... Dec-29 17:15:03 X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x5E 0xE4 Dec-29 17:15:03 X10 DEBUG CM11A.SendIt(): Success! 0.812 seconds for CM11a to send. Dec-29 17:15:03 X10 DEBUG CM11A.SendIt(): Got ack of: 0x55 Dec-29 17:15:03 Event Event Trigger "Movement FD Opened" Dec-29 17:15:03 X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line). Dec-29 17:15:03 X10 DEBUG CM11A.SendIt(): Received a good checksum: 0xEB Dec-29 17:15:03 X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a... Dec-29 17:15:03 X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x4 0xE7 Dec-29 17:15:03 X10 WARNING 5.281 seconds for CM11A to send data. Possible noise or interference on power line. Dec-29 17:15:03 X10 DEBUG CM11A.SendIt(): Got ack of: 0x55 Dec-29 17:15:03 Z-Wave Device: Sensors Living Area Front Door (34) Set to Off/Closed/No Motion Dec-29 17:15:03 X10 WARNING Still waiting for CM11a to send data... (5.015 sec) Dec-29 17:15:02 X10 WARNING Still waiting for CM11a to send data... (4.031 sec) Dec-29 17:15:01 X10 WARNING Still waiting for CM11a to send data... (3.015 sec) Dec-29 17:15:00 X10 WARNING Still waiting for CM11a to send data... (2.031 sec) Dec-29 17:14:59 X10 WARNING Still waiting for CM11a to send data... (1.015 sec) Dec-29 17:14:58 X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line). Dec-29 17:14:58 X10 DEBUG CM11A.SendIt(): Received a good checksum: 0x9B Dec-29 17:14:58 X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a... Dec-29 17:14:58 X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0xB6 0xE5 Dec-29 17:14:58 X10 DEBUG CM11A.SendIt(): Success! 0.343 seconds for CM11a to send. Dec-29 17:14:58 X10 DEBUG CM11A.SendIt(): Got ack of: 0x55 Dec-29 17:14:57 X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line). Dec-29 17:14:57 X10 DEBUG CM11A.SendIt(): Received a good checksum: 0xEB Dec-29 17:14:57 X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a... Dec-29 17:14:57 X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x4 0xE7 Dec-29 17:14:57 X10 DEBUG CM11A.SendIt(): Success! 0.796 seconds for CM11a to send. Dec-29 17:14:57 X10 DEBUG CM11A.SendIt(): Got ack of: 0x55 Dec-29 17:14:57 X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line). Dec-29 17:14:57 X10 DEBUG CM11A.SendIt(): Received a good checksum: 0xE8 Dec-29 17:14:57 X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a... Dec-29 17:14:57 X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x6 0xE2 Dec-29 17:14:57 X10 DEBUG CM11A.SendIt(): Success! 0.265 seconds for CM11a to send. Dec-29 17:14:57 X10 DEBUG CM11A.SendIt(): Got ack of: 0x55 Dec-29 17:14:56 X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line). Dec-29 17:14:56 X10 DEBUG CM11A.SendIt(): Received a good checksum: 0xE5 Dec-29 17:14:56 X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a... Dec-29 17:14:56 X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x4 0xE1 Dec-29 17:14:56 X10 DEBUG CM11A.SendIt(): Success! 0.718 seconds for CM11a to send. Dec-29 17:14:56 X10 DEBUG CM11A.SendIt(): Got ack of: 0x55 Dec-29 17:14:56 Z-Wave Device: Ground Living Area Porch Lamp (18) Set to 98 Dec-29 17:14:56 X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line). Dec-29 17:14:56 X10 DEBUG CM11A.SendIt(): Received a good checksum: 0xE9 Dec-29 17:14:56 X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a... Dec-29 17:14:56 X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x4 0xE5 Dec-29 17:14:56 X10 DEBUG CM11A.SendIt(): Success! 0.156 second

Latest log entries, all looks good.

[mfisher]

Apparently not, all is working 100% apart from email, not your problem.

As for CPU let me come back to you. Regarding time delay, yes that was pretty accurate untill I updated X10 plugin, don't deleate this version from your archive, it is very stable.

Great! Thanks for letting us know that v.45 is not causing you any problems. No need to provide CPU loading data unless the plugin is causing problems.

Happy New Year!

[Gogs]

Great! Thanks for letting us know that v.45 is not causing you any problems. No need to provide CPU loading data unless the plugin is causing problems.

Happy New Year!

No problems just now, thanks for your help and pointing me to latest update, Have a great 2018

[Pete]

Did some quickie testing with an X10 Lamp module using current V.45 which I just updated to.

[ATTACH]65442[/ATTACH]

OFF

[ATTACH]65435[/ATTACH]

Dec-29 1:48:34 PM X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x4 0x62
Dec-29 1:48:34 PM X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
Dec-29 1:48:34 PM X10 DEBUG CM11A.SendIt(): Received a good checksum: 0x66
Dec-29 1:48:34 PM X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line).
Dec-29 1:48:35 PM X10 DEBUG CM11A.SendIt(): Got ack of: 0x55
Dec-29 1:48:35 PM X10 DEBUG CM11A.SendIt(): Success! 0.394 seconds for CM11a to send.
Dec-29 1:48:35 PM X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x6 0x63
Dec-29 1:48:35 PM X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
Dec-29 1:48:35 PM X10 DEBUG CM11A.SendIt(): Received a good checksum: 0x69
Dec-29 1:48:35 PM X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line).
Dec-29 1:48:35 PM X10 DEBUG CM11A.SendIt(): Got ack of: 0x55
Dec-29 1:48:35 PM X10 DEBUG CM11A.SendIt(): Success! 0.885 seconds for CM11a to send.

ON

[ATTACH]65436[/ATTACH]

Dec-29 2:02:43 PM X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x4 0x62
Dec-29 2:02:43 PM X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
Dec-29 2:02:43 PM X10 DEBUG CM11A.SendIt(): Received a good checksum: 0x66
Dec-29 2:02:43 PM X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line).
Dec-29 2:02:43 PM X10 DEBUG CM11A.SendIt(): Got ack of: 0x55
Dec-29 2:02:43 PM X10 DEBUG CM11A.SendIt(): Success! 0.845 seconds for CM11a to send.
Dec-29 2:02:43 PM X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x6 0x62
Dec-29 2:02:43 PM X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
Dec-29 2:02:43 PM X10 DEBUG CM11A.SendIt(): Received a good checksum: 0x68
Dec-29 2:02:43 PM X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line).
Dec-29 2:02:44 PM X10 DEBUG CM11A.SendIt(): Got ack of: 0x55
Dec-29 2:02:44 PM X10 DEBUG CM11A.SendIt(): Success! 0.33 seconds for CM11a to send.

Brightness 51% via HS3 CM11A

[ATTACH]65437[/ATTACH]

Dec-29 2:05:25 PM X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x4 0x62
Dec-29 2:05:25 PM X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
Dec-29 2:05:25 PM X10 DEBUG CM11A.SendIt(): Received a good checksum: 0x66
Dec-29 2:05:25 PM X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line).
Dec-29 2:05:26 PM X10 DEBUG CM11A.SendIt(): Got ack of: 0x55
Dec-29 2:05:26 PM X10 DEBUG CM11A.SendIt(): Success! 0.101 seconds for CM11a to send.
Dec-29 2:05:26 PM X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0xB6 0x65
Dec-29 2:05:26 PM X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
Dec-29 2:05:26 PM X10 DEBUG CM11A.SendIt(): Received a good checksum: 0x1B
Dec-29 2:05:26 PM X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line).
Dec-29 2:05:27 PM X10 WARNING Still waiting for CM11a to send data... (1.009 sec)
Dec-29 2:05:28 PM X10 WARNING Still waiting for CM11a to send data... (2.014 sec)
Dec-29 2:05:29 PM X10 WARNING Still waiting for CM11a to send data... (3.018 sec)
Dec-29 2:05:30 PM X10 WARNING Still waiting for CM11a to send data... (4.019 sec)
Dec-29 2:05:30 PM X10 DEBUG CM11A.SendIt(): Got ack of: 0x55
Dec-29 2:05:30 PM X10 WARNING 4.256 seconds for CM11A to send data. Possible noise or interference on power line.
Dec-29 2:05:30 PM X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x4 0x62
Dec-29 2:05:30 PM X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
Dec-29 2:05:30 PM X10 DEBUG CM11A.SendIt(): Received a good checksum: 0x66
Dec-29 2:05:30 PM X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line).
Dec-29 2:05:30 PM X10 DEBUG CM11A.SendIt(): Got ack of: 0x55
Dec-29 2:05:30 PM X10 DEBUG CM11A.SendIt(): Success! 0.741 seconds for CM11a to send.
Dec-29 2:05:30 PM X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x5E 0x64
Dec-29 2:05:30 PM X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
Dec-29 2:05:30 PM X10 DEBUG CM11A.SendIt(): Received a good checksum: 0xC2
Dec-29 2:05:30 PM X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line).
Dec-29 2:05:32 PM X10 WARNING Still waiting for CM11a to send data... (1.008 sec)
Dec-29 2:05:32 PM X10 DEBUG CM11A.SendIt(): Got ack of: 0x55
Dec-29 2:05:32 PM X10 WARNING 1.875 seconds for CM11A to send data. Possible noise or interference on power line.

Brightness 17% via HS3 CM11A

[ATTACH]65440[/ATTACH]

Dec-29 2:26:26 PM X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x4 0x62
Dec-29 2:26:26 PM X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
Dec-29 2:26:26 PM X10 DEBUG CM11A.SendIt(): Received a good checksum: 0x66
Dec-29 2:26:26 PM X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line).
Dec-29 2:26:26 PM X10 DEBUG CM11A.SendIt(): Got ack of: 0x55
Dec-29 2:26:26 PM X10 DEBUG CM11A.SendIt(): Success! 0.664 seconds for CM11a to send.
Dec-29 2:26:26 PM X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0xB6 0x65
Dec-29 2:26:26 PM X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
Dec-29 2:26:26 PM X10 DEBUG CM11A.SendIt(): Received a good checksum: 0x1B
Dec-29 2:26:26 PM X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line).
Dec-29 2:26:28 PM X10 WARNING Still waiting for CM11a to send data... (1.004 sec)
Dec-29 2:26:29 PM X10 WARNING Still waiting for CM11a to send data... (2.008 sec)
Dec-29 2:26:30 PM X10 WARNING Still waiting for CM11a to send data... (3.013 sec)
Dec-29 2:26:30 PM X10 DEBUG CM11A.SendIt(): Got ack of: 0x55
Dec-29 2:26:30 PM X10 WARNING 3.824 seconds for CM11A to send data. Possible noise or interference on power line.
Dec-29 2:26:30 PM X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x4 0x62
Dec-29 2:26:30 PM X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
Dec-29 2:26:30 PM X10 DEBUG CM11A.SendIt(): Received a good checksum: 0x66
Dec-29 2:26:30 PM X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line).
Dec-29 2:26:31 PM X10 DEBUG CM11A.SendIt(): Got ack of: 0x55
Dec-29 2:26:31 PM X10 DEBUG CM11A.SendIt(): Success! 0.312 seconds for CM11a to send.
Dec-29 2:26:31 PM X10 DEBUG CM11A.SendIt(): Sending 2 bytes: 0x96 0x64
Dec-29 2:26:31 PM X10 DEBUG CM11A.SendIt(): Data sent, waiting for checksum From CM11a...
Dec-29 2:26:31 PM X10 DEBUG CM11A.SendIt(): Received a good checksum: 0xFA
Dec-29 2:26:31 PM X10 DEBUG CM11A.SendIt(): Send 0x00 to CM11a (command to transmit the data onto the power line).
Dec-29 2:26:32 PM X10 WARNING Still waiting for CM11a to send data... (1 sec)
Dec-29 2:26:33 PM X10 WARNING Still waiting for CM11a to send data... (2.002 sec)
Dec-29 2:26:34 PM X10 WARNING Still waiting for CM11a to send data... (3.005 sec)
Dec-29 2:26:34 PM X10 DEBUG CM11A.SendIt(): Got ack of: 0x55
Dec-29 2:26:34 PM X10 WARNING 3.748 seconds for CM11A to send data. Possible noise or interference on power line.

So here seeing it slower when sending brightness commands versus on and off command.

Did another test using the Leviton PCA program and dimming same unit.
Note here it sends out the command via the Volp dual phased TW-523 device.

Brightness 17% via Leviton OmniPro2 / Volp XTBIIR (dual phased TW-523 emulator)

[ATTACH]65441[/ATTACH]

Dec-29 2:32:11 PM X10 DEBUG CM11A.GetUpload(): Upload byte count: 3
Dec-29 2:32:11 PM X10 DEBUG CM11A.GetUpload(): Upload Data: 0x2 Time: 52331.796
Dec-29 2:32:11 PM X10 DEBUG CM11A.GetUpload(): Upload Data: 0x62 Time: 52331.813
Dec-29 2:32:11 PM X10 DEBUG CM11A.GetUpload(): Upload Data: 0xAA Time: 52331.83

Visually confirmed.

I am not seeing any X10 noise as I have left the old Elk noise meter on line now 24/7.

[concordseer]

Plenty of fresh documentation on how to get HS3 up and running from scratch on Linux. In fact one forum member went into great detail on how to achieve this recently. It's possible to achieve in two hours.

Poor Pete......With all the demands on his time they'll either have to cut him a commission or rename it Homeseer Pete in his honour

[mfisher]

Did some quickie testing with an X10 Lamp module using current V.45 which I just updated to.

......

So here seeing it slower when sending brightness commands versus on and off command.

Thank you for testing this Pete! Glad v.45 is working properly and not causing any issues.

You are absolutely correct, standard Dim and Bright X10 commands take a very long time to transmit over the power line versus On, Off and most of the other commands. Here's why:

Commanding A2 ON sends only 2 data packets onto the power line:
A2 AON
This takes 0.8 seconds at 60Hz (North America) or 0.96 seconds at 50Hz (Europe, Asia)

Commanding A2 Dim 50% (relative dim) sends 12 packets onto the power line:
A2 ADIM ADIM ADIM ADIM ADIM ADIM ADIM ADIM ADIM ADIM ADIM
This takes 2.4 seconds at 60Hz or 2.94 seconds at 50Hz.

Commanding A2 Dim 50% (absolute dim) sends 35 packets onto the power line:
A2 ABRT ABRT ABRT ABRT ABRT ABRT ABRT ABRT ABRT ABRT ABRT ABRT ABRT ABRT ABRT ABRT ABRT ABRT ABRT ABRT ABRT ABRT A2 ADIM ADIM ADIM ADIM ADIM ADIM ADIM ADIM ADIM ADIM ADIM
This takes 6.9 seconds at 60Hz or 8.3 seconds at 50Hz!

This is why I only use modules that support either the Preset Dim or Extended Dim commands as sending those commands take the roughly the same amount of time as sending On and Off commands.

[Archcantor]

I also still use many X10 devices in my HS3 environment including powerline and RF. I have not had any problems using the CM11A X10 interface or the JVDE XTB-232 X10 Serial Powerline Interface whic is a replacement for the CM11a: http://jvde.us/xtb-232.htm

My X10 plugin for the CM11A is 3.0.0.40

If you are experiencing a lot of X10 interference on the powerline you can try to install one or two XTB-ANR Active Noise Reducers
http://jvde.us/xtb-anr.htm

These are devices that monitor the power line and clamp out interference in the X10 signal band. I use these with great success. Many switching power supplies and even LEDs with internal switching power supplies interfere with reliable X10 communications. JVDE designs great products, I don't work for them. I am just a happy customer. -Rick

[Pete]

Thinking that Gogs has the Volp X10 stuff over there across the pond.

The issues relating to powerline and wireless for Gogs probably relate to a home that is a few hundred years old with stone walls as infrastructure.

IE: here my home is typical wood and drywall interior pieces. I can easily pass cables from the basement to the first floor to the second floor to the attic will little work.

It is much more difficult to do this in a stone home that is a few hundred years old.

Thinking for Gogs X10 controllers they are mounted near his fuse panel and using old telephone wire over to his computer. I used to do this in the 1980's and 1990's for X10. Today have my X10 and UPB PIMs adjacent to the fuse panel with their own breakers. Each of these devices have a serial type connection over to Homeseer 3 which is not in the same place or near the fuse panel. These connections were using catxx serial balums. Recently to reduce the footprint have gone to using old conventional telephone wires. They work fine. (CM11A, TW-523, Volp X10 and Volp TW523 stuff).

[Steve Q]

I am still using many x10 devices and for the most they work well. However, I always have issues over the holidays. I am certain these problems are caused by increases in powerline noise due to Christmas decorations and other electronic devices. I consider these issues as minor inconveniences and not worth the effort and cost involved to replace these x10 devices.

I do however have an ongoing problem with dimming my 3 X10 ceiling lights. The behavior of dim/bright is not consistent. The lights will sometimes dim properly to a specified level but often they will dim completely then brighten then repeat that cycle multiple times before reaching the specified level. And sometimes, the light will just turn off. Perhaps this is a powerline noise issue, but I think it could also be something related to how dim/bright commands are being sent by the plugin (ver 45). I never saw this behavior when I was using HS2 for many years.


Sent from my iPad using Tapatalk

[langenet]

I only have one dimmable light switch which I use X-10 dim with. It's in the master bedroom and it is set to come on at 15%, 30% and 99%. It works without issue for me. I would know since it's my wakeup call. So I'm not sure if it's the plugin in your case or noise. I also use the TI103.

Robert