That still image URL opens the live stream in VLC…
The URL’s are from the Hikvision website
I think that is your issue right there. Looking at this PDF from hikvision I would say try changing rtsp to http for still_image_url. Test this in a browser and make sure the snapshot works, once it works there the service call will work as expected.
Using what is in that doc for snapshot doesn’t give me anything in VLC.
Use a browser instead of VLC for the snapshot
Then it must not be the right format, Try this format: "http://user:[email protected]/ISAPI/Streaming/channels/101/picture" taken from Stream Component: Confirmed Cameras and Configurations
Unfortunately that doesn’t work either.
Try to switch to ffmpeg maybe or find a valid URL to use, your issue is actually not HA related because the URL is not working. FFMPEG should take the snapshot from the stream itself since you know that works.
snapshots work with this! I guess that is my best solution then
EDIT: however this only seems good for the snapshot as it doesn’t give me a live feed in Lovelace, only updated stills every 10 seconds. At least I can use the snapshot though, thanks
I actually got this working. Ingress is the problem point.
If you change the port in the Networking section of the integration settings… you then directly connect to motion eye rather than through Ingress. (192.168.1.12:new port #)
Creating the snapshot link from within that direct connection can be then embedded into a notification directly.
Did you find a solution for this delay? I have the same thing when my phone is in a deep sleep mode.
with the ttl setting and priority its better, not 100% , but good enough
pushover is still faster in deliver
Having issues with sending/receiving images to my Android phone. Text is not a problem, this functions properly. I suspect its something silly with my url or simply the fact that I’m not working from the front end of HA and don’t have the html5 platform running or whatever else is required? (please advise exactly what needs to be enabled in my configuration.yaml if this in fact the issue).
camera.snap takes a photo and stores it in config/www folder no worries.
I can see the photo if I go looking for it.
However I can’t seem send the photo using the services dev tool.
Following the instructions on the companion home site, I should be table to send the photo stored in my www folder simply by entering the following into the services dev tool and calling on that service
‘image: http://homeassistant.local:8123/local/www/doorbell.jpg’
However this does not work, nor does any variation of it (including using the lattepanda’s IP address).
The error log I’m seeing is:
Logger: homeassistant.components.websocket_api.http.connection.139772516711120
Source: core.py:1210
Integration: websocket_api (documentation
I’m running HASSIO on Virtualbox (LINUX) from a lattepanda.
Can someone advise how to get this up an running or what I’m doing wrong exactly. I see that many people have it up and running so what am I missing?
Many thanks!
this should be image: http://homeassistant.local:8123/www/doorbell.jpg
Thanks for the speed of reply. I wish it were that straightforward. Still the same error: websocket_api…
I thought I’d send you the full monty (config, the automation, and the HA automaton) but new users can only attach one image…So my yaml config is below for your consideration.
!
The alternative is to install Blue Iris and Mosquito MQTT and be done with it. The end game is to link up 5 cameras around the house. Let me know what you think would be the best given the long term objective.
If I push the button on the webcam I receive the notification ‘message’, but no image…
Many thanks.
can you show the full YAML that you are using?
Sure.
Config:
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
# base_url: example.duckdns.org:8123
# Text to speech
tts:
- platform: google_translate
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
#frontend enabled
frontend:
# Whitelist Folders
homeassistant:
whitelist_external_dirs:
- /config/tmp
- /config/www
- /config/www/doorbell
Automation:
- id: '1586363068403'
alias: Someone is at the front door!
description: Doorbell
trigger:
- device_id: 4fc3dfceb3bd485bbe46664931b8c3d8
domain: binary_sensor
entity_id: binary_sensor.test_esp32cam_button
for:
hours: 0
minutes: 0
seconds: 1
platform: device
type: turned_on
condition: []
action:
- data:
entity_id: camera.test_esp32cam_camera
filename: www/doorbell/doorbell.jpg
service: camera.snapshot
- delay: 00:00:03
- data:
message: Someone is at the front door
service: notify.mobile_app_sm_g930f
- data:
image: http://homeassistant.local:8123/www/doorbell/doorbell.jpg
service: notify.mobile_app_sm_g930f
Many thanks.
This should be
- data:
message: Message goes here
data:
image: http://homeassistant.local:8123/www/doorbell/doorbell.jpg
service: notify.mobile_app_sm_g930f
You were missing one nested data entry, see here for more info on the proper YAML to use: Standard Attachments | Home Assistant Companion Docs
Excellent, the websocket_api error is long gone!
But still no photo on the android…The message shows up on the lock screen sans photo.
I’ve restarted the HA server and also the phone + restarted the app. Still nada.
Maybe a setting in the app?
Aaron
The image actually needs to be publicly accessible via the URL can you try /local/doorbell/doorbell.jpg instead for the path?
Sorry I should’ve mentioned that earlier but its also mentioned in the docs that I linked to.