core icon indicating copy to clipboard operation
core copied to clipboard

Home Assistant for Velbus not connecting to Atlantic CozyTouch

Open ngobadat opened this issue 1 year ago • 3 comments

The problem

In Home Assistant (from Velbus Signum) I have the option to connect to Overkiz. I have an Atlantic CozyTouch. I'm trying to configure it by login with the Atlantic CozyTouch hub. But it's not working, it keep saiing "Failed to connect".

What version of Home Assistant Core has the issue?

core-

What was the last working version of Home Assistant Core?

No response

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

ngobadat avatar Sep 19 '24 23:09 ngobadat

Hi @ngobadat

We use GitHub for tracking issues with Home Assistant Core itself, not for providing support - so if you could provide more details especial which HA core version you're running and logs or any other helpful diagnostics data or error details, than we can handle it as an issue report, else it is a support request and you should try our Community Forum or join our Discord chat server.

Thanks! 👍

mib1185 avatar Sep 20 '24 21:09 mib1185

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Velbus signum is not standard home-assistant, velbus has its own integration build on top of home-assistant, so this problem does not belong in this list, it should be handled via velbus support.

cereal2nd avatar Oct 09 '24 08:10 cereal2nd

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.