Okay, not a lot of help, we know you can command Items from the sitemap, but you want one that responds to your sensor.
Let’s work on that.
Earlier you showed us NEO Coolcam Thing zwave:device:3de88f51:node14
You still have that, it still shows online in PaperUI?
That had an alarm_motion switch type channel.
You had it linked to two Items then.
Are we down to one Item now, and it is a Switch type to match the channel?
But no sign of that in the logs?
You’ll have to investigate zwave device settings, like here
I also had a look at that post you sent and I checked the zwave NEO Coolcam settings but after trying stuff out like in Association Groups changing 1:Life line to Controller and 2:Group 2 to Controller I cant seem to be able to unchange it, it is stuck on that option just like all the other options in there.
I also tryed changing stuff like 6. Re-trigger Interval to 1 accept of default 8 and 8.Lux Level Function Enable from Dissable to Enable as well as 2. ON/OFF Duration Setting from 30 to 35 and non of thoes options saved even that it allowed me to change the name of the Thing.
Some logs appeared but I dont think they give much info
2020-06-19 17:41:44.862 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[ConfigStatusMessage [parameterName=wakeup_node, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null], ConfigStatusMessage [parameterName=wakeup_interval, type=PENDING, messageKey=null, arguments=null, message=null, statusCode=null]]]
2020-06-19 17:42:28.846 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:3de88f51:node14' has been updated.
2020-06-19 17:42:28.855 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]
2020-06-19 17:42:28.959 [hingStatusInfoChangedEvent] - 'zwave:device:3de88f51:node14' changed from ONLINE to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2020-06-19 17:42:28.977 [hingStatusInfoChangedEvent] - 'zwave:device:3de88f51:node14' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2020-06-19 17:42:28.989 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:3de88f51:node14' has been updated.
2020-06-19 17:42:42.482 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:3de88f51:node14' has been updated.
2020-06-19 17:42:42.509 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:3de88f51:node14' has been updated.
2020-06-19 17:42:42.511 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]
2020-06-19 17:42:54.684 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:3de88f51:node14' has been updated.
2020-06-19 17:42:54.687 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]
2020-06-19 17:43:15.435 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:3de88f51:node14' has been updated.
2020-06-19 17:43:15.438 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]
2020-06-19 17:49:30.376 [vent.ItemStateChangedEvent] - zwave_device_3de88f51_node14_sensor_temperature changed from NULL to 20.4
2020-06-19 17:59:40.705 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:3de88f51:node14' has been updated.
2020-06-19 17:59:40.707 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]
Do you think it is worth asking the person that made that post you sent for his configuration on his NEO Coolcam if he can and if he has done anything different from me?
What you need is help getting your device talking to openHAB, it doesn’t matter who from (it won’t be me, I don’t know zwave)
These things usually begin by finding out if your device has completed initialization and you have woken it up a few times.
Changes you make in PaperUI won’t get uploaded until it is intialized, I think. Making random changes doesn’t sound wise.
Well thats ok thank you so much for all the time and help you gave me. I will try out some stuff, dig some more online and if that doesnt help I will probably try redoing everything from scratch on a new RPI or I will try getting some new motion sensors.
Your motion sensor is battery powered, so you will either need to wait for it to wake up several times or manually wake it up for these changes to be picked up by the device.
When making these changes, ALWAYS (until OH 3.0) use Hamin rather than Paper UI, since the latter will send ALL parameters, take a very long time, and can possibly screw things up.
Another thing is that this device has had changes in the device database, so you will need to delete the Thing and rediscover it to pull in the new Thing definitions. If you don’t, strange things may happen. If this is a fresh installation of OH 2.5.5, then this will not be a factor.
So you are right I finnaly got them to work and what I had to do it manually wake it up by clicking a button at the back of it a lot of times and it is working perfectly now. Turns out that NEO products are just weird and they dont fully wake up. Thank you again Scott and rossko57 for help.
