Problem since "Light - x10.py: Improved x10 state monitoring" in 37.0

Configuration
1

Hi all

Exactly since the moment of updating to 37.0 I have had a problem with the Light X10 component. After about fifteen minutes the CM11 becomes unresponsive and the only way I have found to restore functionality so far is to re-boot my Raspberry Pi.

I have tried a number of things to resolve, including replacing the CM11 batteries, making sure heyu engine is starting properly, further upgrading to 37.1, but the aberrant behaviour remains. (I have even updated the yaml for these lights which seems to have subtly changed at some time.) Once the problem kicks in it is also impossible to even send commands from the CLI on the pi.

The release note says that the component was subject to an improvement in the state monitoring - so I’m wondering if, in fact, this has introduced some unanticipated instability?

Given that the component was as reliable as X10 could have allowed it to be, I’ve never experienced problems prior to the specific change.

Anyone any ideas or clues how to approach resolving this or what steps to take next?

2

I also have some issue with heyu. But according to my syslog, it seems some issue with serial port. (NOTE: I have only setup hass (on Pi B+) for less than a week, but I have been using heyu for a long time (like 10 years+) on a different system with the same USB-serial adaptor) To fix it, I didn’t reboot but instead I did heyu restart (which will restart they heyu_relay & heyu_engine). Then I am able to access again. hass uses heyu engine but I had problem with it in the past so I never use the engine but just the heyu relay, not sure that is the problem or not.

Will monitor the heyu and continue using it. I am trying to continue my X10 investment but at some point, I may have to drop them