Telegram, camera_proxy and trusted networks

@tachioma wrote:

On version - 0.101.3
I’ve neglected it recently so I thought I’d update go through trim out any old config and rectify a few issues.
The only one i’m struggling with now is my cameras.

I have 4 cameras as entities and they work great. i did have a few automations setup for a state change on the doorbell or front door based on presence -> telegram push of images grabbed from the cameras.

data:
  photo:
    url: >-
      https://MYURL:8123/api/camera_proxy/camera.front_door?api_password=MySuPeRSeCreTPassWoRd
message: 'Time seen {{ as_timestamp(now()) | timestamp_custom(''%H:%M'', true) }}'
title: Front Door Opened!

This seems to have stopped working at some point. Hitting that URL directly doesnt work either (401: Unauthorized) so i assume legacy_api_password is depracated now.

A quick browse around the forums seems to suggest i should be using :
trusted_networks to combate this

homeassistant:
  customize: !include customize.yaml
  auth_providers:
#    - type: legacy_api_password
#      api_password: MySuPeRSeCreTPassWoRd
    - type: trusted_networks
      trusted_networks:
        - '127.0.0.1'
        - '192.168.169.0/24'
      allow_bypass_login: true
      trusted_users:
        192.168.169.0/24: d9e5b06fbef340e9b436172c90f31a8c
        127.0.0.1: d9e5b06fbef340e9b436172c90f31a8c

However, I’m still receiving 401’s

more searching the forums -
If I fire up postman and hit https://MYURL:8123/api/camera_proxy/camera.front_door? using a newly generated LLT with the authentication set to bearer and it works. Do we have an example of how this should be formatted? I see a fair few questions about this and no full answers.

Thanks!

T

Posts: 2

Participants: 2

Read full topic