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
Add support for Almendo bluSensor AIQ #29
Conversation
Datasheet for this device: https://www.blusensor.com/zdn/pdf/datasheets/BSP02AIQ%20EN%20datasheet.pdf The parser is based on the documentation available at: https://github.com/blusensor/blusensor-api-bluetooth
A set of example packets captured from this device. Wild values provoked by a glass of tea. |
package/bleparser/almendo.py
Outdated
"co2e": co2e, | ||
"tvoc": tvoc, | ||
"aiq": aiq, | ||
"firmware": "bluSensor V1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"firmware": "bluSensor V1", | |
"type": "bluSensor Mini", | |
"firmware": "Almendo V1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this PR. I have a few comments, please have a look.
Thank you for your feedback! I will address those issues as soon as possible. Regarding the choice of Almendo; the manufacturer specific data tag 0x06E8 is the same value as the company identifier for Almendo Technologies GmbH, the manufacturer of the bluSensor series of products. I believe the use of Almendo is a suitable abstraction level, especially if they should begin using their company identifier when producing yelOwl car alarms or redEring false position tracker tags. https://github.com/blusensor/blusensor-api-bluetooth#official-bluetooth-sig-id |
Ok, let's do the following then "firmware": "Almendo V1",
"type": "bluSensor Mini", I'll update my review comments. |
Thanks, merged |
I made some small changes in #30
|
oh, and changed |
Excellent, thanks! Worth noting could be that although Almendo states CO2 sensing capability, their CO2 value is actually CO2e, based on TVOC level and statistics. Other than that minor note, I have nothing to add. I completely forgot about providing a test, my apologies. |
no problem. Has been released as 3.2.0 |
I noticed that the RSSI value is quite strange in the txt file. The example I used in the test results in an RSSI = 61 (`0x3d). RSSI should be a negative value normally. Could you do some test by keeping the sensor close and far away and report back the values here for both situations? Perhaps we have to multiply with -1? |
Oops, you've found a bug in my translator from the nRF52840 sniffer, which return quite large packets with a lot of extra data, to HCI event packets. Use these instead, they're captured using more traditional methods: 043e26020100000eba64c4f5fc1a02010613ffe806010a0a08011800be0a89129d05fb0404020a09d9 043e26020100000eba64c4f5fc1a02010613ffe806010a0a08011800be0a8b128208860505020a09d5 043e26020100000eba64c4f5fc1a02010613ffe806010a0a08011800be0a8b128208860505020a09d8 043e26020100000eba64c4f5fc1a02010613ffe806010a0a08011800bb0aa3110005ab0304020a09cc 043e26020100000eba64c4f5fc1a02010613ffe806010a0a08011800bb0aa3110005ab0304020a09d6 043e26020100000eba64c4f5fc1a02010613ffe806010a0a08011800bb0aa3110005ab0304020a09d1 043e26020100000eba64c4f5fc1a02010613ffe806010a0a08011800d40aea218687e82605020a09d1 043e26020100000eba64c4f5fc1a02010613ffe806010a0a08011800d40aea218687e82605020a09d6 043e26020100000eba64c4f5fc1a02010613ffe806010a0a08011800180baa259728f90b05020a09d6 043e26020100000eba64c4f5fc1a02010613ffe806010a0a08011800180baa259728f90b05020a09db 043e26020100000eba64c4f5fc1a02010613ffe806010a0a08011800180baa259728f90b05020a09da 043e26020100000eba64c4f5fc1a02010613ffe806010a0a08011800160b1c1c75075e0805020a09d1 043e26020100000eba64c4f5fc1a02010613ffe806010a0a08011800160b1c1c75075e0805020a09cf 043e26020100000eba64c4f5fc1a02010613ffe806010a0a08011800150b7a13ec03c50204020a09d1 043e26020100000eba64c4f5fc1a02010613ffe806010a0a08011800150b7a13ec03c50204020a09d0 043e26020100000eba64c4f5fc1a02010613ffe806010a0a08011800150b7a13ec03c50204020a09cb 043e26020100000eba64c4f5fc1a02010613ffe806010a0a080118000e0bf91130048c0204020a09c7 043e26020100000eba64c4f5fc1a02010613ffe806010a0a080118000e0bf91130048c0204020a09d3 043e26020100000eba64c4f5fc1a02010613ffe806010a0a08011800f90ac7106e05ac0204020a09c4 043e26020100000eba64c4f5fc1a02010613ffe806010a0a08011800f90ac7106e05ac0204020a09bd 043e26020100000eba64c4f5fc1a02010613ffe806010a0a08011800f10a0512e5036b0204020a09c3 043e26020100000eba64c4f5fc1a02010613ffe806010a0a08011800f10a0512e5036b0204020a09c3 |
Datasheet for this device:
https://www.blusensor.com/zdn/pdf/datasheets/BSP02AIQ%20EN%20datasheet.pdf
The parser is based on the documentation available at:
https://github.com/blusensor/blusensor-api-bluetooth