mezz64

Looks like you put everything thing as "Params". They should all be in the "Headers" section, no items defined in Params.

Ok, so nothing obvious in there unfortunately. Does the app allow you to manually activate the vibration and/or show an indicator when the vibration is active?

@themistymay Did this correct itself once you collected some data?

Very late reply, but I noticed in your last snippet you are getting a 403 forbidden error. That usually only happens if the login info is incorrect. Please verify you...

I have limited time these days to maintain this library, but will happily review/approve a pull request if you'd like to submit changes to correct these items.

This is largely an issue with Jellyseer creating duplicate entries rather than reusing the same one. I don't use Jellyseer and only see real devices in ha. There isn't currently...

When you look at your devices list in emby do you see the Jellyseer entries? If they are coming back after removing and re-adding the integration that's telling me they...

That error would suggest the updated firmware has changed the form of the XML response in the event stream which either changed the name for the channel field or removed...

You need to use curl to monitor the alertStream output. Something like this: `curl -u username --digest -N http://YOUR_NVR_IP/ISAPI/Event/notification/alertStream` If you look through other active issues you can find some...

I didn't realize initially this is thrown on setup, the alertStream looks OK so something must be different in triggers. Please post the output of this: `curl -u username --digest...