Neo coolcam z-wave devices

[HFM (Henning F. Mettge)]

Hi @dmit2k,

Did you solve the problems? Maybe the last Snapshot or at least 2.5 M1 help?

How did you mount it to the wall? Only with screws?
Do you have some pictures how to mount it?

Thanks in advance and Happy Easter!
HFM

[Guido_van_Haasteren]

I bought the door sensor and the golf-ball-like PIR. The PIR was included easily and started reporting temperature and motion right away. The light didn’t start because there is a threshold of 100 lumen. I waved with a flesh light and then it started.
The door sensor is giving me a headache though. First time it didn’t include but I was on Habian 2.5 snapshot. I went back to 2.4 stable and reseted the sensor (press the button for 10 seconds). After that I could include, but the device was never updated . I clicked the button to wake it up 50 times, I waited for a week, no success. Yesterday I excluded the device, and again included it. The device was included and started initialising right away! I see the vendor and item nr etc in Habmin.
But there is no info about opening the door. There is a led that flashes when I remove the magnate or when I put it back, but no info to the controler.
I have set the association group 1 to ‘controler’ and for what it’s worth the ‘Basic set level’ to ‘0’.
When I press the button to wake the sensor up, I see the message in the log (Debug level):

2019-05-31 18:40:02.574 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:512:node39' to inbox.
2019-05-31 18:40:02.575 [home.event.InboxAddedEvent] - Discovery Result with UID 'zwave:device:512:node39' has been added.
2019-05-31 18:40:13.231 [me.event.InboxRemovedEvent] - Discovery Result with UID 'zwave:device:512:node39' has been removed.
2019-05-31 18:40:13.235 [hingStatusInfoChangedEvent] - 'zwave:device:512:node39' changed from UNINITIALIZED to INITIALIZING
2019-05-31 18:40:13.239 [hingStatusInfoChangedEvent] - 'zwave:device:512:node39' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2019-05-31 18:40:13.249 [hingStatusInfoChangedEvent] - 'zwave:device:512:node39' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to UNINITIALIZED
2019-05-31 18:40:13.268 [hingStatusInfoChangedEvent] - 'zwave:device:512:node39' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2019-05-31 18:40:13.312 **[hingStatusInfoChangedEvent] - 'zwave:device:512:node39' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING**
2019-05-31 18:40:13.322 [hingStatusInfoChangedEvent] - 'zwave:device:512:node39' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2019-05-31 18:40:13.323 [hingStatusInfoChangedEvent] - 'zwave:device:512:node39' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2019-05-31 18:40:13.349 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:40:13.368 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:40:13.398 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:40:13.417 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:40:13.420 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:40:27.616 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:40:44.223 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:41:39.424 [.ItemChannelLinkAddedEvent] - Link 'Achterdeur_sw-zwave:device:512:node39:sensor_door' has been added.
2019-05-31 18:41:39.427 [.ItemChannelLinkAddedEvent] - Link 'Batterij_achterdeur-zwave:device:512:node39:battery-level' has been added.
2019-05-31 18:48:20.208 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:48:28.894 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:49:23.064 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:52:30.490 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:52:41.830 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.
2019-05-31 18:54:05.068 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:512:node39' has been updated.

What can I do to let it finish initialiding?

[Bruce_Osborne]

@sihui

Done:

https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/1014

@sihui,

I have a 2.32 firmware version (100:1027) that does not show some config parameters. My manual does not agree with the device.
Should we split out the 100 type?
Most all Configuration Parameters do not match my manual. When I get home, I can see if Parameter 3 actually disables the LED. If not, we may need to split out my device.

I am not currently using these in Production so I have flexibility to test, assuming I do not brick it.

[Bruce_Osborne]

@Bruce_Osborne

When I get home, I can see if Parameter 3 actually disables the LED. If not, we may need to split out my device.

In a quick test, Parameter 3 disabled the LED as expected from the current device listing. The included manual says Parameter 3 is to configure maximum overload current, ovviously incorrect…

[sihui]

@Bruce_Osborne

Parameter 3 disabled the LED

We changed this device already so many times. I have about 40 emails in my account regarding this device.

[SOLVED] Z-Wave Neo NAS-WR01ZE Power Plug Disable LED Display

I tried to disable the LED Display on the Z-Wave device Neo Coolcam NAS-WR01ZE Power Plug, but I was not able to get it work. Did anybody discover the same problem? Is there anybody, who successfully disabled the LED? If I try to deactivate the LED by HABmin it shows work in progress icon and stays that way. I use the Z-Wave Binding Snapshot 2.5.0 Version. [38] Z-Wave Log, while setting parameter 5 to disable: 2019-04-13 16:02:21.227 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHa…

It looks like even the same firmware version has different functions. Also the manuals which come with the device do not match the device.

Sorry. I won’t touch this crappy device again and won’t make any approvals Please ask Chris.

[HFM (Henning F. Mettge)]

Hi @sihui!

Before I buy any of these NEO coolcam devices (NEO Coolcam Z-wave EU Wireless Smart Control Light Switch 2CH): Is there any problem, that you won’t touch it, too?

Best regards
HFM

[sihui]

@HFM

Is there any problem, that you won’t touch it, too?

It is like all the work done here in the forum: it is volunteer work in our limited spare time.
If knowledge and time is available, people will help, if one of it lacks, there has to be some other solution (for example through the binding maintainer, who is doing this in his free time, too).

[sihui]

@HFM

Before I buy any of these NEO coolcam devices

By the way, I have two of these devices (firmware 3.94), which are working fine.
But I would never buy them again. Range is much less than all the other devices (mostly Fibaro) I own.
You get what you pay for.

[HFM (Henning F. Mettge)]

Hi @sihui,

I think because of my bad English there is a misunderstanding. I like openHAB and I know that there are many hours of developing, testing, documenting, supporting. It is a kind of doing something on a voluntary basis. And this ist fantastic! I do it myself within a citizens’ initiative against a landfill site.

What I meant is: Are there any known bugs with the NEO Coolcam Z-wave EU Wireless Smart Control Light Switch 2CH? I would not buy it if it is not usable. For the power plug I understood that it is not so good.

Thanks for your replies!
HFM

[sihui]

@HFM

Are there any known bugs with the NEO Coolcam Z-wave EU Wireless Smart Control Light Switch 2CH?

I don’t have this device so I can’t tell.

[Bruce_Osborne]

@sihui I meant to confirm the current manual is incorrect and the database appears correct.
Sorry for my poor communication.
I really appreciate all the hard work here. Sorry to frustrate you.

[sihui]

@HFM

there is a misunderstanding.

@Bruce_Osborne

Sorry for my poor communication.

Apologizing is on my side, sorry.
German natives reading and writing in English language is sometimes not a good idea

[Bruce_Osborne]

@sihui

German natives reading and writing in English language is sometimes not a good idea

But without you talented, dedicated Germans, this great project would not exist!

[Tamas_Nadanicsek (TN)]

Could you suggest a good working z-wawe devices (except Fibaro)?
Thank you!

[sihui]

@Tamas_Nadanicsek

Could you suggest

All my Fibaro devices are working without any problems since four years, so no, I don’t have any recommendations, sorry.

[Tamas_Nadanicsek (TN)]

Thank you for your feedback. Do you have Xiaomi devices as well?
Which Z-wave gateway do you use?

[chris (Chris Jackson)]

@Tamas_Nadanicsek

Do you have Xiaomi devices as well?

Note that Xiaomi devices are not ZWave devices.

Aeon also make good quality devices - there are many devices on the market from many manufacturers, and as a general rule most ZWave devices will interoperate just fine with other devices.

[Bruce_Osborne]

@Tamas_Nadanicsek

Could you suggest a good working z-wawe devices (except Fibaro)?

How about looking at this title of this thread?
I have a few inexpensive Neo coolcam devices purchased from aliexpress that work fine.

[Tamas_Nadanicsek (TN)]

I have read this topic of course. As I see there are many problems with Neo products (that is why was my question).

[Seaside]

I own around 50 different zwave devices with a handful of different brands. I have a couple of neo power plugs, door window sensors and motion sensors. They are crappy compared to fibaro. Nowadays I only use the motion detectors on some not so important locations (storage spaces etc). They do work somewhat, direct association work 50% of the time.

If you want to buy cheaper brands then fibaro I would look into zigbee, there you can buy for instance xiaomi which are quite good.

Regards S