HungrySkeltal
Dabbler
- Joined
- Apr 17, 2020
- Messages
- 11
Hi all - I've been rolling with my FreeNAS for about a year now and am loving it.
Since upgrading to 11.3, I've been going through and upgrading my HomeAssistant sensors to start reading from the new v2.0 API instead of the old v1.0 API.
I've managed to navigate the new REST API for everything I need (disk temps, alerts, etc) with the exception of two points:
1 - the CPU temp. Is anyone able to point me what API call I should be making to find this?
2 - the health of a pool. API 1.0 returns a status of 'HEALTHY'/'DEGRADED' etc. However it appears that the new API has switched to reporting the status as 'ONLINE', (and there is an extra field showing a flag of "healthy = true"). I'm concerned that reading the 'ONLINE' status won't change even if a pool becomes degraded. If a pool does become degraded, is the only warning of this the "healthy = false" flag? or am I missing another field in there somewhere which specifies healthy/degraded? I am using this command: http://192.168.XXX.XXX/api/v2.0/pool
Thanks in advance!
Since upgrading to 11.3, I've been going through and upgrading my HomeAssistant sensors to start reading from the new v2.0 API instead of the old v1.0 API.
I've managed to navigate the new REST API for everything I need (disk temps, alerts, etc) with the exception of two points:
1 - the CPU temp. Is anyone able to point me what API call I should be making to find this?
2 - the health of a pool. API 1.0 returns a status of 'HEALTHY'/'DEGRADED' etc. However it appears that the new API has switched to reporting the status as 'ONLINE', (and there is an extra field showing a flag of "healthy = true"). I'm concerned that reading the 'ONLINE' status won't change even if a pool becomes degraded. If a pool does become degraded, is the only warning of this the "healthy = false" flag? or am I missing another field in there somewhere which specifies healthy/degraded? I am using this command: http://192.168.XXX.XXX/api/v2.0/pool
Thanks in advance!