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
Everything works fine with the version 0.0.4. After I upgrade pysesameos2 to 0.0.5, I found the device status callback never executed.
I checked the source code, found the setDeviceStatusCallback of CHSesame2 wrongfully executes pass instead of calling the method extended from its parent:
Description - 説明
Everything works fine with the version 0.0.4. After I upgrade pysesameos2 to 0.0.5, I found the device status callback never executed.
I checked the source code, found the
setDeviceStatusCallback
ofCHSesame2
wrongfully executespass
instead of calling the method extended from its parent:pysesameos2/pysesameos2/chsesame2.py
Lines 169 to 177 in c97d1b5
Expected Behavior - 期待する動作
After device status changed, the callback set with
setDeviceStatusCallback
should be executed.Pysesameos2 version (
pip show pysesameos2
)0.0.5
Python version (
python --version
)3.9.2
OS
pi os
BlueZ version (
bluetoothctl -v
) in case of LinuxNo response
How to Reproduce - 再現方法
Just run the example code and try to lock/unlock with mqtt command.
Output - 出力された内容, 具体的な問題内容
No response
The text was updated successfully, but these errors were encountered: