Control page window bar on Chromium browser in kiosk mode

After updating to 2022.2 a window bar appears in my kiosk screen. Is there a way in Indigo to eliminate this?

I use this method for kiosk mode raspberry-pi-touchscreen-kiosk:

https://desertbot.io/blog/raspberry-pi- ... iosk-setup

[matt (support)]

Are you using Indigo 2022.2.2 that we just released on April 6th? If not, try that version as we made some changes to how Control Page windows are shown.

I tried 2022.2.2 hoping it would work but it is the same. I am back on 22.1.2.

"--disable-infobars --kiosk" setting on Chromium just doesn't seem to work on the new generated web control pages.

[matt (support)]

Exactly how are you specifying the URL that loads the page?

In the Openbox environment file

export KIOSK_URL=http://USERNAME:PW@192.168.1.7:8176/controlpage?name=Dad&useJS=True

In Chromium on the Pi it prompts me to sign in each time then the Devices, Actions, Variables and Control Pages selection web page is loaded. It doesn't go directly to the page specified. So the window with the title bar isn't loaded from the link.

On a Mac web page it prompts me to log in then takes me directly to the Control Page specified. Or directly to the web page specified if I had already logged in on that browser.

They act differently which I don't mind it is just the window bar that is displayed after I select "Control Pages" then "Dad."

If I knew what I was doing I could probably configure Chromium to act like the Mac web browser but It has been working fine for several years. Just displaying correctly was all I needed.

[matt (support)]

Instead of passing the username/pw in the URL, create an API key (in your Indigo Account on our web site), and then pass the API key into a URL formatted like this:

Code: Select all

http://192.168.1.7:8176/web/controlpage.html?id=YOUR_CONTROL_PAGE_ID_HERE&api_key=YOUR_API_KEY_HERE

Note the URL address path has changed. Also, to get the YOUR_CONTROL_PAGE_ID_HERE right-click on the Control Page in Indigo app and choose the Copy ID menu item.

"http://192.168.1.7:8176/web/controlpage.html?id=1492211973&api_key=API_KEY_HERE"

2022.2.2 running and the Openbox environment file edited with Control Page ID and API added to URL.

Logs in automatically, loads "Indigo Touch for Web" page, not the control page specified.

The double window bar remains.

I understand that the problem may be my responsibility to resolve and do appreciate your effort to help me resolve this.

What do others use to set up kiosks with Indigo? This method was so easy to set up and worked well for a long time.

Two different displays. Something else different with the update. One running 22.1.x and the other 22.2.2. With the background size changed on the Control Pages you can see the Indigo Touch for Web window still being generated in the background on 22.2.

Not important but on the pi3b the extra window is generating an under voltage warning. I am right on the edge for power to begin with and plan to upgrade all my touch devices.

[matt (support)]

I'm not familiar with Chromium browser, so can you explain in more detail what you are expecting to see versus what you see? The more details on what specifically is wrong or has changed, the better I can understand how to troubleshoot/fix the problem.

In the 2022.1 screenshot above, is it rendering correctly?

In the 2022.2.2 screenshot above, is there a Chromium feature to make the Control Page go full screen? If so, is the problem just that it doesn't automatically do that when clicking on the control page name in the Indigo Touch for Web table?

[matt (support)]

2022.2.2 running and the Openbox environment file edited with Control Page ID and API added to URL.

Logs in automatically, loads "Indigo Touch for Web" page, not the control page specified.

It is strange that the URL is not loading the Control Page directly. If you are specifying that URL with a valid control page ID (and API KEY) then it should just load the Control Page and not the main Indigo Touch for Web page. Are you sure the page you are seeing isn't left over from a different window or something?