I don’t think it’s possible to fix this unfortunately, the page itself for whatever reason decides to close the connection. My widget can’t change anything in the behavior of the page if it decides to close the connection too early. I think it might be a latency issue, but not much you can do about it.
No problem
I noticed that loading web pages is quite slow, since the Homey API channel that I’m using isn’t optimized for loading full web pages, it’s meant to be used for small status updates.
I’m thinking about setting up a cloud VPS to function as a fast relay server between the widget and the Homey, but I’ll have to check if it’s actually faster first.
I don’t know what else could be done about the slow loading, other than setting up a faster relay server. My Pi-Hole webpage takes 30-60 seconds to load, and any large webpages also take very long to load.
If anyone experiences slow loading of webpages in the current version, please let me know.
It loads faster on SHS, seems to just be my HP2019’s WiFi connection speed. A relay server won’t fix that, so that will not be the solution.
Any plans on custom height and scrolling?
I was already working on custom height and alert() messages, it’s almost done. Scrolling is a bit more difficult, I’m trying to fix it but it isn’t working yet.
Good to hear!
Hi @smarthomesven , I have one local page which is pointing to address http:\LOCALIP\tar1090 but when I tried to use your app, unfortunately it’s not working, the page loads, but it’s somehow broken (even on local connection), it’s not loading correctly. Not sure if you will see anything from the logs, but shared them.
Btw, TAR1090 is my local Raspberry ADB-S exchange tracker server, it loads just fine in the build in web widget. It’s nothing critical but when I saw you app, I was having some hopes
Did you add a / to the end of the URL? I see in the logs that it’s requesting multiple scripts like
http://10.0.0.133/formatter_7f86b20.js which all return a 404. I think the base URL isn’t added correctly, which often happens if you don’t add a / to the end of the URL.
Thank you, interesting, that was not required for Athom build in Web page widget. However, even after adding / at the end, the result is better but still it’s broken, unfortunately. Will send you another log.
That’s because the official widget uses a native web browser. I use an iframe to display the page and then the script modifies the page to inject the scripts/stylesheets. It then injects another script which hooks on some methods like fetch() and href (for intercepting hyperlinks). Since my widget is running in a specialized environment, not all features of a regular web browser are available.
OK, thanks for explanation, so probably it would never work I assume ?
It will, but you need to add a / to the URL
Yeah, I did that as I wrote previously - anyway, thank you for your support, as I mentioned, it’s nothing critical, just nice to have.
What does the page show when you add the / to the URL? Can you share a screenshot?
