Moved KVS to separate module with separate test harness. ...

Will test this in isolation first before integrating with Registry

Managed to persist device configuration to registry.kvs

Beginnings of a persistent version of a class is appearing

Test harness for new Registry and KVS in place

Design of persistent registry store improved after a re-think

Pseudo code for KVS written, ready to be coded up

monitor_mihome now works with auto join and switch toggling

Factory method added to MiHomeDevice to generate a join_req for testing

Registry_test all test cases now pass for discovery

Set up test case for the final discovery test. ...

Test not run yet, and code is missing, marked with ####HERE####

Join_ack working on discovery mode autojoin

Most test cases for discovery modes implemented and passing

Auto discovery tested and working with accept

Initial outer testing of 4 discovery modes done ok

Framework of discovery methods in place, ready to TDD

Design for discovery agents done

Can now construct a device class instance from its product_id

Default incoming message callback added to router, for logging/debug

Router unknown message handling callback registration is cleaner

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

This new architecture ensures default message processing always happens

Synthetic receive working in monitor_mihome.py

energenie.loop() written with FSK receiver connected to fsk_router

Router ready to be tied into a loop()

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

legacy.py rewritten to use new device class interface

Tested on Raspberry Pi, all 4 testers still work with new Message()

Improved debug output for testing

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

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

Code now ready for regression testing with new Message() wrappers added

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

Removed all usages of showMessage, alterMessage