Remote for ESMART Professional MIMOTO

wiz · August 27, 2021, 9:27am

Hi there,

I stumbled over this very interesting project while looking for a solution to control a ESMART Professional MIMOTO motorized screen like this: ESMART Professional MIMOTO Motor-Leinwand in openHAB/via Logitech Harmony Hub. It has a three button RF control up/stop/down with a label telling nothing more than 433.92Mhz.

Here Beamerleinwand per Loxone Miniserver steuern | meintechblog.de I found the information that the remote uses the Intertechno band all FS20 transceivers could be used to control the screen. In the last posting there, the codes for the buttons are also included:

DOWN:

Decimal: 5749700 (24Bit) Binary: 010101111011101111000100 Tri-State: not applicable PulseLength: 266 microseconds Protocol: 1
Raw data: 8264,220,840,760,308,228,836,756,312,220,844,756,308,760,312,756,312,756,312,220,860,740,324,744,320,748,324,212,852,748,324,744,328,740,324,744,324,212,852,212,848,216,844,756,312,220,860,204,860,

STOP:

Decimal: 5749704 (24Bit) Binary: 010101111011101111001000 Tri-State: not applicable PulseLength: 263 microseconds Protocol: 1
Raw data: 8260,224,836,760,312,220,840,760,308,224,848,752,308,760,308,760,308,760,308,224,844,756,308,764,308,760,308,224,844,756,308,760,312,760,308,760,308,224,852,216,852,744,316,220,844,220,852,212,844,

UP:

Decimal: 5749698 (24Bit) Binary: 010101111011101111000010 Tri-State: not applicable PulseLength: 260 microseconds Protocol: 1
Raw data: 8256,228,836,760,308,224,840,760,312,220,840,756,312,756,308,760,316,756,304,228,836,760,308,760,308,764,304,228,832,768,300,768,304,764,304,764,308,224,848,216,844,220,844,220,844,756,316,216,852,

Before I start trying: Is this a scenario OMG would be able to handle? I have a spare NodeMCU V3 ESP8266 here on my desk. Would that be a good choice/what should I use instead? Which transceiver would you recommend? There are some other 433 MHz devices in the house. Would you recommend to build dedicated OMG devices for several such use cases or would it be possible to use one device for more than one use case (speaking of very low usage)?

I already have a openHAB3 server running with a Mosquitto MQTT-Broker and the Harmony Hub is also running already.Therefor I should be able to send the buttons form openHAB to the Broker to tell OMG to send them. As openHAB also recognizes actions started by the Harmony Hub it should be no problem to start this process when the respective “scene” is started by the Harmony Hub.

Is that correct so far?

Any further ideas welcome!

1technophile · August 28, 2021, 2:30am

Looking at the codes there is a good chance for a yes. Nevertheless your best guess is to try it.

This depends on the distance between devices. Necertheless one OMG can handle different use cases.

wiz · November 12, 2021, 12:55pm

Sorry for late reply, and thanks for your answer. I had some other projects to finish before getting back to this one.

In the meantime I bought a set of these WayinTop 3 Set 433 MHz Funk - Sende und Empfänger Modul + 433MHz Antenne Helical Spiral Spring 433MHz Receivers/Transmitters and wired them to my left over NodeMCU V 3 AZDelivery NodeMCU Lolin V3 Module ESP8266 ESP-12F WiFi WiFi Development Board mit CH340

But now I am unsure which version of the OMG I should install? There are a lot of versions for different NodeMCU V2 but none for V3. From the filenames I can judge that some of the versions obviously support some extra features of some boards like BLE, but even after looking around here in the forum I could not find out the version I could use for my NodeMCU V3. Can you help me?

If the left over NodeMCU V3 I have here is not such a good idea, you could perhaps name me a better alternative?

Thanks in advance!

1technophile · November 14, 2021, 11:21pm

Hi,

We can add an environment for NodeMCU V3, you can try first with NodeMCU v2

wiz · November 19, 2021, 2:10pm

OK, now I tried with the “RF” version for NodeMCU v2 which should be compatible to my set of Receiver/Transmitter. Wired everything using VV for 5V currency on the NodeMCU v3, Transmitter on DD2 and Receiver on D1. After powering up I see the following in the Serial Monitor:

N: RF_EMITTER_GPIO: 3
N: RF_RECEIVER_GPIO: 0
N: Switching to RF Receiver
N: OpenMQTTGateway modules: [“RF”]
N: ************** Setup OpenMQTTGateway end **************
W: MQTT connection…
N: Connected to broker
N: Received json : [“RF”]
N: Received json : [“RF”]
N: Received json : [“RF”]
N: Received json : [“RF”]
N: Received json : [“RF”]
N: Received json : [“RF”]
N: Received json : [“RF”]
N: Received json : [“RF”]
N: Received json : [“RF”]
N: Subject: /SYStoMQTT
N: Received json : {“uptime”:4,“version”:“v0.9.8”,“freemem”:36560,“rssi”:-44,“SSID”:“GWA47118611”,“ip”:“192.168.5.155”,“mac”:“D8:BF:C0:14:15:5C”,“actRec”:2,“modules”:[“RF”]}

Following the description here 433toMQTTto433 - Bidirectional ESP8266 NodeMCU gateway between RF 433Mhz signal and MQTT (1technophile.blogspot.com) I should see this
If the connexion to mosquitto is ok you should see on the serial monitor of the arduino “connected” & “subscription OK to home/MQTTto433/”

I tried to receive data from the remote control I want to emulate, but do not see anything in the serial console or on the MQTT Browser.

What is my mistake?

1technophile · December 4, 2021, 9:01pm

Could you post pictures of your setup ?

wiz · December 6, 2021, 8:01am

Thank you for helping me. Here are some pictures:

1technophile · December 7, 2021, 10:02pm

Could you try to power the 2 modules with VIN of the ESP8266?

wiz · December 8, 2021, 2:44pm

I tried, but could see no difference on the serial console or the MQTT Broker, when pushing a button on the rc. I checked voltage as I was a bit concerned about using VIN, and as soon as the modules are connected there, voltage is at just some mV on VIN. So I also checked with VV giving me 4.95V, when the modules are connected there.

I also tried with another receiver and a totally other rc (Brennenstuhl power outlets), but nothing happens.

1technophile · December 8, 2021, 10:25pm

If you have another NodemCU and another emitter I would try the third bullet point of this:
https://docs.openmqttgateway.com/upload/troubleshoot.html#not-able-to-send-or-receive-rf-or-ir

wiz · December 9, 2021, 3:58pm

Thanks so much for your patience!

Before installing the smaller examples I thought I could try directly what I really want to achive. Just controlling the motorized screen. As mentioned in my first posting I already have some codes from the internet for the three buttons, so I read through your instructions how to send the codes (without trying to read them by myself from the rc).

As I know that the coverage of the transmitter is limited I took the whole PoC to my living room and installed it there. As soon as it started I got several messages on my MQTT-Browser with received codes, obviously from a 433MHz thermometer which is installed there. So the receiver seems to work, but does not get the signal from my rc for the screen or from the Brennenstuhl rc for the plugs.

Nevertheless I tried to send the code for one of the buttons for the screen:

openhabian@rp4oh3:~ $ sudo mosquitto_pub -u myuser -P mypassword -t "home/OpenMQTTGateway_ESP8266_RF/commands/MQTTto433" -m '{"value":5749700,"protocol":1,"length":266}'

But first nothing happened, then I got constant exceptions on the NodeMCU like the following

N: Received json : {"value":5749700,"protocol":1,"length":266}
N: RF Protocol:1
N: RF Pulse Lgth: 350
N: Bits nb: 266

--------------- CUT HERE FOR EXCEPTION DECODER ---------------

Soft WDT reset

>>>stack>>>

ctx: cont
sp: 3ffffa30 end: 3fffffc0 offset: 01a0
3ffffbd0:  00000025 3fff0160 3ffffc00 40229844  
3ffffbe0:  401006a8 3ffefc30 00000003 401006d1  
3ffffbf0:  40215f9c 00000003 3ffefc30 40213de1  
3ffffc00:  3fff0301 3ffffc40 00000010 40216385  
3ffffc10:  4027d3f0 3ffe9310 3fff0160 3ffefc46  
3ffffc20:  3ffefc30 000000b0 00000006 40213f2d  
3ffffc30:  3ffffc50 3ffffc40 0000000c 00000000  
3ffffc40:  ffffffff 0000010a 0057bbc4 00000000  
3ffffc50:  3ffefc42 00000014 3ffffc80 40202284  
3ffffc60:  3ffefc30 3fff0160 3ffefc30 0000010a  
3ffffc70:  3ffefc30 3fff0160 3ffffce0 40203bb2  
3ffffc80:  3ffffce0 3ffe8954 00000014 30303739  
3ffffc90:  00000001 0000015e 00000014 0057bbc4  
3ffffca0:  00000000 00000014 007d3636 402036b8  
3ffffcb0:  3ffffcb8 0000002b 00000014 3fff2c5a  
3ffffcc0:  3fff149c 3fff2c27 3ffffce0 40206264  
3ffffcd0:  40229fd0 3ffffce0 00000200 00000068  
3ffffce0:  3ffffcd0 3ffffce8 3ffffd08 3fff2190  
3ffffcf0:  3fff149c 3ffeda48 00000001 3a30433a  
3ffffd00:  3fff14a2 00000001 3ffffd28 40100554  
3ffffd10:  3fff14aa 00000000 00000001 3a30433a  
3ffffd20:  3fff14b3 00000001 00000000 40100554  
3ffffd30:  3fff14b5 00000000 00000001 3a30433a  
3ffffd40:  3fff14bc 00000001 00000005 40101ca0  
3ffffd50:  00000000 00000000 00000020 40100554  
3ffffd60:  40102837 3ffedd90 00000000 40101ca0  
3ffffd70:  3ffea300 40104f3b 3ffedbb0 40102a18  
3ffffd80:  00000005 00000000 00000020 40100554  
3ffffd90:  40104587 1380de50 00000005 40101ca0  
3ffffda0:  3ffea305 40104f53 3ffedd90 401057f9  
3ffffdb0:  00000000 00000000 0000001f 40100554  
3ffffdc0:  00007fff 1380f657 3fffc228 401057f9  
3ffffdd0:  4000050c 00000000 00000000 4bc6a7f0  
3ffffde0:  40100613 00000030 00000010 ffffffff  
3ffffdf0:  40100610 f3026d50 05c5ec94 00418937  
3ffffe00:  00004bc6 f3026d50 00000058 fffffffe  
3ffffe10:  00005794 3fffc6fc a5c06d50 1380fcab  
3ffffe20:  00000000 00000032 00000056 00000030  
3ffffe30:  40102bfc 3fffc200 00000022 fffffffe  
3ffffe40:  40228f3c 00000030 00000010 ffffffff  
3ffffe50:  40228f3c 00000001 fffffffd 0000002c  
3ffffe60:  00001470 0000028e 0000028e 40100d53  
3ffffe70:  00000000 3fffc6fc 00000000 00000001  
3ffffe80:  3fff211c 00000000 00000020 40100fdb  
3ffffe90:  00000000 4bc6a7f0 0004fe33 00000080  
3ffffea0:  00000000 4bc6a7f0 00000000 4023cf48  
3ffffeb0:  00000000 00000000 4bc6a7f0 40236902  
3ffffec0:  0004fe33 00000000 3fff2a64 40209ce2  
3ffffed0:  000007f0 3fffff12 0000007d 40209d3a  
3ffffee0:  3ffffcd0 3fff14c7 3fff14c0 3fff2c0a  
3ffffef0:  0000002b 00000032 00000020 40101012  
3fffff00:  402062bc 40228cdc 0000005f 3fff2c5a  
3fffff10:  3fff14c7 3fff149c 3fff2c27 4020632a  
3fffff20:  3fffff50 00000001 00000002 00000061  
3fffff30:  0004fe33 00000032 3ffefddc 40228cd4  
3fffff40:  0004fe33 3ffefddc 3ffefddc 40206c2c  
3fffff50:  3fffda01 3ffefe60 3fff0b1c 40224981  
3fffff60:  4026b0e7 6e3748c0 3fff02f0 40222eba  
3fffff70:  3ffefe68 00000001 0000002c 00000000  
3fffff80:  3ffefe68 3ffefddc 0004fe33 402046ab  
3fffff90:  3fffdad0 00000000 3fff0520 3fff0560  
3fffffa0:  3fffdad0 00000000 3fff0520 40218938  
3fffffb0:  feefeffe feefeffe 3ffe86b0 401013b9  
<<<stack<<<

--------------- CUT HERE FOR EXCEPTION DECODER ---------------

 ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x4010f000, len 3584, room 16 
tail 0
chksum 0xb0
csum 0xb0
v2843a5ac
~ld

As you can see the parameter length is obviously not interpreted correctly:
RF Pulse Lgth: 350 (no idea where this value comes from)
Bits nb: 266 (this is the value form the length parameter, and as we have more than 255, this may be the reason for the exception)

This is something to talk about, but in total I ask myself if this whole thing may led to anything as long as the receiver is able to receive data from other devices but not of the rc I need this whole stuff for?

1technophile · December 10, 2021, 1:15am

266 bits cannot be handled by rcswitch, from what I see in your first post , your value is 24 bits, you should try:

{"value":5749700,"protocol":1,"length":24,"delay":266}

wiz · December 10, 2021, 9:44am

Sorry, then I misinterpreted the parameters. Following your advice I do not get any exceptions any more and it seems, that everything from the side of the MGTT-Gateway is running now:

N: Received json : {"value":5749700,"protocol":1,"length":24,"delay":266}
N: RF Protocol:1
N: RF Pulse Lgth: 266
N: Bits nb: 24
N: MQTTtoRF OK
N: Subject: /433toMQTT
N: Received json : {"value":5749700,"protocol":1,"length":24,"delay":266}
N: Switching to RF Receiver
N: Received json : {"value":5749700,"protocol":1,"length":24,"delay":266}

But the screen still shows no reaction. I will invest some more time on it over the weekend. What I do not understand is, how the guy posting the cited codes identified them, when my little standard receiver does not react on the RC/the screen does not react on the code when send through my transmitter?

1technophile · December 10, 2021, 10:13pm

I agree with you, maybe these codes are not relevant for your devices.