Sadly, not. That is not available through the API.
Could you try the test version?
If anyone is interested, I have published new code for the ESP32 hub.
This version improves memory usage, adds a few more supported devices and has a redesigned web interface that provides more diagnostics / information.
I installed your latest ino.bin file for the esp32 (3 hours ago uploaded).
I used the OTA method.
When I check the esp by entering the address in a browser I now see version 2.11 and a new layout.
I noticed that you need to update the ESP32 2 times before version 2.11 is active.
I have 2 devices here, one with 2.8, the other with version 2.7.
From 2.8 to 2.11 took 2 update cycles.
From 2.7 to 2.11 was not successfull, so I decided to first use version 2.8 over OTA. From 2.7 to 2.8 went smoothless, to 2.11 is now also successful.
Looks very slick. I updated from 2.9 to 2.11.
With new info comes new questions 
:
I only have one device connected, a Curtain 3 driver. In noted in the âLast 10 Received BLE Commandâ-section of the Homey Registration and Activity page that when I:
- Open the curtains the displayed result is
bad-requestand nothing is shown in the Data field - Close the curtains the result is shown as
completedand the commandâs data is shown in the Data field.
Any idea why the Open action results in a bad-request without data?
Note that the curtain does open when sending that command, and the âLast 10 Push Updatesâ section is updated every few seconds.
That would indicate the command was not received correctly and Homey would fall back to using itâs internal BLE. I will take a look to see why itâs not getting it correctly.
The curtains donât close anymore.
Not even the curtain close to Homey Pro.
The one I activated last you can see in the picture is the curtain which is only addressable by the ESP-hub.
I flashed one ESP32 back to version 2.8 and now both curtains close and open on command (I disconnected the one with 2.11 for this test).
@Andrian, there is something wrong with the 2.11 version.
I think I might have found the issue. It seems the Homey app is sending a floating point number for the position (in my case 15.000000000000002), but the parser is only expecting bytes, so it was treating the packet as corrupted. I will upload another update soon.
New bin files for 2.12 are now in GitHub.
Thanks!
I am trying to update to v2.12, but that does not seem to work.
Normally after selecting the update file and clicking the Update Firmware button, it takes quite some time to compete. Now after approx. 10 seconds the webpage/connection resets (ERR_CONNECTION_RESET > ESP32 restarts I assume) and when I access the ESP32 it is still on v2.11.
I have tried both the RAW download button and the down-arrow download button on GitHub, but get the same result.
Not sure what I am doing wrong. Any idea how to proceed?
Same here. The new file is not updating my device with 2.11 on it.
Expletive, Expletive , Expletive, I broke it. My new web interface doesnât pass through the OTA URLâs.
The bad news it means the next update will have to be done using the Arduino IDE or the Flash loader.
The good news is the next update will fix the OTA going forward. I will let you know when the new binaries are ready.
New binaries are up, V2.14.
Going forward once you have installed this version, the OTA update will have a progress bar during upload and automatically redirect back to the Home page once the update is complete.
Thanks for the quick follow-up! 
Iâll try the new version later today and let you know if it works.
