search

craigmox / cetonproxy

An app that allows a Ceton InfiniTV PCI/network tuner to appear as a SiliconDust HDHomeRun to DVR apps like NextPVR, Plex, and Emby.
GNU General Public License v3.0
23 stars 7 forks source link

Cannot tune in a channel in plex #27

Closed 4MAZ closed 3 years ago

4MAZ commented 3 years ago

I have the proxy installed along side plex. In plex I can see the card and go through the setup and scan all the channels. Once the guide loads I cannot open any channel. I receive the error "could not tune channel. Please check your tuner or antenna. When I do try to load one I did notice in the dashbaord that is does show using one tuner.

mpatriche commented 3 years ago

Hi, Would you post the log file? Also, the CableCard has been activated by your provider, correct? Thanks! Mike

4MAZ commented 3 years ago

Yes the card is for sure activated. The Caton software confirms it and I have used wmc on windows 7 and open channels with it no problem. I apologize for the lack of knowledge but which log would you like?

mpatriche commented 3 years ago

No need to apologize...happy to help.. Within the CetonProxy app, you have a button toward the bottom labeled 'Show config folder'. Click on that, and you should see several files. If you could post 'cetonproxydefault.log' and 'cetonproxydiscovery.log', or email them to me. My email is listed under my GitHub profile if you want to do it that way.

4MAZ commented 3 years ago

Cetonproxydefault: "[2021-03-06 07:22:03.154] Starting cetonproxy [2021-03-06 07:22:04.999] Checking tuner count [2021-03-06 07:22:05.173] Determined tuner count: 4 [2021-03-06 07:22:05.173] Identifying tuner model [2021-03-06 07:22:05.173] Getting diag\Host_Connection for tuner 0 [2021-03-06 07:22:05.193] Received diag\Host_Connection for tuner 0: "pci/ethernet" [2021-03-06 07:22:05.193] Determined tuner model: PCI [2021-03-06 07:22:05.196] Detected tuner listen IP: 192.168.200.2 [2021-03-06 07:22:05.196] Getting diag\Host_Firmware for tuner 0 [2021-03-06 07:22:05.225] Received diag\Host_Firmware for tuner 0: "14.10.3.163" [2021-03-06 07:22:09.643] Received lineup status request from 192.168.2.134: /lineup_status.json [2021-03-06 07:22:09.643] Finished lineup status request from 192.168.2.134: /lineup_status.json [2021-03-06 07:22:15.611] Received device.xml request from 192.168.2.134: /device.xml [2021-03-06 07:22:15.611] Finished device.xml request from 192.168.2.134: /device.xml [2021-03-06 07:22:16.907] Received lineup status request from 192.168.2.134: /lineup_status.json [2021-03-06 07:22:16.907] Finished lineup status request from 192.168.2.134: /lineup_status.json"

Cetonproxydiscovery: "[2021-03-06 07:22:04.967] Received SSDP discovery response from 192.168.200.1 on 192.168.200.2: HTTP/1.1 200 OK CACHE-CONTROL: max-age=300 DATE: Thu, 01 Jan 1970 00:03:10 GMT EXT: LOCATION: http://192.168.200.1/description.xml SERVER: Linux/3.0.1+, UPnP/1.0 ST: urn:schemas-cetoncorp-com:device:SecureContainer:1 USN: uuid:89333102-EBE5-11D8-AC9A-0000080790B0::urn:schemas-cetoncorp-com:device:SecureContainer:1

[2021-03-06 07:22:04.983] Received SSDP discovery response from 192.168.200.1 on 192.168.200.2: HTTP/1.1 200 OK CACHE-CONTROL: max-age=300 DATE: Thu, 01 Jan 1970 00:03:10 GMT EXT: LOCATION: http://192.168.200.1/description.xml SERVER: Linux/3.0.1+, UPnP/1.0 ST: urn:schemas-cetoncorp-com:device:SecureContainer:1 USN: uuid:89333102-EBE5-11D8-AC9A-0000080790B7::urn:schemas-cetoncorp-com:device:SecureContainer:1

[2021-03-06 07:22:04.987] Received SSDP discovery response from 192.168.200.1 on 192.168.200.2: HTTP/1.1 200 OK CACHE-CONTROL: max-age=300 DATE: Thu, 01 Jan 1970 00:03:10 GMT EXT: LOCATION: http://192.168.200.1/description.xml SERVER: Linux/3.0.1+, UPnP/1.0 ST: urn:schemas-cetoncorp-com:device:SecureContainer:1 USN: uuid:89333102-EBE5-11D8-AC9A-0000080790B8::urn:schemas-cetoncorp-com:device:SecureContainer:1

[2021-03-06 07:22:09.623] Received discover from 192.168.2.134, Response: {"FriendlyName":"HDHomeRun PRIME","ModelNumber":"HDHR3-CC","FirmwareName":"hdhomerun3_cablecard","FirmwareVersion":"20160630atest2","DeviceID":"131DA133","DeviceAuth":"abcdefg","TunerCount":4,"BaseURL":"http:\/\/192.168.2.134:5004","LineupURL":"http:\/\/192.168.2.134:5004\/lineup.json"} [2021-03-06 07:22:14.158] Received control data from 192.168.2.134 on 192.168.2.134: 0002000C0104000000010204FFFFFFFF4E507F35 [2021-03-06 07:22:14.158] Received discovery request: Device type: 1, Device ID: FFFFFFFF [2021-03-06 07:22:14.158] Sending discovery response: Device ID: 131DA133, Base URL: http://192.168.2.134:5004, 0003005A0104000000010204131DA1332B07616263646566671001042A19687474703A2F2F3139322E3136382E322E3133343A353030342725687474703A2F2F3139322E3136382E322E3133343A353030342F6C696E6575702E6A736F6EFA3F46C0 [2021-03-06 07:22:14.359] Received control data from 192.168.2.134 on 192.168.2.134: 0002000C0104000000010204FFFFFFFF4E507F35 [2021-03-06 07:22:14.359] Received discovery request: Device type: 1, Device ID: FFFFFFFF [2021-03-06 07:22:14.360] Sending discovery response: Device ID: 131DA133, Base URL: http://192.168.2.134:5004, 0003005A0104000000010204131DA1332B07616263646566671001042A19687474703A2F2F3139322E3136382E322E3133343A353030342725687474703A2F2F3139322E3136382E322E3133343A353030342F6C696E6575702E6A736F6EFA3F46C0 [2021-03-06 07:22:15.609] Received M-SEARCH for rootdevice from 192.168.2.134 on 192.168.2.134 [2021-03-06 07:22:16.905] Received discover from 192.168.2.134, Response: {"FriendlyName":"HDHomeRun PRIME","ModelNumber":"HDHR3-CC","FirmwareName":"hdhomerun3_cablecard","FirmwareVersion":"20160630atest2","DeviceID":"131DA133","DeviceAuth":"abcdefg","TunerCount":4,"BaseURL":"http:\/\/192.168.2.134:5004","LineupURL":"http:\/\/192.168.2.134:5004\/lineup.json"} [2021-03-06 07:22:25.718] Received M-SEARCH for rootdevice from 192.168.2.134 on 192.168.2.134 [2021-03-06 07:22:35.776] Received M-SEARCH for rootdevice from 192.168.2.134 on 192.168.2.134 [2021-03-06 07:22:45.805] Received M-SEARCH for rootdevice from 192.168.2.134 on 192.168.2.134 [2021-03-06 07:22:55.822] Received M-SEARCH for rootdevice from 192.168.2.134 on 192.168.2.134 [2021-03-06 07:23:05.831] Received M-SEARCH for rootdevice from 192.168.2.134 on 192.168.2.134 [2021-03-06 07:23:15.835] Received M-SEARCH for rootdevice from 192.168.2.134 on 192.168.2.134 [2021-03-06 07:23:25.844] Received M-SEARCH for rootdevice from 192.168.2.134 on 192.168.2.134 [2021-03-06 07:23:35.849] Received M-SEARCH for rootdevice from 192.168.2.134 on 192.168.2.134 [2021-03-06 07:23:45.850] Received M-SEARCH for rootdevice from 192.168.2.134 on 192.168.2.134 [2021-03-06 07:23:55.851] Received M-SEARCH for rootdevice from 192.168.2.134 on 192.168.2.134 [2021-03-06 07:24:05.836] Received M-SEARCH for rootdevice from 192.168.2.134 on 192.168.2.134 [2021-03-06 07:24:15.826] Received M-SEARCH for rootdevice from 192.168.2.134 on 192.168.2.134 [2021-03-06 07:24:25.821] Received M-SEARCH for rootdevice from 192.168.2.134 on 192.168.2.134 [2021-03-06 07:24:35.818] Received M-SEARCH for rootdevice from 192.168.2.134 on 192.168.2.134 [2021-03-06 07:24:45.817] Received M-SEARCH for rootdevice from 192.168.2.134 on 192.168.2.134 [2021-03-06 07:24:55.817] Received M-SEARCH for rootdevice from 192.168.2.134 on 192.168.2.134 [2021-03-06 07:25:05.816] Received M-SEARCH for rootdevice from 192.168.2.134 on 192.168.2.134 [2021-03-06 07:25:15.816] Received M-SEARCH for rootdevice from 192.168.2.134 on 192.168.2.134 [2021-03-06 07:25:25.816] Received M-SEARCH for rootdevice from 192.168.2.134 on 192.168.2.134"

mpatriche commented 3 years ago

Hi, Would you be willing to do a Zoom conference? Might be able to get it working quicker if we can work on it together. If so...send me an email....my address is under my GitHub profile.. Thanks!