• State Not Answered
  • Replies 6 replies
  • Subscribers 17 subscribers
  • Views 343 views
  • Users 0 members are here
Options
Related

App that syncs devices heartrate to a philip hue room only working in simulator not on real watch?

okk1980

Hi,

i'm new to garmin development and I try since days to get a fenix 8 to connect via oauth2 to philips hue and change the color of my room according to heartrate.

I now finally thought everything is fine and its working but for some reason it works only in simulator. on the watch it is not able to show the login page from hue via connect app and get back to app when login was completed. On the simulator it work....

here is the git repo: okk1980/GarminHueHeartbeatApp

anyone call help? It's driving me crazy after trying so many hours ...

 

steps in the watch app:

1: hold UP button to go to watch apps settings:

2: click logon on the setting menu

3: login on hue

4. watch menu shows hue rooms and you select one

5. you press start button on watch and it starts reading HR Sensor and sends color change to room.

Please help! WaveBow

  • 0

    Have you looked at your log file from the device? I'm on the phone, so I can't find it for you, but there's details in the documentation for how to do it.

    Anyway, my guess would be that the watch doesn't like the SSL certificate of the hue servers. Unfortunately many Garmin devices don't support the most modern SSL certificate, and will just fail if you try to connect to them. But do some logging and come back with details with what's actually failing, and we can try to help you.

  • 0

    I cloned this repo and tried it out:

    - in the simulator. In this case, a login page for Hue was opened when I followed steps 1 and 2. (I didn't bother to try to log in)

    - on a real FR955, paired with Connect (iOS). In this case, after step 2, I see what looks like it might be the login window flash (appear and disappear) for a split second in Connect. If I repeat step 2 lots of times, maybe I can get the window to flash a handful more times. I tried a few random other URLs like www.google.com, with no difference. I also tried changing the redirect URL, not that it should matter just for opening the initial web view.

    I haven't developed a CIQ app that uses oauth so I don't have any personal experience with seeing this work or fail with my own app.

    It seems to me that if oauth was broken in Connect for all CIQ apps, then there would be a ton of user reports. High-profile apps like Spotify would stop working (for new users).

    So I'm not sure what's different here.

  • 0 in reply to Andreas Tarandi

    Hi, 

    thank you  for your feedback. I already created the log file on watch and took a look. There are no error messages in. Only the prints I create in code to know how far the program get's executed.

    So I get all prints till the hue login page is created - after that there is nothing happening on the Android Connect App/ Watch. No error but also not triggers the callback somehow Disappointed

  • 0 in reply to flowstate

    thanks! I also don't believe oauth can be broken in general. But at least it is not working on real device and not creating any error message that could help to identify potential issue. I hoped someone that has experience can figure out whats wrong with my code Disappointed

  • 0 in reply to okk1980

    I've had reports from iPhone users that makeOauthRequest isn't popping up on the phone. The solution is usually to restart phone and/or watch. 

    forums.garmin.com/.../communication-makeoauthrequest-not-popping-up-on-iphones

  • 0 in reply to Andreas Tarandi

    I tried. Didn't help on android + fenix 8

Copyright © 1996-2025 Garmin Ltd. or its subsidiaries