forum

(I posted this in the RaZberry area already but that was probably the wrong place - my issue isn't related to the RaZberry extension board.)

I know this has been discussed in some ways in the past. I also checked the PDF documentation but in the end I was not able to find all the answers I'm looking for.

So - in an effort to mininize SD Card write accesses on a a Pi 3 (Debian Buster) I noticed the following "offenders":
Those seem to be written to quite frequently. (config/zddx was probabably a bogus hit because I think it's not touched when not running the webif.) My questions on these files would be:

1. Are there ways to limit the frequency with which they are written?
2. Can the amount be controlled?
3. Are all of those files even required for proper operation?
4. Is there any documentation related to my issues and those files I can read?

Any help, hints, pointers will be greatly appreciated!

No one?

In zwayparsedPacketsjson and zwayoriginPacketsjson the incoming and outgoing z-wave packets are logged. As a basis for ZNiffer. Size is fixed in module ZWave/index.js to max 5000 records/ 24 hours.

In notifications the messages for SmartUI page are written. Responsible is module InbandNotifications. There it's fixed, which messages are stored. File size is limited in AutomationController.js.

In DevicesData.xml the current configuration is stored. Don't touch!

One possibility to minimize write access is to switch off debug by setting loglevel to 1 in config.xml.

Thanks for responding, @piet66. You say zwayparsedPacketsjson and zwayoriginPacketsjson is intended for ZNiffer. From that I would gather that those files are not strictly needed for normal operation. What is the maximum Z-Wave packet size, ie. how big can those files grow with 5000 packets and would it be possible to symlink them to a file sitting in tmpfs?

Same question for notifications-f37bd2f66651e7d46f6d38440f2bc5dd.json - would it be ok to symlink it to a tmpfs?

My log level is already set to 2 and thanks for the hint wrt DevicesData.xml, I figured as much

For me:
4500 packets, zwayoriginPacketsjson: 676 KiB, zwayparsedPacketsjson: 750 KiB

The code of InbandNotifications I have changed, so that only the messages of those devices are stored, which I really need. There is a lot of useless messages.

I think all three files are not important. You can decrease the sizes in source code or you can put them to another place. In both cases you have to do that again after an update.

Thanks - I'll be monitoring those files for a little while to get a better feel for the sizes.

Could you also comment on zwayrssidatajson and in what way it is generated and/or required?

no, sorry

No worries.

From your hint to ZWave/index.js I've now seen that rssidata.json is only kept for the past 24 hours.