setup_tool tested in simulation and works OK

setup_tool now written, ready to start testing

About half of the setup tool is written and roughly working

Devices_test is now a unittest

Most of Registry_test completed. ...

Just need to write code that passes the 'rx routes created' test

Managed to persist device configuration to registry.kvs

monitor_mihome now works with auto join and switch toggling

Factory method added to MiHomeDevice to generate a join_req for testing

Join_ack working on discovery mode autojoin

Auto discovery tested and working with accept

Can now construct a device class instance from its product_id

Neater callback mechanism for device class instances to use. ...

This new architecture ensures default message processing always happens

switch.py renamed as control_mihome.py, rewritten for new OO interface

legacy.py rewritten to use new device class interface

Ran all test cases again (no hardware), fixed a few issues. ...

Need to still run this up on the hardware to test properly

Refactored usages of raw message to use Message() ...

Removed all usages of showMessage, alterMessage

Marked with ##HERE markers the refactoring required for new Message() ...

Disabled alterMessage showMessage and createMessage to force this issue

Started to think through a better message abstraction

Improved separation of test harness messages

Moved test harnesses into separate _test.py modules

More representative synthetic data added to FSK receive test

Poked a synthetic switch on message down the MIHO005 receive pipeline

Started to flesh out the MiHome receive pipeline

Spec'ed interface for OOK decoder

Deprecated Messages due to import race with Devices. ...

Template messages (which are cloned with create_message) now in Devices.

Commissioned a tx path for MiHome adaptor Plus. ...

This is a temporary path, but it generates the correct message

LegacyDevice tx path commissioned end to end

Most of the OnAir interface coded or spec'ed now

More design on the tx/rx and air_interface pipeline

Renamed encoder as TwoBit, as it encodes two bits per byte. ...

This is the encoding protocol used with legacy OOK devices