It’d be helpful to see the events.log for a working caldav-command update of your “min” Item
That’s correct. That comes from autoupdate, and
(a) it only appears if a command is expected to make a change e.g. send command ON to a switch with current state OFF, and
(b) autoupdate can be optionally disabled per Item.
This messaging from autoupdate is new in 2.4
This stuff is important here, because if the caldav binding is sending commands and you are looking at states, you are totally reliant on autoupdate working.
I don’t like the long names, but I’m sure other people would have run into this before if there was an issue? Won’t rule it out though - some localised truncation effect would make both your long names appear to refer to the same Item sometimes.
I don’t like these numeric-only commands being sent to
Number:Temperature type Items, because they expect something like 27°C
I’ve little idea of what you are “supposed” to send instead, this UoM stuff seems to be a bit trial and error for me.
No idea why your Items behave differently if its a UoM issue. You seem to be saying there’s persistence involved here as well, restore on startup perhaps?