set_motion_detection docstring and argument name

[FoamyGuy]

Changing the name of this argument to be more descriptive and adding docstring syntax to make it appear nice in docs pages. Also more specifically suggest boolean for type instead of 0 and 1.

I didn't know these were this interchangeable but tested like this and it appears either should work the same:

>>> bytes([0x01, True])
b'\x01\x01'
>>> bytes([0x01, False])
b'\x01\x00'
>>> bytes([0x01, 0])
b'\x01\x00'
>>> bytes([0x01, 1])
b'\x01\x01'

[tekktrik]

Thanks for this! Yeah, I actually think True and False are instances of int which is suuuuuper nice for things like this!

This is technically breaking. To that end, that could almost become a property with a getter and setter for motion_detect. Not sure why a method was chosen, but I also don't know the device that well, so maybe it makes more sense in practice?

[FoamyGuy]

I will bump the major version and explain the breaking change to argument name in release notes.

I do agree it could be made a property, which may be more inline with the code style guidelines (though I'd have to double check). IIRC this was contributed by a community member so they may have just gone with functions if that is what they were familiar / comfortable with.