Neo coolcam z-wave devices

Not sure if anyone else experiences this, but 4 of my recently bought Neo CoolCam devices (0x258:0x1027:0x200) have the configuration parameters shuffled all over (and not matching the printed manuals I got with them in the box :slight_smile: )ā€¦ not to mention OH config.
My devs report (via COMMAND_CLASS_VERSION) to be the following:
version: 3, Protocol: 6.2, Firmware: 2.32, hardwareVersion: 16

The default parameters I get upon device factory reset are:

ID Value Comment (guessed behavior - based on trial and error)
1 1 Remember relay On/Off status
2 1 Button On/Off Enable
3 1 Led Display Enable
4 0 Plug time switch function Enable
5 120 Time switch period
6 1 Meter report enable ?
7 300 Meter Report Interval ?
8 16 Maximum over-load current ?
9 50 Configure power report ?
10 13 Maximum alarm current ?
- No params 11,12 ?

I.e. the Meter Report Interval (formerly param 2) is now param 7ā€¦ and param 3 now controls the LED behavior, while it used to be about overload currentā€¦ And yes, the defaults have changed as well, so have some ranges (e.g. #9 seems to control reporting sensitivity, but no idea what is the unit now as it accepts vals > 100)

Anyone else experienced this? Is there any updated description of the params or new manual available somewhere?

  • Side-note: I also have 0x258:0x1087:0x3 CoolCam devices, reporting:
    version: 2, Protocol: 4.5, Firmware: 3.94, hardwareVersion: 65, which have an OK config (parameters match the manual)

Thanks!

Sadly, the manual I had is already in the trash :-/

You have to use the lastest 2.5 snapshot of the zwave binding. 2.4 release isnā€™t working.
Olli

I can confirm thisā€¦they simply havenā€™t changed the manual. Both versions have the same manual, but a different bevahiour.

Anyone with this device: please update the database accordingly.

I do have this device, but I donā€™t have the old device to compare. But mostly my lack of knowledge is blocking me. If someone is willing to take me by the hand I can execute the necessary steps.

https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-database-guide

Thatā€™s how to update the database, but how do I gather the data I need? Where do get which config parameter is what? How do I test this locally? I am really missing the basics. And the URL is helping but not that much.

From your manual.

The problem is that the product is delivered with the old incorrect manual. Is there an alternative way? Except trial and error?

So how do you know the parameters have changed?

Thatā€™s what mbronk seemed to have found out in the post:

I donā€™t think we should put speculations into the database ā€¦ we need a recent manual.

Found this, looks we need to wait for the engineer to come back to work :grinning::sunglasses:

I do not know if it helps, but I ordered the following device from amazon a few days ago and also received it directly from china (NAS-WR01ZE).

Habmin says:
01

And here the manual:

currently I feel overwhelmed to edit the zwave database directly, sorry ā€¦

and here is a xml file:

network_ee7b3ad4__node_7.xml (10.9 KB)

I canā€™t find a node7.xml file?

  • Platform information:
    • Hardware: raspberry pi 3 b
    • OS: Raspbian GNU/Linux 9 (stretch)
    • Java Runtime Environment: Javaā„¢ SE Runtime Environment (build 1.8.0_181-b13)
    • openHAB version: 2.4.0 (Build) stable

Z-WAVE:
openhab> bundle:list -s | grep zwave
275 x Active x 80 x 2.5.0.201902190011 x org.openhab.binding.zwave
openhab>

This looks indeed like an updated manual! To be honest I also donā€™t feel confident to edit the XML.

I will try to find time for it tomorrow.

Thank you. I have seen, the scan is not the best, if you need a better I can scan the manual even better ā€¦

Fully agree! In fact, I have contacted both the vendor (szneo.com) and the seller from whom I have bought my devices - to get an updated manual. The seller just replied moments ago, providing me with a PDF manual which seems to match-exactly what @miwok has already posted here (which is newer to what I had in the box w/ the device BTW).

Thing isā€¦ this new manual is still not a match to the devices I have wrt. their config pameters. And I am not ruling out anything, incl. having buggy FW on those devs, hence my previous Q - if anyone else is observing this exact weird behavior.

As far as wild speculation goes - aside the entries in the table I have marked with question marks, I am pretty confident that my devices are configurable via the parameters indicated by me (and not what the manual says).

  • Does it extrapolate to other devices with the same FW - no idea.
  • Would I trust myself with this info and update the DB? no :slight_smile:
  • Did it work on my 4 devices - yes!
    So at the moment I can only really say this: I can confirm 4 sightings where the current DB content is not a match to a device, no more, no less.

Hope someone would eventually be able to get something concrete fom the vendor (once the-engineer-who-knows is back at the office :wink: ).

EDIT: Hereā€™s a PDFā€™ed version of the manual that I got. (over 1MB in size, so does not fit as an attachment + I donā€™t have any immediate location to post it at - the link is valid for 14d; if useful, hope someone can put it somewhere more ā€˜permanentā€™)

I have updated the device with the provided manual and edited the database accordingly.
As I donā€™t have this device I am not able to change parameters outside the scope of the manual, sorry.

According to the manual this parameter cannot be stored on the device, it is executed via factory reset.
Iā€™ve added the meter_reset channel which can be linked to a Switch itemtype to reset the values.