from what I can gather so far my testing has been of little value to you.
No, it has been very valuable, thank you very much. 
You have demonstrated that the script works on a SAT>IP system.
original instinct about only having this working with DVBT may be correct
I think perhaps a caveat along the lines of, "Tested and working with DVB-T. Results on other protocols unknown".
This version should:
For the purposes of this specific test, I just need to config dump for comparison purposes. Because you seem to not be getting to the main config screen, I suspect that the config dump is crashing and that will be seen in the Kodi log.
As far as testing goes, I have had two successes and one failure.
In order to assess why the one failure occurred, I added the config dump so that I could compare a working system (yours) to a failed system (crazyturk).
v0.0.6 is a special version that included the config dump.
petediscrete - Thanks for your patience.
From your post dated 19 March 2024, I assumed that the script worked successfully for you. Did it work successfully for you then?
Are you saying that with the config dump version (v0.0.6) that you never see the initial config screen? If this is so, can you please look in the Kodi log? Perhaps there is a crash during the config dump process.
Did you set a password on your TVH server?
Did you install v0.0.6?
The functionality of the script remains essentially unchanged to that of 19-Mar, I have just added a config dump that occurs during startup.
I’m still unsure at my end what is to be expected from your script.
It is the same script that it has always been, I have just added a configuration dump at the beginning.
If you run the script on a configured system (TVH Wizard is fine), it will create the configuration dump file and then present you with the first configuration screen. Exit at that first configuration screen without running the rest of the script. The dump file should be in the addon directory.
Just a small hint: Users love to know what a wizard does under the hood. Something like a visual checklist would be nice.
After the configuration parameters have been set by the user, as the script runs and performs the configuration, it has a status window on the right hand side that shows the progress. More details can also be found in the Kodi log file.
I tried running your new script on the test setup but all it reported was "No adapters available". I removed all traces of TVH from the system, ran the script again. It installed TVH 4.3 server and TVH PVR client and thats it. I had to go to the TVH web UI to complete the setup which of course presents you with the TVH Configuration Wizard (yes it's actually a wizard). Is that all that your script is supposed to do. The dumpfile.txt is empty.
Thanks for trying.
The 'no adapters' message occurs after the dump has been performed. I take it that adapters were installed and that the TVH Wizard found them and was able to correctly configure the system.
Did you try to run the quick start after the TVH Wizard was complete? If so, what was the result?
If I recall correctly, you are using SAT>IP. When you ran the quick start a few days ago, did you do anything special to make TVH see the SAT>IP server?
Will this require a fresh install of LE or can I continue using the setup I used to test your Quick Start script
It needs to be run on a configures/running system, not a fresh system. I would prefer a live system that the TVH wizard created, however, a system created by this script will also so. The script takes a dump of the running configuration so that I can compare configurations.
Just run it and the exit at the first screen. The config dump is done during startup. No need to run through the whole script.
If you are willing, could you please download this special version and install it and run it on your live system?
DO NOT run the whole script, just go to the first menu and then exit.
After you have done this, there should be a file named 'dumpfile.txt' in '/storage/.kodi/addons/script.quicktvh'. This is a dump of your live adapters, networks and muxes. Here is a list of object types that it extracts: "linuxdvb_adapter", "linuxdvb_frontend", "dvb_network", "dvb_mux", "satip_client", "satip_frontend".
DeltaMikeCharlie tell me exactly what info you require and what method/format you wish me to use to collect it. I’m not sure what you want to learn from the Digibit Twin DVBS Sat/IP tuner other than it works flawlessly with TVH/LE.
I have not fully decided yet.
I plan on adding a hidden 'dump config' feature/button/hotkey (undecided) to the addon that will create a file with a copy of your TVH configuration that you can just post. It will probably contain a dump of the whole adapter device tree with all objects and properties as well as the network object(s). Maybe I will include the muxes because with crazyturk, it seems that the leaf adapter and the mux list need to match.
I have some family commitments for the next 4 days or so. Consequently, I probably won't be spending much time on this until next week some time.
Thank you both very much your your assistance in testing.
It seems that crazyturk was using directly connected a tuner card, whereas petediscrete was using an external Sat>IP device.
On top of that, it appears that both of petediscrete's ‘leaf’ adapters point back to the same source. However, crazyturk seems to have multiple leaf devices connected to multiple satellite configurations. Each configuration option is represented as a different branch in the device tree.
Based on a lot of reading, the following is purely hypothetical, and I plan to delve deeper into this with a configuration data request from both of you shortly.
Because the addon takes a very basic approach, it assumes that all of the leaf adapters of the same type all point to the same place and therefore connects them to the same network (group of muxes).
For example, with my configuration, all of my DVB-T leaf adapters are connected to the same antenna on my roof. As TVH tries to tune to each mux, it is attaching to one of the free leaf adapters and configuring it with the appropriate frequency, etc.
On petediscrete's system, it did the same thing and because all of the leaf adapters coincidentally connected to the same place, tuning worked as planned. I suspect that if petediscrete's SAT>IP box was configured for multiple satellites, petediscrete's results would have been different.
With crazyturk, however, I am speculating based on the device tree names, that each leaf adapter instructs the motorised dish to acquire a different satellite. The addon has then lumped all of the DVB-S leaf adapters into one giant group. When TVH tried to tune and scan, it was effectively scanning random satellites for the muxes that crazyturk expected to find on a single specific satellite.
The addon failed for crazyturk, in part, because the muxes selected also need to correspond to the leaf adapter that points to the specific satellite required. Not all DVB-S leaf adapters lead to the same place.
I will ask both of you to provide me with a dump of your configurations. I just need to work out exactly what information I will need. This could take a few days.
Once again, than you both.
In the Kodi ecosystem "Wizards" are mostly associated with piracy add-ons/builds so avoiding that term is a good move
That's good to know.
My reason for renaming was more that a 'Wizard' had full and comprehensive knowledge of a topic, whereas a 'Quick Start' gets you up and running.
I have renamed the threads to refer to 'Quick Start' rather than 'Wizard'.
Can you please post a screen capture of your TVH WebUI Configuration->DVB Inputs->TV Adapters screen? I would like to compare your settings to crazyturk's.
I only have 3 levels to reach my 'leaf' adapters.
Whereas crazyturk has 6 levels.
I never doubted that DVBS would work with your Wizard.
Thanks for your vote of confidence.
From a vanilla LE install and installing your Wizard add on, what should the average user expect from the Wizard.
The average user should expect to see a basic/simple TVH configuration suitable for live TV and PVR operations.
This may be a subtle nuance, the addon is actually called ‘TVHeadEnd PVR Quick Start’, I have not used the term ‘Wizard’ for a long time. Its description reads 'Quickly configure a simple PVR using TVHeadEnd.'
At what stage should they need to visit the TVH web GUI.
If all the user needs is a basic PVR/TV experience, they need never visit the TVH WebUI. Viewing the EPG, changing channels and managing recordings will be handled by Kodi’s PVR module. Although the URL for the WebUI is displayed in the heading of the addon should the user choose to go there.
Do you see where I’m coming from.
No, not really.
The addon is designed to automate the tasks of:
petediscrete - Thank you very much for your efforts.
After the report from crazyturk, I was expecting much worse and I am pleasantly surprised.
Have you any other questions you feel you need to ask me.
Is your satellite dish fixed or motorised?
This won’t be some comparison test between your addon setup in LE v CE.
Agreed.
I'd like to see the result with DVB-S on LE as the addon was designed for LE. I don't know enough about CE to determine how much that contributed to crazyturk's result. However, if I get a similar failure in LE, then I can be fairly certain that my addon is to blame and decide where to go from there.
I’ll gladly do a fresh install of LE and install your Wizard addon in a DVBS environment and post back here with my findings.
Thanks.
petediscrete - Thanks for your interest.
If you are still willing, I am still curious to see if it works on DVB-S. If you have a really positive result, I may reconsider my stance.
I'd like to know if crazyturk's result was an outlier or typical of the DVB-S experience. Perhaps there was an unexpected complication with CE.
I will install Kodi v21 on a test machine and see if the script fails.
I managed to get the script to run successfully on Kodi v21-RC1 in Ubuntu (not LE or CE) without error. I had to fudge some of the addon validations, however, those sections have no impact on how the script actually operates.
No I was meaning make download.py and settings.xml more automated.
My apologies.
Also if someone downloads the server you could modify tvheadend43.start to optionally install pvt.hts and then configure the server.
Good idea.
Why not just merge your addon in the python addon that already exists when the server gets installed?
I assume that you are referring to the LE Setup Wizard: Although I have now abandoned this plan, my original idea was to add a question at the end of the LE Setup Wizard with a menu - 'Install PVR?':
The LE Setup Wizard would then either load and execute the required separate script or exit accordingly.
What do you think would be reasonable for a new user to accept?
It will take as long as it takes. I feel that giving users feedback is important, as the script scans and re-scans looking for LCNs, it updates the percentage complete on the screen. The user can cancel during this process if they become impatient.
I still want to test ATSC
I plan to cripple the existing addon to restrict it to DVB-T. I have a python file with some constants, the cripple flag will be added there. Those people keen enough will be easily able to hack this file and re-enable non DVB-T tuners.
Also how would you handle inevitable questions like, it didn't find any/all the channels, the guide is incomplete etc and my tuner wasn't discovered?
With my normal grace and poise.
