The crash screen is symptomatic of being out of memory for the menu. Something we cannot anticipate, as you will read from the documentation. However your menu definition is really small, so that seems unlikely. Also we would only expect that to be a problem on the widget version running on an old device.
So can you confirm you have actually installed both versions, widget and application as separate Apps from the Connect IQ store? You say you have the problem with both but I just want to rule out lose use of terminology.
What device are you using please?
We are surprised you can get local HTTPS working, as Garmin’s API call requires a publicly signed certificate. Something only the simulator allows us to bypass, but perhaps you have been clever with DNS?
I’m worried you have found a bug . Is there a log file on your device giving a clue as to the cause?
Nono, I may have provided short info.
I use let’s encrypt to generate the domain with certificate, it’s just I’ve setup my local DNS server to resolve the same domain locally with a private IP.
In this way, I don’t have to publish home assistant but able to use https at home. And it is a requirement of HAAD control.
I use a Garmin Venu 2 plus so shouldn’t be short on resources.
I’ve installed both widget and app from the official store and getting the same IQ icon, it’s just the widget before opening it is providing more info about the menu and API.
I hope this helps in order to help me?
Otherwise let me know what kind of info I can share.
I use a Venu 2, so the app absolutely should be working. The JSON is correct bybthe schema. I need to create a similar setup locally to see what is going on.
So I am stuck here…
Also at the beginning I was trying to make it work without the port (like in the guide? but noticed I had to put the port either in my API or Menu URL to have it recognized. Is that correct?
If you use the port to access HomeAssistant via your browser, you should use it here, if not then you shouldn’t (it will use 443 like any other HTTPS), we have a proxy setup that puts it on port 443 but by default it is 8123
That’s what I noticed. Actually when getting the URL through the browser with the port I get the Json, otherwise I got nothing.
I’ll be waiting for your help guys…
Note that the venu 2 doesn’t actually support widgets, it uses glances, the app itself gives provides a glance and the widget is only for older devices that don’t use glances. You probably should just use the app, not the widget.
We’ve just tried to recreate your setup locally by adding DNS resolution for the external URL within the local network. We know that must be working a we can turn off the Internet and the external URL is now still working.
I’ve run up a simulation of the Venu 2+ with this configuration (still no Internet), and all works well. So I’m stuck unable to debug the problem as we can’t recreate it.
Oh…this means I am doing something wrong then…but what?
Once I get back home I’ll posting all the steps I’ve followed and parameters as I have no clue right now on what could be wrong.
Any advice is more than welcome to start troubleshooting
On my watch I browsed to This PC\Venu 2\Internal Storage\GARMIN\APPS\LOGS. Look for a file named something like CIQ_LOG.* (my watch has CIQ_LOG.BAK, so looks like an old renamed file). The file contents had entries like the following:
Of that the Store-Id should match the App URL of https://apps.garmin.com/en-US/apps/db1e9356-8e04-4d6b-ab43-5c70c49b2488 (that’s the beta prototype app you can’t browse to) and then the Error: provides the main piece of useful information, as the only glimpse of what might be wrong.
I would expect yours to contain:
Store-Id: 61c91d28-ec5e-438d-9f83-39e9f45b199d
For a URL of https://apps.garmin.com/en-US/apps/61c91d28-ec5e-438d-9f83-39e9f45b199d.
The aim here is to get a single menu item for a group that contain nothing,. Entering the group should give you a black empty screen. Then swipe right to return to the main menu with just one group item.
By using these menus that contain no entities I hope you can run without a crash as there are zero API interactions. That might tell us that there’s a problem updating the status of your toggle item(s) with your setup. The app should not crash, so I need to figure out how to catch the problem and provide a more useful error message for diagnosis and resolution.
No, there isn’t. Once it crashed I have no option than quiting the app. I tried keeping some buttons pressed in case I had some context menu but nothing…
. Is there a log file on your device giving a clue as to the cause?
