Neo coolcam z-wave devices

chris · December 27, 2018, 12:14pm

What do you see in the debug log when you open/close the door?

nakh_Home · December 27, 2018, 3:27pm

The debug log is enabled.

nothing when opening or closing

from the console, everythings seems ok

1. when i heal the thing, see the log below:

2018-12-27 17:36:25.774 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update received
2018-12-27 17:36:25.785 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration update set action_heal to true (Boolean)
2018-12-27 17:36:25.789 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Starting heal on node!
2018-12-27 17:36:25.793 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 6: Can not start heal as initialisation is not complete (UPDATE_NEIGHBORS).
==&gt; /var/log/openhab2/events.log &lt;==
2018-12-27 17:36:25.823 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:4f0192e8:node6' has been updated.
2018-12-27 17:36:25.828 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=group_4, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=wakeup_interval, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_1, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_3, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=group_2, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]

2. i have removed and readded the thing

[DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Start zwave:serial_zstick:4f0192e8
[DEBUG] [ve.internal.protocol.ZWaveController] - ZWave controller start inclusion - mode 2
[DEBUG] [ve.internal.protocol.ZWaveController] - Event listener added.
[DEBUG] [al.protocol.ZWaveInclusionController] - ZWave controller start inclusion
[DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Added 236 to queue - size 1
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
[DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A C1 A8 D9 
[DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
[DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 236: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 168
[DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
[DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 236: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 168
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
[DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 4A A8 01 00 00 1B 
[DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
[DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=AddNodeToNetwork[74], type=Request[0], dest=1, callback=168, payload=A8 01 00 00 
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=AddNodeToNetwork[74], type=Request[0], dest=1, callback=168, payload=A8 01 00 00 
[DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 236: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 168
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 236: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 168
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 236: (Callback 168)
[DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 236: callback 168
[DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=AddNodeToNetwork[74], type=Request[0], dest=1, callback=168, payload=A8 01 00 00 
[arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@148f1db
[DEBUG] [al.protocol.ZWaveInclusionController] - Inclusion event: Current state IncludeSent, new event IncludeStart
[DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 236: Transaction COMPLETED
[DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Response processed after 40ms
[DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: TID 236: Transaction completed
[DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: notifyTransactionResponse TID:236 DONE
[DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
[DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery completed
[DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 4: Device discovery resolved to thingType zwave:shenzhen_motionsensor_00_000
[DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery completed
[DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery resolved to thingType zwave:shenzhen_doorwindowsensor_00_000
[INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:4f0192e8:node6' to inbox.
[DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery completed
[home.event.InboxAddedEvent] - Discovery Result with UID 'zwave:device:4f0192e8:node6' has been added.
[DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery resolved to thingType zwave:fibaro_fgms001_03_002
[DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 12: Device discovery completed
[DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 12: Device discovery resolved to thingType zwave:shenzhen_eu2_00_000
[me.event.InboxRemovedEvent] - Discovery Result with UID 'zwave:device:4f0192e8:node6' has been removed.
[DEBUG] [org.openhab.binding.zwave           ] - ServiceEvent REGISTERED - {org.eclipse.smarthome.config.core.status.ConfigStatusProvider}={service.id=567, service.bundleid=275, service.scope=singleton} - org.openhab.binding.zwave
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - Initializing ZWave thing handler zwave:device:4f0192e8:node6.
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Controller status changed to ONLINE.
[hingStatusInfoChangedEvent] - 'zwave:device:4f0192e8:node6' changed from UNINITIALIZED to INITIALIZING
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Controller is ONLINE. Starting device initialisation.
[hingStatusInfoChangedEvent] - 'zwave:device:4f0192e8:node6' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
[hingStatusInfoChangedEvent] - 'zwave:device:4f0192e8:node6' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Channel zwave:device:4f0192e8:node6:sensor_door linked - polling started.
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Channel zwave:device:4f0192e8:node6:alarm_access linked - polling started.
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Channel zwave:device:4f0192e8:node6:battery-level linked - polling started.
[me.event.ThingUpdatedEvent] - Thing 'zwave:device:4f0192e8:node6' has been updated.
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Updating node properties.
[me.event.ThingUpdatedEvent] - Thing 'zwave:device:4f0192e8:node6' has been updated.
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Updating node properties. MAN=600
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Updating node properties. MAN=600. SET. Was 600
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Properties synchronised
[me.event.ThingUpdatedEvent] - Thing 'zwave:device:4f0192e8:node6' has been updated.
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Configuration synchronised
[me.event.ThingUpdatedEvent] - Thing 'zwave:device:4f0192e8:node6' has been updated.
[DEBUG] [ve.internal.protocol.ZWaveController] - Event listener added.
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising Thing Node...
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising cmd channel zwave:device:4f0192e8:node6:sensor_door for OpenClosedType
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising state channel zwave:device:4f0192e8:node6:sensor_door for OpenClosedType
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising cmd channel zwave:device:4f0192e8:node6:alarm_access for OnOffType
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising state channel zwave:device:4f0192e8:node6:alarm_access for OnOffType
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising cmd channel zwave:device:4f0192e8:node6:battery-level for PercentType
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Initialising state channel zwave:device:4f0192e8:node6:battery-level for PercentType
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Polling intialised at 1800 seconds - start in 48600 milliseconds.
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Device initialisation complete.
[DEBUG] [wave.discovery.ZWaveDiscoveryService] - ZWave discovery: Stop zwave:serial_zstick:4f0192e8
[DEBUG] [al.protocol.ZWaveInclusionController] - ZWave controller stopping inclusion at IncludeStart
[DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Added 237 to queue - size 1
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
[DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 05 A9 1C 
[DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 237: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 169
[DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
[DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
[DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 237: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 169
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
[DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
[DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 4A A9 06 00 00 1D 
[DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=AddNodeToNetwork[74], type=Request[0], dest=6, callback=169, payload=A9 06 00 00 
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=AddNodeToNetwork[74], type=Request[0], dest=6, callback=169, payload=A9 06 00 00 
[DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 237: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 169
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking outstanding transactions: 1
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Last transaction: TID 237: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 169
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Checking TID 237: (Callback 169)
[DEBUG] [.serialmessage.ZWaveCommandProcessor] - Callback match!
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Correlated to TID 237: callback 169
[DEBUG] [ve.internal.protocol.ZWaveController] - Incoming Message: Message: class=AddNodeToNetwork[74], type=Request[0], dest=6, callback=169, payload=A9 06 00 00 
[DEBUG] [al.protocol.ZWaveInclusionController] - Inclusion event: Current state IncludeDone, new event IncludeDone
[DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Added 238 to queue - size 1
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
[DEBUG] [al.protocol.ZWaveInclusionController] - ZWave controller end exclusion
[DEBUG] [ve.internal.protocol.ZWaveController] - ZWaveController include done
[DEBUG] [nal.protocol.ZWaveTransactionManager] - TID 237: Advanced to DONE
[DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: Response processed after 129ms
[DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: TID 237: Transaction completed
[DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: notifyTransactionResponse TID:237 DONE
[DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
[DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 05 00 B5 
[DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - Message SENT
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage started: TID 238: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 0
[DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 06
[DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=null[0], type=ACK[2], dest=255, callback=0, payload=
[DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 238: [WAIT_REQUEST] priority=Controller, requiresResponse=true, callback: 0
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg: ACK
[DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.
[DEBUG] [sactionManager$ZWaveTransactionTimer] - NODE 255: TID 238: Timeout at state WAIT_REQUEST. 3 retries remaining.
[DEBUG] [sactionManager$ZWaveTransactionTimer] - TID 238: Transaction is current transaction, so clearing!!!!!
[DEBUG] [e.internal.protocol.ZWaveTransaction] - TID 238: Transaction CANCELLED
[DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 255: notifyTransactionResponse TID:238 CANCELLED
[DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start. Holdoff false.
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Polling...
[DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 6: Polling deferred until initialisation complete

deltabert · December 27, 2018, 6:50pm

@chris Sorry, i was in the impression that the binding was not yet updated.
This afternoon i with openhabian-config an update from the 2.5.0-SNAPSHOT installation. After that i deleted all Zwave Things and let the system find them again. So i sould be OK now.
When i look with Karaf conole (like nakh_Home did) then all zwave things are recognized.
Still my items on the sitemap do not see the status of the devices.
Next i stopped openhab, switched DEBUG on for the zwave binding and started openhab again. I also replaced addons.cfg with the origional one (everything commented out).

At the startup I get a FrameworkEvent ERROR for the zwave binding, but nevertheless it continues to initialize the controller:
With karaf i checked all 5 nodes: zwave node3 , zwave node6 , zwave node7 , zwave node8 and zwave node5 (PIR)
I think all this looks OK. But i can not get the status of the items in the sitemap… I guess there is some fault in my openhab cfg… But i can’t see what.

chris · December 27, 2018, 6:56pm

Please provide the log showing what is received when the node sends events.

Again, it would be useful to see the log of this error (assuming it’s related to ZWave) - otherwise I can’t really comment on this.

deltabert · December 27, 2018, 7:13pm

Yes, sorry Chris and thank you for your patience. I restarted openhab again now with DEBUG on: zwave.log

chris · December 27, 2018, 7:38pm

Is this the exception you mentioned on startup -:

org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.zwave [20]
  Another singleton bundle selected: osgi.identity; type="osgi.bundle"; version:Version="2.5.0.201812242048"; osgi.identity="org.openhab.binding.zwave"; singleton:="true"

This means that you have two copies of the ZWave binding running (or you are trying to run two copies - only one is actually running).

It does look like the 2.5 binding is running - at least this time. I’m not sure that this is deterministic, so maybe the other one (probably 2.3 or 2.4) will run sometimes…

There is no logging from the other devices - node 3 has some data - it seems to be a thermostat (your node 3 txt file above links to a node 4 txt file). I guess that these devices haven’t reported anything, or haven’t yet woken up?

deltabert · December 27, 2018, 11:08pm

You are right. my zwave node3, should have been node 4. Node 4, 6, 7 and 8 are the Door/Window Sensors. Node 5 is the PIR Sensor. (node2 is a Fibaro Wall Plug and node3 is a Danfoss Thermostat valve; they are working OK.)

About the (double) bindings, if i check in karaf what zwave bindings are active, I get:

openhab> bundle:list | grep -i zw
 20 x Installed x  80 x 2.5.0.201812241106     x ZWave Binding
246 x Active    x  80 x 2.5.0.201812242048     x ZWave Binding
openhab>

So, yes there seems to be two bindings active. (from 24 dec. one at 11:06 the other at 20:48). Strange because i did an upgrade this afternoon (via openhabian-config). I would have expected a later date binding…
I removed the oldest one (bundle:uninstall 20). Next i tried to update the zwave binding (bundle:update 246), but the zwave binding remains the same

openhab> bundle:list | grep -i zw
246 x Active   x  80 x 2.5.0.201812242048     x ZWave Binding
openhab>

I hope this is your latest binding?
Then i stopped openhab, deleted the ZWave.log file and started openhab again and this is the logfile:ZWave-250-4.log

But when i look at the Things in karaf console

openhab> things show zwave:device:651ad746:node4

i get this output node4 , to me this looks OK? The same applies for the other tree Door/Window Sensors.
Edit:
I think i was too impatient. This morning things look much better:

Chris, I would like to thank you very much for your patience with me.
Kind regards, Bert

chris · December 28, 2018, 10:25am

Glad to hear things are looking better. It may just have been that the device wasn’t initialised fully if it needed to wake up a few times. The above log shows that the initialisation is complete now at least

shorty707 · January 22, 2019, 6:30pm

for whatever reason this seems to happen to me always on those chinese branded sensors like coolcam, heiman etc. … they actually look ok in habmin however if you wake them up couple times you can see that suddenly the initalization is actually done finally and the device works afterwards

never have those issues with eg fibaro … still for sure manufactured in china

soesas · January 23, 2019, 9:28am

I have a couple of the window sensors, they are working to my satisfaction except one.

It only detects motion, when the magnet is in the immidiate vicinity (The cover of the sensor has to be off). It is included and working find otherwise.
Maybe @alefz3r0 or @helmar74 have an idea - from my understanding it must be some kind of hardware failure. Could the reed sensor be broken? Where would I find replacement to solder it in.

Thank you guys! Just slinging the device seems like a waste…

MrManuzz · January 24, 2019, 7:27pm

Hi, new to this forum and hope I can ask a question to other Coolcam users.

I recently purchased 2 Neo Coolcam power plugs after I checked they are supported by Openhab;
https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/397#

The Coolcam power plugs are nicely included in my network. Openhab then logs this;
[wave.discovery.ZWaveDiscoveryService] - NODE 18: Device discovery could not resolve to a thingType! 0258:0200:1027::2.32
[wave.discovery.ZWaveDiscoveryService] - NODE 19: Device discovery could not resolve to a thingType! 0258:0200:1027::2.32

I’ve read through this topic, seen all the tips and tricks like waking up the device, be very patient and wait for the device to complete initialization etc. After excluding, including, heal commands, waking the devices and waiting for more than 24 hours still the devices will not be ‘recognized’ by Openhab. The error message I get about not being able to resolve a thing type seems to be very consistent. I haven’t had any other messages whatever I tried.

I don’t think I’m doing something wrong and I do not think I have a problem with my installation. All other devices were added without any problems or delays. Mesh network and Openhab software, all is working fine.

I’ve seen a sort of explanation from Chris how you can manually add a device to Openhab using his database and exported xml’s but I can only follow his explanation up to where he tells to search for the application version in the XML file.

How can I force Openhab to actually use the predefined device from the zwave binding? After all the coolcam power plugs report themselves exactly as they should (0258:0200:1027) and to my understanding the zwave binding should not have any difficulties resolving / installing / using the power plugs.

Thanks for any tips

sihui · January 24, 2019, 9:19pm

Your id’s were added recently, so you need to upgrade your zwave binding to the latest 2.5 snapshot:

https://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/397#comment-962

MrManuzz · January 24, 2019, 9:50pm

Hi Sihui,

Man you are good! Such a simple answer but yet so right . All working now! Fantastic.
Thanks a lot!

LeoVe · February 1, 2019, 1:58pm

Just added a Neo Coolcam Powerplug, Manufacturer 0258, Type/ID 0200:1027.
It is joined in the openhab2 / z-wave network and states the data as above.
Only it’s not fully discovered ?! It says: “unknown device”.
But if I check the database online, the powerplug is in there !
I’ve got:

Openhab2 v 2.3
Z-wave binding v2.3.0

What to do to fully discover the item?
Would it be possible to only upgrade the version of the z-wave binding to the abovementioned latest 2.5 snapshot ?

mhilbush · February 1, 2019, 2:11pm

This Type/Id was added on January 17, therefore, it’s only in the very latest versions of the binding.

I’m not sure if the 2.5 snapshot version of the binding runs with 2.3 stable. Other will have to weigh in on that.

If you upgrade to a new version of the binding, please be aware that there are breaking changes that will require some work. See here.

LeoVe · February 1, 2019, 3:11pm

Thanks for your quick response !

But … O Boy,
I already did execute the karaf command to load the z-wave 2.5 version you had in a discussion mhilbush.
It was executed but Openhab2 seems to ignore it as in PaperUI it still states z-wave binding v2.3.0…

And the Thing still not discovered…

How easy to upgrade to OpenHab v 2.4 ?

Thanks!

mhilbush · February 1, 2019, 3:16pm

You mean this post?

In the karaf console. what do you see when you run

list -s | grep zwave

I dunno. I’ve only ever used the snapshot releases.

Note that there’s also a 2.5 Milestone 1 release.

LeoVe · February 1, 2019, 6:38pm

Thanks for the reply mhilbush !

Yep, thats the command “bundle:update ….”

I had to restored a backup as after the command z-wave was no longer working and I tried updating to OpenHAB 2.4. So now I’m up and running on OpenHab v 2.3 again.
Only my new thing, the Neo Coolcam powerplug is still in status “unknown device”.
I don’t understand it though, it’s not my first NEO Coolcam device and also not the first powerplug. I’ve got quite a few (powerplug, wall switch and motion sensor) running for months now without any problem…

Updating to v2.4 seems to be quite a problem.

I think I was told the database was queried online, so updating the binding was not necessary for new things? Is that no longer the case or did I misunderstand ?

Anyway, any other ways or suggestions on how to get the NEO Coolcam Powerplug (Manufacturer 0258, Type/ID 0200:1027) working?

Nb.1. I’m running an OpenHabian (RPi) version of OpenHab.
Nb.2. This is the error message:
NODE 23: Device discovery could not resolve to a thingType! 0258:0200:1027::2.32

mhilbush · February 1, 2019, 7:16pm

The database is part of the binding. They are inseparable. To the best of my knowledge, it has always been this way in OH2.

Based on my reading of posts on this forum, many people running openHABian have upgraded from 2.3 to 2.4. You might want to seek some help here on the forum. Unfortunately, I’m not of much help because I don’t run release builds.

Hey @sihui, Can a recent snapshot version of the zwave binding run on the OH 2.3 stable release?

One way or another, in order to use this device, you need to get on a very recent version of the zwave binding. That type:id was added to the binding on January 19, so you need to be running the latest snapshot zwave binding.

sihui · February 1, 2019, 8:03pm

As far as I remember from reading a post from Chris I think that is possible. I too never run release versions, though

I think that is the key for success for @LeoVe