Philip Heyde

Results 7 comments of Philip Heyde

I can confirm I am experiencing the same issue with the Home Assistant MQTT output. I am in Denmark, and am using a Kamstrup meter. I can locate more information...

If it helps, this is the MQTT data received by Home Assistant from AmsToMQTT version 2.1.5: `{ "lv": "", "id": "", "type": "", "P": 468, "Q": 0, "PO": 0, "QO":...

Ok, that makes sense. But the errors actually happen every ~10th second, according to the HA log, so I think it has something to do with this payload. But I'll...

Could the problem be that the lu-value is not in quotation marks? Wrong string: {"tPI":60762.74,"tPO":0.00,"tQI":226.31,"tQO":10839.35,"rtc":lu} Possibly correct string: {"tPI":60762.74,"tPO":0.00,"tQI":226.31,"tQO":10839.35,"rtc":"lu"}

YES! That seems to work! There are no more errors in the HA log, and the payload can be parsed now: ![image](https://user-images.githubusercontent.com/368480/184842653-9d8b113e-34a9-4e03-8031-c40a289c4c8b.png) It'll take a while before this is reflected...

For me, it was solved by enabling Websocket support in my Nginx reverse proxy. No additional settings for the websocket/proxy were needed.