Tvheadend

Well, you could delete the whole hts/.hts/tvheadend directory contents, although this would be a bit drastic and I don't quite know what would happen.

More targeted would be to start at the bottom of the config and delete up to the top, i.e. delete all channels, then all services, then all muxes, then reconfigure to a new US_XXX_XXX setting. If you're lucky, you could perhaps simply delete all muxes and it might take the service and channels with it.

I think the network settings come from outside of tvheadend, as they look suspiciously the same in MythTV and others - part of dvb-tools or similar, I think. Now, sadly, which one you need is beyond me, as we don't have ATSC on this side of the water. A quick Google suggests that Verizon FiOS isn't an over-the-air service, though - it looks like fibre-to-the-home - so is it presented as cable? So you may be adding the wrong type of network?

Again, I'm just reading, and I can't figure out whether FiOS is still presented as ATSC or something else...

This link certainly suggests that tvheadend (under OpenElec, anyway) does work with FiOS if your tuner is working correctly:

https://tvheadend.org/boards/4/topics/9389

Sooo... is your tuenr working correctly? Is it displaying as available, and mapped to /dev/dvb/adapterX?

Frustrating to say the least........

Deleting hts/.hts/tvheadend was not drastic at all. just need to stop and start the service to reset user password.

sudo service tvheadend stop
sudo dpkg-reconfigure tvheadend
sudo service tvheadend start

The system seems to configured properly. All three tuners are displayed Under "Configuration > DVB Inputs> Tv Adapaters" and each tuner is has its own Device Path. /dev/dvb/adapter[0,1,2]

They are also registered in syslog without errors.

Mar 17 17:28:04 plextwo kernel: [ 14.812185] hdhomerun: userhdhomerun connected
Mar 17 17:28:04 plextwo kernel: [ 14.812194] hdhomerun: creating dvb device for 131257B7-0
Mar 17 17:28:04 plextwo kernel: [ 14.812270] DVB: registering new adapter (HDHomeRun)
Mar 17 17:28:04 plextwo kernel: [ 14.846483] DVB: registering adapter 0 frontend 0 (HDHomeRun ATSC)...
Mar 17 17:28:04 plextwo kernel: [ 14.846846] HDHomeRun0: DVB Frontend registered
Mar 17 17:28:04 plextwo kernel: [ 14.846850] HDHomeRun0: Registered DVB adapter0
Mar 17 17:28:04 plextwo kernel: [ 14.847385] hdhomerun: device /dev/hdhomerun_data0 created
Mar 17 17:28:04 plextwo kernel: [ 14.847506] hdhomerun: userhdhomerun connected
Mar 17 17:28:04 plextwo kernel: [ 14.847513] hdhomerun: creating dvb device for 131257B7-1
Mar 17 17:28:04 plextwo kernel: [ 14.847562] DVB: registering new adapter (HDHomeRun)
Mar 17 17:28:04 plextwo kernel: [ 14.848623] DVB: registering adapter 1 frontend 0 (HDHomeRun ATSC)...
Mar 17 17:28:04 plextwo kernel: [ 14.848668] HDHomeRun1: DVB Frontend registered
Mar 17 17:28:04 plextwo kernel: [ 14.848671] HDHomeRun1: Registered DVB adapter1
Mar 17 17:28:04 plextwo kernel: [ 14.848710] hdhomerun: device /dev/hdhomerun_data1 created
Mar 17 17:28:04 plextwo kernel: [ 14.848790] hdhomerun: userhdhomerun connected
Mar 17 17:28:04 plextwo kernel: [ 14.848795] hdhomerun: creating dvb device for 131257B7-2
Mar 17 17:28:04 plextwo kernel: [ 14.848853] DVB: registering new adapter (HDHomeRun)
Mar 17 17:28:04 plextwo kernel: [ 14.849086] DVB: registering adapter 2 frontend 0 (HDHomeRun ATSC)...
Mar 17 17:28:04 plextwo kernel: [ 14.849128] HDHomeRun2: DVB Frontend registered
Mar 17 17:28:04 plextwo kernel: [ 14.849131] HDHomeRun2: Registered DVB adapter2
Mar 17 17:28:04 plextwo kernel: [ 14.849170] hdhomerun: device /dev/hdhomerun_data2 created
Mar 17 17:28:04 plextwo kernel: [ 14.849908] hdhomerun: userhdhomerun connected

Now which DVB network should be selected.

us-ATSC_center_frequencies - gave me the follwing but no channels were available

Mar 17 10:41:32 plextwo kernel: [ 2664.560671] hdhomerun: allocated buffer of 375060 bytes for device 1
Mar 17 10:41:33 plextwo kernel: [ 2665.603749] hdhomerun: allocated buffer of 440860 bytes for device 1

with the following

Mar 17 12:11:34 plextwo tvheadend⁹⁶⁵: subscription: No transponder available for subscription "127.0.0.1 [ xbmc | XBMC Media Center ]" to channel "100"
Mar 17 12:11:39 plextwo tvheadend⁹⁶⁵: subscription: "127.0.0.1 [ xbmc | XBMC Media Center ]" unsubscribing from "100"

atsc_us_Cable_Standard_center_frequencies_QAM256 AND "atsc_us_Cable_EIA_542_HRC_center_frequencies_QAM256" gave me this

Mar 17 15:19:20 plextwo kernel: [ 9550.633559] DVB (dvb_dmxdev_filter_start): could not alloc feed
Mar 17 15:19:32 plextwo kernel: [ 9562.620084] DVB (dvb_dmxdev_filter_start): could not alloc feed

and the "Map DVB Serices to channels" button never became active

Thanks for assistance.

I don't think there's much more I can suggest, then, I'm afraid - I have neither HDHR nor ATSC broadcasts...!

Does this help at all, though: https://tvheadend.org/projects/tvheadend/wiki/HDHomerun/5

Thanks for the effort Prof..

I saw the document you mentioned earlier and did not help.

anyone has other ideas?

::Update

https://tvheadend.org/boards/4/topics/8904 this posting seems to have most of the information needed to setup and HD-Homerun Prime with TvHeadEnd and XBMC.

What i was TOTALLY missing is the configuration files given in "Add DVB Network by Locations" section Sample configuration and are not to be trusted unless they are for particular areas.

I had to build my own custom DVB location. Which seem to add all available muxes.

However after and half of scanning, the app only mapped one channel correctly, in the Channell /EPG section and i have add a temp channel number to the entire list.

but still not go.

i get

Mar 18 01:12:40 plextwo tvheadend⁹⁶⁷: subscription: "192.168.1.7 [ xbmc | XBMC Media Center ]" unsubscribing from "948"
Mar 18 01:12:40 plextwo tvheadend⁹⁶⁷: subscription: No transponder available for subscription "192.168.1.7 [ xbmc | XBMC Media Center ]" to channel "WFDC-HD"
Mar 18 01:12:42 plextwo tvheadend⁹⁶⁷: subscription: "192.168.1.7 [ xbmc | XBMC Media Center ]" unsubscribing from "WFDC-HD"
Mar 18 01:12:42 plextwo tvheadend⁹⁶⁷: subscription: No transponder available for subscription "192.168.1.7 [ xbmc | XBMC Media Center ]" to channel "Channel 849"
Mar 18 01:12:45 plextwo tvheadend⁹⁶⁷: subscription: "192.168.1.7 [ xbmc | XBMC Media Center ]" unsubscribing from "Channel 849"
Mar 18 01:12:45 plextwo tvheadend⁹⁶⁷: subscription: No transponder available for subscription "192.168.1.7 [ xbmc | XBMC Media Center ]" to channel "944"
Mar 18 01:12:47 plextwo tvheadend⁹⁶⁷: subscription: "192.168.1.7 [ xbmc | XBMC Media Center ]" unsubscribing from "944"
Mar 18 01:12:47 plextwo tvheadend⁹⁶⁷: subscription: No transponder available for subscription "192.168.1.7 [ xbmc | XBMC Media Center ]" to channel "940"
Mar 18 01:12:49 plextwo tvheadend⁹⁶⁷: subscription: "192.168.1.7 [ xbmc | XBMC Media Center ]" unsubscribing from "940"
Mar 18 01:12:49 plextwo tvheadend⁹⁶⁷: subscription: No transponder available for subscription "192.168.1.7 [ xbmc | XBMC Media Center ]" to channel "934"

XBMC reports:

01:57:07 T:2968619840 NOTICE: Thread CAddonStatusHandler:pvr.hts start, auto delete: true
01:57:17 T:2762959680 ERROR: AddOnLog: Tvheadend HTSP Client: CHTSPConnection - SendGreeting - failed get a reply after the greeting
01:57:17 T:2762959680 ERROR: AddOnLog: Tvheadend HTSP Client: Connect - failed to read greeting from the backend
01:57:17 T:2762959680 ERROR: ADDON: Dll Tvheadend HTSP Client - Client returned bad status (1) from Create and is not usable
01:57:17 T:2762959680 WARNING: UpdateAndInitialiseClients - failed to create add-on Tvheadend HTSP Client, status =

I am thinking that there is compatibility issue with TvHeadEnd 3.4 and the XBMC HTSP client (1.6.19) ?????