How to debug a JSON/REST-Sensor?

Configuration
1

Hi,
I’m getting my first experience with a REST-sensor, using a XML-API. I’ve read a lot about XML to JSON, the JSON-Path and some more but all my attempts went wrong. So I’d like to start at the root.

Is there any way to get the raw data from the sensor or any error log?
Like

  - resource: "http://192.168.0.1/config/xmlapi/state.cgi?device_id=18854"
    scan_interval: 60
    sensor:
      - name: "My Test"
        unique_id: "my-test"
        #value_template: "{{ value_json.state.device.channel[2].datapoint[5]._name }}"
        value_template: "{{ value_json }}"

The current value of the sensor is “unavailable”.
Before spending more time in the json-path, I’d like to check, if the XML file is correct and converted to JSON (curl via terminal works, I got the raw XML content).
Can I put the raw content to the value of the sensor?

Additionally I’ve startet the debug mode:

logger:
  logs:
    homeassistant.components.rest: debug

But where can I see the details, now?

Thanks for your support!

2

As long as it is less than 255 characters this will return the raw value:

value_template: "{{ value }}"
3

After enabling debug mode, call homeassistant.update entity service to trigger refresh and check logs (not error logs)

4

Hi,
unfortunatly the xml/json-result will be quite more than 255 chars :frowning:
What you mean by “not error logs”? I know the logs at Settings → System → Logs, only. Are there any more log files?
Should I learn something again today…?
Thanks!

5

There are two sections on that page. First section shows warnings and errors but debug logs are printed in second section down below with all other information. It is actually full home assistant log and you can download it to your desktop and search through it

6

Hi, thanks once more for your support!
I didn’t know (or saw) that there is a detailled log for downloading.
First, there was a message about 255 characters… OK. But then I was able to validate the JSON Path and at the end I saw the problem: it was just a character, which was unexpectedly encoded.

Now everything is fine, my JSON-Path works and I’m happy.

1 Like