Hi, I've started flashing my devices on OpenBK (ver. 1.17.405) but I've stopped at one place from which I can't quite get started. I've already set up a connection to Mosquitto broker (ver. 6.4.0) in HA (ver. 2023.12.4). De facto I have a message that the connection to the server has been...

Name: OpenBK - problem with adding devices with the Auto discover function in HAOS
Uploaded: 2024-01-13T21:26:53+01:00
Description: Hi, I've started flashing my devices on OpenBK (ver. 1.17.405) but I've stopped at one place from which I can't quite get started. I've already set up a connection to Mosquitto broker (ver. 6.4.0) in HA (ver. 2023.12.4). De facto I have a message that the connection to the server has been...

This is very strange. The next step in that case would be to suspect in Home Assistant in the log or in listening whether OBK publishes Discovery information when it is called. HASS Discovery works in such a way that when you call it then OBK on the appropriate subject should do a publish with a description of the device. You can also show the OBK configuration, although everything should be ok there. Example of HASS discovery below: Code: text Expand Select all Copy to clipboard Topic: homeassistant/light/WinTest_3145CAFF_light/config Payload: {dev:{ids:[WinTest_3145CAFF],name:WT3145CAFF,sw:Win_Test,mf:Microsoft,mdl:WIN32,cu: You should see similar as you listen under topics starting with homeassistant/.

I think you simply haven't enabled Home Assistant Discovery. You have to click once in the options to get it going. That's because in some cases users prefer to manually write YAML, so Discovery doesn't go in automatically. Below you have the HASS discovery video tutorial: .

Thanks for the reply, but it didn't help - perhaps I'm not clicking where I need to - if you can let me know if those are the two places you meant: Previously I used the tutorial, which is posted on YT - despite several reboots, changes selecting Start Home Assistant Discovery and typing inSet/Change/Clear startup command line - scheduleHADiscovery 10, I still have the same situation. Do you have any idea what else to check/verify? I still see 15 devices in MQTT - which is the same as the initial state.

Thanks for the tip - the cause was the Polish characters used in the name - by the letter Ś in Topic - that's why it wasn't letting me go. Thanks for your help!

Removal of Polish characters from the configuration

[Solved] OpenBK - problem with adding devices with the Auto discover function in HAOS

kamilm20 912 5

Treść została przetłumaczona

Zobacz oryginalną wersję tematu

| New topic

#1 20907210 13 Jan 2024 15:39

kamilm20 kamilm20

Level 10

» |

Post #1
20907210 13 Jan 2024 15:39

Hi,

I've started flashing my devices on OpenBK (ver. 1.17.405) but I've stopped at one place from which I can't quite get started.

I've already set up a connection to Mosquitto broker (ver. 6.4.0) in HA (ver. 2023.12.4). De facto I have a message that the connection to the server has been established:

.

However, still no MQTT does not show my device in the list - it is a BK7231N based bulb.

Of course I have automatic search set up:

I can see some communication:

Does anyone have any idea what is wrong with the configuration? I suspect it's some sort of configuration error or some oversight of mine - generally the unit works - colours etc work fine, it's visible on the network.
ADVERTISEMENT
#2 20907818 13 Jan 2024 21:26

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home

» | Helpful post? (0)

Post #2
20907818 13 Jan 2024 21:26

I think you simply haven't enabled Home Assistant Discovery. You have to click once in the options to get it going. That's because in some cases users prefer to manually write YAML, so Discovery doesn't go in automatically.

Below you have the HASS discovery video tutorial:

.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
ADVERTISEMENT
#3 20907880 13 Jan 2024 22:02

kamilm20 kamilm20

Level 10

» | Topic author Helpful post? (0)

Post #3
20907880 13 Jan 2024 22:02

Thanks for the reply, but it didn't help - perhaps I'm not clicking where I need to - if you can let me know if those are the two places you meant:

Previously I used the tutorial, which is posted on YT - despite several reboots, changes selecting Start Home Assistant Discovery and typing inSet/Change/Clear startup command line - scheduleHADiscovery 10, I still have the same situation. Do you have any idea what else to check/verify? I still see 15 devices in MQTT - which is the same as the initial state.
ADVERTISEMENT
Helpful post

#4 20907889 13 Jan 2024 22:10

p.kaczmarek2 p.kaczmarek2

Moderator Smart Home
» | Helpful post? (+1)

Helpful post
Post #4
20907889 13 Jan 2024 22:10

This is very strange. The next step in that case would be to suspect in Home Assistant in the log or in listening whether OBK publishes Discovery information when it is called. HASS Discovery works in such a way that when you call it then OBK on the appropriate subject should do a publish with a description of the device. You can also show the OBK configuration, although everything should be ok there.

Example of HASS discovery below:
Code: text Expand Select all Copy to clipboard
Topic: homeassistant/light/WinTest_3145CAFF_light/config Payload: {"dev":{"ids":["WinTest_3145CAFF"],"name":"WT3145CAFF","sw":"Win_Test","mf":"Microsoft","mdl":"WIN32","cu":"http://127.0.0.1/index"},"name":"Light","~":"testRGBCW","avty_t":"~/connected","pl_on":"1","pl_off":"0","uniq_id":"WinTest_3145CAFF_light","qos":1,"rgb_cmd_tpl":"{{'#%02x%02x%02x0000'|format(red,green,blue)}}","rgb_val_tpl":"{{ value[0:2]|int(base=16) }},{{ value[2:4]|int(base=16) }},{{ value[4:6]|int(base=16) }}","rgb_stat_t":"~/led_basecolor_rgb/get","rgb_cmd_t":"cmnd/testRGBCW/led_basecolor_rgb","clr_temp_cmd_t":"cmnd/testRGBCW/led_temperature","clr_temp_stat_t":"~/led_temperature/get","min_mirs":"154","max_mirs":"500","stat_t":"~/led_enableAll/get","cmd_t":"cmnd/testRGBCW/led_enableAll","bri_stat_t":"~/led_dimmer/get","bri_cmd_t":"cmnd/testRGBCW/led_dimmer","bri_scl":100}

You should see similar as you listen under topics starting with homeassistant/.

I am creating multiplatform open source firmware (Tasmota replacement), right now supporting BK7231T, BK7231N, XR809, BL602, W800, W600, LN882H and soon supporting RTL and W701:
https://github.com/openshwprojects/OpenBK7231T
If you like my work, support me at: https://paypal.me/openshwprojects

Helpful post? Buy me a coffee.
ADVERTISEMENT
#5 20907973 13 Jan 2024 22:51

kamilm20 kamilm20

Level 10

» | Topic author Helpful post? (0)

Post #5
20907973 13 Jan 2024 22:51

Thanks for the tip - the cause was the Polish characters used in the name - by the letter "Ś" in Topic - that's why it wasn't letting me go. Thanks for your help!
#6 20907992 13 Jan 2024 23:02

kamilm20 kamilm20

Level 10

» | Topic author Helpful post? (0)

Post #6
20907992 13 Jan 2024 23:02

Removal of Polish characters from the configuration
Create an account, log in and become active in a forum and ads will not appear. You will receive points by participating in discussions.
Join this discussion.

Install the application

Didn't find an answer? Ask Artificial Intelligence

*I agree to send the question to OpenAI, Anthropic PBC, Perplexity AI, Inc., Kagi Inc., Google LLC - owners of language models in order to prepare the best response. The companies may monitor and log information entered into the form.

*I agree to publicly display my question and answer. The question and answer will be publicly available to everyone. The process may take a few minutes. Upon completion, you will be redirected to the page with the answer.

Wait...(2min)

| New topic

Report a violation of the law

[Solved] OpenBK - problem with adding devices with the Auto discover function in HAOS

Didn't find an answer? Ask Artificial Intelligence