-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apple watch First Edition #19
Comments
Could you please try the following: On line 60 of the yaml, you can change it to if (data_flags == 0x98 || data_flags == 0x18) { If this doesn't work, please send your full yaml, and verbose debug log from startup, and let it run a few minutes while it scans bluetooth devices. Please make sure your Watch is very close (< 30 cm) to the receiver. Verbose logging can be set: logger:
level: VERY_VERBOSE |
Unfortunately if (data_flags == 0x98 || data_flags == 0x18) { didn't workout. Thank you for your kind help |
Thanks for the debug logs.
if (data_flags == 0x98 || data_flags == 0x18) { to if (data_flags == 0x98 || data_flags == 0x18 || data_flags == 0x1C) {
|
Thanks for the prompt reply, yeah after last tweak now I can see my watch as online! My watch was unlocked at first attempt . And again I have got the result as unlocked again. As you have pointed out, in order to get online, I should get watch very close to esp32 it sensing only 5-10cm close. Finally if you lead me how to tweak distance I will appreciate very much. I have shared latest log with you |
Here is the log after turn off very_verbose option |
Thanks. Both log files were helpful. Try changing line 61 from if (status_flags == 0 || status_flags == 2) { to if (status_flags <= 2) { Also, please see my point (3) above. But let me clarify more: In Home Assistant, you have
See the readme config file explanation -77/-90 values are good defaults and you should only need to change them if your watch is being detected outside the room, or not being detected inside the room. Try the defaults fist, and then tweak later. |
Thank you Dale now working fine. I appreciate your assistance. Last think, is there any way to send messages to mqtt only if certain distance change occurred. Because there is big data flow to mqtt and I afraid it will fill-up all SD card on raspberry pi (Home Assistant) |
I'm glad we got it working. Does it still work when your watch is off your wrist, and auto-locked? Regarding 'too much data': That's a good point. The largest source comes from the internal: true You won't be able to see the rssi in HA any more, so maybe only do this after you've tweaked the |
However, there is also inconsistent action when I am away from esp32 sensor, it remains as detected and not going back not-home state and rssi value remains as last updated state. I couldn't justify somehow. I have shutdown the watch and dale_lounge_presence state not switching to OFF |
Could you send some debug logs of
|
Thank you for the reply, I have attached the log, and sensor states as well as the yaml and automation. When I take off the watch, the rssi pulses stopping after while, also complete shutdown the pulse stopped (roughly took a a minute to stop, I think during shutdown process pulse remains). Watch shutdown at 16:21 and home assistant remains detected never turns to Clear. The main issue is the automation not updating on the rssi signal stops. |
Hi,
I am happily using first generation apple watch! I am starving to use this tool but I couldn't detect my watch ever.
LightBlue App shows my apple watch ID as UUID: 5F666A3B-2EA9-8653-46E8-298D92EAF408
I will be grateful if you lead me to the right direction
The text was updated successfully, but these errors were encountered: