Json_attributes_path: "$.data.smart_results" So looks like the information is available. Clicking the link gives me a list of datapoints. I used the below example and updated IP and ADDONPORT accordingly. The sensor only shows “OK” and no value at all. Which seems that the json attribute path is incorrect. JSON result was not a dictionary or list with 0th element a dictionary. Unfortunately I can’t get it working to show me the data. But I would like to setup a sensor for warning purpose for specific data points, such as LBA written, power-on-hours or endurance remaining. The Add-on is great and shows me all the necessary data in the dashboard. I hope you can help with an issue I have with Scrutiny. (3) Protection mode must be disabled in scrutiny (full access) otherwise it will not be able to get SMART data for the same reason. Docker scrutiny is already a member of the group “ disk” so technically there should not be a problem but it does not get permission to get to the hardware. and (2) scrutiny retrives SMART data only in full access mode otherwise it will generate similar error as above. So important here is to set device type sat and do not leave it auto. Time="" level=info msg="Sending detected devices to API, for filtering & validation" type=metrics Time="" level=error msg="Could not retrieve device information for sda: exit status 2" type=metrics Time="" level=info msg="Executing command: /usr/sbin/smartctl -info -json -dev auto -device sntrealtek /dev/sda" type=metrics Time="" level=info msg="Executing command: /usr/sbin/smartctl -scan -json -dev auto" type=metrics I could see while debuging that auto device type was selecting sntrealtek automatically internally and log was generatting following error time="" level=info msg="Verifying required tools" type=metrics Finally after debugging a lot and entering inside grafana’s container, I managed to get smart data from scrutiny as below (no wonder I see my SMART data failed as there was some issue but I rectified it now.) I am using HA on Rpi-4b model and SSD is connected through NVMe enclosure (Realtek RTL9210B chip) so now learned that scrutiny (full access) works just fine on Rpi-4.Ĭouple of important things, I’d like to mention here to get scrutiny working: (1) My SSD enclosure chip is Realtek RTL9210B so scrutiny (as per smartmontools) I should get SMART data if I set smartctl_command_device_type to auto or sntrealtek but it does not work that way probably because old kernel does not support.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |