Open sstolk90 opened 1 year ago
This is the screen but the PV inverter is not yet visible:
I dont think you need to switch to another datatype, float should work fine.
All this driver does is to bring your data to the dbus on the GX. Can you verify that all data which you sendt is actually put on the dbus using the "dbus-spy" command line tool?
This is the first think to check. If all data is there, then the driver works. The next thing is to figure out the send the "correct" paths.
Which ones I unfortunately do not know because I do not have a PV-invterter myselv. But I did a quick google search, and found this code: https://github.com/fabian-lauer/dbus-solax-x1-pvinverter/blob/main/dbus-solax-x1-pvinverter.py#L232 Maybe this helps?
------- Original Message ------- On Saturday, January 21st, 2023 at 13:38, sstolk90 @.***> wrote:
I've tried simulating the PV inverter via this driver but I cannot get the AC Phase L1 Watts to show in the Victron GX. This is the payload from Node-Red towards the right topic for this script: image The Victron shows this: image
I've tried filling all the fields and switching from interger to float etc. Nothing gets the Watts in this field. I think that the field must be filled all in the correct manner before the Victron shows it as a PV inverter in VRM or GX Display.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>
This is my payload and this are the Watts that are appearing in the AC Totals but not in the AC L1 Watts.
DBUS-Spy reports no data of this value I send:
So "/Ac/L1/Current" works but not "/Ac/L1/Power"?
Yes
Op zo 22 jan. 2023 20:29 schreef Sebastian Dehne @.***>:
So "/Ac/L1/Current" works but not "/Ac/L1/Power"?
— Reply to this email directly, view it on GitHub https://github.com/sebdehne/dbus-mqtt-services/issues/1#issuecomment-1399583155, or unsubscribe https://github.com/notifications/unsubscribe-auth/APTUHJJ2MAI6Z7DVTEMKJU3WTWDC5ANCNFSM6AAAAAAUCMCL4M . You are receiving this because you authored the thread.Message ID: @.***>
Try to send 0 to L2 and L3
That seems to work and is up and running without problems. However I do have a second PV inverter but the MP-II deletes this instance because it's duplicate. See this topic: https://community.victronenergy.com/questions/183853/vrm-instance-for-a-pv-inverter-by-script.html Has it something to do how VRM instances are handed out?
This is what I see in the VRM portal. The ID is VRM 0, where my ET112 has an official VRM ID of 30.
For PV it should be something in the 20 till 29 as by this excel sheet from Victron.
The product VPN as a name doesn't ring a bell also. VPN as a abbreviation stand for? Virtual PV instsance? I have no clue.
Still haven't got it working. Somebody here who has?
Since the problem is related to the VRM ID only one PV inverter can be used by the MQTT script. Issue is still there but I will not use this script
The problem is that the script registers the MQTT service at an unique ID on the DBUS. This number is unique for this driver. When a pvinverter is used to insert data and a second pvinverter or temp or anything else is inserted, the same unique ID shows up and the DBUS drops the payload and removes the duplicate from the bus. It has something to do with this part of the dbus-mqtt-services.py script: dbus_service_instance on line 43-46
I've tried simulating the PV inverter via this driver but I cannot get the AC Phase L1 Watts to show in the Victron GX. This is the payload from Node-Red towards the right topic for this script:
The Victron shows this:
![image](https://user-images.githubusercontent.com/65487781/213867123-bddeb6b7-c1e3-45a7-86db-2243d999432e.png)
I've tried filling all the fields and switching from interger to float etc. Nothing gets the Watts in this field. I think that the field must be filled all in the correct manner before the Victron shows it as a PV inverter in VRM or GX Display.