Thank fmb you for this link, this explane’s mist of my quistions. Im goiing to try this.
Did it work as intended?
Im sorry, ik did not had the motivation to try-out this. Sorry, i ll let you know.
Verzonden vanaf Outlook voor Android
1 Like
Installed today, up and running in like 3-4 minutes. Thanks
This is not my experience. Have you tried pushover website? You can send a message there as well.
I installed the app on my Homey shs. Text messages are working, but when I add an image it gives a 404 error in the flow step.
Sending the same image as a native Homey push message (in the same flow) is working, so the tag is working.
Any thoughts?
Hmmm can you send a screenshot of your flow - maybe I can spot an possible issue.
How about the size of the image - could that be an issue?
I did have an issue at some point myself, but that was the source/tag that had a flaw - had to restart my homey for it to work again. Not saying that this will help you.
The red line under a flow card indicates there’s an error, you can connect a card to send it to the timeline for example or hover your mouse over it. The actual (exact) error can help a great deal to troubleshoot this!
I know. It’s a 404 error on all three failed actions. The one blue underlined action succeeded with the same image tag.
Hi @EdP
Do you by chance know the size of the image that you are trying to send? Could be size too large (bytes/pixels)
Can you please try the card without emergency and expiration.
I’m getting a very similar error with a very basic flow that I’ve just created. Replacing with a pushover notification with no image works fine, as does sending the image via Homey’s native app.
Hi @Kim_Kokholm
I grabbed a similar image from the developer tools. A camera snapshot is 213 KB in size.
I’ve amended the flow to reveal the error message: connect ECONNREFUSED HomeySelfHosedServerIP:80
This is with a Blink doorbell, in case that’s relevant.
Hi are you both using Self Hosted?
I’m using Homey device and it’s working just fine.
I’m using this flow:
Looks more similar to @BigSniffer example.
I did some debugging as well, way back, where I also testet if the image/token worked with “native” notification.
It’s a bit difficult for me to replicate your setup.
How do you guys suggest we approch this?
I don’t know if you can access the log, if I make a new test version where I write the whole request to log…
Yes, I’m using the latest release Homey Self-Hosted Server on a Raspberry Pi (Homey distribution).
I have a Blink doorbell which is integrated using the Blink for Home app ( Blink for Home | Homey ).
Very happy to help debug with logs files etc. but I’m not the most technical so will need some handholding.
Sorry, how do I access that image file?
I’ve done the next-best thing, which is to use another available file (album art from the speaker in the lounge) with this result:
It works fine with the Mobile card.
Please install the app:
I just want to make sure that the image is correct.
One thing is communication with Pushover another is the image - how this is accessed. It’s called a token in Homey.
