Google Home v1.30 will be launched today with a minor rebranding function and some internal changes that show a continuous development in Google for homes, possibly with support for multiple households. There are also more functions for remote control of the smart home, and Smart Displays will use the Google Home application to configure Duo calls. As always, the download links are at the bottom.
Unofficial change log: (things we found)
- Change of name of contexts to live mode
Contexts becomes live mode
 Left: v1.29 . Center: v1.30. Right: looks the same in both versions.
It's a purely cosmetic change, at least for now, but we'll have to get used to a new name. The function that had the Cast devices that went in bicycle through galleries of varied images happens to be called Environment mode. Nothing seems to have changed beyond the name and most of the places where it is referenced, but a name change like this is usually a sign that something else will happen in the near future. There is a small oversight in which the name of the background is still in the title of the screen used to change the settings.
The features described below are probably not yet live, or can only be live for a small percentage of users. Unless stated otherwise, do not expect to see these features if you install the apk. All screenshots and images are true unless otherwise indicated, and the images are only modified to delete personal information.
Follow-up: Google Assistant for Households
A few months ago, the Google application included some references to something called Google Assistant for Households, which seems to carefully identify the differences between the members of their household. We've seen continued growth, since Google may want to know their birthdays and relationships with each other and give them common titles about how they are linked to you.
Now the Google Home application is entering the game. Added some new placeholder chains that will be used to manage household members and their status, so to speak. All the chains are empty, but their names reveal the intention quite clearly. The basic summary is that people can be invited to join a group, which can be accepted or rejected.
There are also chains related to the "managers" and how they are invited. It seems more or less the same situation, but presumably gives them the ability to invite or remove members of the group.
< string name = " add_household_member_label ]" />
< string name = " delete_invitee_failure " />
< string  name = " delete_invitee_success " />
< string name = " cell_label_unassigned " />
< string name =  " candidate_header " />
< string name = " candidate_message " />  < string name = " accept_applicant " />
< string name =  ] " accept_applicant_failure  31] " />
< string name = " invitee_header " />  < string  name = " invitee_message " />
< string name =  " join_this_home ] " />
< string name = " join_this_home_desc " />  < string ] name = " reject_applicant " />
< string name = " reject_applicant_failure " />
< string name = " reject_button_text " />
< string name = " request_failed " />
< string n ame = " request_sent " />
< string name ] = " send_request " />
< string name = " invite_manager_failure " />
< string name = " invite_manager_success " />
< string name = " message_managers_only_you "  />
< string name = " new_manager_invite_message " / >
< string name  = " new_manager_summary_header " />
< string name = " new_manager_services_message " />
< string name = " new_manager_settings_mes salvia " />
< string name = " confirm_manager_message " />
< string name = " confirm_manager_title " />
< string name = " resend_manager_invite_failure " />
< string name = " resend_manager_invite_success " />
< string name = " ] structure_invite_accepted_message " />
< string name = " structure_invite_declined_message " />
< ] c adena name = " structure_invite_device_migration_message " />
< string name = " structure _invite_device_migration_title " />
< string name = " structure_invite_message " />
< string name = " structure_invite_nickname_hint " />
< string name = " structure_invite_nickname_message " />
< string name = " structure_invite_nickname_title " />
< string name = " structure_invite_personal_results_message " />
< string name = " structure_invite_response_title " />
< string name = " structure_invite_response_title_default_home " />
< string  name = " structure_invite_services_message " />
< string name = " structure_invite_settings_message "  />
< string name = " structure_invite_summary_header "  />
< string name  = " accept_button_text " />
< string name  = " confirm_button_text "  />
< string name = " dec line_button_text " />
It should be noted that there are also strings of" applicant "characters, which means that someone can ask for some kind of permission. It is not clear if this is for people who apply to enter a home or request to become a manager. Either way, it's unusual to see both an invitation and application workflow, but it might make more sense when we get some more details.
Support for several homes, maybe?
I will be the first to say that I am skeptical about framing this section as support for multiple houses because it can be easily interpreted differently, but I also recognize that this is a scenario that Google must really support. If you live in more than one place, as many college students and regular travelers often do, you can be part of more than one family group.
There are now chains of placeholders that seem to allow users to add multiple houses. They describe only some basic functions, such as adding new homes, giving them names and opening device configurations for them. Without more text or significant references in the source code, that is the maximum that can be seen from here.
< string name = " add_another_home_label " />
< string name =  " home_name_hint " />
< string name = " home_naming_page_body " />  < string name = " home_naming_page_title " />
< string name = ] "