logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

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

Filip8X8 579 19
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  
    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  
    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.
  • ADVERTISEMENT
  • #3 21146393
    Filip8X8
    Level 3  
    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
  • ADVERTISEMENT
  • #4 21146397
    p.kaczmarek2
    Moderator Smart Home  
    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.
  • #5 21149885
    Filip8X8
    Level 3  
    Okay, and how do I configure this to show parameters intake etc? Aubess doped on openebeken - no device in Home Assistant via MQTT .
  • #6 21149916
    p.kaczmarek2
    Moderator Smart Home  
    And in the middle is the BL0942 or BL0937?
    Helpful post? Buy me a coffee.
  • #7 21149930
    Filip8X8
    Level 3  
    >>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 .
  • #8 21150086
    p.kaczmarek2
    Moderator Smart Home  
    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.
  • ADVERTISEMENT
  • #9 21150092
    Filip8X8
    Level 3  
    >>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  
    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  
    >>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  
    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  
    >>21150128 O geez, I didn't think one command was enough. Thanks!
  • #14 21150332
    Filip8X8
    Level 3  
    One command was enough.
  • #15 21152265
    Filip8X8
    Level 3  
    >>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.
  • #17 21152434
    Filip8X8
    Level 3  
    >>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  
    The short startup command is executed after the reboot.
    Helpful post? Buy me a coffee.
  • #19 21152454
    Filip8X8
    Level 3  
    >>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  
    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.
Summary generated by the language model.
Popular Topics
ADVERTISEMENT