Add Airflow, Application, Channel, and Mode Semantic Properties

[jimtng]

Add new properties to support TV and Airconditioner points

Also upgrade groovy version to work with Java21
Adjust copyright header

[jimtng]

@andrewfg fyi

[lsiepel]

Please separate version upgrade from semantic tags.

Not sure about Mode, might be fine but it seems not as specific as channel and application. Also wondering if adding these tags would need additional work in mainUI, @ghys ?

[jimtng]

I've split them up into separate commits

[lsiepel]

I've split them up into separate commits

All commits are pushed? As I still see the version change and the tag together

[jlaur]

@jimtng - can you add Airflow to the PR title as well (for the release notes)?

[jimtng]

I've split them up into separate commits

All commits are pushed? As I still see the version change and the tag together

Yes they are split up properly. There are 4 commits with airflow in a separate commit to the other 3 tags. Should I split each tag into a separate commit?

[jimtng]

@jimtng - can you add Airflow to the PR title as well (for the release notes)?

Title updated

[rkoshak]

Also wondering if adding these tags would need additional work in mainUI, @ghys ?

I can't definitively answer but given that custom tags are supported everywhere and I believe MainUI uses the REST API endpoint to get the lags there shouldn't be any wider changes required.

But I wonder if it makes sense to have a more deliberate discussion on what tags belong or not at a higher level and come up with a PR to address them all instead adding two here and four there in separate PRs without really designing the tags.

For example, Battery, online status, pressure, VoC, Radon, air quality, are missing properties. There are a bunch of car related points and properties missing and car is missing from Equipment.

On-the-other-hand, do we really need seven different types of Doors at the Equipment level and does it make sense to have smokealarm at all given the alarm/smoke point/property combo?

I worry that if we just add stuff here and there the lists will always remain inconsistent and eventually grow beyond usability.

Note, I'm all for adding the four properties listed here. Even mode makkes sense: HVAC Equipment has a Control/Mode Point to set the heating/cooling/auto status.

[andrewfg]

I worry that if we just add stuff here and there the lists will always remain inconsistent and eventually grow beyond usability.

See #4615 in which we are seeking to apply an XSD schema restriction so that addon developers will be able to offer one “point” tag and one “property” tag; this offer would be a hint that users could choose to accept or override.

Battery, online status, pressure, VoC, Radon, air quality, are missing properties.

@rkoshak may I therefore make a call to action on you to open a PR for those; or at least open an Issue..

do we really need seven different types of Doors at the Equipment level

PS see also #4617 ..

[rkoshak]

@rkoshak may I therefore make a call to action on you to open a PR for those; or at least open an Issue..

That misses my whole point.

But I was already creating a PR. #4619

[lolodomo]

Also upgrade groovy version to work with Java21
Adjust copyright header

Please create a separate PR for that to have it merged quickly even if your proposal of new properties is finally not validated.

[jimtng]

Please create a separate PR for that to have it merged quickly even if your proposal of new properties is finally not validated.

#4621

[lolodomo]

Should be rebased now that #4621 is merged.

[jimtng]

rebased

[lsiepel]

I've split them up into separate commits

Bit late, but I meant PR’s not commits.