Shelly Binding

moody_blue · June 19, 2020, 11:02pm

If I use just the last 6 digits in my manual definition they are discovered again. I use OH 2.5.5 in QNAP TS-253A (intel x64 platform).

hmerk · June 19, 2020, 11:06pm

What firmware are your devices running ? Mine are on 1.60/1.61 and discovery gives just 6 digits.
The example given is working for all of my 17 Shelly devices

moody_blue · June 19, 2020, 11:08pm

Shelly1 @ 1.7.0 and Shelly1PM @ 1.6.1

hmerk · June 19, 2020, 11:09pm

I am out of ideas now. Please file a bug report at github.

moody_blue · June 19, 2020, 11:10pm

I will, thanks

markus7017 · June 20, 2020, 7:10am

are the devices password protected? if yes, the naming is different and you habe to specify the credentials
what’s the device name in the json db when you discover them with paperui? that’s the easiest way to pick the device name

Depending on the device type and firmware release the device name has the last 6 or full 12 digits.

markus7017 · June 20, 2020, 7:12am

fyi: I don’t use habmin anymore for a long time, editing in palerui to set the location is no problem

moody_blue · June 20, 2020, 8:26am

I use the same password for all my Shellys, and that password is defined in the binding, not in the things for each device. Do I need to repeat the password in the things file ?

If the match is done using a device name that can change with firmware version, why not do matching using ip ?

moody_blue · June 20, 2020, 8:56am

Removing userid/password from the binding config does not disable auto discovery.

markus7017 · June 20, 2020, 9:04am

again: check the json db, get the device name there

moody_blue · June 20, 2020, 9:16am

I hope this is what you are requesting (things did not initialize because I did not specify a password):

  "shelly:shellydevice:8caab50569bd": {
    "class": "org.eclipse.smarthome.core.thing.internal.ThingImpl",
    "value": {
      "label": "shelly1pm-8caab50569bd - 192.168.129.81",
      "channels": [],
      "configuration": {
        "properties": {
          "deviceIp": "192.168.129.81"
        }
      },
      "properties": {
        "deviceType": "shelly1pm",
        "deviceMode": "",
        "modelId": "unknown",
        "serviceName": "shelly1pm-8caab50569bd"
      },
      "uid": {
        "segments": [
          "shelly",
          "shellydevice",
          "8caab50569bd"
        ]
      },
      "thingTypeUID": {
        "segments": [
          "shelly",
          "shellydevice"
        ]
      }
    }
  },
  "shelly:shellydevice:8caab505429f": {
    "class": "org.eclipse.smarthome.core.thing.internal.ThingImpl",
    "value": {
      "label": "shelly1-8caab505429f - 192.168.129.80",
      "channels": [],
      "configuration": {
        "properties": {
          "deviceIp": "192.168.129.80"
        }
      },
      "properties": {
        "deviceType": "shelly1",
        "deviceMode": "",
        "modelId": "unknown",
        "serviceName": "shelly1-8caab505429f"
      },
      "uid": {
        "segments": [
          "shelly",
          "shellydevice",
          "8caab505429f"
        ]
      },
      "thingTypeUID": {
        "segments": [
          "shelly",
          "shellydevice"
        ]
      }
    }
  }

What are the device names I should use in my things file ?

Please note that I also have the discovered shellys in disabled state, and this solves my problem.

markus7017 · June 20, 2020, 10:02am

as I said, pick the device name from json db
and use it in .things

I suppose you already had configured the password protection when running the discovery the first time. In that case the binding can’t query all required information from the device, the thing is created with shelly:shellydevice:xxxx rather than the correct device type. Once credentials are set the thing type is adjusted, but I can’t change the device name in the db.

You have 2 options
a) just use the name above in Our .things
b) cleanup you installation

remove all Shelly things from the configuration and Inbox
stop OH
clean out all Shelly related entries from the json db

then

set credentials in the binding config
add devices to .things file
if in between devices show up in the inbox let then sit
when things are online remove discovered things in the inbox (if any) and run the discovery, no new results should pop up

sjheinz · June 21, 2020, 11:25am

Sorry … wrong location - I got a post in an other topic and my reply is here. Don´t now why. Sorry

markus7017 · June 21, 2020, 10:15pm

first version with support for Shelly Gas and Button 1 is online. Not fully done (e.g. setting event urls and localization of new channels are missing), but should already work in general. I’ll implement the missing stuff and then continue with i3. README is not yet updated.

markus7017 · June 22, 2020, 7:50am

This is interesting information from Alterco to maximize battery life of sensors:

How to improve work of battery operated Shelly devices

How Shelly battery-powered devices work and why some users complain about the speed at which devices connect to the home network and respond.

How they work ?

All battery devices are actually turned off all the time. They have a second ultra-low power processor that takes care of measuring the sensors, the battery and the buttons. In the event of a change, this processor wakes up the main CPU to transmit the information over the Wi-Fi network.

How does the device connect to the Wi-Fi network quickly?

There are 2 ways to connect to the Wi-Fi network. The standard way is to scan all channels, finding the strongest signal if there are multiple access points (APs). This usually takes about 6-10 seconds.

To make this happen faster, in less than 3 seconds, the battery device remembers which channel, MAC address of the access point was connected during the initial setup. Then it does not scan all the channels and does not look for the strongest signal but tries to connect to the stored settings. In case it fails to connect, it does a full scan and remembers the new one. But even if the signal of the first who is remembered is weaker, it has an advantage.

Why do some users still have connection speed issues?

If during installation the battery device has memorized another AP because it was in place its signal is stronger and then moved to a new location but this AP is still visible, it will try to connect always to him. And although it takes more time, he will not change it because he will never scan for a new network.

Users who use only one AP, do not have repeaters or mesh network always have report in less than 3 seconds.

How do I set the device to connect quickly each time?

First rule - always set the Wi-Fi network of the device where it’s will be located. In this way it will remember the AP, with the strongest signal at this place and will always connect to it. If you have set it up elsewhere, it is best to reset it when you put it where it will work and set it up Wi-Fi network again.
Add a static IP address. To wake a device from sleep mode, it takes about 300 milliseconds to connect to an already stored AP, it needs another 700 milliseconds with a good signal. If you do not have a static IP address, it is likely to wait for it from the router for 3-5 seconds, otherwise this time is just 500 milliseconds.

If you follow point 1 and point 2 after 1.5 seconds the device will start transmitting the information and will fall asleep again by the 4th second. Which safe alot’s of battery.

If you have completed steps 1 and 2 but the device still connects slowly, check the signal strength at the location of the device. You can see this while it is awakened in setup mode, which lasts 3 minutes. Then reset it and remember the Wi-Fi network again.

What are we working on to improve speed:

From the next version of fw, we will add a command with which the user to make the device find and remember the strongest signal. (we can do that also with Hot-fix when is ready).
If the connection time takes more than 4 seconds, the battery device will scan all channels again to check if there is no other AP with the same name and password but with a stronger signal.
Works on technology that will allow continuous connection of devices in the Wi-Fi network without them consuming energy. Don’t ask us what it is, we won’t tell you, for now!

markus7017 · June 23, 2020, 7:48pm

I’ve uploaded 2.5.7-SNAPSHOT, which includes support for Gas an Button (some localizations are missing), please not that version has been switched to 2.5.7, you need to uninstall 2.5.6 before installing this build.
https://github.com/markus7017/myfiles/blob/master/shelly/org.openhab.binding.shelly-2.5.7-SNAPSHOT.jar?raw=true

Uwe_Samer · June 24, 2020, 2:43pm

Hi there,

first of all, thank you for the great work and the efforts you’ve put into this binding creation!

I see some log file swamping:

2020-06-24 16:37:10.432 [vent.ItemStateChangedEvent] - ShellyB8A9C0_Rollo_Sued2_Roller_RollerControl0Open100Closed changed from 0.0 to 100.0

2020-06-24 16:37:10.487 [vent.ItemStateChangedEvent] - Shellyswitch25B9525A_Roller_RollerControl0Open100Closed changed from 0.0 to 100.0

2020-06-24 16:37:11.285 [vent.ItemStateChangedEvent] - ShellyB8A9C0_Rollo_Sued2_Roller_RollerControl0Open100Closed changed from 100.0 to 0.0

2020-06-24 16:37:11.343 [vent.ItemStateChangedEvent] - RolloOST_3_68742C_Roller_RollerControl0Open100Closed changed from 100.0 to 0.0

2020-06-24 16:37:11.506 [vent.ItemStateChangedEvent] - Shellyswitch25B9525A_Roller_RollerControl0Open100Closed changed from 100.0 to 0.0

2020-06-24 16:37:11.999 [GroupItemStateChangedEvent] - Rollo_West changed from 100 to 0 through ShellyB8B02CROLLO_WEST_6_Roller_RollerControl0Open100Closed

2020-06-24 16:37:12.003 [vent.ItemStateChangedEvent] - ShellyB8B02CROLLO_WEST_6_Roller_RollerControl0Open100Closed changed from 100.0 to 0.0

2020-06-24 16:37:13.202 [vent.ItemStateChangedEvent] - RolloOST_268757F_Roller_RollerControl0Open100Closed changed from 100.0 to 0.0

…

So the roller shutter 2.5 is changing from open to closed (0 to 100) back and forth, all the time!

Does anybody else having kind of the same issue?

I am currently running release build 2.5.6.

Man thanks in advance!
BR
Uwe

Mario_Aerni · June 24, 2020, 3:12pm

Heya, thx again for this nice binding!

I tried the new Snapshot (2.5.7-SNAPSHOT) with the button 1 implementation and got the following “problem”.

When I press a button (e.g. short press) the binding registers this multiple times, over and over again (as shown in the trace). If I then press the button again (e.g. double press), this new “event” will be triggered infinite times.

My button setting is (things - config).

Thing shelly:shellybutton1:a4cf12f450b6                     "Shelly 1 Button - OG Bedroom: Roller"          [deviceIp="192.168.2.172", userId="", password=""]

The log output is:

2020-06-24 17:02:20.426 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6: CoIoT Message from /192.168.2.172:5683 (MID=5385): {"G":[[0,77,100][0,118,0],[0,119,"S"],[0,120,1]]}
2020-06-24 17:02:20.427 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6: Duplicate serial 512 will be processed, because payload is different: {"G":[[0,77,100][0,118,0],[0,119,"S"],[0,120,1]]} vs. {"G":[[0,77,100],[0,118,0],[0,119,"S"],[0,120,1]]}
2020-06-24 17:02:20.429 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6: CoIoT Sensor data {"G":[[0,77,100],[0,118,0],[0,119,"S"],[0,120,1]]}
2020-06-24 17:02:20.431 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6: 4 CoAP sensor updates received
2020-06-24 17:02:20.432 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6:  Sensor value[0]: id=77, Value=100.0 (Battery, Type=B, Range=0/100, Link=1: sensors)
2020-06-24 17:02:20.434 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6:  Sensor value[1]: id=118, Value=0.0 (Input, Type=S, Range=0, Link=1: sensors)
2020-06-24 17:02:20.436 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6:  Sensor value[2]: id=119, Value=-1.0 (Input event, Type=S, Range=S/SS/SSS/L, Link=1: sensors)
2020-06-24 17:02:20.439 [vent.ChannelTriggeredEvent] - shelly:shellybutton1:a4cf12f450b6:sensors#button triggered SHORT_PRESSED
2020-06-24 17:02:20.438 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6:  Sensor value[3]: id=120, Value=1.0 (Input event counter, Type=S, Range=U16, Link=1: sensors)
2020-06-24 17:02:20.540 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyswitch25-68da9c: Coap update for button (type toggle)
2020-06-24 17:02:20.543 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyswitch25-68da9c: Coap update for button (type toggle)
2020-06-24 17:02:21.500 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shelly1pm-76af9e: Coap update for button (type edge)
2020-06-24 17:02:26.517 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shelly1pm-76bc68: Coap update for button (type edge)
2020-06-24 17:02:30.139 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shelly1pm-76b2f4: Coap update for button (type edge)
2020-06-24 17:02:32.312 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shelly1pm-76ba66: Coap update for button (type edge)
2020-06-24 17:02:32.359 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shelly1pm-76b397: Coap update for button (type edge)
2020-06-24 17:02:32.969 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shelly25-roller-687d55: Coap update for button (type toggle)
2020-06-24 17:02:32.973 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shelly25-roller-687d55: Coap update for button (type toggle)
2020-06-24 17:02:33.315 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shelly1pm-76ec70: Coap update for button (type edge)
2020-06-24 17:02:35.483 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6: CoIoT Message from /192.168.2.172:5683 (MID=5386): {"G":[[0,77,100][0,118,0],[0,119,"S"],[0,120,1]]}
2020-06-24 17:02:35.485 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6: Duplicate serial 512 will be processed, because payload is different: {"G":[[0,77,100][0,118,0],[0,119,"S"],[0,120,1]]} vs. {"G":[[0,77,100],[0,118,0],[0,119,"S"],[0,120,1]]}
2020-06-24 17:02:35.489 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6: CoIoT Sensor data {"G":[[0,77,100],[0,118,0],[0,119,"S"],[0,120,1]]}
2020-06-24 17:02:35.492 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6: 4 CoAP sensor updates received
2020-06-24 17:02:35.494 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6:  Sensor value[0]: id=77, Value=100.0 (Battery, Type=B, Range=0/100, Link=1: sensors)
2020-06-24 17:02:35.501 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6:  Sensor value[1]: id=118, Value=0.0 (Input, Type=S, Range=0, Link=1: sensors)
2020-06-24 17:02:35.504 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6:  Sensor value[2]: id=119, Value=-1.0 (Input event, Type=S, Range=S/SS/SSS/L, Link=1: sensors)
2020-06-24 17:02:35.510 [vent.ChannelTriggeredEvent] - shelly:shellybutton1:a4cf12f450b6:sensors#button triggered SHORT_PRESSED
2020-06-24 17:03:39.135 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6: CoIoT Message from /192.168.2.172:5683 (MID=12489): {"G":[[0,77,100][0,118,0],[0,119,"SS"],[0,120,1]]}
2020-06-24 17:03:39.142 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6: CoIoT Sensor data {"G":[[0,77,100],[0,118,0],[0,119,"SS"],[0,120,1]]}
2020-06-24 17:03:39.146 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6: 4 CoAP sensor updates received
2020-06-24 17:03:39.149 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6:  Sensor value[0]: id=77, Value=100.0 (Battery, Type=B, Range=0/100, Link=1: sensors)
2020-06-24 17:03:39.153 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6:  Sensor value[1]: id=118, Value=0.0 (Input, Type=S, Range=0, Link=1: sensors)
2020-06-24 17:03:39.155 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6:  Sensor value[2]: id=119, Value=-1.0 (Input event, Type=S, Range=S/SS/SSS/L, Link=1: sensors)
2020-06-24 17:03:39.160 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6:  Sensor value[3]: id=120, Value=1.0 (Input event counter, Type=S, Range=U16, Link=1: sensors)
2020-06-24 17:03:39.161 [vent.ChannelTriggeredEvent] - shelly:shellybutton1:a4cf12f450b6:sensors#button triggered DOUBLE_PRESSED
2020-06-24 17:03:40.821 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shelly25-roller-b8a5b4: Coap update for button (type toggle)
2020-06-24 17:03:40.825 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shelly25-roller-b8a5b4: Coap update for button (type toggle)
2020-06-24 17:03:47.345 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shelly1pm-76ba66: Coap update for button (type edge)
2020-06-24 17:03:47.388 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shelly1pm-76b397: Coap update for button (type edge)
2020-06-24 17:03:47.789 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shelly1pm-76bc96: Coap update for button (type detached)
2020-06-24 17:03:48.338 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shelly1pm-76ec70: Coap update for button (type edge)
2020-06-24 17:03:50.608 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyswitch25-69219c: Coap update for button (type toggle)
2020-06-24 17:03:50.612 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyswitch25-69219c: Coap update for button (type toggle)
2020-06-24 17:03:51.555 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shelly1pm-76af9e: Coap update for button (type edge)
2020-06-24 17:03:54.135 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6: CoIoT Message from /192.168.2.172:5683 (MID=12490): {"G":[[0,77,100][0,118,0],[0,119,"SS"],[0,120,1]]}
2020-06-24 17:03:54.141 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6: Duplicate serial 256 will be processed, because payload is different: {"G":[[0,77,100][0,118,0],[0,119,"SS"],[0,120,1]]} vs. {"G":[[0,77,100],[0,118,0],[0,119,"SS"],[0,120,1]]}
2020-06-24 17:03:54.144 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6: CoIoT Sensor data {"G":[[0,77,100],[0,118,0],[0,119,"SS"],[0,120,1]]}
2020-06-24 17:03:54.147 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6: 4 CoAP sensor updates received
2020-06-24 17:03:54.152 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6:  Sensor value[0]: id=77, Value=100.0 (Battery, Type=B, Range=0/100, Link=1: sensors)
2020-06-24 17:03:54.156 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6:  Sensor value[1]: id=118, Value=0.0 (Input, Type=S, Range=0, Link=1: sensors)
2020-06-24 17:03:54.160 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6:  Sensor value[2]: id=119, Value=-1.0 (Input event, Type=S, Range=S/SS/SSS/L, Link=1: sensors)
2020-06-24 17:03:54.165 [vent.ChannelTriggeredEvent] - shelly:shellybutton1:a4cf12f450b6:sensors#button triggered DOUBLE_PRESSED
2020-06-24 17:03:54.166 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6:  Sensor value[3]: id=120, Value=1.0 (Input event counter, Type=S, Range=U16, Link=1: sensors)
2020-06-24 17:04:02.354 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shelly1pm-76ba66: Coap update for button (type edge)
2020-06-24 17:04:02.788 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shelly1pm-76bc96: Coap update for button (type detached)
2020-06-24 17:04:03.348 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shelly1pm-76ec70: Coap update for button (type edge)
2020-06-24 17:04:05.687 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyswitch25-69219c: Coap update for button (type toggle)
2020-06-24 17:04:05.692 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyswitch25-69219c: Coap update for button (type toggle)
2020-06-24 17:04:06.554 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shelly1pm-76af9e: Coap update for button (type edge)
2020-06-24 17:04:07.798 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shelly1pm-766d4e: Coap update for button (type detached)
2020-06-24 17:04:09.147 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6: CoIoT Message from /192.168.2.172:5683 (MID=12491): {"G":[[0,77,100][0,118,0],[0,119,"SS"],[0,120,1]]}
2020-06-24 17:04:09.150 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6: Duplicate serial 256 will be processed, because payload is different: {"G":[[0,77,100][0,118,0],[0,119,"SS"],[0,120,1]]} vs. {"G":[[0,77,100],[0,118,0],[0,119,"SS"],[0,120,1]]}
2020-06-24 17:04:09.153 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6: CoIoT Sensor data {"G":[[0,77,100],[0,118,0],[0,119,"SS"],[0,120,1]]}
2020-06-24 17:04:09.157 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6: 4 CoAP sensor updates received
2020-06-24 17:04:09.159 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6:  Sensor value[0]: id=77, Value=100.0 (Battery, Type=B, Range=0/100, Link=1: sensors)
2020-06-24 17:04:09.162 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6:  Sensor value[1]: id=118, Value=0.0 (Input, Type=S, Range=0, Link=1: sensors)
2020-06-24 17:04:09.165 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6:  Sensor value[2]: id=119, Value=-1.0 (Input event, Type=S, Range=S/SS/SSS/L, Link=1: sensors)
2020-06-24 17:04:09.169 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellybutton1-a4cf12f450b6:  Sensor value[3]: id=120, Value=1.0 (Input event counter, Type=S, Range=U16, Link=1: sensors)
2020-06-24 17:04:09.170 [vent.ChannelTriggeredEvent] - shelly:shellybutton1:a4cf12f450b6:sensors#button triggered DOUBLE_PRESSED

Do I have to change something in the config, or is here something wrong with the binding, maybe even the button itself (no it doesn’t flash after the first event triggers).

markus7017 · June 24, 2020, 10:33pm

I uploaded the current build, which has a revised handling of input channels and adds Shelly ix3
The button handling is still work in progress. Problem I need to think about

The device sends a CoAP update indicating that the button has pressed, type and count
but doesn’t send a message when the button is released
which means the input stays ON
Not sure how to handle input and button triggeres in thise

The release is work-in-progress, don’t expect anything to be final.

You need to rediscover things after installing the jar

markus7017 · June 25, 2020, 10:14pm

New build adds support for Shelly Dimmer 2, Vintage A60/ST64/G125 verified
still work-in-progress, now need to test through the different functions etc.