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
if you input a higher cased Mac address like 00:1A:22:0D:E9:B4 , this will lead the noble-device function discoverWithFilter (in utils.js from the noble-device JS libs) to never match with 00:1a:22:0d:e9:b4 as represented by noble. I suggest you to insert a function to force the letters to be lowerecased before passing it to the different discover functions in order to let the users of the library to have the freedom of Case sensitiveness of the Input.
The text was updated successfully, but these errors were encountered:
Hi, thanks for your positive feedback, unfortunately I have very few coding skills (it took me more than 7 hours to dig in the code and print some debugging infos to find this....) but i ll ask one friend used to JS to have a look together. If he has time , we ll send you a pull request within 2/3 weeks, otherwise I ll inform you in this thread.
Regards.
Hi,
full issue here ont the cool node-red-contrib-eq3-bluetooth project : alikh31/node-red-contrib-eq3-bluetooth#10 (comment)
if you input a higher cased Mac address like 00:1A:22:0D:E9:B4 , this will lead the noble-device function discoverWithFilter (in utils.js from the noble-device JS libs) to never match with 00:1a:22:0d:e9:b4 as represented by noble. I suggest you to insert a function to force the letters to be lowerecased before passing it to the different discover functions in order to let the users of the library to have the freedom of Case sensitiveness of the Input.
The text was updated successfully, but these errors were encountered: