Thanks but this doesn’t work still. I think you’re referencing the wrong part of the api? It’s not under smart_results it’s in the first part of device.device_status
Hehe you are right it should like be {{ "on" if value_json.data.device[0].device_status in [1, 2] else "off" }} I’m not at my computer so did not test it
Just curious, I have an nvme drive(Samsung 970 evo) that scrutiny says has failed test. It has 520 media errors.
I replaced this drive with a brand new drive (Samsung 980 pro) and scrutiny says it has still failed with 520 media errors… (even though the drive name had changed in the report)
Any ideas what’s going on / how to refresh the report?
There is something weird going on with the ports in the addon. Ingress wasn’t defined. But if I do, it doesn’t save? I changed to the host IP and the template worked when I changed it to:
rest:
- verify_ssl: false
scan_interval: 60
resource: http://my.local.host.ip:8086/api/device/aa235110163/details
binary_sensor:
- name: "SSD - System SMART Status"
value_template: "{{ 'on' if value_json.data.device.device_status in [1, 2] else 'off' }}"
device_class: problem
unique_id: SSD System SMART Status
- verify_ssl: false
Hi, if you use ingress and disable the external port the API is likely exposed through the ingress url based on the homeassistant port. Anyway most important thing is that it works
Hi, not all ssd support smart as I as surpsied to learn ; does yours? The add-on should have in theory max permissions, and I guess you tried also the full access version
I recently found that the addon is not working anymore in a remote installation
The plugin is NOT running and if I try to start it the whole system becomes unresponsive (I’m using tailscale for remote access) and I can only remotely reboot the raspberry using a WiFi power socket
The update function is not working for me. I have set to “hourly” but it never does.
I am using the collector spoke option since I have a docker hub running on another server within the same local network.
I am running Full Access scrutiny addon.
I heard from several non-related addons similar elements. I think something is messed up in HA itself since a recent version, but this happened on such different addons (qbittorrent ; *arr addons ; this one) that the only common point is HA itself …
There was indeed an issue upstream with Scrutiny itself which gave this issue, then was solved and the issue went away. As my own code didn’t change and it was working before perhaps it’s again the upstream app ?