logo elektroda
logo elektroda
X
logo elektroda

Openbeken Flashed Devices (Smart Plug & Wifi Bulb) Not Discovered by Home Assistant

DCG 936 8
ADVERTISEMENT
  • #1 20722917
    DCG
    Level 6  
    Hi All,

    I recently flashed two devices (Smart Plug & Wifi Bulb) to Openbeken via Tuya cloud cutter.
    Everything went perfectly fine, and I am able to access both the devices via web server.
    I have configured MQTT correctly and both devices say it's "Connected to MQTT".

    I have started "Home Assistant discovery" also but the devices are not being discovered by Home Assistant.

    Screenshot showing device connection information to MQTT network.

    What could be the issue? I have tried restarting Home Assistant and also restarted MQTT services but nothing seems to be working.

    Please help
  • ADVERTISEMENT
  • #2 20722973
    p.kaczmarek2
    Moderator Smart Home
    Please post full specs of your devices, preferably including the OBK JSON template from the Web App.
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #4 20722993
    p.kaczmarek2
    Moderator Smart Home
    The following device should be correctly discovered by HA.

    Please redo the Discovery and paste Home Assistant log here, maybe something goes wrong.

    Or wait, maybe you have whitespace in device name?
    Helpful post? Buy me a coffee.
  • ADVERTISEMENT
  • #5 20723018
    DCG
    Level 6  
    this is the HA log

    Logger: homeassistant.components.mqtt.discovery
    Source: components/mqtt/discovery.py:114
    Integration: MQTT (documentation, issues)
    First occurred: 12:05:12 PM (24 occurrences)
    Last logged: 1:09:56 PM

    Received message on illegal discovery topic 'homeassistant/sensor/Zunpulse Smart Plug _sensor_7/config'. The topic contains not allowed characters. For more information see https://www.home-assistant.io/integrations/mqtt/#discovery-topic
    Received message on illegal discovery topic 'homeassistant/sensor/Zunpulse Smart Plug _sensor_8/config'. The topic contains not allowed characters. For more information see https://www.home-assistant.io/integrations/mqtt/#discovery-topic
    Received message on illegal discovery topic 'homeassistant/switch/Zunpulse Smart Plug _relay_1/config'. The topic contains not allowed characters. For more information see https://www.home-assistant.io/integrations/mqtt/#discovery-topic
    Received message on illegal discovery topic 'homeassistant/light/Syska Bulb_light/config'. The topic contains not allowed characters. For more information see https://www.home-assistant.io/integrations/mqtt/#discovery-topic
    Received message on illegal discovery topic 'homeassistant/switch/ZunpulseSmartPlug _relay_1/config'. The topic contains not allowed characters. For more information see https://www.home-assistant.io/integrations/mqtt/#discovery-topic
  • #6 20723024
    p.kaczmarek2
    Moderator Smart Home
    You have spaces in the device name. I wll try to fix that issue soon.
    Helpful post? Buy me a coffee.
  • #7 20723034
    DCG
    Level 6  

    Oh God, just noticed I had a space at the end of the device name, that stopped HA discovery.

    Issue is fixed now :) I have corrected the names...

    Thanks for your support and yes please fix that in the next update.
  • ADVERTISEMENT
  • #8 20723526
    p.kaczmarek2
    Moderator Smart Home
    We're testing it with @DeDaMrAz right now, I hope to resolve it soon.
    Helpful post? Buy me a coffee.
  • Helpful post
    #9 20723633
    DeDaMrAz
    Level 19  

    Test is complete, short names will be forced to have underscores in place of spaces and long names can have spaces (those are not sent to HA) - starting with build 1.17.238

Topic summary

The discussion revolves around issues with Home Assistant not discovering two devices (a Smart Plug and a Wifi Bulb) flashed with OpenBeken firmware via Tuya Cloud Cutter. The user confirmed successful MQTT configuration and web server access but faced discovery problems. Responses suggested checking the device specifications, particularly the OBK JSON template, and highlighted that illegal characters in the MQTT discovery topic, specifically spaces in the device name, were causing the issue. The user resolved the problem by correcting the device names, removing trailing spaces, and confirmed successful discovery afterward. Future updates to the firmware will enforce naming conventions to prevent similar issues.
Summary generated by the language model.
ADVERTISEMENT