Open MDAR opened 4 years ago
Hi
Here's a funny observation.
One / Some of my OLED panels don't have all of their sub addresses populated, to give me the ability to "hide" the middle pages, so that I can add them later, without losing the ability to scroll directly to the the buttons I configured first.
As in.. I can go backwards from page 1 to page 8, and miss out 3,4,5,6 until I want them. (Instead of going backwards from 1 straight to page 4)
So the base addresses might look like
01, FF, FF, 04,05
But what happens when I press Button 32 on the OLED. (Page 8, button 4) is that openHAB2 shows it as 'velbus:**:01:ch16'
If I populate the middle two sub address' and re-inialise the OLED Thing, openHAB2 sees button 32 as 'velbus:**:01:ch32'.
Totally my own fault for trying to be clever.
Thanks for your amazing efforts.
I'm building up a new instance of openHAB2 on a new machine (alongside the current setup), using text Item files so that I can explore the Metadata options.
I can report that this behaviour can be seen with all the OLED glass panels I've added so far.
VMBGPOD & VMBELO button events
Buttons 1 to 8 show only as 1 to 8
17 to 32 show in events.log correctly as 17 to 32
However, 9 to 16 double up as HEATER, COOLER, BOOST, PUMP, ALARM1, ALARM2, ALARM3 & ALARM4
(I tried a VMBELO first out of curiosity and it seems the same)
(Also noticed that the VMB4AN data is present, I'll refer to the other issue)