Homatics Box R 4K Plus

Help & Support Hardware
4573

Tried that a few times, but no such luck. Strangest thing. In bluetoothctl, holding the 2 pairing buttons for an existing paired remote:

For the B25 I see:

hci0 XX:XX:XX:XX:XX:E6 type LE Public disconnected with reason 3
[CHG] Device XX:XX:XX:XX:XX:E6 ServicesResolved: no
[CHG] Device XX:XX:XX:XX:XX:E6 Connected: no
hci0 XX:XX:XX:XX:XX:E6 type LE Public connected eir_len 18
[CHG] Device XX:XX:XX:XX:XX:E6 Connected: yes
[CHG] Device XX:XX:XX:XX:XX:E6 ServicesResolved: yes

For the B21 I see:

hci0 XX:XX:XX:XX:XX:DE type LE Public disconnected with reason 3
[CHG] Device XX:XX:XX:XX:XX:DE ServicesResolved: no
[CHG] Device XX:XX:XX:XX:XX:DE Connected: no
hci0 XX:XX:XX:XX:XX:DE type LE Public connected eir_len 18
[CHG] Device XX:XX:XX:XX:XX:DE Connected: yes
[CHG] Device XX:XX:XX:XX:XX:DE ServicesResolved: yes

After repairing both, Kodi responds to the B25, but not the B21 still.

If I run btmon and press the down button on the B25, then the B21 I see:

ACL Data RX: Handle 65 flags 0x02 dlen 11
ATT: Handle Value Notification (0x1b) len 6
Handle: 0x001f
Data: 43000000
ACL Data RX: Handle 65 flags 0x02 dlen 11
ATT: Handle Value Notification (0x1b) len 6
Handle: 0x001f
Data: 00000000
ACL Data RX: Handle 64 flags 0x02 dlen 11
ATT: Handle Value Notification (0x1b) len 6
Handle: 0x001f
Data: 43000000
ACL Data RX: Handle 64 flags 0x02 dlen 11
ATT: Handle Value Notification (0x1b) len 6
Handle: 0x001f
Data: 00000000

Same values, just a different handle, I assume as they are separate devices. Really seems like BlueZ has the B21 just fine, but Kodi won’t do anything with its inputs.

4574

You need to check with evtest program from system tools addon to see if remote is registered to input devices. You can also see the button presses but for this you need to stop kodi.

4575

Well, I opened this topic exactly one year ago, no one thought then that it would be so popular.
Thanks to the CE team, to made this possible :slight_smile: :sunglasses:

4 Likes
4576

Thank you! That seems to be something. Not 100% familiar with that command, but running I see:

/dev/input/event0: input_ethrcu
/dev/input/event1: cec_input
/dev/input/event2: input_btrcu
/dev/input/event3: vad_keypad
/dev/input/event4: meson-ir
/dev/input/event5: eventlircd
/dev/input/event6: B25 Keyboard
/dev/input/event7: B25 Consumer Control

Which looks like it’s not seeing the B21. What’s the trick to get it registered? Missing module that would need to be added to CE (if one exists to include)?

For some extra context, udevadm monitor shows the following when it connects:

KERNEL[744.796595] add      /devices/virtual/misc/uhid/0005:0957:0006.0003 (hid)
ACTION=add
DEVPATH=/devices/virtual/misc/uhid/0005:0957:0006.0003
SUBSYSTEM=hid
HID_ID=0005:00000957:00000006
HID_NAME=B21
HID_PHYS=XX:XX:XX:XX:XX:dd
HID_UNIQ=XX:XX:XX:XX:XX:de
MODALIAS=hid:b0005g0001v00000957p00000006
SEQNUM=4302

UDEV  [744.798547] add      /devices/virtual/misc/uhid/0005:0957:0006.0003 (hid)
ACTION=add
DEVPATH=/devices/virtual/misc/uhid/0005:0957:0006.0003
SUBSYSTEM=hid
HID_ID=0005:00000957:00000006
HID_NAME=B21
HID_PHYS=XX:XX:XX:XX:XX:dd
HID_UNIQ=XX:XX:XX:XX:XX:de
MODALIAS=hid:b0005g0001v00000957p00000006
SEQNUM=4302
USEC_INITIALIZED=744796179
4577

Above you wrote B25 doesn’t work but now you are talking about B21.

Basically both remotes should work but as written few times BT doesn’t behave very friendly.

4578

Hi,
with atv12.8.3054, in CE 20.3-Nexus_nightly_20230902, when using worldlivetv add-on I had stuttering/freezes on some h264 channels (for example BFM Tech&Co), and also purple/green colors…
Setting accelerate h264 to never fixes all (in parameters/player/allow hardware acceleration - amcodec) Btw, for pink/green colors, setting atv to adaptive hdr fixes it too
Just in case someone has this issue too

4579

Hmm, a bit odd. BlueZ seems to be totally fine with it. UDev seems to not realize that it’s an input device.

To clarify the B25 works, the B21 pairs and sends events according to btmon, but udev doesn’t create a device for it. It’s HWID seems to match the same one in the stock hwdb file, so it doesn’t seem like it’s some new hardware revision.

Not really sure where to go from here if udev or the kernel won’t create a device for it.

4580

Most of us has B21 and works for us.

As I wrote you should see events on button pressing with evtest program when kodi is stopped. If you don’t something is wrong temporary.

What does

udevadm info /dev/input/eventX

returns (with correct X number)? And is event even there?

4581

I don’t think I can run that. There is no device for the B21 in /dev/input/ to describe. It pairs, connects, and sends events only according to BlueZ. According to udevadm an event file isn’t created for it. Evtest shows the B25, but does not show the B21, so I couldn’t use evtest to monitor for events as there was no B21 device to monitor.

Available devices:
/dev/input/event0:	input_ethrcu
/dev/input/event1:	cec_input
/dev/input/event2:	input_btrcu
/dev/input/event3:	vad_keypad
/dev/input/event4:	meson-ir
/dev/input/event5:	eventlircd
/dev/input/event6:	B25 Keyboard
/dev/input/event7:	B25 Consumer Control

When I reconnect the B21 I also see the following dmesg:

hid-generic 0005:0957:0006.0006: item fetching failed at offset 22/23
hid-generic: probe of 0005:0957:0006.0006 failed with error -22

Thank you for helping me dig into this a bit btw, much appreciate it

4582

When I don’t see my remote in evtest than I just press pairing buttons again and then it works.
Hard to say what is going wrong in your case.
Same problem also without connected B25 remote?
Try to remove bt cache folder and reboot.

rm -fr /storage/.cache/bluetooth
reboot
4583

Started to think the same thing. Like maybe even though they are different hardware IDs, maybe hid-generic didn’t like how similar they were and wouldn’t allow it to bind to the same interface. Disconnected both, deleted that folder, rebooted, attempted to connect only the B21, but still no joy. Same hid-generic errors in dmesg and no device created. I’ll poke at it a bit more later today and see what I can coax out of it. Will report back here if I end up getting it working. Thanks for the tips!

I think I saw some others in Sept with a similar issue connecting the Homatics white B25 to a Dune box, but they gave up and went IR :slight_smile:

4584

can use this way:
[removed because of incompatible method]
for Homatics Box R 4K Plus ?

4585

@Zuma
https://discourse.coreelec.org/t/homatics-box-r-4k-plus/19596/278?u=rome1931

4586

Got it figured out! I suspected it was a firmware issue. So I booted into Android, paired the remote, then updated the firmware to 2.04. Then I went back to CoreELEC and paired the B21 and it worked! Was also able to pair the B25 at the same time with both working. Thanks again for the tips, wouldn’t have gotten there without knowing how to dig down the stacks.

2 Likes
4587

Ok, I’m really enjoying this box, but I’m getting a nasty stuttering issue that I can NOT resolve. I’ve spent countless hours diagnosing my network, getting a steady 960mbp/s down and up between homatics and the nas where my media files are stored. I thought this was maybe a bad cable, maybe the router, maybe my MoCa adapters, no clue. So I brought out my old Odroid C2 and played back a 4k blu-ray on latest coreelec ng. Stutters are completely gone. What gives? So it’s not network, back to the drawing board I go, and brought the homatics back out. I even went and made an advancedsettings.xml with a much higher cache size, still no dice. I was thinking maybe it’s heat concenered, as I was seeing temperatures in peaks of 167f, however I unplugged the device and let it cool, after 15 minutes plugged in back in an immediately played a video, but stutters continued and device was only at 115f.

I made a comment here on this post earlier on my concerns of the use of a USB drive, for which I’m using a Samsung Bar Plus 3.1 64gb. I just did a clean install on a Corsair GTX 256gb a few moments ago, and I currently am playing back a film to see if my issues continue. It seems temperamental, and why I was investigating heat as a possible concern.Thing is, the bar plus was working fine for weeks and now stuttering has become this issue the past 2 days. No new addons or any configurations changes were done to my device, with the exception of network tools so I can install iperf on it. Regardless, doesn’t kodi cache to the ram and not the install directory? So I’m not expecting this usb to fix it.

Rather I’m hoping a clean install resolves this, or i guess the faster drive but I’m looking to see if anybody else is having any issues or can at least report a stable experience playing full 4k blu-ray’s on this device over the network.

edit: Stuttering is back, into an hour of playback. I’m out of ideas, however I’m going to try to copy a movie straight to the us as a last resort. I actually did this over the network, from the nas to the smb share coreelec supplies, and didn’t have any issues or dropouts during it. https://i.imgur.com/dm5bUFJ.png

4588

Such a long post with only one small information like it doesn’t work :roll_eyes:

4589

So DV is no longer working in CE after the last beta update to ATV12. Hope that it will be restored asap. Thanks to devs.

4590

Enable terminal sharing so I can see what was changed.

https://wiki.coreelec.org/coreelec:term_share

4591

New kernel: 5.4.242

4592

I think DV should work now on your device - can you confirm?