Hello everyone, Current adapter status: current version: 0.1.13 installation via npm is available Node.js requirement is now >= 22 the state structure has been expanded quite a bit and remains stable under the same ioBroker paths for both Genie and M5/M9 it now includes status, diagnostics, location, consumable, zone, control, and command states M5/M9-specific payloads for status, network, RTK, map status, and total mowing time/area are now also mapped into the existing state structure on AWS IoT 403 responses, temporary IoT credentials are refreshed once automatically and the failed shadow read or command publish is retried Over the last few days I also split up and cleaned up the adapter internally and expanded the checks so the internal modules and tests are validated properly. Functionally, this should not have changed any state IDs or command payload behavior. The submission for the ioBroker latest repository has already been started and is currently waiting for review. It would be especially helpful to get confirmations from users with an M5 or M9 that the new payload mappings work reliably in day-to-day use. If anyone tests the current build, these points are especially interesting: login and device discovery shadow/status updates over longer runtimes manual and automatic zone mowing point mowing near-charger mowing behavior after connection issues or 403 errors As always, feedback is welcome together with adapter version, js-controller version, Node.js version, and relevant log output.

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

Github Link and list of devices supported by LAN API unfortunately mine are not supported, so I have to stay with the cloud :(

@sonusfaber i see 3 kind of solutions you can create a normal datapoint with your adapter with permissions only read you can safe your information in the object data of a datapoint, maybe in the datapoint that represence your instance (adapter.0) for example the history adapter safes his data with the object path common.custom.history.0 and the sql adapter safes the data in common.custom.sql.0 to see this in real life go to a datapoint, enable the logging with the history/and/or the sql-adapter, open the datapoint setting with the pen icon beside and select the object data tab. you can safe your data as a file below the following path /opt/iobroker/data-files/(name of your adapter) my adapter tvprogram, the history and the backup adapter also safe also some data here