according to some posts found on the web, the watch 5 has a low latency problem and that the transmission data should be modified with the “command” command, but I couldn’t figure out how to do it they said via script I read the guide copied yaml by inserting mine device obviously but it doesn’t give me a valid one I can’t understand.
I changed the parameters you suggested by setting 5 for timeouts and 60 for away
but sadly I still don’t see it
Are you using MQTT-Explorer? If so, can you account for all the devices in the espresense/devices topic?
Can you post the log you mentioned where you see the beacon id? What are you using to receive the beacon and send it’s distance to the MQTT topic?
I found that using espresense with the galaxy watch 5, is draining it’s battery really quickly.
on a 12 hours period, it drained 37% of battery power.
did anyone else experience the same?
Advertise mode: balanced
Measured power: -59
Supports transmitter: true
Transmitting power: high
id: cca19497-*******_100_1
icon: mdi:bluetooth
friendly_name: Galaxy Watch5 (29PP) BLE Transmitter
Hi,
I tried turning the BLE transmitter on/off on my galaxy watch 5 pro by using command from this guide:
automation:
- alias: Turn off BLE transmitter
trigger:
...
action:
- service: notify.mobile_app_<your_device_id_here>
data:
message: "command_ble_transmitter"
data:
command: "turn_off"
This doesn’t work but I understand it used to.
Does anyone know what command I should use to achieve that ?
Show your automation and not the example. 
And what does it exactly mean, “it’s not working”? Is the sky turning purple when you run it? You see where I’m going with this? 
1 Like
not really 
by not working I mean not changing status from on/off and vice versa.
service: notify.mobile_app_galaxy_watch5_pro_cqkx
data:
message: command_ble_transmitter
data:
command: turn_on
ttl: 0
priority: high
This setting doesn’t change status (picture taken from phone app but I am referring to the watch os HA app)
1 Like
I’m trying to do the “ID change” as in the OP, but am having difficulties. E.g. I put a message to:
espresense/settings/iBeacon:xxxxx-100-1/config
with the message:
{“id”:“david”,“name”:“DavidWatch”}
I didn’t see any noticeable difference within MQTT. I added david to the filtering, and now it’s not tracking my beacon anymore. What am I doing wrong?
I restarted both the Esp as well as my watch, but still no luck.
What tool are you using to publish and read the MQTT topics? Also, what version of Espresense are you running on your BLE device?
I’m using MQTT Explorer, and Espresense is v3.2.4.
(not sure if I need to mask those Beacon ids, but I did anyway)
I figured it out. Do not copy/paste the payload from the OP post, as it will copy the left quote and right quote. They all need to be plain ascii quote characters ("), i.e.:
{"id":"david","name":"DavidWatch"}
1 Like
hello everyone,
I have a little problem with my galaxy watch.
Sometimes the beacon not report presence in espresense. to solve it, I must open the home assistant companion app in the watch again.
After this, the beacon report correctly.
do yo know how to solve this.
its frustrating if the beacon stop working 
Is the only way to change the device “alias” (like “david”, above) through sending an MQTT message?
Is there no way to change the device ID using the Home Assistant UI?
Not natively, no. Keep in mind the ESPresense project is not tightly coupled to Home Assistant, it simply uses MQTT.
That said, you could easily create an automation that would publish the topic required through Home Assistant, using a text input entity for example. A change of the text could trigger the automation and then you could but the text input in a dashboard for easy changes.
You might look at this project which is similar but based on ESPHome. It may be more tightly coupled. ESPHome component for ESPresense-like room tracking - ESPHome - Home Assistant Community (home-assistant.io)
SOLVED: Remember to post the Config message as “Retained”!
I’m not seeing the ability to use the alias (from the config entry) in the receiver’s filtering.
When I add the config, and I see it appear properly in MQTT, even though the updates in the MQTT messages are using the alias, the receiver doesn’t appear to be filtering with that alias.
If I add the actual device ID back into the “Filter” field, all works fine, and ESPresense/Home Assistant see the “alias” device.
But the receiver itself doesn’t appear to use the config from MQTT, which actually makes sense, no?
The receiver knows nothing about that config entry. But once it publishes the message, ESPresense takes over and uses the alias for all its work…
Am I missing something?
It’s likely you have something wrong in your topic. Post the topic as seen by a tool like MQTT Explorer.
I figured it out…
Important note… First learn how MQTT Explorer works!
I didn’t publish the Config as “Retain”. and though it remained on my Explorer screen (even though it had already been consumed), the rebooted receivers were not receiving the message.
Once I published the Config message “retained” (Duh!) it all worked fine…
Thanks for the help!
1 Like