-
Notifications
You must be signed in to change notification settings - Fork 34
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
Screencast somehow collides with Remote Control API and the Integration to Home Assistant #122
Comments
@fribse Hmm my intial guess would be a port collision or something similar. Do you have any logs of this? and what exactly are you using for Home Assistant and Remote Control? I might have some time to dig into this. |
Odd, Remote control uses port 8080, where can I find some extra log files? |
Open ports without ScreenCast module active:
|
With ScreenCast in there are a lot more ports:
Not sure if that helps at all? |
This list might be better, without ScreenCast:
With screencast:
|
I just tested some more together with the @sindrebroch that does the Home Assistant Integration. Without ScreenCast With ScreenCast Hmmm? So both the module scheduler and the remote-control is somehow affected. |
I just did a complete reinstall on a new SD card. Raspbian Buster, monitor in portrait mode (display_rotate=1). |
Yeah, I know this is fluffy.
There is an integration into Home Assistant that uses the Remote Control API.
If I activate the ScreenCast module, the integration doesn't work.
I'm posting it here, but I will of course also post it in the Home Assistant Integration.
Maybe you can explain me how this might happen, so I can explain it to the developer of the integration?
The text was updated successfully, but these errors were encountered: