logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

Aubess doped on openebeken - no device in Home Assistant via MQTT

Filip8X8 837 19
Best answers

How can I make an OpenBeken Aubess relay appear in Home Assistant over MQTT when MQTT shows connected but no device is discovered?

You need to trigger Home Assistant discovery manually; MQTT being connected does not create the HA device by itself [#21145577] If you also need to run another startup action, put the commands on one line with `backlog`, for example `backlog startDriver BL0942; scheduleHADiscovery 10`, because the short startup command is executed after reboot [#21152407][#21152437] If discovery still fails, check whether the device name contains strange characters and use Home Assistant MQTT listen/logging to see exactly what the device is publishing [#21146397] The thread also suggests manually checking whether discovery appears in Home Assistant and verifying the device name you used [#21152521]
Generated by the language model.
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
Report a violation of the law
Reply | New topic
  • #1 21144027
    Filip8X8
    Level 3  
    Posts: 138
    Rate: 2
    Hi, I have just sflashed the aubess relay on openebeken, I have set pin 26 as relay and via the website I can control it. But I want to connect it to homeassistant via MQTT, and I have a problem because I have MQTT connected (data is 1000000% good) and it even says mqtt connected but no new device appears. What can I do in this case?
  • ADVERTISEMENT
  • #2 21145577
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14416
    Help: 650
    Rate: 12371
    Home Assistant Discovery must be triggered manually from the Config - > Home Assistant menu (or something like that). Only then will the HA see the device.



    .
    Helpful post? Buy me a coffee.
  • #3 21146393
    Filip8X8
    Level 3  
    Posts: 138
    Rate: 2
    I have been doing it. I'm going to keep trying. Although you might know how to reverse the relay? BO now when I have an entity switched to ON the relay is in the off state, and so in reverse
  • #4 21146397
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14416
    Help: 650
    Rate: 12371
    Maybe you've typed some strange characters into the device name and it's messing up HASS discovery?

    Can you in Home Assistant listen in on MQTT and capture what your device is publishing?

    As a rule you don't need to reverse relay, but there is an option. Instead of the Rel role, select the Rel_n role.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #5 21149885
    Filip8X8
    Level 3  
    Posts: 138
    Rate: 2
    Okay, and how do I configure this to show parameters intake etc? Aubess doped on openebeken - no device in Home Assistant via MQTT .
  • ADVERTISEMENT
  • #6 21149916
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14416
    Help: 650
    Rate: 12371
    And in the middle is the BL0942 or BL0937?
    Helpful post? Buy me a coffee.
  • #7 21149930
    Filip8X8
    Level 3  
    Posts: 138
    Rate: 2
    >>21149916 I don't know completely.... But there is something like this Aubess doped on openebeken - no device in Home Assistant via MQTT Aubess doped on openebeken - no device in Home Assistant via MQTT .
  • ADVERTISEMENT
  • #8 21150086
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14416
    Help: 650
    Rate: 12371
    This is not enough. The circuit you are looking for is rather on the bottom of the PCB. Read the markings.
    Helpful post? Buy me a coffee.
  • #9 21150092
    Filip8X8
    Level 3  
    Posts: 138
    Rate: 2
    >>21150086 There are not very many markings Aubess doped on openebeken - no device in Home Assistant via MQTT .
  • #10 21150103
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14416
    Help: 650
    Rate: 12371
    After all, I can see in the picture that there is some text, which BL is it?
    Aubess doped on openebeken - no device in Home Assistant via MQTT .
    Helpful post? Buy me a coffee.
  • #11 21150109
    Filip8X8
    Level 3  
    Posts: 138
    Rate: 2
    >>21150103 O mother of one that's what you meant, so small that I missed it myself. Please Aubess doped on openebeken - no device in Home Assistant via MQTT .

    BL0942
  • Helpful post
    #12 21150128
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14416
    Help: 650
    Rate: 12371
    In that case, it will be enough startDriver BL0942 on the boot command line, reboot and then calibrate with a second, reliable meter, via VoltageSet/CurrentSet/PowerSet
    Helpful post? Buy me a coffee.
  • #13 21150329
    Filip8X8
    Level 3  
    Posts: 138
    Rate: 2
    >>21150128 O geez, I didn't think one command was enough. Thanks!
  • #14 21150332
    Filip8X8
    Level 3  
    Posts: 138
    Rate: 2
    One command was enough.
  • #15 21152265
    Filip8X8
    Level 3  
    Posts: 138
    Rate: 2
    >>21150128 I have one more important question. In the startup command I entered this command everything works great, it shows the parameters. But now I have no idea how to connect it to homeassistant using MQTT, I mean I know but it doesn't go. Previously in the startup command I had entered "scheduleHADiscovery 10" and somehow it worked because the device appeared in homeassistant, but now it doesn't work by itself, and I tried adding something like "startDriver BL0942; scheduleHADiscovery 10" but that doesn't work all the more. What can I do? The data to MQTT is 10000% correct, I even write that it is connected.
  • #16 21152407
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14416
    Help: 650
    Rate: 12371
    backlog command1; command2
    Helpful post? Buy me a coffee.
  • #17 21152434
    Filip8X8
    Level 3  
    Posts: 138
    Rate: 2
    >>21152407 I added something like this, and what does this do to these commands? Because I added it, well the parameters are shown but in HA you still can't see it. The mqtt configuration looks like this Aubess doped on openebeken - no device in Home Assistant via MQTT .
  • #18 21152437
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14416
    Help: 650
    Rate: 12371
    The short startup command is executed after the reboot.
    Helpful post? Buy me a coffee.
  • #19 21152454
    Filip8X8
    Level 3  
    Posts: 138
    Rate: 2
    >>21152437 Well, yes, and I did reboot the device. But it didn't show up in my mqtt
  • #20 21152521
    p.kaczmarek2
    Moderator Smart Home  
    Posts: 14416
    Help: 650
    Rate: 12371
    Then do the HA discovery manually, it appears? What did you name the device?
    Helpful post? Buy me a coffee.
Reply | New topic
Report a violation of the law

Topic summary

✨ A user flashed an Aubess relay with OpenEbekan firmware, configured GPIO 26 as a relay, and confirmed control via the device's web interface. The user connected MQTT successfully, with confirmed data transmission and connection status, but the device does not appear automatically in Home Assistant (HA) via MQTT discovery. It was advised to trigger Home Assistant MQTT discovery manually through the HA interface. The user inquired about reversing relay logic, which can be done by selecting the "Rel_n" role instead of "Rel." The device includes a power monitoring IC identified as BL0942, confirmed by PCB markings. To enable power measurement features, the command "startDriver BL0942" should be added to the startup commands, followed by calibration using VoltageSet, CurrentSet, and PowerSet parameters. The user reported that a single command was sufficient to activate the driver. For combining multiple startup commands, the "backlog" command syntax is recommended (e.g., "backlog startDriver BL0942; scheduleHADiscovery 10"). Despite correct MQTT data and device reboot, the device still does not appear in HA, suggesting manual HA discovery triggering and verifying device naming to avoid invalid characters that may disrupt discovery. The user shared MQTT configuration screenshots but still faced issues with device visibility in Home Assistant.
Generated by the language model.
Today's popular

FAQ

TL;DR: Fix “no device in Home Assistant via MQTT” by issuing 1 command and triggering discovery: “it will be enough startDriver BL0942.” [Elektroda, p.kaczmarek2, post #21150128] Why it matters: This FAQ helps OpenBeken users make Aubess relays appear in Home Assistant and report energy data reliably.

Quick Facts

How do I make my Aubess/OpenBeken device show up in Home Assistant via MQTT?

Confirm MQTT connects, then trigger Home Assistant Discovery from OpenBeken’s Config → Home Assistant menu. Discovery is manual. If it still doesn’t appear, run discovery again after setting correct device name and topics. Many users miss the discovery step and expect auto‑import. Quote: “Home Assistant Discovery must be triggered manually.” [Elektroda, p.kaczmarek2, post #21145577]

My relay state is inverted (ON shows OFF). How do I fix the reversed relay?

Change the pin role from Rel to Rel_n in OpenBeken. Rel_n inverts the logic so the physical relay follows the entity correctly. This adjustment is safer than wiring changes and takes effect immediately after saving. It specifically addresses devices wired with opposite active level on the coil driver. [Elektroda, p.kaczmarek2, post #21146397]

How do I enable energy metering on an Aubess relay that uses BL0942?

Identify the metering chip as BL0942, then add startDriver BL0942 to the boot commands. Reboot the device. Calibrate using VoltageSet, CurrentSet, and PowerSet against a reliable meter to improve accuracy. Expert tip: “it will be enough startDriver BL0942 … then calibrate.” [Elektroda, p.kaczmarek2, post #21150128]

What exact boot command sequence should I use for BL0942 plus HA discovery?

Use OpenBeken’s backlog to chain actions in one line. Example: backlog startDriver BL0942; scheduleHADiscovery 10. This starts the BL0942 driver, then triggers Home Assistant Discovery after a short delay. Reboot to execute the startup line. [Elektroda, p.kaczmarek2, post #21152407]

My MQTT says connected, but no new device appears. What should I check?

Trigger HA discovery manually. Verify the device name contains no unusual characters, as naming can break discovery payloads. Use Home Assistant’s MQTT listen tool to inspect what the device publishes. If payloads look wrong, adjust name and re‑trigger discovery. [Elektroda, p.kaczmarek2, post #21146397]

What does the OpenBeken backlog command do?

backlog lets you sequence multiple commands with semicolons in the order given. It’s ideal for startup routines, such as enabling BL0942 and scheduling Discovery in one shot. Place the backlog line in the device’s startup field and reboot. [Elektroda, p.kaczmarek2, post #21152407]

Do startup commands apply immediately or only after reboot?

Startup (short) commands run after the next reboot. After editing the startup line, always reboot the device to execute it. Without a reboot, your changes will not take effect, so HA discovery or drivers will not run. [Elektroda, p.kaczmarek2, post #21152437]

How do I calibrate voltage, current, and power after enabling BL0942?

Connect a trusted reference meter. Issue VoltageSet, CurrentSet, and PowerSet in OpenBeken while measuring the same load. Adjust until readings align with the reference. This improves accuracy for long‑term energy tracking. Quote: “…then calibrate with a second, reliable meter.” [Elektroda, p.kaczmarek2, post #21150128]

Can I really fix this with just one command?

Yes. Users confirmed that a single startDriver BL0942 added to startup enabled metering. After this, calibration and discovery complete the setup. Statistic: 1 command enabled the feature before calibration. [Elektroda, Filip8X8, post #21150332]

What is OpenBeken, in simple terms?

OpenBeken is alternative firmware for smart devices that replaces vendor clouds. It lets you set pin roles, run drivers like BL0942, and publish states via MQTT for Home Assistant. It emphasizes local control with flexible commands and startup scripts. [Elektroda, p.kaczmarek2, post #21150128]

What is MQTT and why do I need it here?

MQTT is a lightweight messaging protocol that Home Assistant uses to discover and control devices. OpenBeken publishes topics with states, telemetry, and discovery payloads. After a successful broker connection, you still must trigger HA discovery to register entities. [Elektroda, p.kaczmarek2, post #21145577]

How do I manually trigger Home Assistant Discovery from OpenBeken?

Open the device’s web UI, go to Config → Home Assistant, and trigger Discovery. Some setups also schedule it with scheduleHADiscovery 10 to publish after 10 seconds. If needed, repeat after name or driver changes. [Elektroda, p.kaczmarek2, post #21145577]

Edge case: discovery still fails—what could be wrong?

Atypical characters in the device name can break HA discovery topics. Rename the device using simple ASCII, save, and re‑trigger discovery. Use HA’s MQTT listener to verify the discovery topic appears and matches expectations. [Elektroda, p.kaczmarek2, post #21146397]

How do I listen to what my device publishes to MQTT in Home Assistant?

Use the MQTT integration’s Listen to a topic tool. Subscribe to the device’s discovery and state topics to confirm payloads arrive. If messages are missing, retrigger discovery or simplify the device name. “Can you in Home Assistant listen in on MQTT…?” [Elektroda, p.kaczmarek2, post #21146397]

Quick 3‑step: get BL0942 data into Home Assistant over MQTT

  1. In Startup, add: backlog startDriver BL0942; scheduleHADiscovery 10.
  2. Reboot the device to run the startup line.
  3. In HA, confirm entities appeared; then calibrate with VoltageSet/CurrentSet/PowerSet. [Elektroda, p.kaczmarek2, post #21152407]

What does scheduleHADiscovery 10 do?

It schedules an MQTT discovery publish after approximately 10 seconds. This delay helps ensure the MQTT connection and driver initialization complete before discovery runs, improving reliability of entity creation. [Elektroda, Filip8X8, post #21152265]
Generated by the language model.
ADVERTISEMENT