Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"No characteristic was found" error #1

Closed
dnicolson opened this issue Feb 9, 2020 · 2 comments
Closed

"No characteristic was found" error #1

dnicolson opened this issue Feb 9, 2020 · 2 comments

Comments

@dnicolson
Copy link
Contributor

When communicating with a SwitchBot device I received a characteristic error, I was able to successfully communicate with it by removing the device UUID check:
https://github.com/futomi/node-switchbot/blob/202044a6c48fa5149c5d25a3adba1ec14b20c1ac/lib/switchbot-device.js#L190

I'm wondering if it's necessary to check for the _CHAR_UUID_DEVICE value:
https://github.com/futomi/node-switchbot/blob/202044a6c48fa5149c5d25a3adba1ec14b20c1ac/lib/switchbot-device.js#L27

As when I query discoverAllServicesAndCharacteristics on the peripheral, I don't get 2a00 but get the following UUIDs:

fec8
fec7
fec9
cba20003224d11e69fb80002a5d5c51b
cba20002224d11e69fb80002a5d5c51b
@futomi
Copy link
Collaborator

futomi commented Feb 10, 2020

I got the following UUIDs from my Bot:

2a00
2a01
2a04
fec8
fec7
fec9
cba20003224d11e69fb80002a5d5c51b
cba20002224d11e69fb80002a5d5c51b

It seems that there is a model which does not support 0x2a00. I wonder there are differences depending on when it is manufactured or which country it is sold...

Anyway, I updated this module so that the 0x2a00 is optional. Try the latest version of this module (v0.0.3). You can use the npm to install the latest version.

Thank you.

@dnicolson
Copy link
Contributor Author

Thanks for the quick fix, it works now.

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

No branches or pull requests

2 participants