Unable to set sensitivity on Neo Coolcam motion sensor NAS_PD02Z-2

[Mastiffen]

Checklist

• I have read and followed the above instructions

• I have checked the troubleshooting section and my problem is not described there.

• I have read the changelog and my problem was not mentioned there or the fix did not work.

Describe the issue

What is happening?
When trying to update the sensitivity parameter it stands "chewing" until it fails.

What did you expect to happen instead?
Values should be updated.

Steps to reproduce the behavior:

1. Go to configuration V1
2. Click on Sensitivity value
3. Change the setting
4. Click on the update arrow

Anything else we should know?

Software versions

Driver (node-zwave-js): ...

Z-Wave JS UI: 9.27.7.d3d7049

Home Assistant Z-Wave Integration: N/A

Home Assistant Z-Wave JS Addon: N/A.

ioBroker.zwave2 Adapter:

If you are using something non-standard, tell us here: ...

Z-Wave Controller (Stick/Dongle/...)

Aeotec Z-Stick Gen 5 Firmware 1.0

Device information

Manufacturer: Shenzhen Neo Electronics Co., Ltd.
Model name: Motion Sensor NAS_PD02Z-2
Node ID: 62

Checklist

• I made sure to provide a driver log on level debug.

• The log includes a re-interview of the problematic device (if applicable).

• The log includes the problematic interaction with the device (if applicable).

• I provided the node ID of the problematic device (if applicable).

Upload Logfile

zwave-js-ui-store.zip

[Mastiffen]

I have tried different settings between 1 and 99 (which is the interval that the GUI gives me), but nothing works. I have a sneaking feeling that the problem is that the parameter is not the one it says it is. The motion sensor is unusable as it is, because it far to sensitive and triggers on nothing.

[Mastiffen]

I just remembered that I had another one of those, slight difference, this one has a magnetic mount. I took that out of the drawer, and it has the exact same problem.

[kpine]

It's a battery device, did you wake it up to apply the configuration change?

[kpine]

The log Embedded device config loaded means the custom file was not found. Make sure the file is in the correct directory <store>/config by default. You showed a screenshot of some directory which by name looks reasonable, but from that I cannot tell whether it's the correct one or not. Is your Data directory being mapped to /usr/src/app/store?

From a brief inspection I don't see a problem with the json file itself, so I suspect it's just not being found.

[Mastiffen]

Thank you very much for your patience! I have it mapped like this:

volumes: - /media/pi/Docker/Docker-Compose/Z-Wave-JS-UI/Data:/usr/src/app/store

I can't imagine that it isn't correct, because every thing else works, and all the other files are in this directory:

Is it possible that there is a capital letter or something somewhere that makes the filename itself nas-pd02z-2.json wrong?

[kpine]

The filename doesn't matter (except for maybe .json extension). Is your "Config priority dir" setting still the default?

[kpine]

If that last one is not a problem, I only have one more idea.

See these import lines?

node-zwave-js/packages/config/config/devices/0x0258/nas-pd02z-2.json

Lines 181 to 184 in c80a52d

	{
	"#": "7",
	"$import": "templates/shenzhen_neo_template.json#blink_on_motion"
	},

I suspect it's trying to load these from your config directory (you might see an error in the Docker logs). Try creating a config/template directory and download the shenzhen_neo_template.json file into the new template directory, then restart.

The imports with the tilde in the path (e.g. ~/templates/master_template.json) should be OK as-is.

[Mastiffen]

You posted the second one while I was writing! Damned good catch about the directory, it was the one from before I went Docker! Now you are really getting somewhere (I'm just the monkey at the keyboard right now). And the message is indeed what you thought:

2024-12-13T07:27:49.089Z CONFIG Error parsing config file nas-pd02z-2.json: Could not parse config file /usr/s rc/app/store/config/templates/shenzhen_neo_template.json: ENOENT: no such file or directory, open '/usr/src/app/store/config/templates/shenzhen_neo_template .json' Import stack: in #blink_on_motion in /usr/src/app/store/config/nas-pd02z-2.json (ZW0340)

There is no directory called config/templates, I created it now and downloaded the template. And the orange "Auto discovery functionality has changed" reinterview button came up! The interview was successfull, and the value updated!!!! Thank you again very much for your help and patience! Have a brilliant weekend!

[kpine]

You can fix this by also modifying the import statements (#6067) to fallback to the embedded manufacturer template. This rang a bell because it was a feature I requested. 😆

Just change:

 { 
 	"#": "7", 
 	"$import": "templates/shenzhen_neo_template.json#blink_on_motion" 
 }, 

to:

 { 
 	"#": "7", 
 	"$import": "~/0x0258/templates/shenzhen_neo_template.json#blink_on_motion" 
 }, 

etc., and you should be able to delete your local copy of shenzhen_neo_template.json.

[Mastiffen]

Nice to revisit old requests? 😉 But it seems that there is an error either in the change or the file name. Am I correct in assuming that if it was a line in the file it would refer to that line, or is that off? I saved a copy of everything before I started, as usual.

2024-12-13T07:52:14.008Z CONFIG Error parsing config file templatesbak/shenzhen_neo_template.json: The device config file is malformed! packages/config/config/devices/templatesbak/shenzhen_neo_template.json: manufacturer id must be a lowercase hexadecimal number with 4 digits (ZW0340)

I changed the file name to 0x0258.json, but got the same error. And still:

2024-12-13T07:56:36.996Z CNTRLR [Node 062] User-provided device config loaded 2024-12-13T07:56:37.002Z CNTRLR [Node 063] User-provided device config loaded

Edit: But I see in the actual device that it isn't parsed correctly, because it's mostly "vundefined" there now.

[Mastiffen]

Here is the file 0x0258.json.

It's probably a "monkey at the keyboard" error...