REST sensor to 2nd HA instance / attributes not effective

[plo53]

Hello,

I am implementing a rest sensor to connect a remote HA “slave” entity to my main instance.

sensor:
  - platform: rest
    resource: https://IP:8123/api/states/sensor.philips_aj7010
    name: Philips AJ7010
    unique_id: aj7010_1
    value_template: '{{ value_json.state }}'
    json_attributes:
      - attributes
    headers:
      Authorization: Bearer ...

The sensor’s attributes seem correct in my main HA instance, the state_class, the unit, …, are well defined:

However, I cannot get a History curve card, only a state bar ?

To enable a History curve, I have to redefine the state_class into the rest sensor definition:

sensor:
   - platform: rest
     resource: https://IP:8123/api/states/sensor.philips_aj7010
     name: Philips AJ7010
     state_class: measurement
     

What can be wrong ?

Thx

[Troon]

@plo53

    json_attributes:
      - attributes

I don’t think this is doing what you think it is.

[koying (Chris B)]

I created (and still use) an integration to do “master/slave” HA through MQTT:

MQTT DiscoveryStream integration

This is an “extension” (and compatible replacement) of the builtin mqtt_statestream integration. Besides the functionalities of the here-above, it also allows to publish and handles an MQTT “disvovery” setup. This is specifically useful in “Master-Slave” HA scenarios. A “slave”, by instance a specific HA instance handling zigbee and / or Bluetooth, would use this component to publish states and discovery via MQTT. A “master” would use the built-in MQTT discovery mechanism to subscribe to sta…

It handles all this automagically