Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remote HomeAssistant doesn't work if "mobile_app" not active #246

Open
denkyem opened this issue Aug 2, 2023 · 1 comment
Open

Remote HomeAssistant doesn't work if "mobile_app" not active #246

denkyem opened this issue Aug 2, 2023 · 1 comment

Comments

@denkyem
Copy link

denkyem commented Aug 2, 2023

Hi

I'm implementing a 2nd instance of HomeAssistant connected to my main one with limited access to entities, services, etc.
This is to give access to guests to some functions, like lights, covers, etc, but I don't want them to change my AC or activate/deactivate my alarm (for example).

So I installed my 2nd instance on docker and I'm deactivating everything that I don't need.
Instead of have "default_config:" on my configuration.yaml, I'm replacing with the integrations that I really need.
For example, I don't need automations, scripts, scenes, etc.

I only need history, logger and person, but for some reason the "remote_homeassistant" needs the "mobile_app" integration or it returns an error and the entities states are not updated.
image

As soon as I activate the mobile_app integration, the remote_homeassistant works fine.

It is possible that this is not an error and the integration "mobile_app" is actually necessary. Just want to confirm that.

@Nornode
Copy link

Nornode commented Aug 5, 2023

I wonder, do you see the same behaviour as in #245 ?

In my case I got mobile_app active on both instances.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants