You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to ask if anyone has actually tested the set_rotate method in FanMiot. I'm using the FanP10 class with a P18 device as they have the same services definition. As far as I was able to test, everything works as expected except the set_rotate method.
Version information (please complete the following information):
OS: Linux,Windows
python-miio: 0.5.6
Device information:
If the issue is specific to a device:
Model: P10 (I'm using it with P18 but hopefully that should not matter)
Hardware version: esp8266
Firmware version: 2.0.7
To Reproduce
Steps to reproduce the behavior:
try to send set_rotate command for an instance of FanP10 by: fan.set_rotate(MoveDirection("left"))
the device beeps but nothing happens
Expected behavior
device should turn 5°
Console output
If applicable, add console output to help explain your problem.
If the issue is about communication with a specific device, consider including the output using the --debug flag.
The text was updated successfully, but these errors were encountered:
Describe the bug
I wanted to ask if anyone has actually tested the
set_rotate
method inFanMiot
. I'm using theFanP10
class with a P18 device as they have the same services definition. As far as I was able to test, everything works as expected except the set_rotate method.This is the message that is being sent:
This is what I think should've been sent (it works):
the urn file for both p10 and p18 says value should be uint8 (if I understant that correctly)
Version information (please complete the following information):
Device information:
If the issue is specific to a device:
To Reproduce
Steps to reproduce the behavior:
fan.set_rotate(MoveDirection("left"))
Expected behavior
device should turn 5°
Console output
If applicable, add console output to help explain your problem.
If the issue is about communication with a specific device, consider including the output using the
--debug
flag.The text was updated successfully, but these errors were encountered: