The short answer is probably not..
The longer more involved answer is there are potential workarounds.. each with their own issues etc.
- Sharing your devices from your remote site to your main site using an older but awesome community app called Hub Connect.
The issue here is you'd need to have a mostly persistent link between your remote and main sites - like with a VPN. Also you'd have to name your devices specifically to distinguish one site for another.. Alexa turn on "Cabin Lights" vs "Home Lights" etc.
- Incorporate a companion server like a Raspberry PI and run Node-RED on it. This will allow you to install a node called node-red-contrib-alexa-remote2-applestrudel.
This does not require a "skill" and will allow you to control devices through custom routines. Not as nice as direct sharing of devices like you can do with HE Alexa Skill. The cool bit is the commands can be the same at both the remote site and the local site.
- "HomeAssistant" companion server - a very flexible/powerful home automation system in it's own right but can be bridged to HE and use the HE's devices. Drawback for HA is it can get complicated and requires some technical skill.. I have not implemented any of these potential solutions so cannot say if they would work for you or not. Also this article is old so not sure if all these are still working - the subscription one probably is but not a fan of that.
-
HomeBridge companion server with HomeBridge Alexa. This requires a paid subscription to a company/individuals I am not familiar with so can't recommend at the moment (plus I hate cloud subscriptions!).
-
There might also be a way to share devices via MQTT but that involves more fun technical things..
