It might be a problem with the Android Go edition. Because if I have Kiosk running, the show dashboard works (homeydash.com), but if I use flow to launch another app, it shows up, but I can’t go back using flow. The only thing that works is to manually tap the back arrow on the tablet and I’m back in the dashboard.
I meant to say, it might be netatmo app related somehow.
So to return to the dash,
if you first start, say, com.android.gallery3d, and then a few secs later “show dashboard”
Maybe it works
As mentioned before the ‘Show Dashboard’ action card should resolves this. This basically instructs Fully Kioskbrowser to show the browser on the foreground and to load the default URL.
If this does not work, it might be a bug in the Fully Kiosk browser itself and maybe you can ask them for additional support.
Yeah I haven’t tested it with dashboard which are positioned in portrait landscape. So the used CSS will definitely mess it up.
Could you write a specific Github issue so that when I got the time I can fix it. Thank you for mentioning it.
Just for everyone’s information, these API calls are also used within the application. For info see:
Hi, I’m struggling with what flow to create so that if I launch Spotify, it will launch the Spotify app on the dashboard. Spotify doesn’t offer any when tab, only then… how did you solve this please?
Hi @Miroslav_Gluch Try the THEN “start application” card.
Enter com.spotify.music
(or if it doesn’t work: search for the exact Spotify app ID with the android app “package name viewer 2.0” from the ggle store).
yes I understand that, but I don’t know how to create a WHEN card - WHEN Spotify is playing… If there is some way, for example, via API or similar.
For example, with MagicMirror if I start Spotify on any device, it shows me the currently playing song https://github.com/raywo/MMM-NowPlayingOnSpotify
Since yesterday I get this popup shown below on all my Android dashboards when it should show an image from one of the cameras, and it is the same for Onvif and Eufy cameras.
Sorry guys, so unfortunately I accidentally committed some debug code for an upcoming fix for an issue to the main branch and thus it was released in the latest 0.3.2 version. I’ve just released a new version what should fix this in 0.3.3.