Before one had to update the list of not-running devices in the tests,
after adding new devices.
This had not been done recently so tests where failing.
Avoid needing to do this by computing the expected-not-running devices
based on the known tests devices and all configured devices

The argument definition a method is only evaluated once,
at module load time, so multiple instances of States()
actually shared instances of .lock and .opener

Caused problems when adding some new tests for States,
probably did not have any ill effects otherwise

This should avoid MQTT messages being spammed continiously in this case
Fixes #14