15.10.2021, 12:58
Daniel,
Thanks for the feedback. I'm not sure how Google's constraints is affecting this though. From my understanding there is a mapping between LM objects and traits. You should be free to implement your own converter logic to make it consistent, as I don't see myself or others redoing all curtains configurations and changing Mosaic widgets to work with inverted state just for this integration. In my opinion there should be converter within LM cloud that just does the conversion from trait states to KNX-defined states and vice versa, Google testing process does not need to fail on this check as feedback from converter should be consistent for Google on one side, and consistent for KNX on the other.
2) The same goes with thermostat. You're creating abstraction layer (not 1:1 value mapping) for KNX thermostats and just need to make it a bit more consistent.
I don't really want to change object type as I don't want to research what it will affect, I will probably wait for the fix. Also i just noticed that for some reason Mosaic2 settings are now broken - I cannot select HVAC mode object in the "mode" selection (for the same reason – filtered out), but previously created widget retained old connection with this object and still works, although its settings screen have empty field now. Mosaic3 don't have this problem but it seems it allows to choose almost any object except 1bit.
I haven't migrated interface to Mosaic3 as it seems a bit more buggy than version 2.
Back to the thermostat, I've followed your suggestion and created Control trait, but since i cannot remove default trait, it does not override thermostat UI (that is, UI is still non-functional). If i remove all settings in the default, the thermostat UI is just empty. And refrigerator UI doesn't have UI in GH yet
Thanks for the feedback. I'm not sure how Google's constraints is affecting this though. From my understanding there is a mapping between LM objects and traits. You should be free to implement your own converter logic to make it consistent, as I don't see myself or others redoing all curtains configurations and changing Mosaic widgets to work with inverted state just for this integration. In my opinion there should be converter within LM cloud that just does the conversion from trait states to KNX-defined states and vice versa, Google testing process does not need to fail on this check as feedback from converter should be consistent for Google on one side, and consistent for KNX on the other.
2) The same goes with thermostat. You're creating abstraction layer (not 1:1 value mapping) for KNX thermostats and just need to make it a bit more consistent.
I don't really want to change object type as I don't want to research what it will affect, I will probably wait for the fix. Also i just noticed that for some reason Mosaic2 settings are now broken - I cannot select HVAC mode object in the "mode" selection (for the same reason – filtered out), but previously created widget retained old connection with this object and still works, although its settings screen have empty field now. Mosaic3 don't have this problem but it seems it allows to choose almost any object except 1bit.
I haven't migrated interface to Mosaic3 as it seems a bit more buggy than version 2.Back to the thermostat, I've followed your suggestion and created Control trait, but since i cannot remove default trait, it does not override thermostat UI (that is, UI is still non-functional). If i remove all settings in the default, the thermostat UI is just empty. And refrigerator UI doesn't have UI in GH yet