Custom Component: Nikobus

Xtov · October 5, 2025, 4:44pm

Hi, thanks for your answer. I detected the correct com port via the software and tried to connect (driver is installed and correct setting) but COM port always closes. I use the HAMA 0037903 USB to RS232 adapter coupled with home made cable. I tried a reset on the PC link module (with power off- press V and X- power ON. It stays forever in the test mode (LEDs blinking) until I use the arrow and then it ends with message (NBB01 → tlgrm test NOK.). Could this indicate a problem with the 05-200 or with the cables ? It is a second hand module and maybe you know the correct way to reset. Thanks for your efforts.

fdebrus · October 5, 2025, 5:51pm

at this stage, I can think of a cable wiring issue, make sure TX/RX are crossed and the ground is well connected. My modules were new, so I do not how to reset them, someone else in the forum might comment.

hansolu · October 7, 2025, 9:45pm

HI,
I bought a RS232 cable and then had only 8 wires, not 9 as needed. I was buying some others until i found one with 10 wires after 2 times checking and double check the connection was okay and everything was fine.

My issue was at beginning: I had the config files not modified and both config files were not in the root folder of HAOS.
Once I updated (first installed the original software, connect to it, found the address of each module) and copied to the proper folder, everything is fine

However, My homemade cable is not so nice, would be glad for a link to buy one proper one

hansolu · October 7, 2025, 9:48pm

Hi,
i did run the scene in HAOS, I could turn on the lights, but the one with the sensor stayed on all the time.
its running now and i do now why excatly,

thanks

hansolu · October 7, 2025, 9:53pm

Hi,
one problem is still availble with my rollershutter module.

I figured the position of the rollos is absolut. So normally once I set a position of e.g. 5 % it should always be the same height. Somehow thats not the case.

A fix I am using now is to close it completly, wait 30 secs, and go to e.g. 5%. Thats kind of working but is also slow

How do you all controll them to e.g. just move a bit up in the morning to let light in, but also check if they have been closed actually.

thanks

fdebrus · October 8, 2025, 9:03am

The roller position feedback does not exists in Nikobus. So we ‘simulate’ setting position on roller by estimating their run time from fully opened or fully closed.

It will not be consistent, eg my shutter do not have the same operation time based on weather, external temp, it can vary by 1 to 2 secs. Also If I open right after a close while the engine is hot vs from a cool start, I get variations.

It’s a workaround to enable a ‘feature’ that does not exist at Nikobus level ‘set_position’.

To complexify, Nikobus does not report neither on status OPENED or CLOSED, this is simulated as well.

Nikobus reports only OPENING / CLOSING / STOPPED.

hansolu · October 8, 2025, 4:46pm

Ahh, thanks for the clarification. So its only a workaround, therefore not consistent. With this I can work and do not need to wonder if there is some deviations.

Thanks a lot

Xtov · October 10, 2025, 8:35pm

I finally managed to get my project working. It was a cable issue. I managed to make a new one, and I was very happy to see everything connecting and working. Thanks for all the tips.

dewildep · October 21, 2025, 12:17pm

Hi @fdebrus , quick question (and sorry if i already asked it in the past).
Is it possible to send a simulated button press from your integration to the Nikobus ?
So like a human would press a button. Do the same from a HA automation?

fdebrus · October 31, 2025, 4:23pm

yes,

find the button like bt_gf_living_garden_light_on

        {
            "description": "BT_GF_Living_Garden_Light_On",
            "address": "2A2481",
            "impacted_module": [
                {
                    "address": "4707",
                    "group": "2"
                }
            ]
        },

then send a press command in your automation


alias: Jardin - Allumer au coucher du soleil
id: jardin_allumer_sunset
trigger:
  - platform: sun
    event: sunset
condition: []
action:
  - service: button.press
    target:
      entity_id: button.bt_gf_living_garden_light_on
mode: single

dewildep · November 3, 2025, 6:05pm

I suppose this is for a 2 button config where you have one physical button for ON and one physical button for OFF defined?

fdebrus · November 4, 2025, 12:58pm

I would just name the button accordingly and trigger it only if the light is off for a toggle single push button vs 2 button on/off

        {
            "description": "BT_GF_Living_Garden_Light_Toggle",
            "address": "2A2481",
            "impacted_module": [
                {
                    "address": "4707",
                    "group": "2"
                }
            ]
        },

alias: Jardin - Allumer au coucher du soleil
id: jardin_allumer_sunset
trigger:
  - platform: sun
    event: sunset
condition:
  - condition: state
    entity_id: light.garden_light
    state: "off"
action:
  - service: button.press
    target:
      entity_id: button.bt_gf_living_garden_light_toggle
mode: single

dewildep · November 12, 2025, 3:11pm

What is the best procedure to delete / clean up old devices and scenes?

I had a switch module defined in nikobus_module_config.json and some scenes in nikobus_scene_config.json.
I deleted the entries and rebooted HA but they persisted in HA.
The switch module i disabled via devices and as far as i understood it is now hidden (but is it also properly deleted?)
For the scenes i could just remove them from HA, so that seems to be ok.

any thoughts about this?

fdebrus · November 12, 2025, 8:06pm

When removed from config, the entity shall no longer be provided and you will get

note: this is an example from another integration, but message is the same “entity no longer provided”

then the delete button will be available on the bottom left

if many, go to entities - filter on Nikobus integration and status unavailable - select - then top right corner “…” - then delete

fdebrus · November 12, 2025, 9:59pm

I have a new beta version that would delete automatically the orphan entries.

You need to manually download the integration files fdebrus/Nikobus-HA and overwrite your Nikobus integration.

** Take a backup before testing a beta **

I removed my discovered button from the config file as a test and it was erased from the integration. It’s logged as WARNING so you can see it in the logfile without enabling debuglog

Logger: custom_components.nikobus
Source: custom_components/nikobus/init.py:119
integration: Nikobus (documentation, issues)
First occurred: 11:13:04 PM (45 occurrences)
Last logged: 11:13:04 PM

Removing orphan Nikobus device: DISCOVERED - Nikobus Button #N752A02 (id=aff1d9b852caa92fce970e3875f57737, identifiers={(‘nikobus’, ‘752A02’)})
Removing orphan Nikobus device: DISCOVERED - Nikobus Button #NF52A02 (id=d8b909b137df9255a708d2545a5b676b, identifiers={(‘nikobus’, ‘F52A02’)})
Removing orphan Nikobus device: DISCOVERED - Nikobus Button #NFF7FFF (id=8421742852d02e830d0231fc7f0bc4d5, identifiers={(‘nikobus’, ‘FF7FFF’)})
Removing orphan Nikobus device: DISCOVERED - Nikobus Button #NC60FFF (id=926d5fa78f4904c56314ab9a7425a3a5, identifiers={(‘nikobus’, ‘C60FFF’)})
Removing orphan Nikobus device: DISCOVERED - Nikobus Button #NF83C00 (id=8db834277ae43b342331dc7b7818e8bb, identifiers={(‘nikobus’, ‘F83C00’)})

dewildep · November 13, 2025, 1:32pm

Downloaded the BETA version

Cleanup seems to be working fine:

2025-11-13 14:19:17.053 WARNING (MainThread) [custom_components.nikobus] Removing orphan Nikobus entity: switch.s5_helper_1 (unique_id=nikobus_A1B1_1)
2025-11-13 14:19:17.053 WARNING (MainThread) [custom_components.nikobus] Removing orphan Nikobus entity: switch.s5_helper_2 (unique_id=nikobus_A1B1_2)
2025-11-13 14:19:17.054 WARNING (MainThread) [custom_components.nikobus] Removing orphan Nikobus entity: switch.s5_helper_3 (unique_id=nikobus_A1B1_3)
2025-11-13 14:19:17.054 WARNING (MainThread) [custom_components.nikobus] Removing orphan Nikobus entity: switch.s5_helper_4 (unique_id=nikobus_A1B1_4)
2025-11-13 14:19:17.054 WARNING (MainThread) [custom_components.nikobus] Removing orphan Nikobus entity: switch.s5_helper_5 (unique_id=nikobus_A1B1_5)
2025-11-13 14:19:17.054 WARNING (MainThread) [custom_components.nikobus] Removing orphan Nikobus entity: switch.s5_helper_6 (unique_id=nikobus_A1B1_6)
2025-11-13 14:19:17.054 WARNING (MainThread) [custom_components.nikobus] Removing orphan Nikobus entity: switch.s5_helper_7 (unique_id=nikobus_A1B1_7)
2025-11-13 14:19:17.054 WARNING (MainThread) [custom_components.nikobus] Removing orphan Nikobus entity: switch.s5_helper_8 (unique_id=nikobus_A1B1_8)
2025-11-13 14:19:17.054 WARNING (MainThread) [custom_components.nikobus] Removing orphan Nikobus entity: switch.s5_helper_9 (unique_id=nikobus_A1B1_9)
2025-11-13 14:19:17.055 WARNING (MainThread) [custom_components.nikobus] Removing orphan Nikobus entity: switch.s5_helper_10 (unique_id=nikobus_A1B1_10)
2025-11-13 14:19:17.055 WARNING (MainThread) [custom_components.nikobus] Removing orphan Nikobus entity: switch.s5_helper_11 (unique_id=nikobus_A1B1_11)
2025-11-13 14:19:17.055 WARNING (MainThread) [custom_components.nikobus] Removing orphan Nikobus entity: switch.s5_helper_12 (unique_id=nikobus_A1B1_12)
2025-11-13 14:19:17.055 WARNING (MainThread) [custom_components.nikobus] Removing orphan Nikobus device: scene my test (id=ecfee3dafa9e3172a8703b2b87effe51, identifiers={('nikobus', 'my_test')})
2025-11-13 14:19:17.056 WARNING (MainThread) [custom_components.nikobus] Removing orphan Nikobus device: scene my test 2 (id=1972c404cc1621ab13574929af07f566, identifiers={('nikobus', 'my_test_2')})
2025-11-13 14:19:17.056 WARNING (MainThread) [custom_components.nikobus] Removing orphan Nikobus device: Turn on driveway lights (id=327ba29d50b4f4d3d29521971e5c038c, identifiers={('nikobus', 'scene_turn_on_driveway_lights')})
2025-11-13 14:19:17.056 WARNING (MainThread) [custom_components.nikobus] Removing orphan Nikobus device: Turn off driveway lights (id=de740cb3584694693cfefd6ec69fda69, identifiers={('nikobus', 'scene_turn_off_driveway_lights')})
2025-11-13 14:19:17.056 WARNING (MainThread) [custom_components.nikobus] Removing orphan Nikobus device: Switch Module S5 (Helper) (id=683dff90f6199c2344e7f9fbb3c8fc02, identifiers={('nikobus', 'A1B1')})

fdebrus · November 13, 2025, 7:00pm

New Release 0.6.4

Scene Feedback LED Support

Scenes now support a new optional field: “feedback_led”
You can assign it to the address of a feedback button, allowing that button’s LED to automatically activate when the scene is triggered.
This makes it easier to provide immediate visual confirmation for scene status.

Automatic Cleanup of Removed Configuration Entries

Home Assistant will now automatically remove entities and devices when the corresponding entries are removed from your configuration files. This means less manual cleanup and a configuration that always stays in sync on restart.