Yes indeed! I was looking if scrutiny can also monitor other servers. Do you know? Because currently I run HA on a raspberry pi. But I have a self-build NAS based on unraid with several harddisks. I was researching if I could run HA on unraid which seems possible. Still not sure if I should run HA in a VM or docker. But also wondering how scrutiny would fit in this case.
Well the collector can get data from several servers but the Scrutiny server needs to be run from each instance as I understand from the Scrutiny github. I’m no experts on those systems so I can’t really comment but I think running directly HA through docker is what is called a supervised installation, which can cause more issues. Running through the VM would run HA os I suppose which can allow a system more stable
Good luck!
1 Like
Thanks for the suggestion. I’ll make sure to look into it further.
1 Like
Hi, I’ve checked and this info is not reported.
Actually, here is a real life example that is referenced on Google that you can use to check how it looks like : scrutiny
1 Like
Hey,
Tried to install this add-on, but failed with following error message (when addon ‘install’ button is clicked):
Failed to to call /addons/db21ed7f_scrutiny/install - The command '/bin/sh -c chmod a+x /run.sh && sed -i 's/bash/bashio/g' /etc/cont-init.d/10-adduser && sed -i 's/{PUID:-911}/(bashio::config "PUID")/g' /etc/cont-init.d/10-adduser && sed -i 's/{PGID:-911}/(bashio::config "PGID")/g' /etc/cont-init.d/10-adduser && sed -i 's| /config| /data|g' /defaults/scrutiny.yaml && sed -i 's| /config| /data|g' /etc/cont-init.d/* && sed -i 's| /config| /data|g' /etc/logrotate.d/scrutiny && sed -i 's| /config| /data|g' /etc/crontabs/root && grep -rl '/web/' /app/scrutiny-web/ | xargs sed -i 's|/web/|./|g'' returned a non-zero code: 1
I’d like to pull data from my other server located in same lan (running Scrutiny) and use it in my Home assistant dedicated box. Am I missing something obvious?
HA version: core-2021.12.7
Supervisor version: supervisor-2021.12.2
1 Like
Thanks for reporting, indeed it’s a bug I’ve solved it and pushed a new version named -4 it should work now!
1 Like
I’ve allowed full access in the addon. There is only one user case : when HA boots from HDD it blocks access to the /dev device. In all other cases, you can disable full access and it will work fine!
Hello, is there anything I should configure in the add-on for it to work? I installed the full access version (I am using the external HDD as datadisk), but the UI is empty (no disks and nothing works) and the log shows the following error:
time="2022-03-11T20:56:52+01:00" level=info msg="Verifying required tools" type=metrics
time="2022-03-11T20:56:52+01:00" level=info msg="Executing command: smartctl --scan -j" type=metrics
time="2022-03-11T20:56:52+01:00" level=info msg="Executing command: smartctl --info -j -d sat /dev/sda" type=metrics
time="2022-03-11T20:56:52+01:00" level=error msg="Could not retrieve device information for sda: exit status 2" type=metrics
time="2022-03-11T20:56:52+01:00" level=info msg="Sending detected devices to API, for filtering & validation" type=metrics
time="2022-03-11T20:56:52+01:00" level=info msg="127.0.0.1 - db21ed7f-scrutiny-fa [11/Mar/2022:20:56:52 +0100] \"POST /api/devices/register\" 200 413 \"\" \"Go-http-client/1.1\" (3ms)" clientIP=127.0.0.1 hostname=db21ed7f-scrutiny-fa latency=3 method=POST path=/api/devices/register referer= respLength=413 statusCode=200 userAgent=Go-http-client/1.1
time="2022-03-11T20:56:52+01:00" level=info msg="Collecting smartctl results for sda\n" type=metrics
time="2022-03-11T20:56:52+01:00" level=info msg="Executing command: smartctl -x -j -d sat /dev/sda" type=metrics
time="2022-03-11T20:56:52+01:00" level=error msg="smartctl returned an error code (2) while processing sda\n" type=metrics
time="2022-03-11T20:56:52+01:00" level=error msg="smartctl could not open device" type=metrics
time="2022-03-11T20:56:52+01:00" level=info msg="Publishing smartctl results for \n" type=metrics
2022/03/11 20:56:52 /app/scrutiny/webapp/backend/pkg/web/handler/upload_device_metrics.go:31 WHERE conditions required
time="2022-03-11T20:56:52+01:00" level=error msg="An error occurred while updating device data from smartctl metrics WHERE conditions required"
[0.388ms] [rows:0] UPDATE `devices` SET `created_at`="2022-03-11 20:50:25.712",`updated_at`="2022-03-11 20:56:52.816",`device_name`="sda",`device_type`="sat"
I am using the Home Assistant Blue with external SSD, everything updated to latest version.
1 Like
Hi, are you sure you disk supports smart? Lots of ssd don’t have smart support
And are there error messages in the Supervisor log?
Hi, I’ve pushed a new version (16) that works with full access actually I still needed to leave priviledged permissions despite full access
I think it does support SMART. It is an external NVME enclosure with JMicron chip. I am mainly interested in the temperature. There is another addon which also does not work for me, because they have to merge a change allowing special parameter for JMicron devices. Do you think it may be relevant for this addon as well?
I do not see any errors in the Supervisor log.
1 Like
Hi, actually I found the issue and have solved it in the v16 version just wait for it to be available and let me know! Have a nice afternoon
I’ve seen the link that you propose with adding the device type but for that it should be implemented in the Scrutiny app itself, I can’t add it in the addon as it is only a shell around the app
Mmh strange but then if there is a modification required in the source app (scrutiny) as you described, I won’t be able to help you… The best solution would be to open an issue on scrutiny’s github here… GitHub - AnalogJ/scrutiny: Hard Drive S.M.A.R.T Monitoring, Historical Trends & Real World Failure Thresholds
1 Like
I don’t know why, but I’m getting this error with the current version (both with normal and Full Access), that I didn’t had with 0.3.13. So I can’t reach the Web interface.
___ ___ ____ __ __ ____ ____ _ _ _ _
/ __) / __)( _ \( )( )(_ _)(_ _)( \( )( \/ )
\__ \( (__ ) / )(__)( )( _)(_ ) ( \ /
(___/ \___)(_)\_)(______) (__) (____)(_)\_) (__)
github.com/AnalogJ/scrutiny dev-0.4.3
Start the scrutiny server
[GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production.
- using env: export GIN_MODE=release
- using code: gin.SetMode(gin.ReleaseMode)
time="2022-05-11T09:31:02+02:00" level=info msg="Trying to connect to scrutiny sqlite db: \n"
time="2022-05-11T09:31:02+02:00" level=info msg="Successfully connected to scrutiny sqlite db: \n"
panic: a username and password is required for a setup
goroutine 1 [running]:
github.com/analogj/scrutiny/webapp/backend/pkg/web/middleware.RepositoryMiddleware({0xfaf4e0, 0x40001aed08}, {0xfb8000, 0x4000454070})
/app/scrutiny/webapp/backend/pkg/web/middleware/repository.go:14 +0xd4
github.com/analogj/scrutiny/webapp/backend/pkg/web.(*AppEngine).Setup(0x400044e6e0, {0xfb8000, 0x4000454070})
/app/scrutiny/webapp/backend/pkg/web/server.go:26 +0x90
github.com/analogj/scrutiny/webapp/backend/pkg/web.(*AppEngine).Start(0x400044e6e0)
/app/scrutiny/webapp/backend/pkg/web/server.go:97 +0x404
main.main.func2(0x4000429d00)
/app/scrutiny/webapp/backend/cmd/scrutiny/scrutiny.go:112 +0x288
github.com/urfave/cli/v2.(*Command).Run(0x4000435e60, 0x4000429b80)
/root/go/pkg/mod/github.com/urfave/cli/[email protected]/command.go:164 +0x648
github.com/urfave/cli/v2.(*App).RunContext(0x400031e480, {0xf9b6d0, 0x40001b6000}, {0x40001b2000, 0x2, 0x2})
/root/go/pkg/mod/github.com/urfave/cli/[email protected]/app.go:306 +0x840
github.com/urfave/cli/v2.(*App).Run(...)
/root/go/pkg/mod/github.com/urfave/cli/[email protected]/app.go:215
main.main()
/app/scrutiny/webapp/backend/cmd/scrutiny/scrutiny.go:137 +0x73c
2022/05/11 09:31:03 No configuration file found at /opt/scrutiny/config/scrutiny.yaml. Using Defaults.
I’m running HassOS last version on RPi4:
Home Assistant Core 2022.5.3
Home Assistant Supervisor 2022.05.1
Home Assistant OS 7.6
Thank you
1 Like
Hi, thanks it’s a bug in the upstream image Testing influx version and get password and username not found · Issue #234 · AnalogJ/scrutiny (github.com)
As soon as the upstream image is corrected we’ll be able to use again the addon
Edit : I pinned an older version to still allow it to work
1 Like
Can you pin also a working version of Scrutiny FullAccess?
Thank you ^^
Hi, it’s already the case. Isn’t it working for you?
If not just try to click the rebuild button and it will rebuild it using the pinned version
Hi,
For my part I encounter the same problem, Scrutiny FA does not work (the database problem), installs indicating version “2ab714f5-ls35”.
On the other hand if I switch to the “non FA” version, the UI works, still indicating version “2ab714f5-ls35”. The reinstallation doesn’t change anything, and I don’t have a rebuild button for this addon (version FA)
Version “normale”, UI fonctionnelle :
Version “FA”, UI hors service :
1 Like