Why can't Vero restart flawlessly with USB HUB and TV dongle

Good day.

Good day.

I have a very trivial question that I have not yet answered.

How to properly restart Vero4K + with DVB-T2 / DVB-C TV dongle and with 4 Port USB 3.0 Powered Hub ???

All of these devices are said to be compatible with each other, which is not true.

Will I get an answer on how to properly restart this configuration?

To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.

Depending on the used skin you have to set the settings-level to standard or higher, in summary:

  • enable debug logging at settings->system->logging

  • reboot the OSMC device twice(!)

  • reproduce the issue

  • upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A

  • publish the provided URL from the log set upload, here

Thanks for your understanding. We hope that we can help you get up and running again shortly.

OSMC skin screenshot:

I don’t think this is necessary. Tell me how to restart the device set and I will disappear immediately.

You’re not making it clear what part of restart is a problem?

You can restart Vero from the Power menu. Exit restarts just Kodi, Reboot does what it says.

It would also be good to know what version you are on. This was a problem with older versions of OSMC.

Do you think?
OSMC NOVEMBER 2020 2020.11-1.

I’m not as big an idiot as it may seem at first glance.
If I restart from the KODI menu, only the Vero 4k + restarts, but the DVB-T2 / DVB-C TV dongle will most likely NOT restart due to power from the 4 Port USB 3.0 Powered Hub.
After the restart is completed, the DVB-T2 / DVB-C TV dongle for KODI is not available.

If I restart from the KODI menu, only the Vero 4k + restarts, but the DVB-T2 / DVB-C TV dongle will most likely NOT restart due to power from the 4 Port USB 3.0 Powered Hub.
After the restart is completed, the DVB-T2 / DVB-C TV dongle for KODI is not available.

Nobody said that. But you asked how to do it. Now finally we know what the problem is. I have the same setup but with a different USB hub. Normally I can warm-boot Vero without problems but if that doesn’t work the only way to be sure is to cold start both the hub and Vero. What I’ve never really nailed is if the order in which you start them matters. Starting Vero first should always work so if you have nothing else on that USB hub that’s needed at start-up, do it in that order.

Does that help?

But then I just thought: with the OSMC hub, the technique would have to be turn each USB socket off with the switches, then start Vero, then power on the hub and switch each dongle on in turn.

I have an easier way, I disconnect the USB hub from Vero after confirming the restart and I connect it again after restarting Vero. However, this stupid procedure bothers me.

Yes, that works and it bothers me too but I don’t re-boot my TV server that often. Every time I do I think about some way to re-boot the dongles. Maybe something like this: command line - Unplug and plug in again a USB device in the terminal - Ask Ubuntu

i had the same problem with backfeeding. The easiest way is to buy short usb cable and cut +5V line to make it just data or you can use tape to isolate +5V contact. This will divide power feeding between hub and vero.
There is no other solution yet. At least i dont know it.

Does the issue occur with the dongle directly connected?
I’d be surprised if it’s a hub related issue.

Sam

Correct procedure to reboot VERO 4K+ with a USB TV dongle connected using a powered USB hub (not directly into VERO 4K+):

  1. Disconnect VERO 4K+ power.
  2. Disconnect power to USB hub.
  3. Connect power to VERO 4K+.
  4. Connect power to the USB hub.

This is solved on Vero V.

I would need a bit more info about your 4K+ device to solve this, but from the fact that you’ve posted nearly three years later I will assume that this is a testament to the high uptime of the device

Sam