The url I am using to get the screenshot of the Dashboard using the recommended Puppet works perfectly if posted into a browser and dutifully creates 1 800x480 black and white version without issue.
But the ESPHome is just chugging up against this error and I have no idea how to fix it.
Anyone got any ideas?
This is trying every 30 seconds.
I have high hopes this ePaper display will actually do something because at the moment it is just being a ePaperweight
By putting the Home Assistant and ePaper Display (ESPHOME device) on the same vlan fixed it.
Weird thing is they ONLY way to do this, because with the ePaper on the same vlan I could no longer update the esphome device over wifi and had to install the yaml by having the paper device connected by usb to my computer.
But hey it is working and now I can focus on getting the dashboard better and the screen will reflect whatever I put on there
I am continuing to play with it. It may not be a vlan issue after all.
I am looking at why updates using wifi don’t work any and I get a connection refused
BUT if I update manually using a USB cable between computer and esphome device does work and no connection refused when getting the png file from Home Assistant.
The reason I noticed was because when I switched Home Assistant and esphome device to the same vlan I could no longer connect to the esphome device over wifi and had to do a manual install.
Might be a stab in the dark, however recently i noticed that a full reboot is sometimes needed after updating the configuration. Flashing it via USB might have triggered just that.
Based on your explanation however, it is not logical that the network itself would not form some sort of bottleneck though…
If you want something pleasing to play with and learn, pick Esp Wroom32 board.
If you want to challenge yourself find some Tuya device that uses large quantity of undocumented components like port expanders etc…