You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an LXC Debian container that is used to process local apps with Home Assistant integration. Pixlet renders the star file and then pushes the webp image to the Tidbyt. This has been working great for over a year, but yesterday things stopped working.
I found that pixlet render and pixlet serve are failing to open the correct star file unless there are no other star files in the folder.
In the above example, I asked pixlet to render 'ha_now_playing.star' but it is trying to read HA_sonos.star which is the first file in the directory listing. I don't know why it's trying to open the first file available, or why the error says the file doesn't exist when it does.
The workaround has been to put every .star file I need in its own subfolder, so that it is the only .star file in there.
I had been running version 0.29 of pixlet, but upgrading to the latest 0.33.3 version made no difference.
The text was updated successfully, but these errors were encountered:
I have an LXC Debian container that is used to process local apps with Home Assistant integration. Pixlet renders the star file and then pushes the webp image to the Tidbyt. This has been working great for over a year, but yesterday things stopped working.
I found that pixlet render and pixlet serve are failing to open the correct star file unless there are no other star files in the folder.
In the above example, I asked pixlet to render 'ha_now_playing.star' but it is trying to read HA_sonos.star which is the first file in the directory listing. I don't know why it's trying to open the first file available, or why the error says the file doesn't exist when it does.
The workaround has been to put every .star file I need in its own subfolder, so that it is the only .star file in there.
I had been running version 0.29 of pixlet, but upgrading to the latest 0.33.3 version made no difference.
The text was updated successfully, but these errors were encountered: