Yes, with our BKON brand Physical Web beacons, we wrote our firmware and designed our hardware to work perfectly with the Eddystone-URL frame type. Because of this end-to-end process management, we are able to update battery state for our Physical Web beacons right on our PHY.net platform all using just the Eddystone-URL frame.
However, if you want to make things harder on yourself then you can use the Eddystone-TLM frame to pass battery state to your custom service. With PHY.net, there is no need for custom development or the use of complex API's to monitor your Physical Web beacons. Even though PHY.net can work with any brand of Eddystone-URL (aka Physical Web) beacon, the platform level battery monitoring only works with our BKON brand beacons.
There is no longer a need to keep your beacons in connectable mode and expose them to the outside world to collect battery state. Our beacons ship configured as non-connectable, Eddystone-URL frame type so they're ready to go as soon as you receive them.
Be aware that all major beacon protocols (iBeacon/Eddystone) now either promote or mandate that beacons be in a “non-connectible state” (non-connectible means that the beacon is not listening for an external connection). This increases the security and it reduces the battery consumption of both the beacon and users’ mobile devices. Any beacon fleet management platforms that rely upon connecting to beacons (*cough cough* most iBeacon platforms) to monitor their batteries are at risk of becoming obsolete.