Anker Prime 250w Charger - status unvailable

[Trufax]

Hi,

used the latest alpha v3.4.0-rc1 to test the Anker Prime 250w Charger.

It gets discovered via BT just fine, and i can add it:

i select the model and it gets added (i dont need to press any button on the Charger, it does not ask for any paring confirmation or anything):

Once its added all data stays "unvailable":

i removed and added multiple times, no difference. I also reinstalled the addon. BT data via App works fine (ofc not in parallel) so i remove in the Anker app first before adding in HA.

This Device shows a BT symbol on the top left so its thinks it is connected.

[Trufax]

Ah i see now this is related: #18

[martinpelant]

Same issue on my 160w

[flip-dots]

@Trufax @martinpelant are you able to provide debug logs?

Its possible that there is something wrong with my implementation of the communication protocol that means it only works with my specific 160w charger, if that is the case then will either of you be able to follow the app decoding steps in the documentation and post the logs? It's a tad fiddly but necessary to capture the exact handshake between a device and the app and having an example of a successful connection helps to figure out what is wrong with the current version.

[martinpelant]

This shows some errors:
https://gist.github.com/martinpelant/e4bb0d20c961895da152811ce548d111

Eventually got it working after series of disabling & reenabling the integration (which took forever to load) but haven't tried rebooting my HA to see if it recovers automatically. Worth noting that I use exclusively BT proxy

[flip-dots]

This shows some errors: https://gist.github.com/martinpelant/e4bb0d20c961895da152811ce548d111

Eventually got it working after series of disabling & reenabling the integration (which took forever to load) but haven't tried rebooting my HA to see if it recovers automatically. Worth noting that I use exclusively BT proxy

Are you running an older firmware? Your unit appears to be transmitting some data unencrypted and using a different command ID which is a bit strange. My unit is on v1.6.0.6.

[martinpelant]

I'm on 1.6.0.6 too

[martinpelant]

(just disabled to be able to connect from phone and now when I try to reenable I get the same errors) only on like 6th retry it finally initialized https://gist.github.com/martinpelant/cfc674564ee5678e7b9c34488d0e5685

[martinpelant]

more logs with filter on the device MAC: https://gist.github.com/martinpelant/c4318619fb72884eab85c91a90750bb8

[flip-dots]

If you install the latest push of the branch build #18 does it work?

I have modified the SolixBLE library to support reading unencrypted telemetry using the data from your logs and the tests I wrote for it pass, so with any luck it should work.

[martinpelant]

Just installed, rebooted HA and it connected successfully