Since these are new device types I don’t think there is an easy way to make it backwards compatible. At least not that I’m aware off…
Very kind, lets see if we can’t get it to work without it 
Found the problem, new test version within short.
Maybe I misunderstood, but I don’t see a temp value per MPPT for a solarcharger in the modbus specification.
Found the problem, new test version within short.
When trying to add a MPPT that has a low bus ID value (3 or 4) I can click NEXT in the dialog box, but then in the next screen it fails to connect to the Cerbo device. “Couldnt connect to host x.x.x.x on port 502” with x.x.x.x befing the IP of my Cerbo.
When selecting a MPPT with a high bus ID (279 or higher) the wizard wount allow me to press NEXT.
For the temperature reading it doesnt seem to be exposed over modbus, but rather needed to run a shell command.
Is there a way to query the internal temperature of an MPPT controller? - VictronEnergy
is it possible to make the battery part visible on the new energytab?
A few posts above I mention that this is work in progress. I need to split the current device into multiple different devices in order to support new energy concept.
It would be helpful to have an error message and, for instance, trigger a diagnostic report after you have tried to add it. Saying it doesn’t work is like saying it is raining; it doesn’t help me at all.
I know, but it does add a device, but it doesn’t fetch any data. How exactly do you like to get the diagnostic?
There is a possibility to share a diagnostic report with the developer from the app’s page in the homey app.
In the Homey app click ... in bottom right, Apps, Victron app, cog wheel top right, create diagnostic report.
This will send me the last x lines of the logs from the app. If you have restarted the app then it will be empty. In this case it may be best to restart app to empty the log, add the solar charger device, then trigger diag report.
This is the PV inverter I see, which I can test, and it works for me. The Solar charger is the one I can’t test myself. There is no error in the diagnostic log after the device was created, though.
The latest test version doesn’t have many visual changes, but it has a completely new socket and Modbus management, which (hopefully) should perform much better with many different devices polling data.
Found by accident in a Victron document. Maybe worth trying with 100 if 0 doesn’t work.
If the device instance is 0 you can use both 0 and 100 as unit ID. Keep in mind that many modbus TCP clients do not support unit ID 0.
Hello,
I installed version 1.3.6 and all THEN functions of the EV charger stopped working.
I went back to version 1.3.1 and THEN on EV charger works fine.
Can you please check?
Thank you.
Zdenk
Yes, found the problem. Will push a new test version, probably later today.
HI @Richard_B,
I just installed your app, but is it possible to create a schedule of carging with tags?
I made a script by Power by the Hour, which get the cheapest time + duration. And I want to use this information to create a schedule. Any idea? I can only select a tag for the SOC
Hi @Richard_B,
I noticed in release 1.3.6 that when trying to add the ‘växelriktare’ the device type is listed as ‘com.victronenergy.pvinverter’ - is that really right? Anyway I cant add my GX using that.
Neither does any of the solarcharger produce any data - the lower ID ones can be added (0-3) but the ones with high modbus ID (277 and up in my case) still cant be added. Same type of error as previusly - The wizard doesnt let me go past the Connect button on the add screen, nothing happens when I press connect.
/Kaj
Correct, that is for pv inverters on the AC side linked with your Victron system. com.victronenergy.pvinverter is what Victron calls them. I have added my SMA inverter for instance.
Hi @Richard_B
From yesterday I can not see the SOC of my battery pack anymore.
It’s a flat line 62,63%
All the flow cards that used the battery % are also gone.
When I look to the GX device the battery symbol in the bottom is also gone.
Do you have any idea why, and is it possible to fix this again?
Thanks a lot
Yeah, sorry for that. In the latest test version there is a new battery device, which you need to add separate from the GX device. There has been many complaints from folks that doesnt have a vebus that they couldn’t use the GX device. Separating the devices into battery, solar, energy meter, etc is also in line with the new Energy concept from Athom.
Ok thanks,
I updated the last version and now it is working again!
thanks a lot
When I try to add the battery the installation gets stuck in the form with the connect button.
184419d3-f5b1-4a88-998d-7017334e5a17
