Shelly Wifi Door and Window Sensors Review

Hardware
23

Is the triggered number always 128 or does it change depending on how hard you vibrate it?

24

I have tried many times and when the value is 0 the vibration is not triggered instead when it is at 128 (the value does not vary based on how much vibration there is or at least doing 4 or 5 tests the value has always been the same) the vibration is taken

25

Then that makes it easy.

payload_on: '128'
payload_off: '0'
26

yes now everything works thanks for helping me!

place the complete configuration for other people to here could serve

####################################################
#                                                  #
#                Shelly Door/Window                #
#                                                  #
####################################################

binary_sensor:
  - platform: mqtt
    state_topic: "shellies/shellydw-xxxxxx/sensor/state"
    name: "Shelly Door/Window Sensor"
    payload_on: 'open'
    payload_off: 'close'
    qos: 0
    device_class: door
  
  - platform: mqtt
    state_topic: "shellies/shellydw-xxxxxx/sensor/vibration"
    name: "Shelly Door/Window Vibration"
    payload_on: '128'
    payload_off: '0'
    qos: 0
    device_class: vibration

sensor:
  - platform: mqtt
    name: "Shelly Door/Window Lux"
    state_topic: "shellies/shellydw-xxxxxx/sensor/lux"
    value_template: '{{ value|round(0) }}'
    qos: 0
    device_class: illuminance
    unit_of_measurement: 'lux'

  - platform: mqtt
    name: "Shelly Door/Window Battery"
    state_topic: "shellies/shellydw-xxxxxx/sensor/battery"
    value_template: '{{ value|round(0) }}'
    qos: 0
    device_class: battery
    unit_of_measurement: '%'

  - platform: mqtt
    name: "Shelly Door/Window Tilt"
    state_topic: "shellies/shellydw-xxxxxx/sensor/tilt"
    value_template: '{{ value|round(0) }}'
    qos: 0
    unit_of_measurement: '°'
    icon: mdi:angle-acute
27

I followed your advice, but in spite of everything I can’t show the sensor in the home assistant; my configuration in binary sensor is the following:

  • platform: mqtt
    state_topic: “shellies / shellydw-F3BB0E / sensor / state”
    name: “door sensor”
    payload_on: ‘open’
    payload_off: ‘close’
    qos: 0
    device_class: door

  • platform: mqtt
    state_topic: “shellies / shellydw-F3BB0E / sensor / vibration”
    name: “Shelly Vibration door sensor”
    payload_on: ‘128’
    payload_off: ‘0’
    qos: 0
    device_class: vibration

28

Please also follow this advice, (point 11 especially): How to help us help you - or How to ask a good question

29

sensore

30

That’s a screenshot. That is not what point 11 asked you to do. For a very good reason. I can’t cut and paste sections of code for correction from a screenshot to help you.

31

I’m sorry, I don’t know how to send it; could you tell me if the configuration of the “binary_sensor” of the shelly door should be entered in the configurator.yaml?

32

You surround your code with lines consisting of three backticks (on the key to the left of the 1 on UK Windows keyboards). Then it looks like this:

- platform: mqtt
  state_topic: "shellies/shellydw-F3BB0E/sensor/state"
  name: "door sensor"
  payload_on: 'open'
  payload_off: 'close'
  qos: 0
  device_class: door

- platform: mqtt
  state_topic: "shellies/shellydw-F3BB0E/sensor/vibration"
  name: "Shelly Vibration door sensor"
  payload_on: '128'
  payload_off: '0'
  qos: 0
  device_class: vibration

This is important, as your first copy-paste had included “smart quotes” (“”) and spaces between the slashes in the MQTT topic names. We could have wasted time chasing those non-existent errors.

So you have these two blocks within configuration.yaml under a binary_sensor: heading? Have you restarted HA since adding?

33

ok grazie,risolto. Dovevo riavviare HA

34

@tom_l
How did you killed one of your 4 sensors? Have you changed your thoughts since your last review or still the same? I am thinking about ordering one just to fill my basket since I am ordering the Shelly EM.

35

Apparently they are even slower to react on newer firmware.

36

For me they are reacting as long as before. about 8 secs. Regardless of this fact, they drained batteries 2 times faster (in 6-7 weeks) with fw1.8.0

I did several ap settings, tested it half a meter from ap - it does change nothing.

But their HT sensors which are powered by single A123 cell report 100% of battery after 6 months. So it cannot be AP problem

Currently I’m trying to manage it with their support

37

So you were only getting 3 months battery life originally?

38

Yes, about 3 with fw 1.6/1.7.
I forgot to say, since the fw1.8 I started to count usage of those sensors. And found that batteries die regardless of usage. For example one sensor registered 5 changes only before died. Other had recorded 50 state changes.
I have DWs with fw1.7 with more than 200 state changes.

Worth to say that Shelly DW connects periodically regardless normal usage and lowest period to set is 24h.

Maybe those are batteries… don’t know. But mentioned HT sensors works on the same single battery.
On FB support pages I saw that I’m not alone who has problems with DWs

39

Are the posts in this thread concerning V1 or V2?

40

V1.

1 Like
41

I am having the same issues with v2 - two sets of batteries since September.

42

considering you have configured it properly (disabled light sensor, fixed ip) it might happen.

Today new firmware is going to be released for DWs. There is a bug causing battery drain listed In changelog. worth a try. If not work I suggest to contact support and return as faulty device