Sorry for the delay in my response.
Power states in Edison are not officially implemented, there are some workarounds to access Edison's power states. Nevertheless they might cause unexpected behaviors with other functionalities of the board, therefore, they are not recommended.
In case you are still interested, accessing these power states has been discussed in threads, like:
You can try accessing this power state to check if the BLE advertisements work when on that state. You could also try disabling Wi-Fi if it’s not used and enable power management of the serial port, this would decrease power consumption, to do so you might need to run the following commands:
echo auto > /sys/devices/pci0000\:00/0000\:00\:04.3/power/control
systemctl start connman
I hope this information helps.
We understand the documentation is misleading, the numbers listed in the product brief are accurate as the given commands return the same numbers for power consumption.
Could you please let us know how you are measuring power consumption? And, are you getting different numbers than the ones provided in the product brief?
There is no way to put the Edison into standby and keep BLE functioning as listed in the product brief. I cannot measure power consumption to compare against the product brief because there is no way to put the Edison into standby mode and keep BLE functioning.
You said "the numbers listed in the product brief are accurate as the given commands return the same numbers for power consumption." What are those commands? How are you putting the Edison into standby and keeping BLE operating?
As Peter explained to you, power states are not officially implemented in Edison, however, we are currently working on your concerns about the BLE function and the information available in the product brief.
We appreciate your patience. We’ll post an update as soon as possible.
Thank you for your patience, we have an update for this case.
We have been informed that standby mode is no longer a supported feature from our vendor.
We will proceed to update the documentation regarding this subject in order to reflect this update.
We apologize for any inconvenience this might cause.