spacemanspiff2007

> this is why I was telling you to use mqtt explorer, with it's tree view it's quite easy to find all valueIds This is what mqtt explorer is showing...

> You should firstly trigger a notification It's a notification for over-current, meaning the the load exceeds the device specifications. I'm hesitant to try to trigger a notification e.g. by...

> Similar for me, and that was the reason to create this PR. It forces you to add the unit again after retrieving the average. But why? I thought when...

> That's true if you immediately post an update to an item that has the same unit in metadata as the unit for the item you retrieve from persistence. That's...

> ... at least for Zwave and Zigbee, the discovered channels are shown in the Code tab. This is what gets shown for a fully discovered Smart Color Button (Z-Wave)...

> Do you see Channels in the Channels tab? In the RAW JSON from the REST API? Yes - the rest response for the thing correctly returns the channels and...

You assume that all devices are fully discoverable by auto discovery in the first place which is not always the case. Sometimes the thing discovery also does not work or...

> Are there cases where the Thing is manually created but the Channels are discovered? I know of places where the Things are wholly manually configured and other cases where...

What happens when you have `mapdb` configured for the items? Wouldn't then the item state be restored and expire run as expected? > Could also have "initial expiration duration" While...

Sorry - I don't understand your last two points. Can you rephrase them a little bit. My suggestion was that instead of ```` Number MyNumber { expire="5s,state=0,initial_expiration_duration=5s" } ```` this...