Checked my network connections and all is well now relating to Gb Managed switch to managed switch connection was not at Gb speeds. Reset switch and that part is good now.
Watched a few movies last night and all was well. This morning the device was off and I had to restart it. I have no power settings configured. Did configure the included IR remote and it is working fine now.
Not too concerned about heat. Just the auto shutdown or sleep when I switch to another video source.
Power button is working fine on new style IR remote that came with device.
Thank you @freddy . I am using the Ethernet port on the device. The wireless Ruckus APs do have two Gb ports on them. I prefer to use Ethernet as it is all over the house.
Reason for the slow test results earlier was that the main managed switch to the TV managed switch was talking 100Mbs. I reset it and it was fine. Noticed that my Denon AVR only talks 100Mbs.
I switched the configuration of the remote to the included stock remote which is OK. I was though still using the larger MCE IR remote.
It does go to sleep / shuts down when I have the TV set off. The old box would not do this but would turn on the TV via CEC when I would press a button on the remote.
Thank you. Might do that. Now when not utilizing the box it goes to sleep / shuts off. I am able to turn it on and via CEC it turns on the TV which works for me.
around 10 °C of passive cooling would suit me fine. Did you just put a heat sink on the CPU? Do you have any pictures? I have a second one not utilized yet and can take this second one apart before putting it in to production.
Trying to map some buttons of the remote (4 buttons: âAPPSâ, âFORWARDâ, âREWINDâ, âMUTEâ for functions: CODEC INFO / FASTFORWARD / FASTREWIND / PLAY-PAUSE).
Obtaining the keys:
systemctl stop kodi
systemctl stop eventlircd
CoreELEC:~ # ir-keytable -p NEC,RC-5,RC-6,JVC,SONY -t Protocols changed to rc-5 jvc sony nec rc-6 Testing events. Please, press CTRL-C to abort. 200.268020: lirc protocol(nec): scancode = 0x10f 200.268041: event type EV_MSC(0x04): scancode = 0x10f
The codes you scanned are 0x10f, 0x14b, 0x14f, 0x141, but you wrote them as 0x0f, 0x4b, etc in the config, with missing 1, theyâre not the same codes.
Well⊠the codes were right.
The problem was that in .config folder I had other file for other remote (remote2.conf), and, for any reason, CoreELEC used âremote2.confâ also for this remote (priority: remote2.conf > remote.conf).
After deleting remote2.conf, it works with the 4 new mapped keys.
Ok. Remote problem solved⊠but I have other new one
Vontar X4, S905X4, CoreELEC 20.0 ne.
When I shutdown the Vontar X4, with remote, with Power menu, or using ssh:
shutdown now
the TV-box seems really remain in standby or something like that (blue and red lights in LED display).
The âproblemâ is that I have a cooling fan connected using USB to Vontar X4, with the intention of shutdown the cooling fan when Vontar X4 is shutdown⊠but cooling fan continues working after âshutdownâ of the TV-box.
OK; I know that I can remove USB or retire the plug of the TV-Box from electricity, but my intention is to use the TV-Box remotely, and, after ssh:
shutdown now
That all the system be off, including the cooling fan.
Is there any option to âpower offâ the cooling fan after âshutdownâ the Vontar X4?
You can do same thing, as TV-Box usually has a standby-light connector, where a signal-inverter (second link) could be attached to LED(+), which in turn switches off fan with other transister (first link).
Use passive cooling instead. It appears from the posts here that it does work OK.
An alternative as mentioned would be a hardware modification. Here utilize Home Assistant with Tasmota firmware WiFi devices. You could manage your Kodi box with HA. You could configure an ESP01 relay with Tasmota and use MosquittoâŠwhich personally is a tad much.
Here is what you would see in HA with a temperature sensor connected to a Tasmota Device and MQTT.
on idle 42C. I will make some additional holes, should get another 5-10C.
