Testing this with Solix F3800 Plus

[mboisson]

I am testing this with the Anker Solix F3800 Plus, and I don't get much information. I am not sure how to get it working or how to help. Here is an extract of the logs:

DEBUG:SolixBLE:Initializing Solix device 'Anker SOLIX F3800 Plus' withaddress 'F4:9D:8A:81:07:D0' and details '{'path': '/org/bluez/hci0/dev_F4_9D_8A_81_07_D0', 'props': {'Address': 'F4:9D:8A:81:07:D0', 'AddressType': 'public', 'Name': 'Anker SOLIX F3800 Plus', 'Alias': 'Anker SOLIX F3800 Plus', 'Paired': False, 'Trusted': False, 'Blocked': False, 'LegacyPairing': False, 'RSSI': -59, 'Connected': False, 'UUIDs': ['00001800-0000-1000-8000-00805f9b34fb', '00001801-0000-1000-8000-00805f9b34fb', '8c850001-0302-41c5-b46e-cf057c562025'], 'Adapter': '/org/bluez/hci0', 'ManufacturerData': {65535: b'\x01\xf4\x9d\x8a\x81\x07\xd0\x02\xb1\x12T27\x04'}, 'TxPower': 6, 'ServicesResolved': False}}'
DEBUG:SolixBLE:Connecting to 'Anker SOLIX F3800 Plus' with address 'F4:9D:8A:81:07:D0'...
DEBUG:SolixBLE:Connected to 'Anker SOLIX F3800 Plus'
DEBUG:SolixBLE:ID: 14 Service: 8c850001-0302-41c5-b46e-cf057c562025 (Handle: 14): Unknown, description: Unknown
DEBUG:SolixBLE:Characteristic: 8c850002-0302-41c5-b46e-cf057c562025 (Handle: 15): Unknown, description: Unknown, descriptors: []
DEBUG:SolixBLE:Characteristic: 8c850003-0302-41c5-b46e-cf057c562025 (Handle: 17): Unknown, description: Unknown, descriptors: [<bleak.backends.descriptor.BleakGATTDescriptor object at 0x7fbbb502fd50>]
DEBUG:SolixBLE:ID: 6 Service: 00001801-0000-1000-8000-00805f9b34fb (Handle: 6): Generic Attribute Profile, description: Generic Attribute Profile
DEBUG:SolixBLE:Characteristic: 00002b29-0000-1000-8000-00805f9b34fb (Handle: 12): Client Supported Features, description: Client Supported Features, descriptors: []
DEBUG:SolixBLE:Characteristic: 00002a05-0000-1000-8000-00805f9b34fb (Handle: 7): Service Changed, description: Service Changed, descriptors: [<bleak.backends.descriptor.BleakGATTDescriptor object at 0x7fbbb502fad0>]
DEBUG:SolixBLE:Characteristic: 00002b3a-0000-1000-8000-00805f9b34fb (Handle: 10): Server Supported Features, description: Server Supported Features, descriptors: []
DEBUG:SolixBLE:Unexpected disconnect from 'BleakClient, F4:9D:8A:81:07:D0'.
DEBUG:SolixBLE:Connecting to 'Anker SOLIX F3800 Plus' with address 'F4:9D:8A:81:07:D0'...
DEBUG:SolixBLE:Connected to 'Anker SOLIX F3800 Plus'
DEBUG:SolixBLE:ID: 14 Service: 8c850001-0302-41c5-b46e-cf057c562025 (Handle: 14): Unknown, description: Unknown
DEBUG:SolixBLE:Characteristic: 8c850002-0302-41c5-b46e-cf057c562025 (Handle: 15): Unknown, description: Unknown, descriptors: []
DEBUG:SolixBLE:Characteristic: 8c850003-0302-41c5-b46e-cf057c562025 (Handle: 17): Unknown, description: Unknown, descriptors: [<bleak.backends.descriptor.BleakGATTDescriptor object at 0x7fbbb502fd50>]
DEBUG:SolixBLE:ID: 6 Service: 00001801-0000-1000-8000-00805f9b34fb (Handle: 6): Generic Attribute Profile, description: Generic Attribute Profile
DEBUG:SolixBLE:Characteristic: 00002b29-0000-1000-8000-00805f9b34fb (Handle: 12): Client Supported Features, description: Client Supported Features, descriptors: []
DEBUG:SolixBLE:Characteristic: 00002a05-0000-1000-8000-00805f9b34fb (Handle: 7): Service Changed, description: Service Changed, descriptors: [<bleak.backends.descriptor.BleakGATTDescriptor object at 0x7fbbb502fad0>]
DEBUG:SolixBLE:Characteristic: 00002b3a-0000-1000-8000-00805f9b34fb (Handle: 10): Server Supported Features, description: Server Supported Features, descriptors: []
DEBUG:SolixBLE:Successfully re-connected to 'Anker SOLIX F3800 Plus'

Note that I had to change the UUID_IDENTIFIER in the SolixBLE.py:

+# solix f3800 plus
+UUID_IDENTIFIER = "00001800-0000-1000-8000-00805f9b34fb"
+UUID_IDENTIFIER = "8c850001-0302-41c5-b46e-cf057c562025"

both of those seem to work, but the original 0000ff09-0000-1000-8000-00805f9b34fb does not.

[mboisson]

Strangely enough, I am getting

{
   "Address":"F4:9D:8A:81:07:D0",
   "AddressType":"public",
   "Name":"Anker SOLIX F3800 Plus",
   "Alias":"Anker SOLIX F3800 Plus",
   "Paired":false,
   "Trusted":false,
   "Blocked":false,
   "LegacyPairing":false,
   "RSSI":-59,
   "Connected":false,
   "UUIDs":[
      "0000ff09-0000-1000-8000-00805f9b34fb"
   ],
   "Adapter":"/org/bluez/hci0",
   "ManufacturerData":{
      "65535":"b""\\x01\\xf4\\x9d\\x8a\\x81\\x07\\xd0\\x02\\xb1\\x12T27\\x04"
   },
   "TxPower":6,
   "ServicesResolved":false
}

in the DEBUG:bleak.backends.bluezdbus.manager:initial properties:

[mboisson]

Hum... it seems it sometimes shows one uuid, sometimes the other three...

"org.bluez.Device1":{
   "Address":"F4:9D:8A:81:07:D0",
   "AddressType":"public",
   "Name":"Anker SOLIX F3800 Plus",
   "Alias":"Anker SOLIX F3800 Plus",
   "Paired":false,
   "Trusted":false,
   "Blocked":false,
   "LegacyPairing":false,
   "RSSI":-59,
   "Connected":false,
   "UUIDs":[
      "00001800-0000-1000-8000-00805f9b34fb",
      "00001801-0000-1000-8000-00805f9b34fb",
      "8c850001-0302-41c5-b46e-cf057c562025"
   ],
   "Adapter":"/org/bluez/hci0",
   "ManufacturerData":{
      "65535":"b""\\x01\\xf4\\x9d\\x8a\\x81\\x07\\xd0\\x02\\xb1\\x12T27\\x04"
   },
   "TxPower":6,
   "ServicesResolved":false
},

[mboisson]

I think it managed to connect... but I don't know what it's supposed to show...

AdvertisementData(local_name='Anker SOLIX F3800 Plus', manufacturer_data={65535: b'\x01\xf4\x9d\x8a\x81\x07\xd0\x02\xb1\x12T27\x04'}, service_uuids=['00001800-0000-1000-8000-00805f9b34fb', '00001801-0000-1000-8000-00805f9b34fb', '8c850001-0302-41c5-b46e-cf057c562025'], tx_power=6, rssi=-59)
F4:9D:8A:81:07:D0: Anker SOLIX F3800 Plus
INFO:SolixBLE:Initializing Solix device 'Anker SOLIX F3800 Plus' withaddress 'F4:9D:8A:81:07:D0' and details '{'path': '/org/bluez/hci0/dev_F4_9D_8A_81_07_D0', 'props': {'Address': 'F4:9D:8A:81:07:D0', 'AddressType': 'public', 'Name': 'Anker SOLIX F3800 Plus', 'Alias': 'Anker SOLIX F3800 Plus', 'Paired': False, 'Trusted': False, 'Blocked': False, 'LegacyPairing': False, 'RSSI': -59, 'Connected': False, 'UUIDs': ['00001800-0000-1000-8000-00805f9b34fb', '00001801-0000-1000-8000-00805f9b34fb', '8c850001-0302-41c5-b46e-cf057c562025'], 'Adapter': '/org/bluez/hci0', 'ManufacturerData': {65535: b'\x01\xf4\x9d\x8a\x81\x07\xd0\x02\xb1\x12T27\x04'}, 'TxPower': 6, 'ServicesResolved': False}}'
initialized
INFO:SolixBLE:Connecting to 'Anker SOLIX F3800 Plus' with address 'F4:9D:8A:81:07:D0'...
INFO:SolixBLE:Connected to 'Anker SOLIX F3800 Plus'
INFO:SolixBLE:ID: 6 Service: 00001801-0000-1000-8000-00805f9b34fb (Handle: 6): Generic Attribute Profile, description: Generic Attribute Profile
INFO:SolixBLE:Characteristic: 00002b29-0000-1000-8000-00805f9b34fb (Handle: 12): Client Supported Features, description: Client Supported Features, descriptors: []
INFO:SolixBLE:Characteristic: 00002a05-0000-1000-8000-00805f9b34fb (Handle: 7): Service Changed, description: Service Changed, descriptors: [<bleak.backends.descriptor.BleakGATTDescriptor object at 0x7f64ebc56850>]
INFO:SolixBLE:Characteristic: 00002b3a-0000-1000-8000-00805f9b34fb (Handle: 10): Server Supported Features, description: Server Supported Features, descriptors: []
INFO:SolixBLE:ID: 14 Service: 8c850001-0302-41c5-b46e-cf057c562025 (Handle: 14): Unknown, description: Unknown
INFO:SolixBLE:Characteristic: 8c850002-0302-41c5-b46e-cf057c562025 (Handle: 15): Unknown, description: Unknown, descriptors: []
INFO:SolixBLE:Characteristic: 8c850003-0302-41c5-b46e-cf057c562025 (Handle: 17): Unknown, description: Unknown, descriptors: [<bleak.backends.descriptor.BleakGATTDescriptor object at 0x7f64ebc569d0>]
connected

and then it keeps disconnecting and reconnecting, and showing the same thing

[mboisson]

After seeing my iPhone seemed to actually pair with the Solix, I decided to try adding pairing code in the connect function:

                _LOGGER.info("pairing")
                try:
                    await self._client.pair()
                except BleakError as e:
                    _LOGGER.error(f"Error pairing '{self.name}'. E: '{e}'")

but I got:

INFO:SolixBLE:pairing
ERROR:SolixBLE:Error pairing 'Anker SOLIX F3800 Plus'. E: '[org.bluez.Error.AuthenticationFailed] Authentication Failed'
INFO:SolixBLE:Connected to 'Anker SOLIX F3800 Plus'

[thomluther]

Hello
I started to look into the BT stuff as well, but found it difficult to establish the required platform for proper testing.
I use Windows WSL2 together with Home Assistant Visual Studio Code development container.
From what I found in the web, it seems WSL2 does not support Bluetooth out of the box and needs a customized compiled kernel that includes the BT drivers/stack. That would be the minimum before the host BT dongle could be passed and used by the VSC docker container.

I wonder if any of you has a similar setup and any hints how to get BT dongle working under WSL2 docker container?
Optionally I would need to use VSC direcly in Windows to have immediate access to the BT device? But that would it make difficult to develop HA integration if that will be the ultimate goal, so the devices could be recognized by the HA BT integration...

[sd8rdb]

Hello I started to look into the BT stuff as well, but found it difficult to establish the required platform for proper testing. I use Windows WSL2 together with Home Assistant Visual Studio Code development container. From what I found in the web, it seems WSL2 does not support Bluetooth out of the box and needs a customized compiled kernel that includes the BT drivers/stack. That would be the minimum before the host BT dongle could be passed and used by the VSC docker container.

I wonder if any of you has a similar setup and any hints how to get BT dongle working under WSL2 docker container? Optionally I would need to use VSC direcly in Windows to have immediate access to the BT device? But that would it make difficult to develop HA integration if that will be the ultimate goal, so the devices could be recognized by the HA BT integration...

The only way I see is If you run the HA VS Code devcontainer directly from Docker Desktop on Windows, you can:
• Use your Bluetooth dongle directly (Windows supports it natively).
• Map the USB device to the Docker container using --device or via Docker Desktop’s USB passthrough (experimental).
• Develop your HA integration there with full access to the Bluetooth stack.

[thomluther]

Further investigation on my side with Solarbank Gen1 showed that it completely disabled BT while connected via WiFi. No BT Scanner was able to find the device and there is no option in the App to enable BT on purpose.
So BT is no option for my Solarbank if not working in parallel with WiFi.

[gitTinker]

Further investigation on my side with Solarbank Gen1 showed that it completely disabled BT while connected via WiFi. No BT Scanner was able to find the device and there is no option in the App to enable BT on purpose. So BT is no option for my Solarbank if not working in parallel with WiFi.

Ditto.
I have two F3800 (original models) connected with the "double power hub".
In order to see BT with my scanner I had to disable my wifi access point and disconnect the power hub.
Once wifi was restored the scanner no longer saw the F3800s.

[thomluther]

Same with my Solarbank, no BT if wifi connected. If you are bothered with the BT communication limitations, it might be worth looking into MQTT capabilities via cloud. With the MQTT monitor tool you can see messages and commands, only the fields have to be described for proper usage with the Api library. More details in this discussion

[flip-dots]

Hi, sorry for not getting back to you sooner, GitHub was not sending me notifcations for some reason.

I have recently upgraded this library so it should be easier to add support for new devices. The behavior you guys are seeing with Bluetooth and WiFi is expected, I get the same with my C300X unit, you can have WiFi or Bluetooth but not both.

The way all this works is there is a GATT service offered by the power station that you can subscribe to once connected and you then recieve some bytes from the power station when sometime changes, what each byte in the message means is different on a per-device basis. If you do not subscribe to the service once you connect to the power station you get kicked off after a short delay. Its possible that these other units use a different address for subscribing to telemetry. I have recently changed the logging so it should show more detail about the services offered once connected, do you still see the same output on the latest version?

[flip-dots]

Hello I started to look into the BT stuff as well, but found it difficult to establish the required platform for proper testing. I use Windows WSL2 together with Home Assistant Visual Studio Code development container. From what I found in the web, it seems WSL2 does not support Bluetooth out of the box and needs a customized compiled kernel that includes the BT drivers/stack. That would be the minimum before the host BT dongle could be passed and used by the VSC docker container.

I wonder if any of you has a similar setup and any hints how to get BT dongle working under WSL2 docker container? Optionally I would need to use VSC direcly in Windows to have immediate access to the BT device? But that would it make difficult to develop HA integration if that will be the ultimate goal, so the devices could be recognized by the HA BT integration...

For testing the standalone library pretty much anything should work as long as it has Bluetooth. I have been using a mac mini and it works fine, and I think I tested it on Linux as well, but Windows (not WSL) should probably work as well.

In terms of testing the Home Assistant intergration that uses this library I use a Bluetooth proxy (ESP32), trying to pass through a Bluetooth adapder is simply not worth the headache.

[mboisson]

Thanks for the update @flip-dots. With the holidays coming, I should have time to test again and hopefully make this work for the F3800 Plus. I really would rather get the Bluetooth working than MQTT, as I like not to rely on the Internet.

[flip-dots]

In later firmware versions Anker requires an encrypted handshake in order for it to send telemetry, I have an experimental branch/PR (#7) which implements that. If you use that experimental version you should be able to run the device as a generic device and that should help you map out what values correspond to what and then you can either send me a nice table so I can add support or make a PR with the device added. See #8 for an example of what that looks like.