# EaganMatrix Micro input not exposed via Bome Network on Raspberry Pi **URL:** \ **Category:** Bome Products\ **Tags:** bome-network\ **Created:** [May 26, 2026, 10:22pm UTC](https://forum.bome.com/t/eaganmatrix-micro-input-not-exposed-via-bome-network-on-raspberry-pi/7847 "2026-05-26T22:22:25Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![rodiond](https://forum.bome.com/letter_avatar_proxy/v4/letter/r/59ef9b/32.png) [@rodiond](https://forum.bome.com/u/rodiond)\ **Post date:** [May 26, 2026, 10:22pm UTC](https://forum.bome.com/t/eaganmatrix-micro-input-not-exposed-via-bome-network-on-raspberry-pi/7847/1 "2026-05-26T22:22:25Z")
Hi all, I"m using Bome Network Pro on a Raspberry Pi to bridge USB MIDI devices to a Windows 11 PC. Setup: 1. EaganMatrix Micro → Raspberry Pi → Bome Network → Win 2. Rob O"Reilly MIDI Guitar → Raspberry Pi → Bome Network → Win The MIDI guitar works just fine - I can seet it as a MIDI port in various Windows MIDI apps. The EaganMatrix Micro, on the other hand, doesn"t seem to work. I don"t see it in as a MIDI port in Windows MIDI apps. It does **not** appear as an input/source port in Bome"s Add Route page on Windows, only as an output/destination. On the Pi side, ALSA shows the Micro as both input and output. ```auto 32:0 EaganMatrix Micro 010524 MIDI 1 ``` With Bome stopped, this works and receives data when I change presets on the Micro: ```auto aseqdump -p 32:0 ``` With Bome running, the same command fails: ```auto Cannot connect from port 32:0 - Resource temporarily unavailable ``` So it seems Bome is opening the Micro input on the Pi, but not exposing it back to Windows as a usable input/source port. What do I need to do to fix this? Thanks! ---
**Author:** ![FlorianBome](https://forum.bome.com/user_avatar/forum.bome.com/florianbome/32/2367_2.png) [@FlorianBome](https://forum.bome.com/u/FlorianBome)\ **Post date:** [May 26, 2026, 11:05pm UTC](https://forum.bome.com/t/eaganmatrix-micro-input-not-exposed-via-bome-network-on-raspberry-pi/7847/3 "2026-05-26T23:05:16Z")
This is curious! Before considering what happens on the Windows side, let’s first check what’s happening on the Pi. - is the EaganMatrix appearing in the port list when trying to add a MIDI route? - if yes, add a test route with the EaganMatrix to see if it can be opened by Bome Network - in the main window’s log area, enable `verbose` and check if the log shows anything suspicious - restart Bome Network, check the log file(s) in `/tmp` (see [here](https://forum.bome.com/t/bome-software-log-files/4761) for more info) Please get back to us, this is not anything we’ve ever seen. Please post the log file (or the content), too. Thanks! ---
**Author:** ![rodiond](https://forum.bome.com/letter_avatar_proxy/v4/letter/r/59ef9b/32.png) [@rodiond](https://forum.bome.com/u/rodiond)\ **Post date:** [May 26, 2026, 11:32pm UTC](https://forum.bome.com/t/eaganmatrix-micro-input-not-exposed-via-bome-network-on-raspberry-pi/7847/4 "2026-05-26T23:32:26Z")
> is the EaganMatrix appearing in the port list when trying to add a MIDI route? Yes > if yes, add a test route with the EaganMatrix to see if it can be opened by Bome Network > > in the main window"s log area, enable `verbose` and check if the log shows anything suspicious I can successfully create a route from EaganMatrix to my Win PC and can see MIDI messages on the PC when changing EaganMatrix presets. ![image](https://forum.bome.com/uploads/default/original/2X/9/979740ed6a86cd27f19dfbd35e91d3fa8e9fbd18.png) > restart Bome Network, check the log file(s) in `/tmp` (see [here](https://forum.bome.com/t/bome-software-log-files/4761) for more info) What do you want me to look for in the log files? ---
**Author:** ![rodiond](https://forum.bome.com/letter_avatar_proxy/v4/letter/r/59ef9b/32.png) [@rodiond](https://forum.bome.com/u/rodiond)\ **Post date:** [May 27, 2026, 2:19am UTC](https://forum.bome.com/t/eaganmatrix-micro-input-not-exposed-via-bome-network-on-raspberry-pi/7847/5 "2026-05-27T02:19:45Z")
Not sure what happened, but after a couple of restarts and reconnects I can now see EaganMatrix in the list of MIDI port on Windows. Thanks a lot for looking into this! ---
**Author:** ![SteveC](https://forum.bome.com/user_avatar/forum.bome.com/stevec/32/8250_2.png) [@SteveC](https://forum.bome.com/u/SteveC)\ **Post date:** [May 27, 2026, 3:06am UTC](https://forum.bome.com/t/eaganmatrix-micro-input-not-exposed-via-bome-network-on-raspberry-pi/7847/6 "2026-05-27T03:06:32Z")
Are you on Windows 11? ---
**Author:** ![rodiond](https://forum.bome.com/letter_avatar_proxy/v4/letter/r/59ef9b/32.png) [@rodiond](https://forum.bome.com/u/rodiond)\ **Post date:** [May 27, 2026, 5:50am UTC](https://forum.bome.com/t/eaganmatrix-micro-input-not-exposed-via-bome-network-on-raspberry-pi/7847/7 "2026-05-27T05:50:33Z")
Yes, I am. ---
**Author:** ![FlorianBome](https://forum.bome.com/user_avatar/forum.bome.com/florianbome/32/2367_2.png) [@FlorianBome](https://forum.bome.com/u/FlorianBome)\ **Post date:** [May 27, 2026, 9:21am UTC](https://forum.bome.com/t/eaganmatrix-micro-input-not-exposed-via-bome-network-on-raspberry-pi/7847/8 "2026-05-27T09:21:38Z")
So it’s possible that your problem was related to the new Windows MIDI Services on Windows 11. Our own virtual MIDI drivers are usually not affected, but sometimes a reboot is necessary. Microsoft is actively working on improvements, so making sure that you always install the latest Windows Update is a good idea. More info: > **[About Windows MIDI Services](https://microsoft.github.io/MIDI/)** > > Microsoft Windows MIDI Services API, SDK, and tools ---
**Author:** ![rodiond](https://forum.bome.com/letter_avatar_proxy/v4/letter/r/59ef9b/32.png) [@rodiond](https://forum.bome.com/u/rodiond)\ **Post date:** [May 27, 2026, 7:22pm UTC](https://forum.bome.com/t/eaganmatrix-micro-input-not-exposed-via-bome-network-on-raspberry-pi/7847/9 "2026-05-27T19:22:37Z")
Thanks, I’ll keep it in mind going forward. Great product and great support!