NEWS

@trixx
You archived the repo ioBroker.soliscloud.

Please let us lnow if hhe adapter is nonlonger worki g due tp some cganges at the solis website or if you just do not have time or interrest to makntain it any further.

If the later is valud please consider movi g itvinto iobroker-community-adapters.This wpukd ne only a few clicks for you. Transfer ownership of repo to me (mcm1957) would be sufficient. I can do the rest.

Thanks for your feedback
Mcm1956

Edit
https://github.com/iobroker-community-adapters/info?tab=readme-ov-file#ask-to-move-your-repository-to-iobroker-community-adapters

des ribes the steps to initiate a transfer

@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.
___rtl_433 Instanz läuft.png
However, I had to set the protocols manually in the command line:
___rtl_433 Protokolle manuell hinzugefügt.png
There are none in the overview:
___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

stevenengland created this issue in ioBroker/dev-server closed json5 config file not considered when creating browser-sync proxies #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

@sonusfaber only admins can delete.

Please edit your first post and add [Solved]

@zimbl
Was soll das bringen?! Eine Anforderung besteht nur, wenn der Puffer zu kalt ist.

Heizkreis selbst an / ausschalten ist kein Problem. Sowas macht man aber doch nicht über die Anforderung. Da würde wenn dann eh nur der Kessel anspringen.

@ice987

War offenbar ein BUG in admin <v6.0.1.

ggf. kann dieses Thema noch an den korrekten Ort verschoben werden.