Pierre Ståhl

New update pushed, hopefully fixes the issues! 🤞

It was a stupid asyncio mistake (didn't `await` properly). Should be fixed now! Ran pylint on the code a fixed quite a few issues here and there, hope it works...

So, the problem is this. Which "function" that is ought to be used to figure out latest motion, depends on the firmware version. D-link changed it at some point. I...

Now I have resurrected an old sensor so that I can actually try the code myself... Latest push now works with `unique_id`, but I guess I need to use config...

This is much easier to review, I will have look again. Would be great if you could get a beta tester or two to verify that it works out in...

You probably have a sleep proxy on your network, so it goes to sleep. See https://github.com/postlund/pyatv/issues/595 sh or details. Scanning and making pyatv connect again is probably the only solution.

Maybe this is the reason why the integration breaks for some people and doesn't come back up again until a power on+off is done in Home Assistant... Very unclean of...

Yeah, the part of not closing the socket (which is what I meant in the last sentence I wrote in my previous post) is not very sane. One problem with...

The problem is that the connection is not terminated, so pyatv is never notified of what is happening. Since I can't reproduce this myself, it's very hard to debug. But...

I believe this will "sort of" solve itself with the next release of pyatv, since I've added TCP keep-alive now. Keep-alive messages are sent (on TCP level) and the connection...