Did you read, that these calls formats are deprecated? So a removal is not out of range. I would suggest to start directly with the drawcustom. Well described here:
Drawcustom is actually what I am doing with the tags I am making for around the house. The question was just a curiosity.
Here is the screen resolution of 296 x 128:
What do you mean?
From: 2.9âł STâGR29000 ¡ jjwbruijn/OpenEPaperLink Wiki ¡ GitHub
Specs
2.9â ePaper display SSD1619 or UC8151 (BWR) 296x128px
Still not get it. So spec is equal to you picture and not different.
I need stronger glasses.
Apart from the Tindie link does anyone have a shop theyâve purchased from to get either the APs or the tags?
I just got my tags today.
They are really cool, so much fun tinkering with these.
I will spend so much less time with my family from now on.
Anyone know why the tags sometimes does not update?
I managed to get one update done just a few minutes ago, then I made some changes to the code and sent a new one and then the price tag just doesnât respond.
It checks in as it should but it wonât take the new image.
I have tried to clear the pending and send it again. I also tried the force refresh button but none of it has worked.
Tried to unplug the AP and then plug it back in and it started working again.
Seems a bit unreliable, anyone else noticed this? I had the same issue yesterday
Is the new image generated? And only not send? Perhaps you used simulation?
Anyway: I would try a new battery.
Kind of the same as before, I just moved some text a bit down.
No, it was not a dry run. It was the same code.
Perhaps batteries could help. But I tried to send the same code to two tags just to see if it was the tag. None of them responded until I had power cycled the AP.
Probably donât need to say this, but the tag only updates when it wakes up and sees an update pending. The â1â in the lower corner of your image shows that one update is pending. Unless you have changed it, I believe the tags check for updates every 40 seconds.
Yeah⌠But I waited several cycles. Probably upwards to 10 cycles and it did not respond.
Do you have the newest integration version? There were recently some fixes/problems with disconnecting the access point.
There is no updates in HACS.
I installed the integration monday, so I guess I have the latest
Now both of them went in to this mode while I was getting the kids to sleep
Iâll get a bunch of batteries. It could be that there is enough battery to check-in but not to update the screen
Try removing the batteries, short the contacts in the tag then reinsert the batteries.
I donât know if it matters, but be near the Access Point when you reinsert the batteries.
I didnât do that. But this morning they both were back as they where commanded yesterday.
I managed to send one new image and then it stopped responding again.
The tags are still in development and are just beside the laptop and the AP, so it shouldnât be a range issue.
I´ll see what new batteries will do.
I personally noticed that a low battery can result in some strange behavior, so that would probably be a good step indeed.
And make sure to reset them (so shorting the battery contacts).
I got my AP and my tags a few days ago, I love them. I was lucky to get a 4.2" and im using your code for the weather update in the hallway.
I figured out a small issue with the code, in my environment it does not like the Monday (like most people ) Monday will not be displayed:
I could track it down to this section of the code but I really have no clue how to solve it. Yesterday it was the last row, today its the middle day - so based on my understanding is related to Monday.
{% set temp = (state_attr('weather.home', 'forecast')[2].templow |
float) | round(0)|string %} {% set tag =
['Mo','Di','Mi','Do','Fr','Sa','So'][as_datetime(state_attr('weather.home',
'forecast')[1].datetime).strftime('%u')|int] %} {% if temp|length == 1
%} {{tag ~ " " ~ temp ~ "°"}} {% elif temp|length == 2 %} {{tag ~ " " ~
temp ~ "°"}} {% elif temp|length == 3 %} {{tag ~ " " ~ temp}} {% endif
%}
wrong output (MO is missing):
right output but wrong array position:
its reproducable in my HA in the developer tool (states) and in my test HA as well (both docker based) / Version 2024.2.3
I hope this helps - sorry for the long post but I try to provide as much information as possible
Best regards
Marco