Not working with Gadgetbridge

[TheSunCat]

Hi! Thanks for maintaining this watchface, it looks really nice. I was trying it out with Gadgetbridge and unfortunately it seems the weather does not work. I get these logs from the app on my phone every few seconds:

14:16:56.177 [ThreadPoolForeg] DEBUG n.f.g.s.d.p.w.GBWebClient - WEBVIEW shouldInterceptRequest URL: https://api.met.no/weatherapi/locationforecast/2.0/complete?lat=56.4&lon=-2.9
14:16:56.179 [ThreadPoolForeg] DEBUG n.f.g.s.d.p.w.GBWebClient - WEBVIEW request:https://api.met.no/weatherapi/locationforecast/2.0/complete?lat=56.4&lon=-2.9 not intercepted
14:16:56.180 [ThreadPoolForeg] DEBUG n.f.g.s.d.p.w.GBWebClient - WEBVIEW shouldInterceptRequest URL (legacy): https://api.met.no/weatherapi/locationforecast/2.0/complete?lat=56.4&lon=-2.9
14:16:56.181 [ThreadPoolForeg] DEBUG n.f.g.s.d.p.w.GBWebClient - WEBVIEW request:https://api.met.no/weatherapi/locationforecast/2.0/complete?lat=56.4&lon=-2.9 not intercepted
14:17:00.504 [Thread-2] INFO  n.f.g.s.d.p.PebbleProtocol - got APPLICATIONMESSAGE PUSH from UUID : 9040763a-6b35-49d1-82ac-13ce02e31137
14:17:00.511 [Thread-2] DEBUG n.f.g.s.d.p.PebbleIoThread - to WEBVIEW: event: appmessage message: {"payload":{"KEY_TEMPERATURE":0},"data":{"transactionId":20}}
14:17:00.518 [JavaBridge] INFO  n.f.g.s.d.p.w.CurrentPosition - got longitude/latitude from preferences: 56.4/-2.9
14:17:00.523 [JavaBridge] INFO  n.f.g.s.d.p.w.JSInterface - WEBVIEW - geo position{"timestamp":1734445019523,"coords":{"latitude":56.4,"longitude":-2.9,"accuracy":100,"altitude":94,"speed":0}}
14:17:00.527 [main] ERROR n.f.g.u.GB - Refused to set unsafe header "user-Agent" (at file:///storage/emulated/0/Android/data/nodomain.freeyourgadget.gadgetbridge/files/pbw-cache/9040763a-6b35-49d1-82ac-13ce02e31137_config.js: 203)
14:17:00.529 [JavaBridge] DEBUG n.f.g.s.d.p.w.JSInterface - WEBVIEW event finished: appmessage
14:17:00.531 [ThreadPoolForeg] DEBUG n.f.g.s.d.p.w.GBWebClient - WEBVIEW shouldInterceptRequest URL: https://api.met.no/weatherapi/locationforecast/2.0/complete?lat=56.4&lon=-2.9
14:17:00.531 [ThreadPoolForeg] DEBUG n.f.g.s.d.p.w.GBWebClient - WEBVIEW request:https://api.met.no/weatherapi/locationforecast/2.0/complete?lat=56.4&lon=-2.9 not intercepted
14:17:00.532 [ThreadPoolForeg] DEBUG n.f.g.s.d.p.w.GBWebClient - WEBVIEW shouldInterceptRequest URL (legacy): https://api.met.no/weatherapi/locationforecast/2.0/complete?lat=56.4&lon=-2.9
14:17:00.532 [ThreadPoolForeg] DEBUG n.f.g.s.d.p.w.GBWebClient - WEBVIEW request:https://api.met.no/weatherapi/locationforecast/2.0/complete?lat=56.4&lon=-2.9 not intercepted
14:17:00.533 [main] DEBUG n.f.g.s.d.p.PebbleIoThread - Callback from appmessage: null

Normally Gadgetbridge itself should be able to provide weather info communicated from another app, as as far as I know GB does not use the internet permission.

[Sichroteph]

According to the logs, it seems that Gadgetbridge does not allow a custom user agent when launching the JavaScript weather request. This is a mandatory requirement to be able to use the weather service from yr.no, and unfortunately, I don’t see any workaround other than using Rebble. Out of curiosity, why don't you use Rebble ? Le mar. 17 déc. 2024, 15:29, TheSunCat ***@***.***> a écrit :

…

Hi! Thanks for maintaining this watchface, it looks really nice. I was trying it out with Gadgetbridge and unfortunately it seems the weather does not work. I get these logs from the app on my phone every few seconds: 14:16:56.177 [ThreadPoolForeg] DEBUG n.f.g.s.d.p.w.GBWebClient - WEBVIEW shouldInterceptRequest URL: https://api.met.no/weatherapi/locationforecast/2.0/complete?lat=56.4&lon=-2.9 14:16:56.179 [ThreadPoolForeg] DEBUG n.f.g.s.d.p.w.GBWebClient - WEBVIEW request:https://api.met.no/weatherapi/locationforecast/2.0/complete?lat=56.4&lon=-2.9 not intercepted 14:16:56.180 [ThreadPoolForeg] DEBUG n.f.g.s.d.p.w.GBWebClient - WEBVIEW shouldInterceptRequest URL (legacy): https://api.met.no/weatherapi/locationforecast/2.0/complete?lat=56.4&lon=-2.9 14:16:56.181 [ThreadPoolForeg] DEBUG n.f.g.s.d.p.w.GBWebClient - WEBVIEW request:https://api.met.no/weatherapi/locationforecast/2.0/complete?lat=56.4&lon=-2.9 not intercepted 14:17:00.504 [Thread-2] INFO n.f.g.s.d.p.PebbleProtocol - got APPLICATIONMESSAGE PUSH from UUID : 9040763a-6b35-49d1-82ac-13ce02e31137 14:17:00.511 [Thread-2] DEBUG n.f.g.s.d.p.PebbleIoThread - to WEBVIEW: event: appmessage message: {"payload":{"KEY_TEMPERATURE":0},"data":{"transactionId":20}} 14:17:00.518 [JavaBridge] INFO n.f.g.s.d.p.w.CurrentPosition - got longitude/latitude from preferences: 56.4/-2.9 14:17:00.523 [JavaBridge] INFO n.f.g.s.d.p.w.JSInterface - WEBVIEW - geo position{"timestamp":1734445019523,"coords":{"latitude":56.4,"longitude":-2.9,"accuracy":100,"altitude":94,"speed":0}} 14:17:00.527 [main] ERROR n.f.g.u.GB - Refused to set unsafe header "user-Agent" (at file:///storage/emulated/0/Android/data/nodomain.freeyourgadget.gadgetbridge/files/pbw-cache/9040763a-6b35-49d1-82ac-13ce02e31137_config.js: 203) 14:17:00.529 [JavaBridge] DEBUG n.f.g.s.d.p.w.JSInterface - WEBVIEW event finished: appmessage 14:17:00.531 [ThreadPoolForeg] DEBUG n.f.g.s.d.p.w.GBWebClient - WEBVIEW shouldInterceptRequest URL: https://api.met.no/weatherapi/locationforecast/2.0/complete?lat=56.4&lon=-2.9 14:17:00.531 [ThreadPoolForeg] DEBUG n.f.g.s.d.p.w.GBWebClient - WEBVIEW request:https://api.met.no/weatherapi/locationforecast/2.0/complete?lat=56.4&lon=-2.9 not intercepted 14:17:00.532 [ThreadPoolForeg] DEBUG n.f.g.s.d.p.w.GBWebClient - WEBVIEW shouldInterceptRequest URL (legacy): https://api.met.no/weatherapi/locationforecast/2.0/complete?lat=56.4&lon=-2.9 14:17:00.532 [ThreadPoolForeg] DEBUG n.f.g.s.d.p.w.GBWebClient - WEBVIEW request:https://api.met.no/weatherapi/locationforecast/2.0/complete?lat=56.4&lon=-2.9 not intercepted 14:17:00.533 [main] DEBUG n.f.g.s.d.p.PebbleIoThread - Callback from appmessage: null Normally Gadgetbridge itself should be able to provide weather info communicated from another app, as as far as I know GB does not use the internet permission. — Reply to this email directly, view it on GitHub <#1>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEA2MG75VAP3XC2Z6IK25YD2GAYONAVCNFSM6AAAAABTYRYXMSVHI2DSMVQWIX3LMV43ASLTON2WKOZSG42DKMBZGUYDQMY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[TheSunCat]

I always use Gadgetbridge for its features and integrations with other apps (like the ability to export my data and then process it elsewhere). The original Pebble app has trouble running on my phone as well, so I'm mostly stuck with Gadgetbridge.

Normally GB should be able to provide weather directly to the watch apps, as it gets it from a "provider" (in my case the app Breezy Weather) that makes the web requests in its place. I am not sure how this API works on the app side, but if it's possible to detect Gadgetbridge, Din Clear could get its weather data from it instead of making web requests itself.

[Sichroteph]

Yr.NO is special in the sense that it does not require an API key but explicitly states in its Terms of Service (https://developer.yr.no/doc /TermsOfService/) that the application creator must register in the user agent. This is seen by older JavaScript browsers as a security risk, and there is nothing we can do about it. Le mar. 17 déc. 2024 à 17:18, TheSunCat ***@***.***> a écrit :

…

I always use Gadgetbridge for its features and integrations with other apps (like the ability to export my data and then process it elsewhere). The original Pebble app has trouble running on my phone as well, so I'm mostly stuck with Gadgetbridge. Normally GB should be able to provide weather directly to the watch apps, as it gets it from a "provider" (in my case the app Breezy Weather) that makes the web requests in its place. I am not sure how this API works on the app side, but if it's possible to detect Gadgetbridge, Din Clear could get its weather data from it instead of making web requests itself. — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEA2MGZUBSNDFWCIVESFOL32GBFERAVCNFSM6AAAAABTYRYXMSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBYHEZDCNRTGA> . You are receiving this because you commented.Message ID: ***@***.***>

[TheSunCat]

Thanks for explaining. I asked on the Gadgetbridge side and they explain that, as the app itself has no internet access, it instead detects when a watchface is making a web request to OpenWeatherMap and intercepts it and instantly responds back with the weather data (requiring no API key). Because only the OpenWeatherMap API is supported, GB is not detecting Din Clean's yr.no requests which is why I am seeing these errors.
I am not sure how much effort it'd be to use the OpenWeatherMap API (and get intercepted by GB) with Din Clean's existing codebase, or whether it's more efficient to implement support for met.no/yr.no on the Gadgetbridge side.