Hi @Jamie
Wanted to try out your app.
But unfortunately it crashes after install.
the app crash shows this:
Error: ENOENT: no such file or directory, uv_resident_set_memory
at process.memoryUsage (node:internal/process/per_thread:168:5)
at RejectionHandler.getProcessInfo (/app/node_modules/winston/lib/winston/rejection-handler.js:112:28)
at RejectionHandler.getAllInfo (/app/node_modules/winston/lib/winston/rejection-handler.js:93:21)
at RejectionHandler._unhandledRejection (/app/node_modules/winston/lib/winston/rejection-handler.js:168:23)
at process.emit (node:events:529:35)
at emit (node:internal/process/promises:149:20)
at processPromiseRejections (node:internal/process/promises:283:27)
at process.processTicksAndRejections (node:internal/process/task_queues:96:32)
I had the same issue when i made this homey-betterstack - npm but couldn’t find a fix for that aswell.
I’m using a HP23.
If you need a diagnostic report let me know
I installed the Audit app today. I set up the Betterstack integration as recommended here. A lot of data is being collected locally, but no data is reaching Betterstack. Does anyone else have this problem?
@Jamie could it be that your audit app doesn‘t catch all actions? The audit log shows for example an off action of a lamp but not the corresponding on action that one can see in the device log. Noticed that it seemed to have happend several times. Have to do some more research to verify my findings.
The Audit app really seems to have problems with recording OFF actions. Not much activity on homey as far as I can tell and yet quite a number of OFFs from different apps are not recorded. Can you please have a look into this.
Am using level „notice“. Was reffering to plugs of different brands (aqara, fibaro, devolo, qubino) switching lights. They are switched on and off by flows. Checking the audit logs I saw some „off“s without „on“s. Checked the devices log and saw that they were switched on according the settings from the flows. Noticed it at 2 occasions the past 2 weeks (21. and 22.12.). Before I did not check. App and homey 2023 are up to date. Homey itself did not record any problem. Audit didn’t seem to be too busy at that times. Requested only „on“ and „off“ actions. Not all „on“s went unrecorded. Haven’t found a wrongly recorded action at the „on“ time. Difficult to find a reason.
I did a deep dive and testing I am unable to see any issue with off being logged, but I did add a catch all to trigger when the message fails, so perhaps that will help? Let me know how you go.
I also fixed an issue where critical logs, ie home alarm and garagedoor_locked may not log correctly.
Finally did an general update to the latest homey APIs and update the file rotate method.
I’ve just pushed the test version to live, sorry it took a while, this app has a pretty small user base so it took some time to verify it fixed the issue.
Would it be possible to set a cap on the storage it uses or retention times in hours?
Started logging yesterday day due to an issue I had and the issue didn’t happen until the night.
But now I had no space left on the Homey and the app hung.. So it was all gone anyway.
I was looking for a kinda syslog/journald function for homey and found audit whivh is near perfect. other apps need a flow to log which i dont want to.
Is there any way to send logs either instantly or every x min or h to a logserver (ie graylog) WITHOUT cloud based 3rd party apps, all localy or at least just within devices/server i own!
