Dear users of the openHAB Google Assistant integration,
in the next few weeks, we would like to release an update that contains some breaking changes. For some items, users will need to adjust their configuration. A new SYNC will also be required.
For this reason, we would first like to collect feedback and then announce a fixed date for publishing the changes so that everyone can prepare their setup.
Please join the Discussion: openHAB Google Assistant v4 - Breaking changes incoming to clarify any questions, doubts or wishes.
Breaking Changes
- After the update the group members will be stored in customData. This means existing (group) devices will only work after a new SYNC.
- The
modes
configuration for Thermostats will be renamed tothermostatModes
- users will have to adjust their configuration. - The
speeds
configuration for Fans will be renamed tofanSpeeds
- users will have to adjust their configuration. - As item types of group members will then be validated, users might see devices disappearing in Google Home if they used an unsupported item within a group device. (Documentation is updated accordingly)
More details and other changes
-
Item names for group members will be stored in customData to save a query request to openHAB when executing commands.
- For commands that need the current state the query request is still needed (thermostat commands or relative volume).
- Also some other configuration options are stored in customData.
- Item types of group members will now be validated.
- There is no change on the user’s side required but they will need to do a SYNC.
-
Add a lot of new functionality to Fan devices (AirPurifier, Fan, Hood)
- OnOff (separate power switch if used as a group)
- FanSpeed (separate fan speed if used as a group)
- Modes (yes, for the first time modes are available)
- SensorState (for FilterLifeTime and PM2.5 - no clue how to query those)
-
Add AC Unit device
- Basically just a combination of the extended Fan and the Thermostat with all control and config options of both
Potential Issues
- As customData is limited to 512 bytes it could be an issue to store very long item names e.g. for devices with a lot of members like thermostat (ref. Cloud-to-cloud | Google Home Developers)