Hey @r2k Marco, I forgot to update the code above, which I just did. Norway seems to love mondays, they have them twice 
Next weekās monday seems to be a different monday than this weekās.
So it should be
['Mo','Di','Mi','Do','Fr','Sa','So','Mo']
with all the forecast arrays.
Thank you so much, now it works perfectly. Many thanks for your help/update.
best regards from Switzerland
Marco
I need some battery-saving suggestions.
I have one display just showing the default date display. But it eats the batteries in about a week. Should I just show the date and time from an automation once a day at midnight?
Perhaps you can change the check in time, but I donāt think you can do that one just one tag.
I think I have figured some of my reliability issues.
I changed the channel, and it seems you need to save the automation before you run it or it will run the saved version.
When it runs the saved version of the automation then it makes no changes to the display and the AP knows this so it does not send out a new image.
Anyone know what the state of the epaper displays means?
All of mine has the state ā1ā except one that has ā0ā.
Itās probably looking at the date/time of the automation?
Where are you seeing this?
the state seems to correlate with the hwtype in the attributes.
With me it is 0,1,2, or 224ā¦
0 M2 1.54"
1 M2 2.9" (as in your example)
2 M2 4.2"
224 being the AP itself.
Anyone know why a tag would do like this?
This is the image that is the device content in HA.
I have tried to reset it, didnāt work.
I have tried to reboot it, didnāt work.
When I send a weather forecast then it displays correct.
When I send the HA content again after the forecast then it becomes strange again.
The same yaml is also on another display and it looks correct there.
I had this. For me resetting the tag (taking the batteries out, shortening the battery contacts) solved it.
Is your integration up to date? How about the AP software?
Integration is up to date.
Not sure about the AP. I canāt access it from work.
But this started happening literally over night.
Are you sure itās displaying the exactly same thing when it works? The same calendar entry?
If you post something different from HA to the non-working tag, does it display correctly?
I removed the dynamic parts and got this:
Which is correct.
Then I sent the same data that was sent this morning and now it works again as it should again.
Very strangeā¦
I have it sometimes as well. Most of the time a blick rectangle and a shifted rest or the picture. Next send it is most of the time ok again. Seem to be a sending problem. Compare to corrupt loading screens from Commodore Datasette. 
I had one do this, but before I could get around to troubleshooting it, the tag fixed itself. I suspect that a data transfer was corrupted.
Maybe itās the blodpudding that confused the system
If it corrupts again, try to find similarities (same day, dill, no welliesā¦)
Where did you get the png file from? From the HA camera entity? Or the original in the integrations folder?
Since it worked at two other tags, with the same code. I mean really the same code. I had them all three listed as entities in the same service call, then it canāt be any similarities that does it.
The image is from the content in the device in the integrations page
What happens when you add one more line to the menu (maybe add some blodpudding 
) ? Does it still display correctly? Or add yesterdays menu for today? I think I had something similar when displaying stuff outside the displayable areaā¦
No it doesnāt display correctly.
If you look at the previous png file you can actually see there is a fourth line.
But again, it worked fine on two other tags, and the same tag later in the evening.
Do you all know what these work really great as?
Fake thermometer.
Just make sure your normal thermometer stops working, then you send room temperature+little extra and all the complaints that itās cold just disappear.
And you save money on the heating.
Anyone know if you can rotate text?
I see there is two issues on github but they both link to each other as closing reasons.
EDIT:
I found a workaround.
dlimg has the option to rotate.
So I created a php page that displays the time when the display updated as an image and the dlimg rotates the image when it adds it to the display.
