Shelly Binding

  • if this is a binding problem the delay should be around 1 minute (standard polling interval)
  • you could use Shelly Manager to check CoIoT statistics (righzt columns)
  • make sure CoIoT is enabled in the device settings (Web UI), maybe switch it off and on
  • Multicast CoIoT is supported if the network layer is transparent, if you have multiple network segments usually CoIoT doesn’t work without special setup. In this case use CoIoT peer mode and enter the IP of the OH host (no port address!)
  • if the problem persists I need a DEBUG or TRACE log

Hi Markus,

In the Shelly Manager I do see 613 ColoT messages and counting up. I’ve made a trace after changing log:set TRACE. The very first event is where I trigger an event which changes the output of a lamp “zet lamp uit”. At the very same moment, my son changed the state of the Shelly i3 which also changes the state of that lamp: “zet lamp aan” (=last event), but only 21seconds later. I filtered out the lines from other Shelly devices (such as the Vintage lamp).

2021-04-24 14:44:03.795 [INFO ] [org.openhab.core.model.script.Switch] - zet lamp uit
2021-04-24 14:44:24.867 [TRACE] [y.internal.handler.ShellyBaseHandler] - shellyix3-8caab542bab7: Updating status (refreshSettings=false)
2021-04-24 14:44:24.870 [TRACE] [ng.shelly.internal.api.ShellyHttpApi] - shellyix3-8caab542bab7: HTTP GET for http://192.168.1.235/status
2021-04-24 14:44:24.929 [TRACE] [ng.shelly.internal.api.ShellyHttpApi] - shellyix3-8caab542bab7: HTTP Response 200: {“wifi_sta”:{“connected”:true,“ssid”:“Mbr”,“ip”:“192.168.1.235”,“rssi”:-70},“cloud”:{“enabled”:false,“connected”:false},“mqtt”:{“connected”:false},“time”:“14:44”,“unixtime”:1619268265,“serial”:32,“has_update”:true,“mac”:“8CAAB542BAB7”,“cfg_changed_cnt”:2,“actions_stats”:{“skipped”:0},“inputs”:[{“input”:0,“event”:“”,“event_cnt”:0},{“input”:0,“event”:“”,“event_cnt”:0},{“input”:0,“event”:“”,“event_cnt”:0}],“temperature_status”:“Normal”,“update”:{“status”:“pending”,“has_update”:true,“new_version”:“20210413-154502/v1.10.2-gb89901a”,“old_version”:“20210115-104138/v1.9.4@e2732e05”},“ram_total”:51272,“ram_free”:39860,“fs_size”:233681,“fs_free”:151855,“uptime”:143018}
2021-04-24 14:44:24.934 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellyix3-8caab542bab7: Channel device#heartBeat updated with 2021-04-24T14:44:24.000+0200 (type class org.openhab.core.library.types.DateTimeType).
2021-04-24 14:44:24.937 [TRACE] [y.internal.handler.ShellyBaseHandler] - shellyix3-8caab542bab7: Watchdog restarted (expires in 70 sec)
2021-04-24 14:44:24.946 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellyix3-8caab542bab7: Channel device#uptime updated with 143018 s (type class org.openhab.core.library.types.QuantityType).
2021-04-24 14:44:24.951 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellyix3-8caab542bab7: Channel device#wifiSignal updated with 2 (type class org.openhab.core.library.types.DecimalType).
2021-04-24 14:44:24.957 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellyix3-8caab542bab7: Channel status1#input updated with OFF (type class org.openhab.core.library.types.OnOffType).
2021-04-24 14:44:24.961 [TRACE] [y.internal.handler.ShellyBaseHandler] - shellyix3-8caab542bab7: Watchdog restarted (expires in 70 sec)
2021-04-24 14:44:24.988 [INFO ] [org.openhab.core.model.script.Switch] - zet lamp aan

I hope this trace reveals something.

PS: on the device website itself I didn’t find any way to change ColoT setting, I guess it’s only in Openhab (AutoColoT enabled) and in the Thing:

Thanks,
Mario.

I see no CoIoT messages in the trace nor an event “which changes the output”

This is the thing config, not the device UI. open the browser on Shelly’s IP address
also upgrade to firmware 1.10.3

Go to Internet & Security:ADVANCED - DEVELOPER SETTINGS
Should look like

Hi Markus,

The developer setting only showed MQTT option, so I upgraded to 1.10.2 as 1.10.3 was still not available (I saw that this version came 2 days after 1.10.2 release due to bugs, that’s why I decided to stick with the 1.9.4 version in the first place)
I unchecked “Enable ColoT”, rebooted the device and re-enabled it and rebooted again but situation remains the same as before.
Tomorrow I’ll continue and try to add more logs (including debuglog from the device itself, maybe we’ll find something interesting there).

Thanks for the help so far !

I did some more tests and reaction times were between 1 & 60 seconds. I also tried to add the username/password in the Thing (although the setting in the binding should be OK as all devices have the same un/pw). I watched the ColoT messages in Shelly manager and saw it increment by one or two after each test, except for my last test where the counter remained as-is. Here’s again a log from Openhab:

> 2021-04-25 20:24:06.573 [INFO ] [org.openhab.core.model.script.Switch] - zet lamp aan
> 2021-04-25 20:24:52.540 [TRACE] [y.internal.handler.ShellyBaseHandler] - shellyix3-8caab542bab7: Updating status (refreshSettings=true)
> 2021-04-25 20:24:52.543 [TRACE] [ng.shelly.internal.api.ShellyHttpApi] - shellyix3-8caab542bab7: HTTP GET for http://192.168.1.235/status
> 2021-04-25 20:24:52.602 [TRACE] [ng.shelly.internal.api.ShellyHttpApi] - shellyix3-8caab542bab7: HTTP Response 200: {"wifi_sta":{"connected":true,"ssid":"Mbr","ip":"192.168.1.235","rssi":-68},"cloud":{"enabled":false,"connected":false},"mqtt":{"connected":false},"time":"20:24","unixtime":1619375092,"serial":14,"has_update":false,"mac":"8CAAB542BAB7","cfg_changed_cnt":4,"actions_stats":{"skipped":0},"inputs":[{"input":0,"event":"","event_cnt":0},{"input":0,"event":"","event_cnt":0},{"input":0,"event":"","event_cnt":0}],"temperature_status":"Normal","update":{"status":"idle","has_update":false,"new_version":"20210413-154502/v1.10.2-gb89901a","old_version":"20210413-154502/v1.10.2-gb89901a"},"ram_total":50952,"ram_free":38116,"fs_size":233681,"fs_free":150851,"uptime":88352}
> 2021-04-25 20:24:52.605 [TRACE] [ng.shelly.internal.api.ShellyHttpApi] - shellyix3-8caab542bab7: HTTP GET for http://192.168.1.235/settings
> 2021-04-25 20:24:52.665 [TRACE] [ng.shelly.internal.api.ShellyHttpApi] - shellyix3-8caab542bab7: HTTP Response 200: {"device":{"type":"SHIX3-1","mac":"8CAAB542BAB7","hostname":"shellyix3-8CAAB542BAB7","num_inputs":3, "num_outputs":0},"wifi_ap":{"enabled":false,"ssid":"shellyix3-8CAAB542BAB7","key":""},"wifi_sta":{"enabled":true,"ssid":"Mbr","ipv4_method":"dhcp","ip":null,"gw":null,"mask":null,"dns":null},"wifi_sta1":{"enabled":false,"ssid":null,"ipv4_method":"dhcp","ip":null,"gw":null,"mask":null,"dns":null},"ap_roaming":{"enabled":false,"threshold":-70},"mqtt": {"enable":false,"server":"192.168.33.3:1883","user":"","id":"shellyix3-8CAAB542BAB7","reconnect_timeout_max":60.000000,"reconnect_timeout_min":2.000000,"clean_session":true,"keep_alive":60,"max_qos":0,"retain":false,"update_period":30},"coiot": {"enabled":true,"update_period":15,"peer":""},"sntp":{"server":"time.google.com","enabled":true},"login":{"enabled":true,"unprotected":false,"username":"admin"},"pin_code":"","name":"Sheli_01","fw":"20210413-154502/v1.10.2-gb89901a","factory_reset_from_switch":true,"discoverable":true,"build_info":{"build_id":"20210413-154502/v1.10.2-gb89901a","build_timestamp":"2021-04-13T15:45:02Z","build_version":"1.0"},"cloud":{"enabled":false,"connected":false},"timezone":"Europe/Brussels","lat":51.035000,"lng":4.484210,"tzautodetect":true,"tz_utc_offset":7200,"tz_dst":false,"tz_dst_auto":true,"time":"20:24","unixtime":1619375092,"led_status_disable":false,"debug_enable":true,"allow_cross_origin":false,"actions":{"active":false,"names":["btn_on_url","btn_off_url","shortpush_url","longpush_url","double_shortpush_url","triple_shortpush_url","shortpush_longpush_url","longpush_shortpush_url","btn_on_url","btn_off_url","shortpush_url","longpush_url","double_shortpush_url","triple_shortpush_url","shortpush_longpush_url","longpush_shortpush_url","btn_on_url","btn_off_url","shortpush_url","longpush_url","double_shortpush_url","triple_shortpush_url","shortpush_longpush_url","longpush_shortpush_url"]},"hwinfo":{"hw_revision":"prod-2020-04-21", "batch_id":1},"longpush_duration_ms":{"min":800, "max":3000},"multipush_time_between_pushes_ms":{"max":500},"inputs":[{"name":"Ch_Sheli_01_01","btn_type":"toggle","btn_reverse":0},{"name":null,"btn_type":"momentary","btn_reverse":0},{"name":null,"btn_type":"momentary","btn_reverse":0}]}
> 2021-04-25 20:24:52.683 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellyix3-8caab542bab7: Channel device#heartBeat updated with 2021-04-25T20:24:52.000+0200 (type class org.openhab.core.library.types.DateTimeType).
> 2021-04-25 20:24:52.685 [TRACE] [y.internal.handler.ShellyBaseHandler] - shellyix3-8caab542bab7: Watchdog restarted (expires in 70 sec)
> 2021-04-25 20:24:52.688 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellyix3-8caab542bab7: Channel device#uptime updated with 88352 s (type class org.openhab.core.library.types.QuantityType).
> 2021-04-25 20:24:52.692 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellyix3-8caab542bab7: Channel status1#input updated with OFF (type class org.openhab.core.library.types.OnOffType).
> 2021-04-25 20:24:52.695 [TRACE] [y.internal.handler.ShellyBaseHandler] - shellyix3-8caab542bab7: Watchdog restarted (expires in 70 sec)
> 2021-04-25 20:24:52.698 [TRACE] [y.internal.handler.ShellyBaseHandler] - shellyix3-8caab542bab7: 0 more updates requested
> 2021-04-25 20:24:52.720 [INFO ] [org.openhab.core.model.script.Switch] - zet lamp uit

And a log from the device itself during same test (206 is my Raspberry with Openhab, 221 is my Windows PC from which I’m connecting to everywhere):

88277947515 mgos_sys_config.c:232   Loading conf3.json
88278048037 mgos_sys_config.c:174   Saved to conf9.json
88278149301 mgos_http_server.c:180  0x3fff225c HTTP connection from 192.168.1.221:60240
88278628042 mgos_http_server.c:180  0x3fff1c9c HTTP connection from 192.168.1.221:60241
88278639519 json.c:412              RAM: 50952 total, 37512 free
88280363814 ix3.c:533               temperature 71.153529
88283641208 mgos_http_server.c:180  0x3fff1c9c HTTP connection from 192.168.1.221:60242
88283649677 json.c:412              RAM: 50952 total, 37512 free
88285363822 ix3.c:533               temperature 70.809772
88288634988 mgos_http_server.c:180  0x3fff21a4 HTTP connection from 192.168.1.221:60244
88288645263 json.c:412              RAM: 50952 total, 37876 free
88289395239 mgos_http_server.c:180  0x3fff221c HTTP connection from 192.168.1.206:48524
88289404151 json.c:412              RAM: 50952 total, 38116 free
88289435432 mgos_http_server.c:180  0x3fff22d4 HTTP connection from 192.168.1.206:48526
88290363815 ix3.c:533               temperature 70.809772
88292587942 mgos_http_server.c:180  0x3fff1c9c HTTP connection from 192.168.1.206:48542
88292597870 json.c:412              RAM: 50952 total, 37752 free
88293629959 mgos_http_server.c:180  0x3fff1d54 HTTP connection from 192.168.1.221:60248
88293640112 json.c:412              RAM: 50952 total, 37328 free
88295363775 ix3.c:533               temperature 70.639233
88298631931 mgos_http_server.c:180  0x3fff1d54 HTTP connection from 192.168.1.221:60249
88298642294 json.c:412              RAM: 50952 total, 37328 free
88299746832 shelly_sntp.c:433       minute tick at 20:24:00
88300363788 ix3.c:533               temperature 70.809772
88303733756 mgos_http_server.c:180  0x3fff1d54 HTTP connection from 192.168.1.221:60250
88303743915 json.c:412              RAM: 50952 total, 37872 free
88305363733 ix3.c:533               temperature 71.153529
88307298487 shelly_switch.c:161     switches: 00000007
88307301109 ix3.c:314               ==== physical inputs changed: 0x06 -> 0x07 is_initial=0
88307304291 ix3.c:498               ==== input 0 (switch 1) has new logical state: 0
88308629678 mgos_http_server.c:180  0x3fff221c HTTP connection from 192.168.1.221:60251
88308639291 json.c:412              RAM: 50952 total, 37876 free
88310363849 ix3.c:533               temperature 70.981201
88313635717 mgos_http_server.c:180  0x3fff221c HTTP connection from 192.168.1.221:60253
88313644194 json.c:412              RAM: 50952 total, 37876 free
88315363713 ix3.c:533               temperature 70.981201
88318633812 mgos_http_server.c:180  0x3fff221c HTTP connection from 192.168.1.221:60254
88318647177 json.c:412              RAM: 50952 total, 37876 free
88320363848 ix3.c:533               temperature 70.981201
88323632314 mgos_http_server.c:180  0x3fff221c HTTP connection from 192.168.1.221:60255
88323644007 json.c:412              RAM: 50952 total, 37876 free
88325363846 ix3.c:533               temperature 71.153529
88328663465 mgos_http_server.c:180  0x3fff221c HTTP connection from 192.168.1.221:60256
88328673988 json.c:412              RAM: 50952 total, 37876 free
88330363712 ix3.c:533               temperature 70.981201
88333657178 mgos_http_server.c:180  0x3fff221c HTTP connection from 192.168.1.221:60257
88333668190 json.c:412              RAM: 50952 total, 37876 free
88335363717 ix3.c:533               temperature 70.981201
88338639200 mgos_http_server.c:180  0x3fff221c HTTP connection from 192.168.1.221:60258
88338654934 json.c:412              RAM: 50952 total, 37876 free
88340363731 ix3.c:533               temperature 70.981201
88343636074 mgos_http_server.c:180  0x3fff221c HTTP connection from 192.168.1.221:60259
88343646660 json.c:412              RAM: 50952 total, 37876 free
88345363823 ix3.c:533               temperature 70.809772
88348636642 mgos_http_server.c:180  0x3fff221c HTTP connection from 192.168.1.221:60260
88348646244 json.c:412              RAM: 50952 total, 37876 free
88350363834 ix3.c:533               temperature 70.981201
88352664348 mgos_http_server.c:180  0x3fff221c HTTP connection from 192.168.1.206:48692
88352672247 json.c:412              RAM: 50952 total, 38116 free
88352727512 mgos_http_server.c:180  0x3fff1c9c HTTP connection from 192.168.1.206:48694
88353640136 mgos_http_server.c:180  0x3fff1c9c HTTP connection from 192.168.1.221:60267
88353649861 json.c:412              RAM: 50952 total, 37512 free
88355363795 ix3.c:533               temperature 70.981201
88355818171 mgos_http_server.c:180  0x3fff1c9c HTTP connection from 192.168.1.206:48700
88355828931 json.c:412              RAM: 50952 total, 37752 free
88355856077 mgos_http_server.c:180  0x3fff1d54 HTTP connection from 192.168.1.206:48702
88358623145 mgos_http_server.c:180  0x3fff1e0c HTTP connection from 192.168.1.221:60268
88358634770 json.c:412              RAM: 50952 total, 37144 free
88359746896 shelly_sntp.c:433       minute tick at 20:25:00
88360363786 ix3.c:533               temperature 70.981201
88361963325 mgos_http_server.c:180  0x3fff1e0c HTTP connection from 192.168.1.206:48738
88361974143 json.c:412              RAM: 50952 total, 37384 free
88362013359 mgos_http_server.c:180  0x3fff2784 HTTP connection from 192.168.1.206:48740
88363627296 mgos_http_server.c:180  0x3fff221c HTTP connection from 192.168.1.221:60269
88363659049 json.c:412              RAM: 50952 total, 37144 free
88365363801 ix3.c:533               temperature 71.153529
88368635848 mgos_http_server.c:180  0x3fff21a4 HTTP connection from 192.168.1.221:60270
88368645964 json.c:412              RAM: 50952 total, 37508 free
88370363766 ix3.c:533               temperature 70.981201
88371178852 mgos_http_server.c:180  0x3fff21a4 HTTP connection from 192.168.1.206:48760
88371203423 json.c:412              RAM: 50952 total, 37748 free
88371235902 mgos_http_server.c:180  0x3fff221c HTTP connection from 192.168.1.206:48762
88373620933 mgos_http_server.c:180  0x3fff1e84 HTTP connection from 192.168.1.221:60272
88373634756 json.c:412              RAM: 50952 total, 37508 free
88374350157 mgos_http_server.c:180  0x3fff1e84 HTTP connection from 192.168.1.206:48770
88374360569 json.c:412              RAM: 50952 total, 37748 free
88374390208 mgos_http_server.c:180  0x3fff221c HTTP connection from 192.168.1.206:48772
88375363763 ix3.c:533               temperature 70.809772
88378627560 mgos_http_server.c:180  0x3fff22d4 HTTP connection from 192.168.1.221:60273
88378639531 json.c:412              RAM: 50952 total, 37144 free
88380363856 ix3.c:533               temperature 70.809772
88383627321 mgos_http_server.c:180  0x3fff22d4 HTTP connection from 192.168.1.221:60274
88383642135 json.c:412              RAM: 50952 total, 37508 free
88385363831 ix3.c:533               temperature 70.639233
88388634358 mgos_http_server.c:180  0x3fff225c HTTP connection from 192.168.1.221:60275
88388642881 json.c:412              RAM: 50952 total, 37872 free
88390363761 ix3.c:533               temperature 70.809772
88393448879 mgos_http_server.c:180  0x3fff1c9c HTTP connection from 192.168.1.221:60276
88393452381 mgos_http_server.c:180  0x3fff1d54 HTTP connection from 192.168.1.221:60277
88394094474 json.c:412              RAM: 50952 total, 37876 free
88395363779 ix3.c:533               temperature 70.809772
88398524793 mgos_http_server.c:180  0x3fff261c HTTP connection from 192.168.1.206:48818
88398547086 json.c:412              RAM: 50952 total, 37936 free
88398603027 mgos_http_server.c:180  0x3fff1c9c HTTP connection from 192.168.1.206:48826
88399102552 mgos_http_server.c:180  0x3fff1c9c HTTP connection from 192.168.1.221:60278
88399112190 json.c:412              RAM: 50952 total, 37512 free
88400363758 ix3.c:533               temperature 70.809772
88401718366 mgos_http_server.c:180  0x3fff1d54 HTTP connection from 192.168.1.206:48842

I have been searching for ColoT in the openhab log but didn’t find any, but I’ve found “Coiot” several times (typo?). Another remark: I saw 192.1.33.3:1883 being referenced in the Openhab log, no idea where that IP comes from because my network doesn’t have anything in that subnet. I’m just guessing for the unknown here… probably nothing to do with it.

not sure if it helps, but I would switch to unicast. maybe multicast gets filtered out by your firewall?
however, if you have two listeners, then you need to stay with multicast

does the binding doesn’t get the event immediately or does it take xx sec until a rule gets triggered?

It it’s a problem with delayed rule execution on OH2, try to include the following rule in the same file:

rule "keep this thing in memory"
when
    Time cron "0 0/1 * 1/1 * ? *"
then
    logInfo("Cache","cron execution to prevent gargabe collection of compiled rules")
end

This makes sure that the rule file doesn’t get disposed by the garbage collector.

Again I see 0 CoIoT messages. This doesn’t matches the statement that CoIoT counters in Shelly Manager are increasing for this device or you didn’t send enough log information.

openhab 2.5.2 motion detector
Various channels are missing

What can you do there ?

Do you think this is proper information to understand your setup and the problem your are facing?

OK, I’m back with some good news and some bad news. I did a complete reboot of my Raspberry and redid some tests. The CoIoT messages were going up in the Shelly manager and the problem seemed to be solved (almost immediate reaction in OpenHab). But after a couple of times, the delays became longer again. Here’s a new log with CoIoT messages, there seems to be a huge delay in reception of the CoIoT message:

2021-04-26 20:56:23.345 [INFO ] [org.openhab.core.model.script.Switch] - zet lamp aan
2021-04-26 20:56:24.699 [TRACE] [y.internal.handler.ShellyBaseHandler] - shellyix3-8caab542bab7: Updating status (refreshSettings=false)
2021-04-26 20:56:24.705 [TRACE] [ng.shelly.internal.api.ShellyHttpApi] - shellyix3-8caab542bab7: HTTP GET for http://192.168.1.235/status
2021-04-26 20:56:24.841 [TRACE] [ng.shelly.internal.api.ShellyHttpApi] - shellyix3-8caab542bab7: HTTP Response 200: {"wifi_sta":{"connected":true,"ssid":"Mbr","ip":"192.168.1.235","rssi":-66},"cloud":{"enabled":false,"connected":false},"mqtt":{"connected":false},"time":"20:56","unixtime":1619463384,"serial":35,"has_update":false,"mac":"8CAAB542BAB7","cfg_changed_cnt":5,"actions_stats":{"skipped":0},"inputs":[{"input":1,"event":"","event_cnt":0},{"input":0,"event":"","event_cnt":0},{"input":0,"event":"","event_cnt":0}],"temperature_status":"Normal","update":{"status":"idle","has_update":false,"new_version":"20210413-154502/v1.10.2-gb89901a","old_version":"20210413-154502/v1.10.2-gb89901a"},"ram_total":50952,"ram_free":38764,"fs_size":233681,"fs_free":155369,"uptime":176642}
2021-04-26 20:56:24.852 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellyix3-8caab542bab7: Channel device#heartBeat updated with 2021-04-26T20:56:24.000+0200 (type class org.openhab.core.library.types.DateTimeType).
2021-04-26 20:56:24.858 [TRACE] [y.internal.handler.ShellyBaseHandler] - shellyix3-8caab542bab7: Watchdog restarted (expires in 70 sec)
2021-04-26 20:56:24.863 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellyix3-8caab542bab7: Channel device#uptime updated with 176642 s (type class org.openhab.core.library.types.QuantityType).
2021-04-26 20:56:24.872 [TRACE] [y.internal.handler.ShellyBaseHandler] - shellyix3-8caab542bab7: Watchdog restarted (expires in 70 sec)
2021-04-26 20:57:10.188 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyix3-8caab542bab7: CoIoT Message from /192.168.1.235:5683 (MID=2122): {"G":[[0,9103,5],[0,2101,0],[0,2102,""],[0,2103,0],[0,2201,0],[0,2202,""],[0,2203,0],[0,2301,0],[0,2302,""],[0,2303,0]]}
2021-04-26 20:57:10.208 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellyix3-8caab542bab7: Channel device#heartBeat updated with 2021-04-26T20:57:10.000+0200 (type class org.openhab.core.library.types.DateTimeType).
2021-04-26 20:57:10.230 [TRACE] [y.internal.handler.ShellyBaseHandler] - shellyix3-8caab542bab7: Watchdog restarted (expires in 70 sec)
2021-04-26 20:57:10.237 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyix3-8caab542bab7: CoIoT Sensor data {"G":[[0,9103,5],[0,2101,0],[0,2102,""],[0,2103,0],[0,2201,0],[0,2202,""],[0,2203,0],[0,2301,0],[0,2302,""],[0,2303,0]]} (serial=9216)
2021-04-26 20:57:10.243 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyix3-8caab542bab7: 10 CoAP sensor updates received
2021-04-26 20:57:10.253 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyix3-8caab542bab7:  Sensor value[0]: id=9103, Value=5.0 (cfgChanged, Type=EVC, Range=U16, Link=4: device)
2021-04-26 20:57:10.257 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyix3-8caab542bab7:  Sensor value[1]: id=2101, Value=0.0 (input, Type=S, Range=0/1, Link=1: input_0)
2021-04-26 20:57:10.268 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyix3-8caab542bab7:  Sensor value[2]: id=2102, Value=-1.0 (inputEvent, Type=EV, Range=S/L/SS/SSS/SL/LS;, Link=1: input_0)
2021-04-26 20:57:10.271 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyix3-8caab542bab7:  Sensor value[3]: id=2103, Value=0.0 (inputEventCnt, Type=EVC, Range=U16, Link=1: input_0)
2021-04-26 20:57:10.274 [TRACE] [lly.internal.api.ShellyDeviceProfile] - shellyix3-8caab542bab7: Checking for trigger, button-type[0] is toggle
2021-04-26 20:57:10.278 [TRACE] [ly.internal.coap.ShellyCoIoTProtocol] - shellyix3-8caab542bab7: Check button[0] for event trigger (isButtonMode=false, isButton=false, hasBattery=false, serial=9216, count=0, lastEventCount[0]=0
2021-04-26 20:57:10.281 [TRACE] [lly.internal.api.ShellyDeviceProfile] - shellyix3-8caab542bab7: Checking for trigger, button-type[0] is toggle
2021-04-26 20:57:10.286 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyix3-8caab542bab7:  Sensor value[4]: id=2201, Value=0.0 (input, Type=S, Range=0/1, Link=2: input_1)
2021-04-26 20:57:10.290 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyix3-8caab542bab7:  Sensor value[5]: id=2202, Value=-1.0 (inputEvent, Type=EV, Range=S/L/SS/SSS/SL/LS;, Link=2: input_1)
2021-04-26 20:57:10.294 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyix3-8caab542bab7:  Sensor value[6]: id=2203, Value=0.0 (inputEventCnt, Type=EVC, Range=U16, Link=2: input_1)
2021-04-26 20:57:10.297 [TRACE] [lly.internal.api.ShellyDeviceProfile] - shellyix3-8caab542bab7: Checking for trigger, button-type[1] is momentary
2021-04-26 20:57:10.301 [TRACE] [ly.internal.coap.ShellyCoIoTProtocol] - shellyix3-8caab542bab7: Check button[1] for event trigger (isButtonMode=true, isButton=false, hasBattery=false, serial=9216, count=0, lastEventCount[1]=0
2021-04-26 20:57:10.310 [TRACE] [lly.internal.api.ShellyDeviceProfile] - shellyix3-8caab542bab7: Checking for trigger, button-type[1] is momentary
2021-04-26 20:57:10.313 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyix3-8caab542bab7:  Sensor value[7]: id=2301, Value=0.0 (input, Type=S, Range=0/1, Link=3: input_2)
2021-04-26 20:57:10.317 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyix3-8caab542bab7:  Sensor value[8]: id=2302, Value=-1.0 (inputEvent, Type=EV, Range=S/L/SS/SSS/SL/LS;, Link=3: input_2)
2021-04-26 20:57:10.323 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellyix3-8caab542bab7:  Sensor value[9]: id=2303, Value=0.0 (inputEventCnt, Type=EVC, Range=U16, Link=3: input_2)
2021-04-26 20:57:10.326 [TRACE] [lly.internal.api.ShellyDeviceProfile] - shellyix3-8caab542bab7: Checking for trigger, button-type[2] is momentary
2021-04-26 20:57:10.329 [TRACE] [ly.internal.coap.ShellyCoIoTProtocol] - shellyix3-8caab542bab7: Check button[2] for event trigger (isButtonMode=true, isButton=false, hasBattery=false, serial=9216, count=0, lastEventCount[2]=0
2021-04-26 20:57:10.332 [TRACE] [lly.internal.api.ShellyDeviceProfile] - shellyix3-8caab542bab7: Checking for trigger, button-type[2] is momentary
2021-04-26 20:57:10.337 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellyix3-8caab542bab7: Channel status1#input updated with OFF (type class org.openhab.core.library.types.OnOffType).
2021-04-26 20:57:10.342 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyix3-8caab542bab7: 1 channels updated from CoIoT status, serial=9216
2021-04-26 20:57:10.424 [INFO ] [org.openhab.core.model.script.Switch] - zet lamp uit

I continued testing but now switched the CoIoT peer setting to unicast and yes: problem solved (thanks for the suggestion Oliver2 !), but it still limits my future ambition to install a second (standby) Raspberry. So I’m still interested in finding a solution for the multicast setup.

And thanks a lot for the help so far, support of OpenHab is an example for many paying services !

For me this sounds like a network issue. The binding handles Unicast the same way as Multicast.Did you tried to monitor the traffic with Wireshark/tcpdump?

Unfortunately there is no channel {channel = “shelly: shellymotion: XXX226: sensors # motion”} but the {channel = “shelly: shellymotion: XXX226: device # wifiSignal”} works.
I’m just missing channels at shellymotion.
Everything else works fine I have 25 Shelli devices.
Can you add the missing channels by hand? or it depends on the Openhab version 2.5.2

Hi Markus,

I thought that it wouldn’t be that simple. I’m not really an expert in network tracing, so I’ll put it on my “when I have more time” todo list :wink:
Before my tests yesterday I performed a firmware upgrade of my Deco-M9 wifi-mesh system as I already suspected network to be part of the problem.

Thanks anyway and thanks for sharing the Shelly Manager: it’s a great tool and helps a lot in troubleshooting and maintaining the devices.

always welcome :slight_smile:
Do OH and Shellys sit on the same IP subnet? or do you have multiple segments?

Yes, all my iot devices are on same subnet as OpenHab - to avoid network tracing challenges :wink:

Hi Markus

I’m wondering if the shelly binding also will support a feature to adjust some settings of the device. To be precise I would like to change the offset of my ext_temperature sensors on the shelly UNI by openhab. Is this possible by CoIoT?

I already tried to do this by http but there is no such endpoint to set a offset on the device I guess.
The only endpoint which i could figure out by the official api documentation is for: /settings/adc/0
Thanks for your help so far!

This is a config and therefore nothing for the binding. I can‘t of a OH rule doing that

Make that setting in the device‘s Wen UI while running Wireshark, this provides you the endpoint/URL to call and patameters

Hi Markus,
is filtering of events from buttons in detached mode included in 3.1M4?
Just asking as I couldn‘t find it in the release notes and there is no guarantee that release notes are complete.

yes, from my understanding this should be included (already in M3)