I’m running OH3 M2 on a rPi 4. In using the Astro Binding, I need to link items to the channels rise#start and set#start. However, when I link one of them and then link the other, both get updated to the currently linked item values. In other words, when I link rise#start then link set#start, the rise#start gets overwritten with the the values in set#start.
Is this is bug or am I not using the binding correctly?
Look closely, you’ll see it’s actually the same item.
I think it’s a little flaw in the default suggested name when you use the “Add as Equipment/Add Points” screen, since the 2 channels have the same label.
Try again and pay attention to the names, they have to be different.
The Item name “LocalSun_StartTime” is linked to both rise#start and set#start Channels. Unfortunately, the item name cannot be changed in the UI. Would this be considered a bug then? The fix would be to give unique items names to the items linked with rise#start and set#start.
There was a long thread on this on the forum already and the tl;dr is it’s not that simple. The only reason it works that way using .items files is that when you reload it, all of those Items and links are deleted and then recreated.
But when stuff is stored in JSONDB, the links are stored separately from the Items and the Things and there is a ripple effect that can cause serious problems. I think the conclusion was that it cannot be handled strictly in the UI and the core maintainers do not want to implement that in core because of the complexity and potential for corruption. That’s my recollection at least. I may be misremembering.