@boriswerner Hi, Yes, I’m German – thanks for the tip, I’ll cross-post this in the German section as well. Yes, I know leapmotor-api/leapmotor-ha from markoceri/kerniger – I cross-referenced them several times during development, e.g. for the B10/C10 signal mapping and cloud endpoints. Good call that you’re familiar with that project too. Regarding charge limit: the adapter actually already supports setting it (cmd.charge_limit_set, 50-100%), but I just found and fixed a bug – the limit wasn’t reliably applied because it was accidentally disabling the existing charge schedule every time it was set. The fix is currently being tested on my end and will be pushed to GitHub shortly. Feel free to test the adapter already, but I’d wait for the next release before relying on the charge limit feature specifically. Looking forward to your testing on the T03!

ich habe mal nen fork erstellt und nacharbeiten "lassen" ;) greets

@Qlink I'm fairly certain the Iiyama protocol is standard across the ProLite range, for the basic functions if nothing else. The adapter is based on the model I have access to but it would be great if others could test it on other models. I'm more than happy to update the adapter as required for any other models.

Adapter has been release to LATEST repository.

Adapter has been release to latest repository.

That would be great if you could, every little helps.

@Leonie sagte: I can not only speak german perfectly , I'm also a german native speaker. I'll contact homoran to gain access to the german area. I know ... if google did not report the wrong person :-)

@honnkoponko [image: 1756310914909-ac50af6f-024d-4807-ae30-cc71248608f1-image.png] This adapter is no longer maintained. I do not have any information WHY it was archived. IF the adpater is still working (and change by solis cloud etc.) is the reason to stop maintaining this adapter we could move it to iobroker-community-area so that at least base maintainance can be provided. Adding new features is always possible but depends on available developers. Please let me know if adapter is still working and if you eventually would help testing after migration to iobroker-community-area. (Please ping me again if I miss any answer)

@norfer Just for all of us with same problem: at the beginning there was no station-ID shown in my soliscloud-URL - being logged in and all the values were shown. Only after various new attempts on the following days the ID was shown - without any modifkation by me. So just wait and try!

@pixelsolution Oh - noticed U-Match isn't supported?

Hello everyone, I have just released version 0.3.0 on NPM. This includes some improvements as well as a basic setup guide. The guide can also be found here: https://github.com/danieldriessen/ioBroker.google-home-nest/blob/main/docs/en/README.md If anyone tries the adapter and follows the instructions, it would be very kind if you could give me feedback on how it went. By the way, I am just waiting for the approval (as an additional owner of the NPM package) from @Bluefox. Afterwards, I think I am ready to include the adapter in the beta repository. Best regards, Daniel

Hi @phillipssc, I have an ioBroker installation on Ubuntu and your Adaper works. [image: 1712082938389-___rtl_433-instanz-l%C3%A4uft.png] However, I had to set the protocols manually in the command line: [image: 1712082980135-___rtl_433-protokolle-manuell-hinzugef%C3%BCgt.png] There are none in the overview: [image: 1712083004662-___rtl_433-keine-protokolle.png] Any ideas? What is wrong?

Long story short: I opened this issues to solve the root cause: https://github.com/ioBroker/dev-server/issues/471

Feel free to follow the discussions in the german iobroker forum