Closed aicarmic closed 3 years ago
The short answer is "I have no idea". The slightly longer answer is just speculation. You mention that it's a "Gen 2" so that makes me wonder if they've changed what GATT profile it's responding to or have changed the sensor indexes or something.
Looks like they do have different code for an "Airthings Wave Plus": https://github.com/Airthings/waveplus-reader/blob/master/read_waveplus.py
When I get some more time, I can compare and see how they're different and perhaps mod this code. But since I don't have a device to test it with, I'll be shooting in the dark.
...unless you're feeling adventurous...
Thanks @hpeyerl for the reply and pointers – I was suspecting something similar but wasn't sure if this project had been tested against a Wave gen 2 yet.
I will do some more debugging tonight and see if I can pin down what's changed with the gen2. Airthings themselves have a separate read script for the gen2 devices, so that's another hint. Will reply back or suggest a PR if I figure it out!
@hpeyerl you were correct, they significantly changed the bluetooth stack on wave2 models. I was able to put together a project that does functionally the same thing, but for wave2
s. Thanks for the inspiration!
Firstly, thanks for this project. Hoping to publish the readings from my Wave 2 to my Home Assistant over MQTT. Unfortunately I've been unable to get this working with my Wave (gen 2).
find_wave2.py
works and I am able to pick up my Wave's mac/serial, so I know the bluetooth stack is up and running on my RPi3. Any ideas what might be causing this? All dependencies are installed and up-to-date. Output below: