pdbjjens

@AlCalzone To which two lines in the template are you referring to? The template seems to have changed since you wrote your comment. Which lines should I comment out if...

@AlCalzone Thanks a lot for the quick reply. I'll give it a try.

@mcm1957 @DutchmanNL It is my intention to release it to stable asap. Since I just released a minor version with a new feature two weeks ago, I would like to...

@mobifu1 For the current v0.7.0 there is one issue fixed ([Detect SMA EM1.0 SUSy 270]) and one pending (#552 ). As soon as I can close #552 I will prepare...

@GermanBluefox @DutchmanNL I have implemented a detector module for this adapter sma-em. I also developed a method for SMA Speedwire discovery. They are ready for a PR against the ioBroker.discovery...

@GermanBluefox @DutchmanNL I have issued a PR against the ioBroker.discovery adapter recently https://github.com/ioBroker/ioBroker.discovery/pull/284

@TGuybrush I am really glad that you agree to work on this issue. I think that having 2 separate debounce times for realtime and nonrealtime values is a good proposal...

@TGuybrush While you are working on this issue #142, please also correct the new issue #152

@TGuybrush We got another incident of issue #137 with some details. Also the originator of #137 sent some more details in the forum [warnungen-sma-em-adapter](https://forum.iobroker.net/topic/42269/warnungen-sma-em-adapter) Currently I do not have any...

@TGuybrush Meanwhile the reason for issue #137 seems to be identified. The warnings orinate from the fact that the adapter interprets multicast response messages from the SMA Device Discovery Protocol...