Rest sensor config doesn't initialize in 101.2

@Mariusthvdb wrote:

HI,

not sure where to look for breaking changes, but this sensor doesn’t show anymore:

  - platform: rest
    name: Hassio Rpi4 config
    resource: !secret resource_hassio_rpi4_config
#    authentication: basic
    value_template: >
      {{ value_json.version }}
    json_attributes:
      - components
      - unit_system
      - config_dir
      - version
    headers:
      Content-Type: application/json
      Authorization: !secret api_bearer_token
      User-Agent: Home Assistant REST sensor

which of the breaking changes could be responsible for that? don’t fully grasp the authentication change, but suspect it to be causing this? If so, how to mitigate it?
thanks for having a look.

this is in the logs:

Error fetching data: <PreparedRequest [GET]> from https://redacted/api/config failed with HTTPSConnectionPool(host='redacted ', port=redacted): Max retries exceeded with url: /api/config (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0xaeffe630>: Failed to establish a new connection: [Errno 111] Connection refused'))

also:

Platform rest not ready yet. Retrying in 30 seconds.

and finally:

REST result could not be parsed as JSON

in the end, it might also be responsible for this auto ip-ban:?

Banned IP 192.168.1.1 for too many login attempts

which is a real pain…

Posts: 1

Participants: 1

Read full topic