Requesting Support for New Devices
If you own a device that is not yet supported, you can send us a request to add it, but we do need some data from the device. This page will explain how to obtain this data.
Important
All devices that can connect to the app over bluetooth are theoretically possible to add to this integration, but some of them may need more work than others. This integration does not support all of the available protocols, but it should work with most of the 3rd generation and some 2nd generation devices.
It is possible to add support for more protocols, but it would take too much effort trying to reverse engineer it without owning these devices - main developers of this integration only own a few of the 3rd generation devices.
Starting from version v0.6.0, this integration allows connection to devices that are not yet supported for the purpose of collecting raw packets that we can use for adding support for new devices.
The following sections are steps to get the diagnostics info.
| Step 1 | Step 2 |
Add Integration
|
Select Ecoflow BLE
|
| Step 3 | Step 4 |
|
Click Next. If you have discovered device that you didn't or don't want to add, see the next table otherwise. 
|
Fill in your user id or fill it with the login form and click Submit. Wait until the device connects - there are few different errors you can get, see error section to see how to resolve them.
|
If you have some discovered devices, the form will have one more step that adds discovered devices.
| Step 3 A | Step 3 B |
Select Set up another instance of Ecoflow BLE
|
Select the [Unsupported] device and continue from step 4
|
There are few types of common errors that can occur during connection:
- Device disconnected before it could authenticate - if switching to different packet version does not help, this device uses currently unsupported packet version or different authentication procedure - in this case it has to be reverse engineered.
- Could not connect to the device - connection timed out - device may have turned off, connected to another device or there is a lot of interference - try increasing connection timeout and bring the device closer to the bluetooth adapter
- Device authentication failed - your user ID is most likely incorrect, you may have logged in to a server in a different region - try changing the region. If this does not help, the authentication procedure may have changed and it has to be reverse engineered.
If you successfully added the device, go to the device page and wait until the sensor Collecting diagnostics data changes to done. Packets are stored in a bounded queue so packets are collected even after this sensor changes to done, just the old ones are being overriden. This means that diagnostics data changes in time and this can help with identification of fields. Try to have the device under load and mark what ports are being active when you download the data.
Caution
Some devices may send identifying information about you in the messages such as time zone, serial numbers or in the worst case your full GPS information (i.e. SHP). If you don't want to risk sharing these publicly, you can send it as an email to requests@gnox.dev as an attachment or a single use link to a file using a service such as https://wormhole.app.
NOTE: Starting from v0.6.9, potentially sensitive data is encrypted and only accessible by developers of this integration.
| Step 5 | Step 6 |
Wait until collection sensor changes to done and try to have the device under load on different ports during this timeframe
|
Data is still being collected after sensors changes to done - what matters is the time of downloading. This means that you can for example put different port under load for few seconds and download the data even after collection is done and upload multiple files. Make sure to mark what ports are under load and approximate values - this will really speed up development.
|
| Step 7 |
You can now use button Download diagnostics and create a github issue and upload json(s) there.
|