Sensor not seen in Home Assistant

Configuration
1

I have some sensors where I can read the contents via a json.

In my configuration.yaml I have sensor: !include sensors.yaml
In my sensors.yaml I have:

  - platform: rest
    resource: http://xxx.xxx.xxx:51/json
    method: GET
    name: "Temperatuur"
    value_template: '{{ value_json["Sensors"][0].TaskValues[0].Value | int }}'
    scan_interval: 60

I have validated my configuration and I know that the value_template is correct.

However after restarting the sensor does not appear in the STATES of Developer Tools.

Can someone tell me what I do wrong?

2

What does your log show?

3

Timeout fetching Waterval data

19:48:31 – (ERROR) Shelly - message first occurred at 16:43:46 and shows up 25 times

Licht in de bijkeuken aan.: Already running

19:01:54 – (WARNING) Automation - message first occurred at 16:42:15 and shows up 5 times

Licht in de gang aan: Already running

17:35:49 – (WARNING) Automation

YAML file /config/configuration.yaml contains duplicate key “sensor”. Check lines 6 and 53

17:33:11 – (WARNING) util/yaml/loader.py - message first occurred at 17:23:57 and shows up 5 times

Error handling request

17:24:21 – (ERROR) /usr/local/lib/python3.9/site-packages/aiohttp/web_protocol.py

device 192.168.178.104 initialize error - TimeoutError()

16:39:54 – (WARNING) /usr/local/lib/python3.9/site-packages/aioshelly/block_device.py - message first occurred at 16:39:50 and shows up 3 times

Config entry ‘EPSON WF-3720 Series’ for ipp integration not ready yet: Invalid response from API: Error occurred while communicating with IPP server.; Retrying in background

16:39:36 – (WARNING) config_entries.py - message first occurred at 16:39:29 and shows up 5 times

Loading enphase_envoy via platform config is deprecated; The configuration has been migrated to a config entry and can be safely removed

16:39:25 – (WARNING) Enphase Envoy

[140223101043520] Received invalid command: mobile_app/push_notification_channel

16:39:21 – (ERROR) Home Assistant WebSocket API

4

Solved. Your remark about the log brought me to a problem in the configuration.yaml.

1 Like