Did you select a device from the drop list in the settings when you added the widget?
Than you for your reaction!
When I choose to add the widget to the dashboard, I can choose between advanced display and advanced status. I choose for advanced display.
Then I get a page with settings. I left them unchanged. And the I clicked the blue bar âAdd widgetâ
I get u black empty surface where the widget should be with a rotating cursor.
This night Homey updated the app to version 27, but I had the same result as yesterday.
Regards,
Koos
Thank you.
I tried it, and it worked.
Maybe it would be better if there was an error message, or that the blue bar does not appear if a device is not chosen.
Thank you very much, I experiment further. It looks like a promising widget!
Regards,
Koos
Hi Adrian, Today my Homey updated the Enhanced Device Widget app to version v1.1.28.
I have a lot of Status Display widgets using custom HTML. Since the update table, text and image elements have increased in size.
Did anything change in how the Status Display widget handles HTML and/or default sizes?
An example:
Before
After
I wonder if itâs this addition of the following in the header:
<meta name="viewport" content="width=device-width, initial-scale=1.0">
The only other change is the removal of style=âdisplay:blockâ from:
I canât remember why I made that change, but I could roll it back if itâs a big issue for you.
Yes, please if you could do that.
I am not sure which of the two changes is causing this behavior. But I could not solve it in my HTMLs.
Rolling back those changes would save me a lot of time figuring out how to address the issue.
I did some further digging on whether I could solve the HTML formatting issues.
I managed to solve one issue: the example above. Apparently, when specifying the width or height of an image I now need to explicitly include the unit, px in my case. So e.g. height: 20px instead of height: 20, which worked before (pixels is the default unit).
I could not however, in all cases, solve the issue of extra space that is being added between table rows when it includes an image. See the following example of a remote, which is basically a table with images. On the left the old version and on the right how it is displayed in v1.1.28.
The button images have the display: inline-block style and that seems to be adding the extra space.
I have tried using the the margin-top and margin-bottom commands to set those to 0 pixels, but that does not have an effect.
In some cases I can remove the display: inline-block styling, which removes the extra space. But that requires that each image is in its own cell, otherwise the images are stacked on separate lines.
For the example of the remote in some cases multiple images need to be next to each other in the same spanned cell (e.g. the directional pad images). For that I need to style them with display: inline-block or display: inline. Both result in the same extra space.
So if it is not too much trouble and it does not affect other changes your implemented, then rolling back your HTML changes would hopefully solve my formatting issues.
I will roll back, as far as I can remember I made the changes to fix linter warnings so the html was more confirming.
Test version is in the store.
Thank you for your efforts!
I tested v1.1.29. Unfortunately that did not solve it. Very strange. Have you got any clues on what might be causing that behavior?
Iâll have to check if I can find some other way to remove the spacing.
I found a solution for the inline-block images that removes the extra blank space: apply negative bottom margin: display: inline-block; margin-bottom: -4px;
That solved the formatting issue 
What version are you using, live or test?
The actual version number would be useful.
Of course, sorry about missing that.
I am running v1.1.29.
And the Title and Text text is just a space (not empty as I first wrote).
Background and Text colour is set to black (000000).
Hmm I will take a look.
In version 28 I âfixedâ some conformance issues to remove the red underlines in the editor and that changed the behaviour for some users. Version 29 should have rolled back those changes, but maybe I missed something.
I have found that I hadnât roiled back the changes in the style sheet for the status widget, so maybe that is the issue.
I have published a new test version with that rolled back.
That did the trick, thanks.
