HeedfulCrayon
HeedfulCrayon
Related to #168 too
If it is MQTT related, it is likely the autodiscovery in hass-workstation-service isn't quite right. I haven't experienced this in other integrations
> The media_player entity as it currently exists is mostly a dummy entity for service calls to target, but you should still be able to use the normal media_player functions...
I don't even know if these are accessible, but it would be nice to get this info into home assistant (if anything, just basic counts for most things) PFBlockerNG IP...
They definitely did accomplish it. They didn't have a whitelist functionality, they just had a sensor for all the processes using the microphone/webcam 
Creating a new user only fixes it temporarily. After a few days it will go back to doing the same thing
> I'm a bit concerned the dev doesn't seem to react on this issue... Is there anyone still maintaining this code ? Calm down, last commit was 14 days ago....
Just saying, mine is still going just fine
@Snacker001 I am using it in the Home Assistant add-on and I am using the native yaml automations: ``` id: 'google_assistant_relay_heartbeat' alias: Google Assistant Relay Heartbeat description: 'Keeps the token...
Mine finally died. Looks like running an automation periodically doesn't seem to fix the issue