Skip to content

Conversation

@jonnor
Copy link
Owner

@jonnor jonnor commented Jan 12, 2020

Closes #14

Note that one can still get 1 per second when a user actively holds a button down. This should be rare enough to not be disruptive.

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unecessary MQTT messages when door is unlocked

2 participants