UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[Trixx]

@schneider_helmut said in New Adapter - Soliscloud:

@Trixx

If I want to install the adapter over this link

https://github.com/Trixx34/ioBroker.SolisCloud

Could you try using: https://github.com/Trixx34/ioBroker.soliscloud (without caps).

[Homoran]

@trixx sagte in New Adapter - Soliscloud:

without caps

I fixed this in both threads.
please tell me if there are more typos

[mcm1957]

@schneider_helmut
@Trixx

I tried now and the installation worked as expected (I did not test the functionality).

BUT a look at the console output look a little supect:

Installing Trixx34/ioBroker. SolisCloud#b39242521a5f9f1b7eee929cc6589b1c4af0170

For me, there seems to be a SPACE between the dot and the S of SolisCloud. Please retry and check your input.

I do not think that capital letters cause a problem here, as urls are case insensitive.

[Homoran]

@mcm57 sagte in New Adapter - Soliscloud:

there seems to be a SPACE between the dot and the S of SolisCloud.

@schneider_helmut sagte in New Adapter - Soliscloud:

Installing Trixx34/ioBroker. SolisCloud#b39242521a5f9f1b7eee929cc6589b1c4af0170... (System call)

here it is, too!

[Schneider_Helmut]

@trixx

Thank you. Everything works great now. Grate job! I waited over a year for a Solis adapter for IO Broker because I wasn't able to use the Solis API myself.
Perhaps it would be important to mention that for "Station/Plant ID" you do not have to enter the ID "1668XX" from the Soli portal as expected, but rather the id from the browser address while you are logged in to your solis account "https://www.soliscloud.com/#/station/stationdetail_1?id=12984919194490002YY". "Station/Plant ID" must be entered here "12984919194490002YY".

[Trixx]

@Schneider_Helmut

Good to hear everything is working now for you!

You're correct on the information regarding the plant ID, I'll update the documentation to make that more clear.
If there's any value you are missing and would like to have available in in ioBroker, let me know and I'll see what I can do!

Regards,
Trixx

[Schneider_Helmut]

@trixx
I really appreciate your support. Your adapter will be very useful to Solis as people increasingly want to network systems. I can't understand why manufacturers don't make an effort to open up to common automation solutions and offer adapters themselves. For example, I have been looking for a wallbox for months where the manufacturer offers an IoBroker adapter with which I can start charging via IO-Broker and specify the charging current for the car myself.
And I still did not find one.

[Trixx]

The latest version on github is broken, I broke it while trying to fix something else...
I'll try fixing this tonight.

Edit; small fix. Already ok again

[Luapsi]

@trixx
I am also interested in the “Soliscloud” adapter.
The installation was successful, unfortunately I can't get any further with the settings so that access to the SolisCloud is possible.
No SolisCloud is displayed in the instances, but that's okay in the objects?
I have already activated the Solis API.
I have only recently started using ioBroker.

Thk Sven

[Trixx]

@luapsi

Hi,
Thanks for trying my adapter. Once the install from github is completed, you should now be able to find the solis adapter in the "adapters" screen.
From there you should be able to add an instance of the adapter to your ioBroker installation. Once the instance is installed, it will take you directly to the configuration screen.

[Homoran]

@luapsi sagte in New Adapter - Soliscloud:

No SolisCloud is displayed in the instances

that is the regular behavior by installing via github.
The instance has to be added manually

[Luapsi]

@homoran
Hello, I just found it in the documentation.
Thank you very much:)

[Luapsi]

@trixx sagte in New Adapter - Soliscloud:

battery_current_usage

hi @trixx,

The SolisCloud adapter also works for me. Thank you for your implementation.

As you requested, it would be great if these values ​​could be added:

from the Power Station List:

1. batteryTodayDischargeEnergy
2. batteryTodayChargeEnergy
3. homeLoadTodayEnergy
4. state
5. oneSelf

from the Inverter List:

1. eToday
2. etodayStr
3. state

Gerne teste ich für Dich!

[Trixx]

@luapsi said in New Adapter - Soliscloud:

@trixx sagte in New Adapter - Soliscloud:

battery_current_usage

hi @trixx,

The SolisCloud adapter also works for me. Thank you for your implementation.

As you requested, it would be great if these values ​​could be added:

from the Power Station List:

1. batteryTodayDischargeEnergy
2. batteryTodayChargeEnergy
3. homeLoadTodayEnergy
4. state
5. oneSelf

from the Inverter List:

1. eToday
2. etodayStr
3. state

Gerne teste ich für Dich!

Thanks for the suggestions, I'll see what I can do. The first 5 shouldn't be to much work, I should be able to do that right away. The other ones require an additional API call, but still shouldn't be a problem.
I'll let you know once I have an update on this.

[Luapsi]

@trixx

hi @Trixx

thank you for taking the suggestions!
Here's a little addition!
In ioBroker, instances are assigned a category!
Would you be so kind as to put your instance in the “Energy” category?

Here is an excerpt from instances in this category

Thx Sven

[Trixx]

@luapsi

Hi,

I've just pushed a new version to github, I think it should include all requested additions :)

Regards,
Trixx

[Luapsi]

@trixx
Your performance is great, thank you very much.
I will test extensively and give you feedback.

I wish you a pleasant day

[Luapsi]

Hi @trixx,

all data fields are correct.
Thanks for the quick and professional work.

As you requested, it would be great if these values ​​could be added:

from the v1/api/InverterDetail:

4. familyLoadPower
5. familyLoadPowerStr
6. id inverter id
7. sn inverter sn
8. iAc1 AC current R
9. iAc2 AC current S
10. iAc3 AC current T
11. uAc1 AC voltage R
12. uAc2 AC voltage S
13. uAc3 AC voltage T
14. inverterTemperature
15. batteryPower
16. batterypowerStr
17. batteryPowerPec
18. batteryTodayChargeEnergy
19. batteryTodayChargeEnergyStr
20. batteryMonthChargeEnergy
21. batteryMonthChargeEnergyStr
22. batteryYearChargeEnergy
23. batteryYearChargeEnergyStr
24. batteryTotalChargeEnergy
25. batteryTotalChargeEnergyStr
26. batteryTodayDischargeEnergy
27. batteryTodayDischargeEnergyStr
28. batteryMonthDischargeEnergy
29. batteryMonthDischargeEnergyStr
30. batteryYearDischargeEnergy
31. batteryYearDischargeEnergyStr
32. batteryTotalDischargeEnergy
33. batteryTotalDischargeEnergyStr

another note about the data structure:

Is it possible to create a separate folder for each API group, which would allow the data fields to be better allocated

• Power Station List (v1/api/userStationList)
• Power Station Detail (v1/api/stationDetail)
• Datalogger List (v1/api/collectorList)
• Data logger details (v1/api/collectorDetail)

Inverter List (v1/api/inverterList)

• Inverter details (v1/api/inverterDetail)
  possible!

If I can support you here, please let me know.

Greetings from Saxony

PS: the app currently available from Solis cannot be used in this way.

[Trixx]

@luapsi

Hi,

I've pushed another version to github.
The values are split up between the inverter & station details, for the values I did have to switch some things.
The month & year values aren't exported correctly for the inverter api call (they are returned as '0'), the stationDetail does provide the correct values so they are available under stationDetails instead.

I still have a few more to add and need to adjust some units .
I'll try to get to those later today or later this week.

Regards,
Trixx

[Luapsi]

@trixx

Hi,

Thank you for your enthusiasm and commitment!
For me the values ​​are also "zero", I will create a ticket with "Soliscloud" so that we can achieve clarity here.
Let me know if there is any news.

Greetings Sven