Hello,
Im using local api to get information from my venus A but its very buggy abd is making it reset.
Can i use this integration just to get data leaving the
If you just want to monitor I recommend you that you use another modbus integration like Viperrnmc's. If you want the integration to control the battery and enjoy other functionalities like peak shaving, time slots, dynamic grid charging, then yes, this integration will allow you to do so and monitor the batteries.
1 Like
Thank you,
using it right now until i learn more how this works,i will surely try your integration in a near future, seems the way to go if i want the full power.
Hi ffunes!
Thanks for the recent update fury, the integration works wonderfully. The last update was for battery cell heath (decrease charging rate >95%, good addition!). What also is very important for battery health is temperature.
Viper's modbus has 4 temperature values:
| internal_temperature | Internal device temperature | int16 | 2 | 0.1 | °C | 35000 | 35000 | 35000 | 35000 |
|---|---|---|---|---|---|---|---|---|---|
| internal_mos1_temperature | MOS1 internal temperature | int16 | 2 | 0.1 | °C | 35001 | 35001 | 35001 | 35001 |
| internal_mos2_temperature | MOS2 internal temperature | int16 | 2 | 0.1 | °C | 35002 | 35002 | 35002 | 35002 |
| max_cell_temperature | Max cell temperature | int16 | 2 | 0.1/1 | °C | 35010 | 35010 | 35010 | 35010 |
Your integration has one? Would it be possible to get all 4? My plan would be to make a script that decreases the charge watt limit to prevent overheating / reduced cell lifespan or that turns on a simple fan. Which temp value do you use in your integration? Cell temperature is the most important one. Inverter can get hot, no problem. Should i open a github issue?
Hi Funes,
Great work, great features.
On the capacity protection (I'm from Flanders, Belgium. Peak shaving is a thing overhere), when peak shaving has taken place and SoC is lower then the set reserve, will the battery charge on grid power (given no PV surplus available) till reserve level is reached again, for a potential next peak?
Filip
Hi Flup!
Yes and no, if you use predictive grid charging, and the system determines that charging is needed, then it will do so automatically.
If that weren't the case, you could still create an automation and use manual mode to charge the battery from grid.
Best regards
Hello @ffunes,
Your integration looks very promissing.
I am currently using the viper integration in combination with the marstek AI.
Well guess what, so far I dont like the AI mode like many others.
But my question, is it easy to change from viper integration to yours?
Since I build up some history already in the HA energy dashboard ofcourse.
Or are entities getting named the same at your integration?
Kind regards
Hi,
I don't poll those registers right now, I try to keep the modbus polling to a minimum since it adds delay and chances that a modbus lock occurs. But I will add those in the future.
Best regards
Hi,
Unfortunatelly not, there is no way to easy migrate the info from one integration to the other. I guess you could do some operations at the DB level to merge sensor data, but that is not supported by the integration.
Best regards
I would say if I do the following I would continue where I was left with my history?
- Note current charge and discharge entity ID's from each battery.
- Remove Viper integration
- Reboot HA
- Install your integration
- Rename charge and discharge entity ID's to the ones I had earlier.
I don't think that would work... From the sensor data perspective it would, but I am not sure if that would break something within the integration. Now I am not sure. I would do a DB migration, if you ask gemini or every other AI it would give you the commands to achieve it.
Hm, I was thinking a bit but.... the integration reads the values from the marstek modbus. That means it doesnt start from scratch but just shows the real usage so far isn't it?
Like someone that uses marsteks for a few months, then connect them to modbus integration it will just show the charge/discharge rates so far (ofcourse no historie can be seen).
Yes, the integration reads the batteries' Modbus registers. However, that information is stored in a new sensor. If, for example, the total yield sensor, its value would jump from 0 to 980 kWh (for example) in a single day, which would distort all your historical recordings.
Hm well, so just use the new entities from your integration would do the job and wouldnt give me any problems then.
Old history will be kept from viper integration automatically in the energy dashboard and new battery info from your integration will be added with new entity ID's then.
I recieved my Venus D battery today. I looked at a few integrations and this was the most promising by far. However, i don't seem to be able to connect to modus over TCP on Port 502. Firmware Version is v142
Battery is connected through ethernet and on the Same VLAN as homeassistant.
Does anybody has a D connected this way? Or do I need to order a separate rs485 to ETH convertor
Thx in advace!
I got it fixed. Had to ask Marstek for an update and the made v147 available for my device. Updated and modbus is now working
Hello, first of all, thank you for this integration; it works great. I had a Homewizard battery and have now switched to the Marstek Venus E V3. Homewizard had an ideal operating mode that I used a lot, which was
- Net Zero (charge only)
- Net Zero (discharge only).
This was an ideal option in an automation to charge the battery during the day and discharge it in the evening, without the battery automatically switching between charging and discharging during the day.
Now, if I set the operating mode on Marstek to manual and set the forced mode to discharge (or charge) and set it to 1000 watts, it will actually deliver 1000 watts and therefore also feed back into the grid if my own consumption is only 600 watts, for example. Would it be a good idea to add these two operating modes, or do you have a workaround for this in YAML so that the battery determines what power is needed itself, rather than relying on a specifically set wattage?
Hi,
There is a toggle per battery to enable discharge and charge. Maybe that is what you are looking for?
In my setup the Marstek Venus Energy Manager continuously determines the charge and discharge power for my two batteries, balancing between both, and trying to keep net zero all the time. When more PV is generate then the batteries can charge, or when full (depending on your max SoC) ofcourse you will inject. but the net zero, as well during day and night works excellent out of the box. I don't expect your night time electricity price to be higher then daytime, so it is even better to have daytime net zero rather then only nighttime net zero.
Hi,
My Venus A is at a place in the house where there's no cabled lan and the wife won't allow some cable through the room. Is it possible to make a wifi connection to the Venus (probably with some adapter) and connect it to my RPi running this integration?