A) Version 10 matches Version 11 Legacy.
B) Version Generic-11.0.3 should work on you NUC, I would expect you need to use Generic-Legacy based on you nuc.
C) no reason why both Generic-11.0.3 or Generic-Legacy-11.0.3 should not work with Wifi
Will need to see your logs?
What is not working with WiFi?
What is the flickering you are talking about?
Please use the nightly (at least 20230816) https://github.com/LibreELEC/LibreELEC.tv/issues/8013
ejwjohn - since Kodi 19 (Matrix) Feb 2021, 20 (Nexus) - Python 3 is used. Previously releases of Kodi used Python2. I would expect that all current addons will have been updated by now, or there will be a newer similar in function Python3 compatible available.
Known issue. Will fix in next system-tools - https://github.com/LibreELEC/LibreELEC.tv/issues/8010 - interim fix, use previous system-tools release.
Added a pr to add aac support into pipewire.
This still needs to be run tested.
osen - I’m unsure of the other “boot” error you are experiencing.
suggest reaching out to the addon developers to update the code
Issue is with Pillow, tiff and libjpeg and jpeg12 functions being brought in by tiff. We are working with the Pillow developers.
Thanx for a quick fix.
Applied your patch and dstat is working again
Since dstat is terminated maybe could the fork Dool be included in next version of system tools?
👍 have to look at dool again - looks to be maintained. Whereas last I looked it hadn’t moved on from dstat.
Fix was trivial. Will be included in next system-tools. No need for six.
Some quick checking - this is the module - https://kodi.tv/addons/matrix/script.module.six/
Add six.py to the addons
cd /storage/.kodi/addons/virtual.system-tools/bin
wget https://raw.githubusercontent.com/benjaminp/six/master/six.py
Does not seem to help, as dstat seems to need some further python3 patches.
# dstat
You did not select any stats, using -cdngy by default.
Traceback (most recent call last):
File "/storage/.kodi/addons/virtual.system-tools/bin/dstat", line 2825, in <module>
main()
File "/storage/.kodi/addons/virtual.system-tools/bin/dstat", line 2684, in main
scheduler.run()
File "/usr/lib/python3.11/sched.py", line 151, in run
File "/storage/.kodi/addons/virtual.system-tools/bin/dstat", line 2782, in perform
line = line + o.show() + o.showend(totlist, vislist)
^^^^^^^^
File "/storage/.kodi/addons/virtual.system-tools/bin/dstat", line 515, in show
if isinstance(self.val[name], collections.Sequence) and not isinstance(self.val[name], six.string_types):
^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'collections' has no attribute 'Sequence'Edit dstat and change “import collections” to “import collections.abc”
And “collections.Sequence” to “collections.abc.Sequence”
dstat is unfortunately a archived project. https://github.com/dstat-real/dstat So whilst the above will get you going - not sure on longevity.
This photo probably shows it clearest.
https://www.pulse-eight.com/generated-assets/products/0000381.jpeg
Control your TV from Kodi, or vice versa! USB - CEC Adapter
HDMI IN (to PC)
HDMI OUT (to TV)
DATA - this is the USB and allows Kodi/LE/Kernel to read/write CEC.
I have the internal versions which behave exactly the same way (except the HDMI IN-OUT are on those AA pins.) the other connection in the NUC manual is for the USB 2.0 that the pulse8 is connected to. [DATA above]
It shows up here
nuc11:~ # lsusb | grep Pulse
Bus 003 Device 003: ID 2548:1002 Pulse-Eight CEC AdapterThanks - this is reminding me of IBM 4341 mainframe assembler - that made my head hurt as well.
Yup. You’re in the right mindset now 
This is probably the best answer once you deal with the hardware purchase. - “The Kodi implementation of CEC isn’t too bad - doesn’t do everything but depends on the special/corner cases you are trying to solve.”
I probably paint a more pessimistic picture than the normal use case. But I was trying to do all that crazy
Display MoreFirst, thank you for trying to help. However, as you can guess I'm not going to opt for a sat>IP tuner and I really don't care about 4KUHD (at 72 I've seen enough overhyping, but to be fair moving from SD to HD in the US was a big deal, not so much in the UK, and please do not get me started on about PC screens that need to be at 200% to have readable text).
I'll have a look at the Rock machines and see if I can find any performance comparison.
Thanks for that - it explains the very limited command set table
At least I now have some idea where I'm going and the fact that I'll need to add £40 to my budget for the Pulse8 USB adapter
Out of interest is there any usable documentation regarding CEC out there - if there is I was searching for the wrong terms.
Some reading on CEC when I was puzzling it out.
It will lead you down many rabbit holes. Note: it all “might” work (and it all doesn’t) lots of caveat. But as a project it was a good learning - though deep. And my requirements were complex. Since then I have replaced much of the AV equipment - TV, AVR, NUCs - but the other hangers on are still there and work.
My advice is if you do end up chasing the rabbit - I did. You may need to run a customised image (I have been upstreaming much - but some of my corner case automation stuff is not suitable for upstream.)
