cURL/JSON sensor unique id - can see it in HA, but entity 'unmanageable'

Hi there - hoping someone might be able to help me please with a cURL sensor from a server. I followed this guide to use lm-sensors to send a cURL command with a long-lived access token to HA: https://smarthomescene.com/guides/easy-way-to-monitor-proxmox-host-temperatures-in-home-assistant/
It works in that I can see the output. However, HA says the entity is unmanageable because it’s not got a unique ID. But there is a unique ID, it shows it under Attributes.
Or is this wrong? Is this not what a ‘unique ID’ is and is this just a useless attribute because the JSON is formatted wrongly? If so, where should unique_id appear in the cURL payload?
Any help anyone can lend would be gratefully received!
Many thanks.

Wow that’s a lot more mucking about than just installing Glances from a helper script.

1 Like

Yes! But I found Glances used a lot of processing power, which is in short supply on the machine I’m monitoring unfortunately. If there’s a better way that’s also lightweight, I’m all ears!

1 Like