[SOLVED] Zwave, unknown device NEO Coolcam power plug

[mariofrombelgium (Mario)]

@Bruce_Osborne

try excluding it from the network and performing a hardware reset of the device before re-including

Thx for the tip. I’m going to do that. I need to know whether I can trust this device. I’m planning to use it on my waterpump…it will be a backup check but still I would like to know whether it can be trusted.

[Bruce_Osborne]

All I can say is I have 3 and have not experienced an issue with them yet. I have the US version though.

[sihui]

@chris

There appear to be two devices with the same IDs and overlapping versions

Thx, I looked through my emails and found:

A user request on 2019/09/26 to change firmware versions:

{
    "database_id": 1014,
    "label": "NAS-WR01ZE",
    "manufacturer_name": "Shenzhen Neo Electronics Co., Ltd",
    "manufacturer_id": "0258",
    "device_ref": [
        "0100:1027",
        "0200:1027"
    ],
old:    "version_min": 2.32,
new:    "version_min": 2.21,
    "version_max": 2.32,

which you reverted during approval to

{
    "database_id": 1014,
    "label": "NAS-WR01ZE",
    "manufacturer_name": "Shenzhen Neo Electronics Co., Ltd",
    "manufacturer_id": "0258",
    "device_ref": [
        "0100:1027",
        "0200:1027"
    ],
old:    "version_min": 2.32,
old:    "version_max": 2.32,
new:    "version_min": 0,
new:    "version_max": 255.255,

for reasons I don’t know (I don’t remember any forum discussions about either of those changes).

[JdeJong (Jasper)]

Hi @mariofrombelgium,

Since the device was recognized by the binding, I did not experience any issue anymore.
I have two more powerplugs on the shelf and will implement them soon. They will be on the tree lighting (it’s almost xmas after all ). They will be switched through a rule based on astro-binding sunset / sunrise. I’ll let you know once done! (have to do some physical wiring first).

/Jasper

[chris_me]

I’m running now on openhab3. I have 2 NEO Coolcam power plug, and they work fine. Yesterday I received 2 new ones, they look only a bit different but both are not recognized, it says unknown device.

Maybe there’s a new firmware installed? In Openhab3 I don’t know where to find the information about the firmware version or Type/ID

[rpwong (Russ)]

I’ve heard that the NEO Coolcam devices can be flaky, so you may need to wake them many times to get them to be recognized. If not, here’s the guide for checking and updating the database.

Z-Wave Device Database Guide

Changes will be merged into a future snapshot binding, which you can install manually.

Zigbee and zwave manual install script

A number of people have run into trouble performing manual installs of the Zigbee and Z-Wave bindings. A manual install (dropping the jar into addons) is rarely needed, but some people prefer a manual install over apt-get, or want to use a stable OH release with a recent Zigbee or Z-Wave binding. Here is a script that will hopefully make it easier to install, upgrade, and uninstall these bindings, and prevent some of the common issues. Who would benefit from this script: Anyone wanting to tes…

Note the latest comment about how to make the script work in OH3.

[chris_me]

The first link says:

“Devices are identified in the database by 4 pieces of information that are provided by the device during the initial discovery process.”

Where can I find

Manufacturer ID
Device Type
Device ID
Firmware version

in openhab3?

[rpwong (Russ)]

It’s in the userdata/zwave folder.

[chris_me]

Thank you, found that folder. But the 2 new wall plugs are not listed, in openhab I get a node number, and it says online when it is online, and offline when I pull it out, but unknown device and in the zwave folder both are missing.

[rpwong (Russ)]

You might need to delete the thing and try readding it to get it to initialize. I’ve had to do that multiple times with some battery-powered devices.

Zwave node xml file for sensor not being created

No xml file until the binding receives the NIF (Node information Frame) from the device. sometimes i have had to delete the Thing from OH (do NOT exclude from the network) and rediscover / add Wake up the device until discovery is complete. If left too long I have found that sometimes the thread gets orphaned.

[Bruce_Osborne]

@rpwong

I’ve had to do that multiple times with some battery-powered devices.

I have never heard of a battery operated power plug

I have found that for some of my cheap coolcam devices they actually needed to be factory reset before they would include properly into the network. If you are going to do that , try excluding them first in the hope you do not end up with zombie nodes in your network.

[rpwong (Russ)]

@Bruce_Osborne

I have never heard of a battery operated power plug

Oops.

That being said, you’ll appreciate this nugget from a CES announcement earlier today.

Signify is releasing a Philips Hue wall switch module that upgrades existing switches to smart units. The add-on not only keeps lights available regardless of the switch position, but lets you specify what happens when someone toggles that switch.

…

It’s also battery-powered, so you’ll need to dismantle your switches every five-plus years to keep the module running.

I’m assuming that this was done so that it doesn’t need a neutral wire, and that Signify’s engineers failed to adequately explain it to the people who wrote the press release.

Philips Hue module turns any light switch into a smart switch

[Bruce_Osborne]

@rpwong

I’m assuming that this was done so that it doesn’t need a neutral wire, and that Signify’s engineers failed to adequately explain it to the people who wrote the press release.

If it fits in the electrical box, what happens with those older grounded metal electrical boxes? They should block the RF signal pretty well…

[chris_me]

That was it, factory reset and after that it worked. Thank you.

[Bruce_Osborne]

I hope you have better luck with Neocam than me. I have already replaced one sensor due to being a battery hog. I am getting ready to replace another because at times it fails to detect motion.

[chris_me]

Actually I like Neo Coolcam, I had already 2 power plugs for 2 years now, I never had a problem.

I have as well 2 power plugs from fibaro, and they need to be reset from time to time because they stop working.

[Bruce_Osborne]

I have not used my power plugs much but I suspect weak radio reception. The plugs I used with the Christmass tree lights worked much better than the Zooz one the previous year. It decided it was overloaded with just the tree leds and an led star. They replaced it with a heavier duty model. The Neocam one worked flawlessly though.

[Dominik_Jeziorski]

Hi @chris I have simialr problem with Neo Coolcam power plug and need help/advice (I’m not sure if new thread is needed). The 2 devices I have are not recognized in OH 3.2

I was looking in DB and found this device.

NAS-WR01ZE Wall Plug Switch - OpenSmartHouse Z-Wave Device Database

With type
Type 0003:0087,0003:1087,0003:1483,0003:2087,0020:0707

When I’m adding my device to controller I see ID like this one - 041A:0200:0008:2.23
Details inside:

zwave_version - 2.23
zwave_manufacturer - 1050
zwave_devicetype - 512
zwave_deviceid - 8

My other device that is looking exactly same but bought 2years earlier has this params - matching the 397 db reference:

zwave_version - 3.94
zwave_manufacturer - 600
zwave_devicetype - 3
zwave_deviceid - 4231

Is there a way to modify (something) locally and check if it will work or do I need to do something else / wait for the next z-wave binding release?

Thanks

[anon71759204]

@Dominik_Jeziorski

zwave_manufacturer - 1050

Smart socket - Keemple

Please add your new device to the Z-Wave database:

Z-Wave Device Database Guide

Request review, wait for approval, install new Z-Wave Binding snapshot.

[chris (Chris Jackson)]

@Dominik_Jeziorski

Is there a way to modify (something) locally and check if it will work

In theory you should be able to modify the XML file generated for this device to set the manufacturer / type and id to match another entry in the database. This isn’t a long term solution, but for testing it should work (for a while - the binding may update this data from the device so it may stop working at any time).

The correct solution is as written by @anon71759204 - to update the database to add the new device.