Plex dont find it about antennas

[behinddesign]

"changed also from bridge to host." - I would suspect this is the magic fix. The port allocations will no longer work alone with SSDP. It will all work however if running Plex on host and Antennas on host (Or both on bare metal). This is due to the way Plex uses SSDP (multicast) now.

TheJF - Perhaps the readme should be changed? (I'm not a network expert but googling around for multicast and SSDP repeatedly explain that it won't work out of the box).

[behinddesign]

Similar issue. If your case is like mine then you'll need to use host networking on docker and not bridge. You will then see device.xml being requested (see docker logs). Without this the SSDP packets never get handled properly and Plex doesn't know the device is 'alive'.

[etheralm]

I have both plex and antennas running in host network mode and it did work up until a month ago when after a plex server server update it stopped being able to find the tuner at all, so not sure if switching to host will help.

[behinddesign]

After writing the above I had a few issues. Even after adding the device I could not edit channels shortly after - showing the can't find device message in the DVR settings.

I tinkered around with this a little on my fork https://github.com/behinddesign/antennas (behinddesign/antennas) for the docker image.

With this, I've adjusted the device.xml to output a valid UUID and change the location of the connectionmanager, which to me seemed to be missing the .xml extension (However I didn't see logs of it ever being called)

Things to note:

1. If you can't find the device, restart plex and don't leave any time attempting to add the device, in failing that manually specify the IP and port of antennas
2. Immediately after adding the dvr device to plex, restart plex. This will cause the device not found error to go away. On my version it doesn't appear to ever show the device not found error when editing channels. With this original version it would break after a certain amount of time or almost immediately, there appear to be no rhyme or reason to this.
3. You may have to delete and re-add your device if you test my fork to see if the changes fix it for you. I suspect the valid UUID (UDN) is the cause?

YMMV, Hopefully TheJF will be able to shed more light on this.

[behinddesign]

I've now added a pull request with the code changes #24

[etheralm]

thank you, I tried you docker image today but plex still couldn't find the antennas dvr even when entering the ip/hostname manually. I'll try to run both on seperate physical hosts over the weekend and see if I can get it to work that way.

[Oggymator]

At the moment I tried Antennas und Telly(Plex DVR for IPTV).
Telly works at the moment a bit better, I think one reason could be the name. Possible to change in antennas dockers?

But for both I have the problem, Plex find it, I click on it and it is dead.

I run Antennas and Telly in Docker.
Plex on an other Windows VM.

[behinddesign]

etheralm - Then I have a feeling that our issues aren't related. In any case the fix will, once you do manage to get it working should make it work better.

Oggymator - On my pull request I've adjusted the name and you can test this docker image : behinddesign/antennas until TheJF reviews the pull request or comes back with something better. 12dc9e3#diff-274b92298b37e3a907329082c8c2e38eL4

[jfarseneau]

Thanks for the PR @behinddesign ! I looked at it and it looks very solid. I'll give it a whirl tonight or early tomorrow for testing's sake, but pretty sure that it'll work out of the box and won't need changes, and I'll merge it in if there's no problem.

[Oggymator]

hm, I played a bit with it and it seems working now. don't know what was the problem first :(
changed also from bridge to host.

at the moment I could finish the settings for DVR the first time, now I have to wait for EPG data.

EDIT: but the stream will not start now loads endless and say error, hm.

[behinddesign]

I have found the web interface viewing for plex to be very flakey with DVR. I use a firestick and Plex Media Center (on Windows and Mac) and they all work fine.

If TVH shows that the stream is running and the webinterface continues to 'load', this is a sign that it is working, but not via the web interface, at least for me.

[jfarseneau]

Yeah, hmm, I merged in your changes @behinddesign, those were great, but there's definitely a problem with the Docker config. If you run it straight from Node, discovery now works flawlessly which is excellent. But if I try to run it on Docker, it doesn't work even after exposing port 1900 and 65001. And --net=host for me actually doesn't allow me to even access Antennas' frontend now, which is super weird.

I'll add a thing to run it straight using node as a process, using node index.js >/dev/null 2>&1 & and that makes it run pretty smooth, but definitely not a perfect solution.

[Oggymator]

Docker is no more working, with your changes:

`Broadcasting to SSDP for discovery...

events.js:165

  throw er; // Unhandled 'error' event

  ^

Error: listen EADDRINUSE :::5004

at Server.setupListenHandle [as _listen2] (net.js:1346:14)

at listenInCluster (net.js:1387:12)

at Server.listen (net.js:1475:7)

at Application.listen (/antennas/node_modules/koa/lib/application.js:64:19)

at Object.<anonymous> (/antennas/index.js:27:7)

at Module._compile (internal/modules/cjs/loader.js:654:30)

at Object.Module._extensions..js (internal/modules/cjs/loader.js:665:10)

at Module.load (internal/modules/cjs/loader.js:566:32)

at tryModuleLoad (internal/modules/cjs/loader.js:506:12)

at Function.Module._load (internal/modules/cjs/loader.js:498:3)

at Function.Module.runMain (internal/modules/cjs/loader.js:695:10)

at startup (internal/bootstrap/node.js:201:19)

at bootstrapNodeJSCore (internal/bootstrap/node.js:516:3)

Emitted 'error' event at:

at emitErrorNT (net.js:1366:8)

at process._tickCallback (internal/process/next_tick.js:178:19)

at Function.Module.runMain (internal/modules/cjs/loader.js:697:11)

at startup (internal/bootstrap/node.js:201:19)

at bootstrapNodeJSCore (internal/bootstrap/node.js:516:3)`

[jfarseneau]

@Oggymator What is the docker command you've used to run this?

Because it works for me like this:

[Oggymator]

I used;
sudo docker run -p 5004:5004 --network host - e ANTENNAS_URL=http://xxx.xxx.xxx.xxx:5004 -e TVHEADEND_URL=http://test:[email protected]:9981 thejf/antennas

[jfarseneau]

Personally, I never got it to work using --net=host or --network host

What seems to be happening in your case is that you have another server (another Antennas, or maybe Telly?) that's running on port 5004 (that's what they mean by Error: listen EADDRINUSE :::5004, which, isn't very clear English :P) Ports can only be used by one thing at a time, so if something else is already using it, it'll cause an error for anything else that tries to use it.

So this is why in your case your Antennas server isn't working, because there's already something else using port 5004. If you get rid of the other thing, then it should work.

[Oggymator]

damn, you are right.
there was a docker with cowries names, so I never thought that could be antennas.
Now it works again.

But I could not solve the problem, that now stream is starting.
I used it on Web App and iOS and tvOS device.
TVH client works well.

[jfarseneau]

Discovery should now be solved on the latest version