Closed AminShAT closed 3 months ago
Hello @AminShAT,
Most likely the unit ID of your other pv inverters isn't being scanned by the 0.1.7 release. The main branch contains code that will most likely cause your pv inverters to be detected correctly. You can install this via going to:
HACS
Selecting the hass-victron integration
Selecting the hamburger menu in the top right.
Selecting redownload
Clicking the drop down and selecting main as the version
Clicking download
Please let me know if after installing the main version your other PV inverters are being correctly detected
Hello, thanks for your detailed instructions. I followed them, but to no avail so far.
Here are a few screenshots:
Installed version of the Victron integration
Found devices
List of openDTU inverters registered in the Cerbo
Hello @AminShAT,
The provided unit id's cannot be found anywhere in the xlsx spec history. However, this seems to be a bug for older installs where the unit id was incrementally assigned from 34 onwards. The new specification doesn't use the <100 id range any longer. So for new installs these id's shouldn't be used anymore.
However, this doesn't fix the issue you are experiencing, for that I've created another commit that includes 35 and 36 as valid unit id's. This change is now located on main. Could you follow the redownload procedure again in order to download the version that should detect id's 35 and 36 upon a rescan?
Thanks for this. Actually the IDs are assigned manually by the openDTU addon for the Cerbo. I can assign numbers > 100 as well, if that helps.
Would you like me to test this to ensure in a regular installation these would be found?
That would also be helpfull as a future test. Please see https://github.com/victronenergy/dbus_modbustcp/blob/master/CCGX-Modbus-TCP-register-list.xlsx for a list of unit id's that victron is supposed to expose.
Just to confirm, have you managed to get the pvinverter detected with the latest main version? Since there are also other users (with for example issue #137) that report unit's with id 35 and 36 not being found. If you are able to get it detected with id 35 in the latest main version it would allow me to create an release that would solve unit detection issues for a lot of people.
Unfortunately not. I tried both. Switching to 101-103 and leaving at 34-36. in both cases, it shows only the one at 34. even when switching to 101-103 it does not find anything new and still claims to have only one at 34.
Could you perhaps send me another screenshot of the installed commit with which you performed the test? And just to confirm the manual triggered rescan only resulted in 34 being found as a device?
Apologies, I was too quick in clicking. Seems, you need to wait until the right version is really selected before installing.
I tried now with 34-36 and all inverters are found.
No worries, I've made the same mistake in the past :). Thanks for testing and your quick replies.
Great to hear that units 35 and 36 are now discovered by the integration. This means that in the next release a lot of unit id related issues are going to be closeable. #8 #36 #137 and possibly #129, #157, #179.
The release (v0.2.0) has been shipped. Closing issue, feel free to re-open if the issue persists with the new release
I got a forth microinverter meanwhile. It is at ID 37, but is not found by the integration. I think you only included up to 36.
Is it possible to add the numbers above as well? I will get even 2 more microinverters, so a total of 6 (range 34 - 39).
Thanks in advance
Amin
Hello Amin,
Please open a new issue so that this can be tracked seperately.
Will do.
btw: when I did the rescan for new devices now the parameters are wrongly assigned again.
Is might be possible the reassignment to MPPT or Settings only happen when you do a rescan.
I will test tonight and do a rescan then. If I am right, the parameters should then be assigned back to settings again.
Best
Amin
Hi, I am using a couple of decentralized Hoymiles invertes additionally to my Victron MPPT loader. They are all nicely integrated into Victron via the openDTU.
The integration manages to find the find first one, but only one. The others don't show up as devices.