I have made mistakes and slowly learning - the hard way. I have a home in MA and vacation home in NH. I have a Habitat hub in each home. I also have an Amazon account to use voice commands to control devices in those homes. In an effort to make usage of the system easier by voice for everyone in the home, I have learned / found that I really need to have 2 completely separate Amazon accounts; one for each home (not just using individual accounts in an Amazon Family account). The need to preface each command by calling out the home location complicates usage far too much. I currently have one email address for my Habitat account that allows me to select access to the two individual habitat hubs one at a time. Rather than tell you what I've been told by AI Chatbots - I'd rather hear from those who have similar situations of 2 or more properties with 2 or more Hubitat hubs and using voice control with Amazon Echo devices to operate their homes. Please detail the drawbacks and perks you learned along the way. Thank you.
Google is your friend. Easy to set up a separate Gmail account for one of the properties. Assuming you have more than one credit card a second Amazon account should be simple enough.
Yeah, I’ve chatted with Gemini Pro Deep Thinking mode several times and learned bits and pieces - each time requiring significant changes that don’t quite measure up. Email accounts are easy. Credit cards are easy. 2 Alexa accounts are too. Do I need 2 seperate Hubitat accounts as well?
The Hubitat Amazon Echo Skill (Amazon Echo Skill | Hubitat Documentation) is tied back to your hub via your Hubitat account, so I think you need 2 separate Hubitat accounts to have Alexa connecting to separate hubs.
I have seen this mention before, however it appears that you have to select which hub(s) on your Hubitat account should be connected to the Echo Skill - - from the graphic Step 8 the link you provided above (I’m unable to include the image in this post - for whatever reason).
They show a single hub, but the instructions show that you can “Select the hub you would like allow access” (from multiple hubs - if you have more than one on your account).
Am I misunderstanding something here?
Join the Owners Group so you can post images:
https://community.hubitat.com/g/owners
As I understand it, only a single hub from your Hubitat acccount gets exposed to Alexa with the existing skill. That's why I think you'd need a 2nd Hubitat account (for the 2nd hub, to expose the other Alexa on the 2nd Amazon account).
I have a very similar scenario. Three hubs and eight Alexas at our winter house, one hub and three Alexas at our summer house. Not that it’s relevant, but I have all of the Alexas set to sassy mode, which makes things interesting at times.
All of the Alexas are on the same account. The Alexa integration runs on a hub at our winter home.
Both homes have Ubiquity hardware; a UDM-PRO SE at the winter house and a UDR at the summer house, with a permanent site-to-site VPN connecting the two. Secure and IOT networks at both, with appropriate firewall zones and rules.
All of the hubs at the winter house have hub mesh set up between them. The hub at the summer house also has hub mesh connecting it to one hub at the winter house.
I also use Owntracks to track presence (it’s just me and my wife). Our phones report to one of the hubs at the winter house, and that hub forwards the data to a “secondary” Owntracks app at the summer house, so both hubs always have our location info.
Then I use presense to control where things happen. I have Alexa device groups set up in Echo Speaks, and a general purpose notify rule in RM. It makes decisions based on where we are and plays notifications on the appropriate Alexa device groups. If we’re not at either location, important notifications get sent to our phones using Pushover.
For commands I do something similar. For example, we have a “goodnight” routine I set up in the Alexa app, which toggles a virtual switch on the hub at our winter house, which in turn causes a RM rule to fire. Depending on where we are, it turns the bedroom lights off and the bedroom fan on in the appropriate bedroom. If we’re at the winter house, it just invokes those switches directly. If we’re at the summer house, it invokes the switches on the summer house hub via hub mesh.
I have some automations that are more complex, but they’re basically variants of this. This eliminates the need to have multiple Amazon accounts, which isn’t ideal because you won’t get notifications for package deliveries and such if all your devices aren’t on the same account.
Two of the key pieces that makes all this work is using Hub Mesh across different subnets, and the site-to-site VPN. It took two summers of tinkering to sort it all out, but it works well.
And WAF is high, which is the primary metric when determining the success of any home automation project 
Hi! I also have a similar scenario, with a twist!
We have had two separate residences for some time, but with a wife who is into real estate, we have swapped houses several times, making for some interesting permutations and combinations! Generally, utilities such as electricity and internet at each residenceare with different providers (with different accounts) due to regional variations in pricing and availability.
The solution I am implementing is to have three (yes three!!) gmail addresses - one for each property and one for me personally. My logic is that anything that belongs to the property entity such as rates, electricity, internet, Amazon accounts, etc, are assigned to the respective property email accounts, whilst anything personal is assigned to the third email account. Redirection/forwarding can consolidate if having separate accounts is problematic.
This will also prove beneficial if we again change a property (again!!), as the property email address can be assigned to the new owner. I have two Amazon accounts, but (at the moment) a single Hubitat account and all seems well - including voice commands.
mclass