Design for all setup_tool actions done

setup_tool main menu written and working

Defined requirements for demo apps including setup tool menu

Specified the demos that we want to write as part of the device classes testing

Receive counter implemented and tested

Devices_test is now a unittest

All registry tests now pass. ...

Requirements list reviewed.
TODO list updated for next steps

Just the route creator to test now

Most of Registry_test completed. ...

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

KVS all test cases pass

KVS.DEL() passing tests

Factory creation in ADD is now working

kvs remove functionality working

KVS.remove() test now passes

KVS tested in non persisted mode and works. ...

KVS mostly tested in persisted mode, but more code to write and test

KVS tests for non persistent KVS all pass

Test harness and functionality for KVS defined

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

Design for Registry data store (KVS) done

Thought through next set of demos

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