melyux

Besides porting to the rewrite, the only outstanding code review comment is [that last one](https://github.com/pilight/pilight/pull/435#pullrequestreview-208149677), right?

Ah, @saak2820 was so close...

I played with the code and realized this doesn't actually implement the Bresser-3CH protocol. It implements something else. It doesn't match up with the bresser-3ch protocol in RTL_433, which is...

@saak2820 Welcome back! Do you want to change the name of this since your protocol is not Bresser 3CH? Maybe you could find what RTL_433 calls this protocol and rename...

I tried this on ESPilight (by just adding the new files to the protocols folder and adding the inits to the right places), but it didn't run and blocked other...

I could do that, but I don't have the actual Bresser device (or whatever this protocol is for) to test it with... I got some Bresser 3CH ones only. :(...

Hard to find info about that sensor, but I did find [this page](http://flux242.blogspot.com/2018/06/how-to-collect-wireless-sensors.html) that links to [this Amazon page](https://www.amazon.de/Bresser-Thermometer-inklusive-Außensensoren-schwarz/dp/B01JS4I17M/) that matches your EAN. It says that `rtl_433` recognizes that sensor...

This was the preferred way of publishing a timestamp that I thought was implied through some documentation, probably, so whether it was a "support request" or a bug was something...

Hey @ponchio, could you fix the submodule? Had the same problem as above and the workaround works.

Having this problem inside a Linux container on a Linux machine. Also had it on a Mac. Check out this issue for hundreds of people with this problem using another...