VMBSIG upgrade to its own custom home assistant

[tomfriart]

The problem

I have the expensive VMBSIG which was useless by itself until I integrated it via network to my home assistant. Velbus recently released an upgrade and my module now has its own home assistant instance builtin with “signum cloud” custom integration. My already working HA is now unable to connect to my module and am stuck with 2 HA instances.

What version of Home Assistant Core has the issue?

2024.2.5

What was the last working version of Home Assistant Core?

2024.2.5

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Velbus?

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @cereal2nd, @brefra, mind taking a look at this issue as it has been labeled with an integration (velbus) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `velbus` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign velbus` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

velbus documentation velbus source _{^{(message by IssueLinks)}}

[Cereal2nd]

What's the exact problem?

Even after upgrading your signum you can still connect the same way to the bus as before nothing changes.

But yes you will have 2 Hass instances running, one on the signum and one on another device.

I do not see this as a bug ...

[tomfriart]

I am unable to connect since the upgrade. Tried multiple times with multiple reboots. Will look into it. Issue may be closed if this setup has been tested and should indeed work.

[Cereal2nd]

this setup is running here at home for over a year.

signum including hass does still allow to connect over tcp port 27015, but the new signum has authentication enabled.

so either disable auth or add the password to your connection string in hass