Spec'ed out work required to add the new devices

working notes file device_classes_branch.txt moved over to an issue

Reviewed TODO list from the device_classes branch ...

The remaining items will be moved to an issue for later mop up

New tests documented. ...

All tests done and pass

All test cases now run fine. ...

There is no capture/compare at the moment, so verification is manual

Rationalised all comment styles. ...

The double hash (##) is reserved for commented out lines of code.
The single hash (#) is reserved for normal comments.

Moved setup code from global scope of Registry to energenie.init() ...

This makes it possible to use the registry in test cases

auto variable create example added. ...

Tested in simulation, seems to work, but need to re-test on hardware

setup_tool tested in simulation and works OK

setup_tool now written, ready to start testing

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

Receive counter implemented and tested

All registry tests now pass. ...

Requirements list reviewed.
TODO list updated for next steps

Just the route creator to test now

KVS all test cases pass

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

Join_ack working on discovery mode autojoin

Most test cases for discovery modes implemented and passing

Auto discovery tested and working with accept

Reviewed discovery user requirements, updated todo list

Design for discovery agents done

Updated plan for next steps

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