Discussion: openHAB Google Assistant v4 - Breaking changes incoming

The integration is completely detached from any openHAB release.

It is an standalone service that is only communicating with openHAB through the myopenHAB cloud service.
This means, no matter what openHAB version you are running, you will be affected.

1 Like

Thanks a lot for the suggestions.

  1. I very much agree with the idea regarding documentation. As I have nothing to do with the myopenhab service myself, the second suggestion will require the involvement of other people.

  2. I am very open to setting a release date. So it’s fine for me to wait until the beginning of next year.

  3. Again, as I have no connection to myopenhab myself, we need to find other people if we want to pursue this idea.

1 Like

I’m guessing the myopenhab suggestions would have to go to @digitaldan for consideration?

I don’t think the myopenhab.org home page is going to be a help here, the majority of users are using mobile, voice assistants, etc… with the service, not really so much logging in to the myopenhab Web administration. Its not somewhere i would expect to get news about the Google Home Integration.

We can however pin something to the forum so its visible here as a banner, or top topic. This is where i would expect most people to look first, and where we generally direct people with questions. Happy to help if you want to post/pin an announcement.

1 Like

Fair enough. Would it be possible and of interest to do an opt-in on myopenhab accounts to notify people by email? I’m thinking that would be similar to any other online service.

I just hate the idea of waiting for people to come to us after breaking changes, since it’s out of their control.

No, i don’t think we want to email people from myopenhab, we have only done this once in 10 years, and that was b/c we actually shut down the old service and moved myopenhab to a completely different domain with a different user agreement (and completely deleted the old service and data) . Starting to email people becomes a tricky business with privacy, opt in, email providers, spam, etc… I don’t think this warrants that effort. I have pinned the announcement so its visible for the next 2 weeks.

Sounds good. I’d still favour doing it in January.

1 Like

Great with upgrades so openhab keeps it position.

Is this upgrade going to bring back structure hint to life?

I did not change anything in that regard.
Are there issues that I am not aware of and might require some investigation?

[EDIT] Looked in the latest docs…

structureHint is not (anymore) listed in “action.devices.SYNC” Cloud-to-cloud  |  Google Home Developers
but somehow still in “Method: devices.sync” Method: devices.sync  |  Cloud-to-cloud  |  Google Home Developers

:person_shrugging:

I had been having troubles with structurehint for almost a year or so. Maybe google disabled it or changed method for it. It seems odd if they totaly disabled it hence you could add new homes and rooms i google home. However structurehint stopped working for med so I had to make different prefixes to the rooms instead of using different homes. Is there a way to verify what theyvreally mean in the docs.

Happy new year everyone!

We now entered January… any preferences on how to continue?

Set a date and prepare some more docs?

Happy new year!

I think you’ve covered the changes pretty well in your initial post. We could add some specific examples for the breaking changes to thermostat modes and fan speeds (UI and text-config), so that people will know exactly what to do and can make the edits quickly. I know it’s pretty simple, but examples will just make it crystal clear for people who haven’t touched their configs in a long time.

In the banner announcement, I suggest emphasizing that this change significantly improves the control users have over HVAC items in their homes.

Can users make the changes in advance, or do we have to wait for it to break and then fix it?

Good point. With the current state, things will either break before - if you change the config already or afterwards.
I might introduce an intermediate release, that already provides support for the changed configuration values.

4 Likes

I’m always in favor of having a transition period, even if it’s only brief.

2 Likes

Ditto. I would be inclined to say 4-6 weeks for the intermediate release. We’re still going to have people caught unawares, but then they can’t say we didn’t give ample warning in the community.

I have subscribed to the announcement topic of this forum. This emails me instantly when a topic is posted in the announcement category of this forum and since the replies are locked out, the emails are minimal and always of interest. No need to create a new way when one already exists, but maybe that could be promoted more as a way to stay informed?

Yeah, I think that’s a great idea. I don’t see a “subscribe” option. Am I correct in thinking that you’re setting the Announcements category to “Watching”…

And then enabling “Email me when I am quoted, replied to, my @username is mentioned, or when there is new activity in my watched categories, tags or topics”?

image

The only downside I see is that there’s no way to only get the watched categories. It’s all or nothing. But that’s less of a concern for people who don’t visit the community daily.

Yes that is what I did, it’s normal to know at a topic level this exists, but my guess is most people do not know you can do it at the category level. You only get 1 to 3 a month so this works well at staying updated and I know exactly when the latest milestone is ready for download.

1 Like

I definitely didn’t know it could be done on a category level. But don’t you also get emails whenever someone replies or @'s you?

@ yes
A direct reply to a post = yes
A reply in the thread = no

I use tracking level not watching on threads, like this one, so that no emails get sent unless it is a direct reply. Not sure if I changed the default somewhere to make it default to tracking.

2 Likes