Closed garfieldhy closed 3 years ago
Hi @garfieldhy,
Thank you for the details. Looks like this is an issue with the plugin when you're not setting any filter ruleset. You can solve this if you set at least one filter for the sensor (you can filter by Plex account/server name or player name). However, I'm working on a patch what will fix this issue and I'll release it in an hour so, after the update everything should work smoothly.
Great!I tried, now it works perfectly!Thanks a lot!
Glad to hear it! Thanks for reporting the issue! :)
Before you raise an issue ticket, please turn on verbose logging in the plugin's config or run homebridge with
-D
(or--debug
) option.Node.js version Can be found on the Status page of Homebridge UI.
Homebridge version Can be found on the Status page of Homebridge UI.
Plex Webhooks Server plugin version Can be found on the Plugin page of Homebridge UI.
Configuration Can be found on the Config page of Homebridge UI. Only the plugin's related part is needed.
Error message Error message in homebridge log if any. No error message in red
Payload Please note, the payload can carry sensitive information (e.g.: your uuid, your ip address). Before you share, make sure you removed sensitive data from the payload.
Additional info Any information what you think can help the investigation. I can see the payload, playing pause stop information in homebridge log, it means Plex can talk to homebride via webhook, right? But the trigger in homebridge and home app never shows change, no light on, no triggered. My homebridge server is on my Synology Nas (192.168.1.10), My plex server is on one windows pc and one MacMini in the same local network. I want the sensor work so that I can control the theatre led lights on and off using home app automation. Thanks a lot!