(SOLVED) Zwave unlink automatic created items in PaperUI create manual, result a warning

@chris
Are there any specific reason why I get an warning, after I have unlinked automatic created links to items from PaperUI, and then create the very same items (same ID) manually in a file afterwards?
I get the same warnings when I did the same to another z-wave device. And it tends to continue given me these warnings each time I reboot/restart OpenHab2.
Everything seem to work fine though, it´s just annoying seeing these warnings.

This is my logfile:

2018-07-18 22:12:23.064 [temChannelLinkRemovedEvent] - Link 'ZWaveNode11ZG8101GarageDoorTiltSensor_BinarySensor => zwave:device:fef78fef:node11:sensor_door' has been removed.
2018-07-18 22:12:26.501 [temChannelLinkRemovedEvent] - Link 'ZWaveNode11ZG8101GarageDoorTiltSensor_AlarmBurglar => zwave:device:fef78fef:node11:alarm_burglar' has been removed.
2018-07-18 22:12:30.589 [temChannelLinkRemovedEvent] - Link 'ZWaveNode11ZG8101GarageDoorTiltSensor_BatteryLevel => zwave:device:fef78fef:node11:battery-level' has been removed.

2018-07-18 22:12:45.996 [INFO ] [el.core.internal.ModelRepositoryImpl] - Refreshing model 'zwave.items'
2018-07-18 22:12:46.024 [WARN ] [ore.common.registry.AbstractRegistry] - ContactItem with key 'ZWaveNode11ZG8101GarageDoorTiltSensor_BinarySensor' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!
2018-07-18 22:12:46.028 [WARN ] [ore.common.registry.AbstractRegistry] - SwitchItem with key 'ZWaveNode11ZG8101GarageDoorTiltSensor_AlarmBurglar' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!
2018-07-18 22:12:46.031 [WARN ] [ore.common.registry.AbstractRegistry] - NumberItem with key 'ZWaveNode11ZG8101GarageDoorTiltSensor_BatteryLevel' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

==> /var/log/openhab2/events.log <==

2018-07-18 22:12:46.042 [.ItemChannelLinkAddedEvent] - Link 'ZWaveNode11ZG8101GarageDoorTiltSensor_BinarySensor-zwave:device:fef78fef:node11:sensor_door' has been added.
2018-07-18 22:12:46.050 [.ItemChannelLinkAddedEvent] - Link 'ZWaveNode11ZG8101GarageDoorTiltSensor_AlarmBurglar-zwave:device:fef78fef:node11:alarm_burglar' has been added.
2018-07-18 22:12:46.058 [.ItemChannelLinkAddedEvent] - Link 'ZWaveNode11ZG8101GarageDoorTiltSensor_BatteryLevel-zwave:device:fef78fef:node11:battery-level' has been added.

This isn’t anything to do with ZWave - the error is coming from the framework so I’m not sure I can comment too much. If I understand what you’re doing, you’re defining the same item twice - once in PaperUI, and once in an items file? This is probably causing an issue within ESH.

Not eaxctly…
First I remove (delete) the automatic created links from PaperUI.
Afterwards I create the very same items in an manual created items file. Like this:

//Vision ZG8101 Garagedoor tilt sensor

Contact ZWaveNode11ZG8101GarageDoorTiltSensor_BinarySensor "Garage door tilt binary sensor [%s]" 	<door> 					{channel="zwave:device:fef78fef:node11:sensor_door"} 
Switch ZWaveNode11ZG8101GarageDoorTiltSensor_AlarmBurglar "Garage door tilt alarm sensor [%s]"		<door> 					{channel="zwave:device:fef78fef:node11:alarm_burglar"} 
Number ZWaveNode11ZG8101GarageDoorTiltSensor_BatteryLevel "Garage door tilt sensor battery level [%s]" 	<Battery> 	(BatteriLevel) 		{channel="zwave:device:fef78fef:node11:battery-level"} 

Reason why I created the same item ID is to avoid having to change my sitemaps, rules etc which contain these item ID´s.

As I am pretty sure you have set “Simple Mode” to OFF you should try clearing cache and tmp … :sunglasses:

I´m not sure what simple mode has to do with this. But I have switch off automatic creating links when I install a new device.
I have tried clearing the cache. It does not do any change.

EDIT… Ahh I see, Simple mode OFF = no automatic creating items of things :smiley:

Yes I do have Simple Mode OFF.

:point_up_2:

I would then check your jsondb if any of those items are still in there: GUI created items go to jsondb, manually created items should not show up there.

I have no idea how to check or even where this jsondb is located.
Yes, it sounds like they´re still in there, which is why I get this warning. The bug could then be, that they don´t get deleted from this jsondb.

We don’t know either because you did not tell your installation method. So please look at:

I have no idea why your system behaves different from other systems. I could not find or remember any reference mentioning similar problems, sorry.

Sorry…
It´s an apt-get rasbian hasslefree Openhab 2.3 stable, running on an Rpi3B.

But I suspect it would be rather easy to test. I just changed 4 devices last night, all 4 ended up with the same warning message.

Later I´ll give it a try and reboot the Rpi. But I´m pretty sure this didn´t change anything last time, as I tend to reboot quite often. I will also try an clear cache as well.

I don’t use any GUI configured items, but I did now to test for you :grinning:

created item Test via PaperUI
linked zwave channel to that item
put that item to my sitemap
verified it’s working
unlinked the channel from Test
deleted item Test from PaperUI
created items file with item Test linked to the same zwave channel as before
verified it’s working
deleted items file and sitemap entry
restarted openHAB

Result: no item Test anymore.

This test was done on openHAB snapshot 2.4 #1310

Here are the relevant log entries from events.log:

2018-07-19 10:59:10.037 [.ItemChannelLinkAddedEvent] - Link 'test-zwave:device:uzb:node36:switch_binary1' has been added. //item added through PaperUI
2018-07-19 11:01:36.656 [temChannelLinkRemovedEvent] - Link 'test => zwave:device:uzb:node36:switch_binary1' has been removed.  //item and linked channel deleted through PaperUI
2018-07-19 11:03:59.679 [.ItemChannelLinkAddedEvent] - Link 'Test-zwave:device:uzb:node36:switch_binary' has been added.  //added item through items file
2018-07-19 11:06:46.199 [temChannelLinkRemovedEvent] - Link 'Test => zwave:device:uzb:node36:switch_binary' has been removed.  //item and linked channel removed from items file

Thats odd. I can´t really see how this would be any different, or that I can make something different. Perhaps a glitch in openhab 2.3 then.

If that is the case there would be a couple of more posts regarding that problem :grinning:

Perhaps…
I have a slight feeling it´s not the most common way I´m doing it. First create link items from PaperUI, and after som time, move them to a manuel created item file.
Reason why I´m doing this, is because it´s alot easier to test new devices first, and if/when I´m happy with them, I move them to an item file. Most people would probably use PaperUI created linked items, or manuel created items files, and continue like that.

But I do agree, I would suspect at least one doing the same… It´s only my mother who believe I´m unique :smiley:

1 Like

I just clear the cache and tmp, and rebooted my Rpi. This is what I get:

2018-07-19 23:11:50.808 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'zwave.items'

2018-07-19 23:11:50.895 [WARN ] [ore.common.registry.AbstractRegistry] - SwitchItem with key 'ZWaveNode5ZW100MultiSensor6_BinarySensor' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-19 23:11:50.911 [WARN ] [ore.common.registry.AbstractRegistry] - NumberItem with key 'ZWaveNode5ZW100MultiSensor6_SensorRelativeHumidity' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-19 23:11:50.914 [WARN ] [ore.common.registry.AbstractRegistry] - NumberItem with key 'ZWaveNode5ZW100MultiSensor6_SensorUltraviolet' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-19 23:11:50.917 [WARN ] [ore.common.registry.AbstractRegistry] - NumberItem with key 'ZWaveNode5ZW100MultiSensor6_SensorTemperature' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-19 23:11:51.017 [WARN ] [ore.common.registry.AbstractRegistry] - NumberItem with key 'ZWaveNode5ZW100MultiSensor6_SensorLuminance' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-19 23:11:51.021 [WARN ] [ore.common.registry.AbstractRegistry] - SwitchItem with key 'ZWaveNode5ZW100MultiSensor6_MotionAlarm' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-19 23:11:51.035 [WARN ] [ore.common.registry.AbstractRegistry] - SwitchItem with key 'ZWaveNode5ZW100MultiSensor6_TamperAlarm' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-19 23:11:51.038 [WARN ] [ore.common.registry.AbstractRegistry] - NumberItem with key 'ZWaveNode5ZW100MultiSensor6_BatteryLevel' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-19 23:11:51.047 [WARN ] [ore.common.registry.AbstractRegistry] - NumberItem with key 'ZWaveNode8ST814TemperatureAndHumiditySensor_SensorRelativeHumidity' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-19 23:11:51.060 [WARN ] [ore.common.registry.AbstractRegistry] - NumberItem with key 'ZWaveNode8ST814TemperatureAndHumiditySensor_SensorTemperature' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-19 23:11:51.065 [WARN ] [ore.common.registry.AbstractRegistry] - NumberItem with key 'ZWaveNode8ST814TemperatureAndHumiditySensor_BatteryLevel' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-19 23:11:51.097 [WARN ] [ore.common.registry.AbstractRegistry] - NumberItem with key 'ZWaveNode8ST814TemperatureAndHumiditySensor_SensorTemperature1' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-19 23:11:51.111 [WARN ] [ore.common.registry.AbstractRegistry] - NumberItem with key 'ZWaveNode8ST814TemperatureAndHumiditySensor_SensorRelativeHumidity1' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-19 23:11:51.117 [WARN ] [ore.common.registry.AbstractRegistry] - SwitchItem with key 'Node13_BinarySensor' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-19 23:11:51.120 [WARN ] [ore.common.registry.AbstractRegistry] - NumberItem with key 'Node13_SensorLuminance' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-19 23:11:51.127 [WARN ] [ore.common.registry.AbstractRegistry] - SwitchItem with key 'Node13_AlarmBurglar' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-19 23:11:51.131 [WARN ] [ore.common.registry.AbstractRegistry] - NumberItem with key 'Node13_BatteryLevel' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-19 23:11:51.146 [WARN ] [ore.common.registry.AbstractRegistry] - SwitchItem with key 'Node10_BinarySensor' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-19 23:11:51.149 [WARN ] [ore.common.registry.AbstractRegistry] - NumberItem with key 'Node10_SensorTemperature' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-19 23:11:51.152 [WARN ] [ore.common.registry.AbstractRegistry] - SwitchItem with key 'Node10_AlarmBurglar' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-19 23:11:51.155 [WARN ] [ore.common.registry.AbstractRegistry] - NumberItem with key 'Node10_BatteryLevel' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

So as mentioned. It doesn´t go away clearing cache and rebooting.

This is really starting to get on my nerves. I just discovered two of the items does not work as they´re suppose to…

I´ll try explain again, cause I´m pretty sure this is a bug in Openhab 2.3.0 stable.

  1. I delete all links to items I had created from within PaperUI:
    (notice they´re all gone).

And the logfile:

2018-07-20 23:03:32.366 [temChannelLinkRemovedEvent] - Link 'ZWaveNode5ZW100MultiSensor6_MotionAlarm => zwave:device:fef78fef:node5:alarm_motion' has been removed.
2018-07-20 23:03:32.370 [temChannelLinkRemovedEvent] - Link 'ZWaveNode5ZW100MultiSensor6_SensorRelativeHumidity => zwave:device:fef78fef:node5:sensor_relhumidity' has been removed.
2018-07-20 23:03:32.385 [temChannelLinkRemovedEvent] - Link 'ZWaveNode5ZW100MultiSensor6_BatteryLevel => zwave:device:fef78fef:node5:battery-level' has been removed.
2018-07-20 23:03:32.406 [temChannelLinkRemovedEvent] - Link 'ZWaveNode5ZW100MultiSensor6_SensorUltraviolet => zwave:device:fef78fef:node5:sensor_ultraviolet' has been removed.
2018-07-20 23:03:32.414 [temChannelLinkRemovedEvent] - Link 'ZWaveNode5ZW100MultiSensor6_TamperAlarm => zwave:device:fef78fef:node5:alarm_tamper' has been removed.
2018-07-20 23:03:32.455 [temChannelLinkRemovedEvent] - Link 'ZWaveNode5ZW100MultiSensor6_SensorLuminance => zwave:device:fef78fef:node5:sensor_luminance' has been removed.
2018-07-20 23:03:32.469 [temChannelLinkRemovedEvent] - Link 'ZWaveNode5ZW100MultiSensor6_SensorTemperature => zwave:device:fef78fef:node5:sensor_temperature' has been removed.
2018-07-20 23:03:32.475 [temChannelLinkRemovedEvent] - Link 'ZWaveNode5ZW100MultiSensor6_BinarySensor => zwave:device:fef78fef:node5:sensor_binary' has been removed.

8 items gone.

  1. I then create the items manually in an items file, looking like this:
// Aeotec Multisensor6
Switch  ZWaveNode5ZW100MultiSensor6_BinarySensor 				"Multisensor6 Binary Sensor [%s]"  					<cum_motion>  				{channel="zwave:device:fef78fef:node5:sensor_binary"} 
Number  ZWaveNode5ZW100MultiSensor6_SensorRelativeHumidity 			"Multisensor6 SensorRelativeHumidity [%.0f %%]"   			<Humidity>  	(Fugtighed)		{channel="zwave:device:fef78fef:node5:sensor_relhumidity"} 
Number  ZWaveNode5ZW100MultiSensor6_SensorUltraviolet 				"Multisensor6 ltraviolet Sensor [%.0f %%]"   				<Temperature>  				{channel="zwave:device:fef78fef:node5:sensor_ultraviolet"} 
Number  ZWaveNode5ZW100MultiSensor6_SensorTemperature 				"Multisensor6 Temperatur Sensor [%.1f °C]"   				<cu_heating>  	(Temperatur)		{channel="zwave:device:fef78fef:node5:sensor_temperature"} 
Number  ZWaveNode5ZW100MultiSensor6_SensorLuminance 				"Multisensor6 Lumiance Sensor [%.0f Lux]"   				<Temperature>  				{channel="zwave:device:fef78fef:node5:sensor_luminance"} 
Switch  ZWaveNode5ZW100MultiSensor6_MotionAlarm 				"Multisensor6 MotionAlarm Sensor [%s]"  				<cum_motion>  				{channel="zwave:device:fef78fef:node5:alarm_motion"} 
Switch  ZWaveNode5ZW100MultiSensor6_TamperAlarm 				"Multisensor6 Tamper Alarm Sensor [%s]"  				<switch>  				{channel="zwave:device:fef78fef:node5:alarm_tamper"} 
Number  ZWaveNode5ZW100MultiSensor6_BatteryLevel 				"Multisensor6 Battery Level [%s]"   					<Battery>  	(BatteriLevel)		{channel="zwave:device:fef78fef:node5:battery-level"} 

Notice - I use exactly the same items ID (names) which was created at first in paperUI.

When I save the above item file. OpenHab read the file, and I end up with this log:

2018-07-20 23:15:36.870 [INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'zwave.items'
2018-07-20 23:15:36.973 [WARN ] [ore.common.registry.AbstractRegistry] - SwitchItem with key 'ZWaveNode5ZW100MultiSensor6_BinarySensor' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!
2018-07-20 23:15:36.975 [WARN ] [ore.common.registry.AbstractRegistry] - NumberItem with key 'ZWaveNode5ZW100MultiSensor6_SensorRelativeHumidity' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!
2018-07-20 23:15:36.979 [WARN ] [ore.common.registry.AbstractRegistry] - NumberItem with key 'ZWaveNode5ZW100MultiSensor6_SensorUltraviolet' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!
2018-07-20 23:15:36.982 [WARN ] [ore.common.registry.AbstractRegistry] - NumberItem with key 'ZWaveNode5ZW100MultiSensor6_SensorTemperature' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!
2018-07-20 23:15:36.985 [WARN ] [ore.common.registry.AbstractRegistry] - NumberItem with key 'ZWaveNode5ZW100MultiSensor6_SensorLuminance' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!
2018-07-20 23:15:36.988 [WARN ] [ore.common.registry.AbstractRegistry] - SwitchItem with key 'ZWaveNode5ZW100MultiSensor6_MotionAlarm' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!
2018-07-20 23:15:36.992 [WARN ] [ore.common.registry.AbstractRegistry] - SwitchItem with key 'ZWaveNode5ZW100MultiSensor6_TamperAlarm' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!
2018-07-20 23:15:36.995 [WARN ] [ore.common.registry.AbstractRegistry] - NumberItem with key 'ZWaveNode5ZW100MultiSensor6_BatteryLevel' already exists from provider ManagedItemProvider! Failed to add a second with the same UID from provider GenericItemProvider!

2018-07-20 23:15:37.198 [.ItemChannelLinkAddedEvent] - Link 'ZWaveNode5ZW100MultiSensor6_BinarySensor-zwave:device:fef78fef:node5:sensor_binary' has been added.
2018-07-20 23:15:37.206 [.ItemChannelLinkAddedEvent] - Link 'ZWaveNode5ZW100MultiSensor6_SensorRelativeHumidity-zwave:device:fef78fef:node5:sensor_relhumidity' has been added.
2018-07-20 23:15:37.213 [.ItemChannelLinkAddedEvent] - Link 'ZWaveNode5ZW100MultiSensor6_SensorUltraviolet-zwave:device:fef78fef:node5:sensor_ultraviolet' has been added.
2018-07-20 23:15:37.219 [.ItemChannelLinkAddedEvent] - Link 'ZWaveNode5ZW100MultiSensor6_SensorTemperature-zwave:device:fef78fef:node5:sensor_temperature' has been added.
2018-07-20 23:15:37.226 [.ItemChannelLinkAddedEvent] - Link 'ZWaveNode5ZW100MultiSensor6_SensorLuminance-zwave:device:fef78fef:node5:sensor_luminance' has been added.
2018-07-20 23:15:37.235 [.ItemChannelLinkAddedEvent] - Link 'ZWaveNode5ZW100MultiSensor6_MotionAlarm-zwave:device:fef78fef:node5:alarm_motion' has been added.
2018-07-20 23:15:37.243 [.ItemChannelLinkAddedEvent] - Link 'ZWaveNode5ZW100MultiSensor6_TamperAlarm-zwave:device:fef78fef:node5:alarm_tamper' has been added.
2018-07-20 23:15:37.253 [.ItemChannelLinkAddedEvent] - Link 'ZWaveNode5ZW100MultiSensor6_BatteryLevel-zwave:device:fef78fef:node5:battery-level' has been added.

And paperUI looking like this:

Everything seems good to go, except for the log showing warnings. But there are only one item on each channel. So how come I get this error anyway?

Continue in next message…

I just noticed something is wrong in one of my sitemaps. Two items (from the manual created item file), is NOT read correctly. And I fail to see whats is wrong:

First a screenshot from BasicUI:

Notice the 2 red circles I´ve draw. These two items does NOT match the item file:
First the sitemap:

sitemap alarm label="Alarm og bevægelsesensore"
{
	Frame label="IHC PIRs"{

		Text item=spise_pir
		Text item=aktivitet_pir
		Text item=stue_pir
		Text item=sove_pir
		Text item=casper_pir
		Text item=amanda_pir
		Text item=marc_pir
		Text item=garage_pir
		Text item=pir_indgang

	}

	Frame label="Andre PIRs" {

		Text item=ZWaveNode5ZW100MultiSensor6_BinarySensor
		Text item=ZWaveNode5ZW100MultiSensor6_MotionAlarm
		Text item=Node10_BinarySensor 
		Text item=Node10_AlarmBurglar 
		Text item=Node13_BinarySensor
		Text item=Node13_AlarmBurglar

		Text item=XiaomiMiMotionSensor_MotionStatus label="Xiaomi Bevægelsessensor [%s]" icon="cum_motion"
		Text item=HUE_Occu label="Hue motionsensor"

	}

	Frame label="PIR opdateringer" {

		Group item=motion_stamp label="PIR opdateringer"

	}


	Frame label="Alarm" {

		Text item=alarm_status label="Alarm status (Grøn=klar. Rød=ikke klar.) [%s] "
		Text item=alarm_totalalarm label="Total Alarm tilkoblet [%s]"
		Text item=alarm_sabotagekreds label="Sabotagekreds [%s]"
	}

}

Notice the first two items underneath the label “Andre PIRs”

And now, these two items from the item file, as showed in previous message:

Switch  ZWaveNode5ZW100MultiSensor6_BinarySensor 				"Multisensor6 Binary Sensor [%s]"  					<cum_motion>  				{channel="zwave:device:fef78fef:node5:sensor_binary"} 
Switch  ZWaveNode5ZW100MultiSensor6_MotionAlarm 				"Multisensor6 MotionAlarm Sensor [%s]"  				<cum_motion>  				{channel="zwave:device:fef78fef:node5:alarm_motion"} 

Something weird is going on with the sitemap. Both item states are gone. Labels seems to be only part of the full label description. And for the second item, the icon is also gone.

What the heck is going on? This happened when I move the items from PaperUI to manual created item file, using the same name/ID. But why?
Yesterday after I moved the items to the items file, I cleared the cache&tmp and rebooted the Rpi. It didn´t help or change anything.

I sure could need some help and advice here. A fix could be to rename all the items ofcouse. But as mentioned earlier, I did this in purpose to avoid having to change all sitemaps and rules as well.

I have not tested it yet, but I have a feeling this problem is not specific related to Z-wave devices. I just happen to notice it because I moved all my z-wave things from PaperUI created items to manual created items.
Since @sihui did test this as well, and didn´t have any problems, though he was testing with openhab 2.4. I assume it´s a bug in 2.3.0, cause I fail to see, how I can do this wrong in any way. It would be perfect if someone with 2.3.0 stable could try this as well just to see what happens.

HMPRF!
Now my rules doesn´t seem to work either: (seems to be all my z-wave devices though). They worked earlier today. They stopped after I resaved my item file, to show the log in previous message.
Here is the rule for Multisensor6, which is the same as mentioned in previous message.

rule "Multisensor6 PIR Last Updated"
when
	Item ZWaveNode5ZW100MultiSensor6_MotionAlarm changed from OFF to ON       // motion begin
then
	ZWaveNode5ZW100MultiSensor6_MotionAlarm_stamp.postUpdate(new DateTimeType())   //defaults to now
    logInfo("PIRupdate.rules", "Multisensor 6 opdatering.")
       // ..... do other stuff
end

There is something really weird going on with the item.
This is another sitemap, where the Multisensor6 is working just fine (except it doesnt update timestamp).

		Text item=ZWaveNode5ZW100MultiSensor6_MotionAlarm label="Multisensor6 Bevægelses Alarm [%s]" icon="cum_motion"
		Text item=ZWaveNode5ZW100MultiSensor6_BinarySensor label="Multisensor6 Bevægelse Bin [%s]" icon="cum_motion"

Differences from the previous sitemap file. This one I have defined the label and icon within the sitemap. And it´s working, and its updating it´s state…

EDIT…
After a new reboot, rules are working again. Sitemap still a problem though.

You’ve stated that you are removing links in PaperUI, but are you also deleting the Items that were created? There are Things, links (between Thing channels and Items), and Items. Removing the links does not remove the Item. Note how @sihui phrased it…

A quick way to remove all managed Items is through Karaf…

smarthome:items clear

This will remove all your Items, but the unmanaged ones (in .items files) will come right back. It is also best to restart OH after this, so persistence can restore values, etc. I just tested this when I posted, and I have some errors popping up from rules that are trying to access items with NULL states.

Hmm… I think this is where I did wrong (as well as I misunderstood @sihui )…

I assumed, when creating a link and new item from PaperUI. Removing that link (item) would remove the item as well as showen in the screnshot above. That would explain why I get these warning ofcouse.
But I see now, this is not the case at all. And I never thought of looking into the item menu :tired_face:

Guess I will have to use karaf now, since I only see one set of items in the Items menu of PaperUI.

I´ll give it a try.