What Victron integration should I use?

[nobthenob]

A couple of month I moved over to the integration fork 0.3.5 created by remcom (https://github.com/remcom/hass-victron), since there were no longer updates to this repo.
Now I noticed that there have been new releases of hass-victron by sfstar. Actually 0.5.0 was released two week ago and it also seems that remcom now contributes to the sfstar project.

However there is a lack of information and guideline about the future development plans. Can anyone (@sfstar, @remcom, ...) please advise on the following questions:

• Will the remcom fork project continue or will there be a joined one?
• Is the latest sfstar release 0.5.0 already stable for production use and does it contain all fixes and enhancements done by remcom?
• Will there be any problem moving back to the sfstar integration now, e.g. regarding the discovered entities, etc.?
• Is the sfstar code also tested with MultiPlus-II firmware 552?

Thank you for providing some clear guide to the users of your integrations, and of course thank you for your efforts in making this code available!

BR, nob

[konus1]

I would also happy if the @sfstar could answer this question.
And yes, thank you for your work!

[Oinq]

I just noticed that @remcom did archived the other integration.

[bidouilleur31]

again months passed and nothing moves anymore. This starts to smell abandonware 'again'. Remco solved pending issues and this section became live again. Guess some discussion was held and Remco went his way and we end again with no updates ..

[Oinq]

The problem is we can't re add Remcom's integration anymore

[lucode]

I have somehow the same problem. I installed both integration in HACS now and tried to delete the Remcon integration, but I get a warning that I need to uninstall the integration in HA first.

But in HA I see that the @sfstar integration is in use (V5.0), but eventually HA can't deal with this situation where two almost identical integrations are provided by HACS. So my question is how to migrate (or delete V3.5) without risking loosing my entities?

[Oinq]

I have somehow the same problem. I installed both integration in HACS now and tried to delete the Remcon integration, but I get a warning that I need to uninstall the integration in HA first. But in HA I see that the @sfstar integration is in use (V5.0), but eventually HA can't deal with this situation where two almost identical integrations are provided by HACS. So my question is how to migrate (or delete V3.5) without risking loosing my entities?

I cut my problems short, removed both. rebooted and installed again. In hacs it will appear only one.

I tried MQTT but somehow I wasn't able to do it. I feel I'm close, but not there yet.

[dmsims]

I have moved to using MQTT natively in Home Assistant.

Pretty easy and updates much faster

[remcom]

I also moved to mqtt. Mainly because of the reason that @dmsims also gives. Faster updates without extra load on the Cerbo device.

For who is interested here is a guide (I didnt write it): https://gist.github.com/KidA001/dc5584db340cf3ad513f9415b20ed5fa

I did it a little different with EMQX as mqtt server. if someone is interested in a guide with the EMQX as mqtt server let me know.

Its a little more work but you have access to almost everything.

[Oinq]

Hello Remcom, thank you very much for pointing the way for MQTT.
Is there a place where we can see what we can get more in EMQX that we can get in Mosquitto?

[remcom]

I typed it al little weird. You can't do more with emqx. I meant that you can do more with the mqtt solution than the integration. But it takes some more manual work and configuration.

[Oinq]

Thank you again for this clear up. I'm actually now busy setting it up.

[Uhae]

I'm also in the process of moving to MQTT and I gotta say: Well worth the effort! The guide linked by remcom was my starting point as well and it proved worthwhile!

[nobthenob]

Hello dmsims & remcon,
thank for commenting on my question!
According to the feedback here, it seems that MQTT is a good alternativ and worth to try.
@remco: Thank you very much you for the link with the detailed description, that looks very helpful.
Cheers, nob