Part 2 of 2
Using a status request in this way does not
guarantee reliability, but it does improve
it. There are basically four scenarios
after sending the command and status
request:
1. You receive the correct status response
(thus you know the status is correct)
2. You receive an incorrect status response
(thus you know the status is not correct)
3. You do not receive status notification
but the module’s status is correct (either
the status request or the status response
were lost)
4. You do not receive status notification
but the module’s status isn’t correct (both
the command and either the status request
or the status response were lost)
In scenario 1 you are happy.
In scenario 2 you will send the command and
status request again and hope it will work
next time. There is a good chance it will
since it did receive the status response
correctly.
To the controller scenario 3 & 4 look the
same. Either way you will send the command
again and hope you will get a response next
time. If you do that is great, but if you
don’t ever receive the correct status, you
are in trouble. In either scenario you
will start flooding the powerline with
commands and status requests and in
scenario 4 you will also be flooding your
grass/garden and maybe even your
basement
.