Open anthonyangel opened 3 years ago
Hi!
Yep I've been using it for quite a while now. I wouldn't call it clean and it could definitely use more error handling but it has stood the test of time
Thank you!
To make this a bit easier, here's what I'm currently using to talk to the GlanceClock.
I hope that it will be at least somewhat helpful even though its's just unpolished copy paste
Be advised that sometimes (I think it's caused by too many invalid requests/connection attempts) the clock looses its pairing information and needs to re-paired.
Unfortunately, this fails silently and can only be noticed by observing that data pushed to it doesn't appear anymore.
The pairing process is still rather tedious for some reason but has been at least mostly reproducible.
For best results, try turning bluetooth off and on again. That seems to help. Pairing looks more or less like this:
run bluetoothctl. In bluetoothctl do:
agent off
power off
power on
agent on
default-agent
menu scan
transport le
back
scan on
//The terminal will most likely be spammed by advertisements. Ignore that
<wait a few moments>
pair MAC_OF_YOUR_CLOCK
//enter pin displayed on the clock
//The clock should confirm pairing on its display. if not do "remove MAC_OF_YOUR_CLOCK" and try again from the start
hi @Hypfer @anthonyangel !
First, thanks for the project !
i've just got the Glance Clock, run successfully the Cybele Project, but it doesn't start any action to my clock
my config.json:
{
"mqtt": {
"url": "mqtt://USER:PASS@MQTT_IP"
},
"dongles": [
{
"hciDevice": "hci0",
"mode": "le",
"services": [],
"devices": [
{
"type": "GlanceClockDevice",
"friendlyName": "GlanceClock_F3",
"mac": "F1:95:1D:7F:D2:F3"
}
]
}
]
}
bluetoot is connected :
Agent registered
[CHG] Controller 00:1A:7D:DA:71:15 Pairable: yes
[GlanceClock_F3]# paired-devices
Device F1:95:1D:7F:D2:F3 GlanceClock_F3
[GlanceClock_F3]# info F1:95:1D:7F:D2:F3
Device F1:95:1D:7F:D2:F3 (random)
Name: GlanceClock_F3
Alias: GlanceClock_F3
Appearance: 0x0100
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (5075f606-1e0e-11e7-93ae-92361f002671)
UUID: Vendor specific (8e400001-f315-4f60-9fb8-838830daea50)
ManufacturerData Key: 0x004c
ManufacturerData Value:
02 15 50 75 f6 06 1e 0e 11 e7 93 ae 92 36 1f 00 ..Pu.........6..
26 71 00 01 00 01 c3 &q.....
The node app.js | grep "F1:95:1D
does'nt show anything. I've tryied to publish to cybele/glanceclock/F1:95:1D:7F:D2:F3/notify
but no effect, netiher on the log of app.js, neither on the clock
Could you help me please ? 🙏🏻
find the solution !
the mac adress in the topic name must be in lowercase and without underscore
thanks again for the Cybele project ❤️
Hi, does the Glance Clock integration work? If so then I'm happy to muddle through working out how to use it and writing up a Readme