panaaj
commented
2 years ago It sounds like Freeboard cannot access localStorage where it stores its configuration so it starts with default values.
This is likely due to a violation of "Same origin Policy" blocking access to LocalStorage. "Two URLs have the same origin if the protocol, port (if specified), and host are the same for both."
If you have control over the page that hosts the iframe then try adding the following attribute:
<iframe href="....." sandbox="allow-scripts allow-same-origin">This worked in my tests.
If this doesn't help I have also seen this happen in later versions of Chrome when "Block third-party cookies" is selected in Chrome settings.
Might want to try changing the setting to "allow all cookies" or " Block third party cookies in Incognito" and this may allow Freeboard to access it's config.
Providing parameters in the start url is only going to mask the real issue and there will be other config (like units selection, etc) which will not be available to Freeboard.
BTW: that is a nice wide screen! .
bergie
I'm running Freeboard embedded in a Grafana dashboard on a kiosk screen in our nav station
Problem is that every time the screen starts we:
Would be great to provide default values for those via URL parameters when opening the app. Then I could easily encode those to the iframe URL. For the moment I need to connect a mouse to the device to get to the desired view.