Hello @Supermarco333, Thanks for this.
Sadly, the 12: device is a programmer, or a thermostat, not a HM80. I see your logs ran for 10 minutes or so? You’ll have to run it for longer, to pick it up.
There is a new version of evohome_rf, so pull the latest commit, and use the bleeding edge branch.
You can start with:
python -O client.py -r listen /dev/ttyUSB0 -o packet.log
…and just run that for a few hours (say 30-120 mins). You can then end evohome_rf via a `Ctrl-C’, and you might see something like:
client.py: Finished evohome_rf, results:
Schema[gateway] = {"main_controller": null, "orphans": ["12:193204", "08:123456"]}
...
Then just look among the orphans for a likely HM80 (e.g. 08:123456 - it may not be an 08:)
-
if you do not find a device that is likely to be a HM80, just re-run the above command, and it will append to the log.
-
if you do find a likely device, say, then execute:
python -O client.py -rr execute /dev/ttyUSB0 -sf 08:123456 -o scan_full.log
The -sf is a full scan (aka --scan-full) - it takes approx 60 seconds to do against a controller, but will likely take a few minutes longer for a HM80.
When the scan is finished, you’ll have to end evohome_rf via a `Ctrl-C’.
Then just send me both logs.
There is no immediate need for this, but if anyone is feeling very adventurous, they can also try:
python -O client.py -rr execute /dev/ttyUSB0 -sh 02:123456 -o scan_hard.log
I’d be particularly interested in the results of hard scans of UFH controllers, which start 02: - this scan will take hours (it used to take 24h, but evohome_rf is much faster now.
Of course, none of the above should cause any issues with your system (but if they do, turning the controller off/on will be sufficient)…
