Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Read data from 2. inverter does not work #24

Open
TrackerTheCode opened this issue Nov 7, 2023 · 9 comments
Open

Read data from 2. inverter does not work #24

TrackerTheCode opened this issue Nov 7, 2023 · 9 comments
Labels
enhancement New feature or request

Comments

@TrackerTheCode
Copy link

Describe the bug
I have connected the first inverter via modbus ID: 1. Unfortunately, the second inverter cannot be connected - Modbus ID: 16.
Additional info from my analyses. I stopped my second instance and change the ID in the first instance to 16. After I successfully saved the new Id, the connection was established and data were displayed, but not correctly. It was exactly the same data as with Id 1. From my point of view, the change of the Id has no impact.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'adapter'
  2. Click on 'add instnace' two times, to have to instance available
  3. configure both adapters, with id 1 and 16

Expected behavior
Second instance of adapter, to connect the other Id should work, so both inverters-instance can be connected and work in parallel.

Versions:

  • Adapter version: 0.0.1
  • JS-Controller version: 5.0.12
  • Node version: v18.18.2
  • Operating system: Docker enviroment on Unraid NAS system

Additional context
I have set up a second instance and taken the ID of the system configuration via the FusionSolar app. The inverters are coupled. The one with ID 1 has the dongle installed.

@TrackerTheCode
Copy link
Author

If i can support with a debug session, i can support in this case.

@daolis
Copy link
Owner

daolis commented Nov 14, 2023

@TrackerTheCode
See #21 Sadly, this will not work (at least for now not with a 2nd instance)

I will check the modbus library if it is easily possible to read modbus registers with a different unitID using the same connection...

@Crissiii10
Copy link

@TrackerTheCode See #21 Sadly, this will not work (at least for now not with a 2nd instance)

I will check the modbus library if it is easily possible to read modbus registers with a different unitID using the same connection...

Hi, bist du weiter gekommen? Ich habe den Adapter installiert und er läuft soweit auch! Klasse Arbeit! Nur „leider“ habe ich 2 wechselrichter und bekomme nur die Daten von einem angezeigt. Könnte das dass Problem hier sein?

Danke dir

@daolis
Copy link
Owner

daolis commented Jan 3, 2024

I have found something, but it will not work with a 2nd instance (Connected to the same dongle).

I have to change the connection code a bit, and id for the 2nd Inverter will be in config!

@Crissiii10
Copy link

Cool thanks for the Feedback. So you would create a New Version with the New Feature?

@TrackerTheCode
Copy link
Author

TrackerTheCode commented Jan 12, 2024

@daolis Do you have something implemented already. Maybe I can test it for you/support you!?

@Crissiii10
Copy link

@daolis Do you have something implemented already. Maybe I can test it for you/support you!?

Sure i have implement it. If you tell me what i should do i can test it

@daolis
Copy link
Owner

daolis commented Jan 12, 2024

@TrackerTheCode still work in progress. Need more or less to 're-implement' the communication.

@Crissii10
Copy link

@TrackerTheCode still work in progress. Need more or less to 're-implement' the communication.

I dont know if it help you but in Home Assistant the Connection to the second work

@daolis daolis added the enhancement New feature or request label Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants