ioBroker / ioBroker.maxcul

Control max! devices over CUL stick
Other
4 stars 8 forks source link

Missing documentation in readme (FakeWallThermostat, FakeShutterContact) #19

Closed danzbox closed 4 years ago

danzbox commented 5 years ago

I am stuck with the iobroker.maxcul adapter due to the lack of documentation. Can you please extend the read me a bit.

  1. Does it support external sensors to be used as MAX! Wallthermostat and ShutterContact replacements like the Pimatic plugin from where it is derived from? Or have developments of both projects split for a long time and since then code is separated? In FHEM and Pimatic this feature is call FakeWallThermostat and FakeShutterContact. It has been added to Pimatic with version 1.0.0 committed on Jan 14, 2018 It would require that components could be "associated" which each other or that the adapter is doing it in the background without visibility for the user. Could you please write (or copy and paste for FHEM/Pimatic) what features the iobroker adpater has and which ones not. Documentation that I find worth to be copied into the readme, if they apply to iobroker.maxcul or would be worth to be mentioned not beeing support at the moment if this is the case: https://wiki.fhem.de/wiki/MAX#Externer_Temperatursensor_f.C3.BCr_Heizk.C3.B6rperregelung https://github.com/fbeek/pimatic-maxcul This has also been raised in iobroker from with no answer: https://forum.iobroker.net/viewtopic.php?t=20684
stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions. Dieses Problem wurde automatisch als veraltet markiert, da es in letzter Zeit keine Aktivitäten gab. Es wird geschlossen, wenn nicht innerhalb der nächsten 7 Tage weitere Aktivitäten stattfinden. Bitte überprüft, ob das Problem auch in der aktuellsten Version des Adapters noch relevant ist, und teilt uns dies mit. Überprüft auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind bzw. aktualisiert diese. Vielen Dank für Eure Unterstützung.

stale[bot] commented 4 years ago

This issue has been automatically closed because of inactivity. Please open a new issue if still relevant and make sure to include all relevant details, logs and reproduction steps. Thank you for your contributions. Dieses Problem wurde aufgrund von Inaktivität automatisch geschlossen. Bitte öffnet ein neues Issue, falls dies noch relevant ist und stellt sicher das alle relevanten Details, Logs und Reproduktionsschritte enthalten sind. Vielen Dank für Eure Unterstützung.