HA EmonCMS History - sensor name too long?

Integrations
1

Hi all,

Trying to add a sensor as input from HA via the EmonCMS History integration. I’ve added two successfully and passed them as feeds through to my ASHP app (outdoor temp and current room temp), but trying to add a 3rd it seems to be crashing the integration. It’s from the Vaillant integration and is for populating the current target room temp. When I have it uncommented below, I can’t see any errors in the logs on HA, but the feeds from the integration on emonCMS stop updating.

emoncms_history:
  api_key: XXXXXXXXXXXXXXXXXXX
  url: https://emoncms.org
  inputnode: 19
  whitelist:
    - sensor.gw2000a_outdoor_temperature
    - sensor.lonners_zone_heating_circuit_0_current_temperature
#    - sensor.lonners_zone_heating_circuit_0_desired_heating_temperature

Is the last commented out one too long? Or any other issues that might stop it coming over to emon?

2

Might have answered my own question, I found there as a similar sensor.lonners_zone_heating_circuit_0_desired_temperature, which I’ve since used and its found its way to emon.

1 Like