Common mistakes — Scheiber gateway

General CanCan problems (LED codes, box invisible on the bus, firmware update) are in Common mistakes. This chapter is what goes wrong with the Scheiber side specifically.

I paired a switch and nothing happens

Likely cause	How to tell	Fix
The box was not restarted	NbEmulatedInter on device/22/<n>/life is lower than the number of slots you filled	the pairing list is built at startup only — always write with --reboot
The identifier was mistyped	the state topic still reports that switch as unknown when you press it	re-read it and write it again
The slot number is not the instance you are watching	slot SfspInter5 publishes on device/23/5/life, not on 0	watch the right instance
The switch is not commissioned in the Scheiber system	the state topic reports nothing at all when you press	fix it on the Scheiber side first — this gateway reads a bus, it does not pair radio switches

Pressing a switch reports nothing on the state topic

That topic only reports switches the gateway does not know. Silence means it is already paired — which is what you want, except when you are trying to read its identifier again. Turn on the report-everything mode for that:

muxen-uds -i can0 -F 22 -I <n> routine --action 1 --routine 2 --payload 01

It turns itself off at the next restart.

A switch stays stuck "pressed"

The gateway holds a button down until the Scheiber side says otherwise, and releases it by itself after 5 seconds without news. A button that stays on longer than that means the press events keep arriving — a stuck wall switch, or a radio problem on the Scheiber side.

The lighting blocks do not appear

They are discovered automatically; nothing to configure. If they do not appear:

Likely cause	Fix
The Scheiber bus is not reaching the box	check wiring and termination on CAN 2
The block is not powered, or has no output configured	check it on the Scheiber side

A block that stops sending is dropped after 5 seconds and its MUXEN lighting device disappears with it. A block that flickers in and out of the boat's screens is a block whose frames are not arriving reliably — suspect the bus, not the gateway.

A MUXEN light command switches the wrong thing

A Scheiber block's coding number becomes its MUXEN lighting instance number, and the gateway forwards any lighting command addressed to that instance. If another lighting device on the boat already uses the same instance number, the two answer the same command.

Lighting instances are shared boat-wide. Check with muxen-uds -i can0 scan before choosing the coding numbers of the Scheiber blocks.

Dimming does not go all the way

The Scheiber range stops at 240, not 255. A command above 240 is clamped, so the last few percent of a slider that assumes 0–255 do nothing visible. Configure the screen's range as 0–240.

Nothing at all from the Scheiber bus

The gateway's second bus runs at 250 kbit/s and the firmware fixes it — it is not configurable, and it cannot be changed by an overlay or a parameter. If the Scheiber installation runs at another speed, no frame is decoded, and the symptom is total silence rather than errors.

Also check, in this order: the CAN 2 wiring, 120 Ω at each end of the Scheiber bus, and that the receiver block is powered.

After a factory reset, every switch is gone

Expected, and not recoverable from the equipment: the pairing lives only in the gateway. Restore it from the CSV you saved at commissioning — or walk the boat pressing every switch again.

muxen-uds -i can0 -F 22 -I <n> readconfig --save-as-csv scheiber-pairing.csv

muxen-uds locate does not blink the box

On this firmware the routine that normally blinks the LED is used for the pairing report mode instead. Identify the box by its UID, not by locate.