How to install in home assistant

[eamonnogorman]

Hi,

Sorry for probably a fact question, but how do I replace my existing velbus integration in home assistant with this one ?

Thanks,
Eamon

[cereal2nd]

Since the 2022.5 release this is the one bundled with home-adsistant

…

On Thu, 3 Aug 2023, 00:04 eamonnogorman, ***@***.***> wrote: Hi, Sorry for probably a fact question, but how do I replace my existing velbus integration in home assistant with this one ? Thanks, Eamon — Reply to this email directly, view it on GitHub <#81>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4LF4PHUYZABWKKTCCV47TXTLFGVANCNFSM6AAAAAA3B4JCH4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[eamonnogorman]

Thanks, it would appear my vmb1dm is not working so as it is detected but can't operate it, do we know if this is supported or is there a way of adding support for it ?

[cereal2nd]

Do you get any error message in the home-assistant log?

[eamonnogorman]

Thanks, the home assistant logs say

"none type" object is not callable

Regards
Eamon

[cereal2nd]

can you get me a bit more info from the logs?
20 lines before and 20 lines after this error?

[eamonnogorman]

Hi,

Thanks again, hope the logs below are enough, i think I captured a few events!

velbus HA LOGS.txt

[eamonnogorman]

Hi cereal2nd, were those logs any good or do you need them in a different format?

[eamonnogorman]

Hi cereal2nd, were those logs any good or do you need them in a different format?

[sidlgor]

Hi, I have a fork (sidlgor) of the code that I would like to load in home assistant but I cannot figure out on how to do it.
I already copied the implementation tree under custom_components but the integration is not loaded and there is also nothing in the logs.
Could you please give me a hint on how to load a new version of the code from source in home assistant (the code is already tested with examples code independent of home assistant)
Any help appreciated

[niobos]

Yeah, it's a pain to set up...
The official docs are here, but I always struggle to get it to work in my docker containers.

[sidlgor]

I am also running HAS docker, so far so good I hope.
I have the impression I completely misunderstand the installation procedure. I just copied the installation tree https://github.com/sidlgor/velbus-aio/tree/master/velbusaio to the custom_components directory which might be very naive. There seems to be not even a manifest.json file in there. In fact I don't find a manifest.json file at all.
I installed several custom integrations (luxtronix, huawei-solar, frigate, ...) from HACS without (to many) problems, but installation from a development project (py sources) seems to be completely different. Please could you guide me the right direction ? Do I have to use custom_components at all? If affirmative, do you have an example of the correct file structure, content?
Would be a great help!

[niobos]

I copied the Velbus integration from the official Home Assastant repo into custom_components. But it needed some fiddling with the manifest.json to get that to work. From memory, I think I needed to add a version attribute.

Next, you can change the dependencies to point to your own velbusaio fork. That part is explained in the docs.

But I didn't manage to get a local velbusaio directory working, and HA tries to be helpful to not download the same dependency twice, so I ended up bumping the version-number and pushing every time I changed something. I'm trying to find an easier way, but haven't found it yet.

[sidlgor]

Thanks a lot for help, but still strugling ... >> I copied the Velbus integration from the official Home Assastant repo <https://github.com/home-assistant/core/tree/dev/homeassistant/components/velbus/> into custom_components. But it needed some fiddling with the manifest.json to get that to work. From memory, I think I needed to add a version attribute. Great to have this reference, looks quit essential to understand >>Next, you can change the dependencies to point to your own velbusaio fork. That part is explained in the docs <https://developers.home-assistant.io/docs/creating_integration_manifest/#custom-requirements-during-development--testing>. Unsure about this: did you mean "requirements" instead of "dependencies" ? (dependencies are set to usb) What would be the correct requirement for my fork ? What should <git ref> look like? "requirements": ["velbus-aio @ git+https://github.com/sidlgor/velbus-aio.git@<git ref>"]

>>> But I didn't manage to get a local velbusaio directory working, and HA tries to be helpful to not download the same dependency twice, so I ended up bumping the version-number and pushing every time I changed something. I'm trying to find an easier way, but haven't found it yet.

Really don't mind about that at this point 🤪 I would be very happy to get anything working!

…

Message ID: ***@***.***>

[sidlgor]

One more thought: instead of adding a requirement to a git fork, wouldn't it work to just copy (merge) the files from the fork into the custom_components? At that moment we could have velbusaio completely local?

…

------ Original Message ------ From "niobos" ***@***.***> To "Cereal2nd/velbus-aio" ***@***.***> Cc "sidlgor" ***@***.***>; "Comment" ***@***.***> Date 24/06/2024 12:22:20 Subject Re: [Cereal2nd/velbus-aio] How to install in home assistant (Discussion #81)

I copied the Velbus integration from the official Home Assastant repo <https://github.com/home-assistant/core/tree/dev/homeassistant/components/velbus/> into custom_components. But it needed some fiddling with the manifest.json to get that to work. From memory, I think I needed to add a version attribute. Next, you can change the dependencies to point to your own velbusaio fork. That part is explained in the docs <https://developers.home-assistant.io/docs/creating_integration_manifest/#custom-requirements-during-development--testing>. But I didn't manage to get a local velbusaio directory working, and HA tries to be helpful to not download the same dependency twice, so I ended up bumping the version-number and pushing every time I changed something. I'm trying to find an easier way, but haven't found it yet. — Reply to this email directly, view it on GitHub <#81 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACBL57RZ4C7OFLVFGG7RNTLZI7XNZAVCNFSM6AAAAABJZH4HRGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQNJYHE4TG>. You are receiving this because you commented.Message ID: ***@***.***>