433toMQTTto433 Gateway Device List

Hardware
167

Well I’m talking about the 433Mhz signal not the intermediate MQTT messages.

168

I have ordered yesterday 3 of this from AliExpress, I will report back when they arrive

169

Hi,

There is no ID reported in the MQTT topic if you use OpenMQTT, there is only the message. The on payload is 7 point higher than off. I have 12 D026 units and they all work great (actually more reliable than Z-wave D-link multisensors).

I think you were referring to RFLink (or other projects) where it identifies the device id and then the payload as on or off.

I have mine setup as following (might have included some additional steps around here but it works quite reliably):

#1. Initial sensor (it reads from the default 433toMQTT topic); this sensor is not published by gateway with retain flag

- platform: mqtt
  state_topic: 'home/433toMQTT'
  name: 'ODOpenDoorLiving'
  payload_on: '11111118'
  payload_off: '11111111'
  device_class: opening

#2. Modified sensor from no. 1 with (simpler) on and off payloads; when I replace the sensor I don’t want to make modifications based on the 8/7/9 digits code sent by the physical unit but rather look for on/off payloads.

- platform: mqtt
  state_topic: 'home/OpenDoorLiving'
  name: 'OpenDoorLiving'
  payload_on: 'on'
  payload_off: 'off'
  device_class: opening

#3. Automation that connects 1 and 2; the messages are posted with retain flag

- alias: OpenDoorLivingON
  initial_state: 'on'
  trigger:
    - platform: state
      entity_id: binary_sensor.ODOpenDoorLiving
      to: 'on'
  action:
    - service: mqtt.publish
      data:
        topic: "home/OpenDoorLiving"
        payload: 'on'
        qos: 0
        retain: true
- alias: OpenDoorLivingOff
  initial_state: 'on'
  trigger:
    - platform: state
      entity_id: binary_sensor.ODOpenDoorLiving
      to: 'off'
  action:
    - service: mqtt.publish
      data:
        topic: "home/OpenDoorLiving"
        payload: 'off'
        qos: 0
        retain: true

#4. The initial sensor is hidden from frontend (so only the one with on/off payload remains)

  customize_glob:
    "binary_sensor.od*":
      hidden: true
1 Like
170

Also, based on the example payload above, the tamper code sent by D026 would be ‘11111115’

171

Hi Petrica,

Yep that’s what I was talking about and what I get from pilight-receive is currently not much use as the devices either change a unit id or have different system ids for on/off open/closed, which makes automations a bit tricky :slight_smile: All my other switches/lights/door and window devices give back the same unit ids and system codes for each device but with an open/closed on/off payload.

172

Hi

I also purchased these. But I have the RFXCOM and it takes 25 second to get a response but the Door sensors send a response straight away.

Do you have the same problems?

173

I’ve tried also RFLink with Domoticz (actually it was fancier than HA with OpenMQTT as the devices were all lined up and ready to be added into the system) however the device id would sometimes get decoded incorrectly.
I’m using OpenMQTT (on a Arduino Mega) for 3mo+ already and I still have to find a flaw in 433Mhz decoding. I have some other 433Mhz devices such as PIR sensors and wall switches (I replaced all wired switches) that control MiLight bulbs (through emulators on NodeMCUs) and the system is quite solid. The weakest link is the MiLight protocol however I’m re-sending each command three times so I cleared also those issues. Although there are multiple 433 Mhz firing the same time, there are no missing messages on the gateway. Also, MQTT stands great to 10-15 messages per second.

174

People please stop the write on this thread.
This thread its not for discussion of codes. Only to insert a new devices already tested.

175

Agreed we should take this discussion elsewhere :slight_smile:

176

Sorry about that.

Could we make the first topic sticky?

Also, some of the devices in the list have expired links.

177

I refreshed the link, but next time, anyone can edit the link and correct the broken one :slight_smile:

178

https://www.gearbest.com/alarm-systems/pp_659761.html?

dont buy it - NOT WORKS

179

I’m using Kerui brand door contact. Check this out.

1 Like
180

Works fine

181

Works fine , and if you install alixpress android app, is more cheaper

each 4.36 eur

182

These Aukey outlets work.

183

So on the github page it says the Sonoff RF Bridge works with this firmware - does it also allow transmitting codes?

184

hello,

yes both, receiving and transmitting, here is the user guide

185

Excellent. I was using Tasmota’s Firmware and after a lot of back and forth it was marked as no transmit.

Any ideas why I am getting this compile error?

C:\Users\simon\Downloads\OpenMQTTGateway\OpenMQTTGateway/ZgatewayRF.ino:54: undefined reference to `RCSwitch::send(unsigned long, unsigned int)'

sketch\OpenMQTTGateway.ino.cpp.o: In function `MQTTtoRF(char*, char*)':

C:\Users\simon\Downloads\OpenMQTTGateway\OpenMQTTGateway/ZgatewayRF.ino:90: undefined reference to `RCSwitch::send(unsigned long, unsigned int)'

C:\Users\simon\Downloads\OpenMQTTGateway\OpenMQTTGateway/ZgatewayRF.ino:98: undefined reference to `RCSwitch::send(unsigned long, unsigned int)'

collect2.exe: error: ld returned 1 exit status

exit status 1
Error compiling for board Generic ESP8266 Module.
186

You should comment the following lines on user_config.h:
//#define ZgatewayIR
//#include “config_IR.h”
//#define ZgatewayBT
//#include “config_BT.h”
//#define ZgatewayRF
//#include “config_RF.h”

and uncomment these ones:
#define ZgatewaySRFB
#include “config_SRFB.h”