search

Blueforcer / awtrix3

Custom firmware for the Ulanzi Smart Pixel clock or self made awtrix. Getting started is easy as 1-2-3
https://blueforcer.github.io/awtrix3/
Other
1.25k stars 108 forks source link

[BUG] Blank screen after a period of days #567

Open jamieyates79 opened 2 months ago

jamieyates79 commented 2 months ago

Bug report

Describe the bug

Our Ulanzi clocks work reliably for around a week or so, then the screen goes blank. After this happens we can connect to the devices by connecting to their IP addresses, and even see the live view in the browser, but there is no display on the physical device screen. The small light on the back by the charging port shows green. We have two Ulanzi clocks which both experience this issue.

They're both connected to Home Assistant via MQTT and we send occasional messages to them via MQTT. Resetting the clocks resolves the issue for period of time.

Additional information

To Reproduce

Steps to reproduce the behavior:

Expected behavior

We expect the display to continue working :)

Blueforcer commented 2 months ago

Sounds like you're just switching off the matrix :) there is no code related part wich switches off the matrix randomly. Make sure you have no automation which switches off all light entities, because the matrix is a light entity in Homeassistant. You can turn on the matrix again by double pressing the middle button. (or via the HA entity in Homeassistant or API call)

dom-gunstone commented 2 months ago

I'm having a similar issue but very, very infrequently. If I had to guess I'd say once every couple of months.

Home assistant shows all of the clock's entities as unavailable until I turn the clock back on by holding the middle button.

Blueforcer commented 2 months ago

Home assistant shows all of the clock's entities as unavailable until I turn the clock back on by holding the middle button.

Holding the middle button doesn't turn on or off the clock. It just enter or leave the onscreen Menü.

Double press turns only the matrix on or off, Awtrix still runs.

Holding left and right switches the power completely on or off.

warp735 commented 2 months ago

I have the same problem. After few days freeze the screen by both Ulanzi´s. Only hard restart with right and left button helps.

jamieyates79 commented 2 months ago

Sounds like you're just switching off the matrix :) there is no code related part wich switches off the matrix randomly. Make sure you have no automation which switches off all light entities, because the matrix is a light entity in Homeassistant. You can turn on the matrix again by double pressing the middle button. (or via the HA entity in Homeassistant or API call)

Thanks for your response. This makes sense. Double-clicking the centre button turns the display back on, and I can also see the Matrix being turned off by a service (possibly where I'm using Node Red to turn off all lights in the area). Based on this, I don't think there is a bug :-)

image

dom-gunstone commented 2 months ago

Holding the middle button doesn't turn on or off the clock. It just enter or leave the onscreen Menü.

Double press turns only the matrix on or off, Awtrix still runs.

Holding left and right switches the power completely on or off.

I probably held the left and right button. It's one of those things that's so infrequent I don't remember the correct way to turn it back on.

Just to be clear, my clock was definitely off. Interestingly, before powering down I saw a decrease in battery level to around 30%. Then when I powered it back on it was about 60% and continued increasing to around 90%. I wonder if I'm having issues with the power supply I'm using. I'll try a different one and see if I have any future issues.

Edit: here's my battery level over a few days (the gap is where the clock was off): image

Blueforcer commented 2 months ago

Just to be clear, my clock was definitely off. Interestingly, before powering down I saw a decrease in battery level to around 30%. Then when I powered it back on it was about 60% and continued increasing to around 90%. I wonder if I'm having issues with the power supply I'm using. I'll try a different one and see if I have any future issues.

The software itself isn't able to shut down the clock because there is no physical connection to the power board. Seems like the battery runs out of power. The battery reading can be inaccurate because there are different clock batches out there with different analog resistors and batteries. You can set you own min and max readings with the dev.json

dom-gunstone commented 2 months ago

I assume your power supply is just not strong enough