Skip to content

Cosmetical issue: ebus signal acquired/lost when NO cable is connected #166

@Commifreak

Description

@Commifreak

ESP32-C6 stick FW 20260330:

When NO ebus cable is connected at att, the log states:

2026-04-01T04:50:39.923Z I exec: ebus
2026-04-01T04:50:39.925Z I ebus: switching to micro-ebusd mode on MQTT (with bitrate deviation 0 and enhanced arbitration delay 200 us)
2026-04-01T04:50:39.925Z I setup_uart: eBUS UART 1 on TX=15(inv) RX=14(inv) with 2400 Bd
2026-04-01T04:50:39.926Z W ebus: bus started
2026-04-01T04:50:39.929Z I ebusd: micro-ebusd started with own address 31
2026-04-01T04:50:39.930Z W ebus: signal acquired
2026-04-01T04:50:39.931Z I exec: exit
2026-04-01T04:50:39.932Z I exec: successfully ran 44/44 cmds from '/data/main.eas'
2026-04-01T04:50:41.603Z I sntp: got NTP time: 2026-04-01 04:50:42
2026-04-01T04:50:41.626Z E ebus: signal lost

There can be no signal ever acquired.

I dont know if this is even worth fixing it, but wanted to leave it here as it seems a bit misleading (imaging some guy having a bad cable and sees this initial "signal acquired" and then "lost" message :D )

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions