{ Success: false, ErrorMessage: ""}
2023-05-26 08:41:25.807 WARNING (MainThread) [homeassistant.components.rest.sensor] REST result could not be parsed as JSON
2023-05-26 08:41:25.894 DEBUG (MainThread) [homeassistant.components.rest.sensor] Erroneous JSON:
Then the text becomes a bit longer when I try to explain it:)
MELCloud is Mitsubishi Electric’s cloud service for controlling air conditioners and heat pumps.
I have a heat pump on it.
The MELCloud is also available as an integration in HA.
The problem is that MELCloud receives more data than is displayed to the “normal” user.
For example, only the flow temperature and return temperature are displayed.
Now comes the point where the REST sensors are used.
When I log in to the homepage via Firefox or Chrome, I can call up the HTML code of the page via F12.
There you can access information such as: Defrost time, Compressor frequency, Compressor working time.
I have commented out the # for testing purposes, so only the “Current Energy Consumption” is queried.
I have explained this in this thread:
Further up in this thread I posted my config.
The X-MitsContextKey: makes access and identification possible for HA to evaluate the MELCloud data, actually more of an authentication code.
In my config above, everything is with big XXXXXX user related data, ex.
Device ID.
Well, one way or another you need to see what the rest sensor is getting back. If it’s that success: false error message, then the problem is with your authentication.
Try commenting out the attribute line and use:
value_template: "{{ value[:240] }}"
The sensor state will then be the first 240 characters of the response, which might help work out what’s going on.
Hey,
if I replace “value_template” with your code, HA doesn’t find the sensor anymore and it is “unavailable”.
So I don’t get any useful data out here either
Why are RESt sensor errors so difficult to detect -.-
The log does not say anything different than before.
I think it has something to do with Mitsubishi Electric and not with HA or do you think otherwise?