Stephen Vanterpool

No pressure :) Just wanted to put it on the docket.

I'm seeing something slightly different. When I have 2 service nodes linked, neither actually calls home assistant. Very strange.

Glad it's not just me screwing up somewhere. I'll take a look after i ship :)

Your fork totally fixed it for me. Thanks!

Did anone ever get this going? I'm poking at ItsEcholot's sensor trying to get it going, but would love to know if anyone has already solved this.

Ahh, I found a simple thing for my needs. I configured a REST sensor using a long lived token for auth and this lets me get my count of inbox...

``` sensor: - platform: rest resource: https://paperless.server.com/api/documents/ headers: Authorization: !secret paperless_auth_header params: query: "tag:inbox" value_template: "{{ value_json.count }}" name: "Paperless Inbox" ``` Then in my secrets file: ``` paperless_auth_header: Token...

I have very similar behavior. When near the problematic AP, it downloads for like 30 seconds, then appears to hunt for a new ap, so download stops, then starts again....

+1 here

Same issue. Was able to wake up via other paths.