Closed crookedstorm closed 2 years ago
Tried popping the battery out of the sensor for a bit and I got back to:
discovered a4c138476b53 a4c138476b53 a4:c1:38:47:6b:53 disconnected -28
invalid peripheral, manufacturerData=[undefined]
This doesn't really seem like progress, but I thought I would report it if that's interesting. Edit: It goes back to the usual after doing that for a bit, which is likely somewhat expected.
discovered a4c138476b53 a4c138476b53 a4:c1:38:47:6b:53 disconnected -31
a4c138476b53: 88ec002d08de0e6402
discovered a4c138476b53 a4c138476b53 a4:c1:38:47:6b:53 disconnected -31
a4c138476b53: 88ec002d08de0e6402
discovered a4c138476b53 a4c138476b53 a4:c1:38:47:6b:53 disconnected -31
a4c138476b53: 88ec002d08de0e6402
discovered a4c138476b53 a4c138476b53 a4:c1:38:47:6b:53 disconnected -31
a4c138476b53: 88ec002d08de0e6402
discovered a4c138476b53 a4c138476b53 a4:c1:38:47:6b:53 disconnected -31
a4c138476b53: 88ec002d08de0e6402
Ok, actually, I see the values now. It's working, but it is doing the disconnecting and possible stale values thing I see in #40, which I see closed as a possible dupe of #19. I'll close this for now pending resolution of that other thing. Thanks!
Describe Your Problem:
New H5074 tested to be working with the official app doesn't get picked up by this plugin. It seems to be complaining about vendor info. I'd be happy to figure out some hack with udev or whatever, but I'm pretty new to BLE. I did notice that the MAC vendor portion is different than what was in the issue that lead to initial support, but it is typical for recent Govee stuff, so nothing terribly strange except the "undefined" manufacturer data in debug mode?
Logs:
in debug mode earlier I was also getting:
But that's not what I see now.
Plugin Config:
Screenshots: None right now. The logs are all that show up in debug mode.
Environment:
From the Govee app when I had it installed for testing: