Closed megawubs closed 2 years ago
What firmware version are you running on the M5stack?
Try an url without https. Just plain http://
What firmware version are you running on the M5stack?
I'm running version 0.6.1 on the M5Stack.
I'll try an non https url later today.
That service needs 0.6.2-development and preferably an ESP with PSram to work. You can grab the latest build from the Actions tab on Github.
I am just developing a media player interface and this works to get the cover image from my media_player. Yoohoo.
I have a question though, is the url templatable?
EDIT Well I can answer that myself, yes it is. http://hass.lan:8123{{state_attr('media_player.kitchen', 'entity_picture')}}
I am just developing a media player interface and this works to get the cover image from my media_player. Yoohoo.
I'm also building a media player interface! Nice to know that this will work. Haven't had the time to look into this yet.
I would like to see your take on a media player interface, do you want to share it? I don't think this issue is the right place for it. Are you on the Home Assistant Discord channel?
Try OpenHASP discord channel instead: https://discord.gg/BNG7mpNW
After pushing a few images successfully, new images that are being pushed become distorted. Is this something with openHASP or is this part of this custom component?
The screenshot below explains it all.
What do you see in the log file?
You should see something like:
[21:18:34.690][88624/91052 2][38336/38836 2] MQTT RCV: hasp/plate01/command/p1b15.src = http://home-assistant.local:8123/api/openhasp/serve/419764c4d81ca01c73307e1dd16274bb
[21:18:34.753][79024/82012 3][38336/38836 2] ATTR: HTTP OK: buffer created of 8196 bytes
[21:18:34.771][79024/83308 5][38336/38836 2] ATTR: * HEADER READ: 4 bytes w=64 h=64
[21:18:34.807][79024/86856 9][38336/38836 2] ATTR: * HTTP READ: 7176 bytes
[21:18:34.823][79024/88612 10][38336/38836 2] ATTR: * HTTP READ: 1016 bytes
[21:18:34.837][79024/88612 10][38336/38836 2] ATTR: * HTTP TOTAL READ: 8196 bytes, 8196 expected
Can you download the src
file and share it?
It only happened a few times. Since posting the issue it didn't happen again
I am just developing a media player interface and this works to get the cover image from my media_player. Yoohoo.
I'm also building a media player interface! Nice to know that this will work. Haven't had the time to look into this yet.
I would like to see your take on a media player interface, do you want to share it? I don't think this issue is the right place for it. Are you on the Home Assistant Discord channel?
No, don't really do discord!
Well I have not developed much yet, and it probably won't be very good! I have a particular need, fat fingers and a controller for next to the spa pool. I intend to only have play, pause and volume functionality, as well as the image of the album cover. The rest I will probably set up from a tablet or PC before going to the spa in the evening.
Version of the custom_component 0.6.3
Configuration
Describe the bug
I'm unable to push an image to an image obj on my m5stack core 2. It doesn't matter if I add a url or path from /littlefs/*.png. The initial image is shown, but i'm unable to update it.
Debug log