Shelly Binding

Please provide a DEBUG log, maybe there is an exception

ok, set log to debug, “deactivated” [thing]:meter1#currentWatts, waited some time and reactivated the meter1 channel.
as you can see, between link removed and link added there are no updates for any times:

2020-12-27 09:59:42.105 [vent.ItemStateChangedEvent] - Shelly_EM3_Watts3 changed from 377.6 to 385.1
2020-12-27 09:59:42.142 [vent.ItemStateChangedEvent] - Shelly_EM3_accWatts changed from 1360.9 W to 1374.1 W
2020-12-27 09:59:44.164 [temChannelLinkRemovedEvent] - Link 'Shelly_EM3_Watts3 => shelly:shellyem3:84cca8ad12a6:meter3#currentWatts' has been removed.
2020-12-27 09:59:55.022 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Message from /192.168.178.212:5683 (MID=16245): {"G":[[0,9103,0],[0,1101,0],[0,4105,564.14],[0,4106,162389.4],[0,4107,108987.4],[0,4108,234.30],[0,4109,3.97],[0,4110,0.61],[0,4205,428.21],[0,4206,79406.1],[0,4207,97461.9],[0,4208,239.46],[0,4209,3.35],[0,4210,0.53],[0,4305,382.30],[0,4306,38384.6],[0,4307,637.3],[0,4308,231.48],[0,4309,3.54],[0,4310,0.47],[0,6102,0]]}
2020-12-27 09:59:55.025 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Sensor data {"G":[[0,9103,0],[0,1101,0],[0,4105,564.14],[0,4106,162389.4],[0,4107,108987.4],[0,4108,234.30],[0,4109,3.97],[0,4110,0.61],[0,4205,428.21],[0,4206,79406.1],[0,4207,97461.9],[0,4208,239.46],[0,4209,3.35],[0,4210,0.53],[0,4305,382.30],[0,4306,38384.6],[0,4307,637.3],[0,4308,231.48],[0,4309,3.54],[0,4310,0.47],[0,6102,0]]} (serial=33306)
2020-12-27 09:59:55.027 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: 21 CoAP sensor updates received
2020-12-27 10:00:10.024 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Message from /192.168.178.212:5683 (MID=16246): {"G":[[0,9103,0],[0,1101,0],[0,4105,559.62],[0,4106,162398.9],[0,4107,108987.4],[0,4108,233.75],[0,4109,3.94],[0,4110,0.61],[0,4205,423.48],[0,4206,79413.2],[0,4207,97461.9],[0,4208,239.55],[0,4209,3.33],[0,4210,0.53],[0,4305,383.07],[0,4306,38390.9],[0,4307,637.3],[0,4308,231.93],[0,4309,3.52],[0,4310,0.47],[0,6102,0]]}
2020-12-27 10:00:10.027 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Sensor data {"G":[[0,9103,0],[0,1101,0],[0,4105,559.62],[0,4106,162398.9],[0,4107,108987.4],[0,4108,233.75],[0,4109,3.94],[0,4110,0.61],[0,4205,423.48],[0,4206,79413.2],[0,4207,97461.9],[0,4208,239.55],[0,4209,3.33],[0,4210,0.53],[0,4305,383.07],[0,4306,38390.9],[0,4307,637.3],[0,4308,231.93],[0,4309,3.52],[0,4310,0.47],[0,6102,0]]} (serial=33306)
2020-12-27 10:00:10.030 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: 21 CoAP sensor updates received
2020-12-27 10:00:25.031 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Message from /192.168.178.212:5683 (MID=16247): {"G":[[0,9103,0],[0,1101,0],[0,4105,558.15],[0,4106,162398.9],[0,4107,108987.4],[0,4108,234.56],[0,4109,3.95],[0,4110,0.60],[0,4205,430.70],[0,4206,79413.2],[0,4207,97461.9],[0,4208,238.88],[0,4209,3.37],[0,4210,0.54],[0,4305,381.52],[0,4306,38390.9],[0,4307,637.3],[0,4308,231.07],[0,4309,3.52],[0,4310,0.47],[0,6102,0]]}
2020-12-27 10:00:25.033 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Sensor data {"G":[[0,9103,0],[0,1101,0],[0,4105,558.15],[0,4106,162398.9],[0,4107,108987.4],[0,4108,234.56],[0,4109,3.95],[0,4110,0.60],[0,4205,430.70],[0,4206,79413.2],[0,4207,97461.9],[0,4208,238.88],[0,4209,3.37],[0,4210,0.54],[0,4305,381.52],[0,4306,38390.9],[0,4307,637.3],[0,4308,231.07],[0,4309,3.52],[0,4310,0.47],[0,6102,0]]} (serial=33306)
2020-12-27 10:00:25.035 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: 21 CoAP sensor updates received
2020-12-27 10:00:34.038 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Message from /192.168.178.212:5683 (MID=16248): {"G":[[0,9103,0],[0,1101,0],[0,4105,564.17],[0,4106,162398.9],[0,4107,108987.4],[0,4108,233.60],[0,4109,3.93],[0,4110,0.61],[0,4205,411.74],[0,4206,79413.2],[0,4207,97461.9],[0,4208,238.64],[0,4209,3.33],[0,4210,0.52],[0,4305,389.95],[0,4306,38390.9],[0,4307,637.3],[0,4308,233.48],[0,4309,3.57],[0,4310,0.47],[0,6102,0]]}
2020-12-27 10:00:34.040 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Sensor data {"G":[[0,9103,0],[0,1101,0],[0,4105,564.17],[0,4106,162398.9],[0,4107,108987.4],[0,4108,233.60],[0,4109,3.93],[0,4110,0.61],[0,4205,411.74],[0,4206,79413.2],[0,4207,97461.9],[0,4208,238.64],[0,4209,3.33],[0,4210,0.52],[0,4305,389.95],[0,4306,38390.9],[0,4307,637.3],[0,4308,233.48],[0,4309,3.57],[0,4310,0.47],[0,6102,0]]} (serial=33562)
2020-12-27 10:00:34.042 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: 21 CoAP sensor updates received
2020-12-27 10:00:47.044 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Message from /192.168.178.212:5683 (MID=16249): {"G":[[0,9103,0],[0,1101,0],[0,4105,559.92],[0,4106,162398.9],[0,4107,108987.4],[0,4108,232.97],[0,4109,3.93],[0,4110,0.61],[0,4205,415.92],[0,4206,79413.2],[0,4207,97461.9],[0,4208,239.59],[0,4209,3.35],[0,4210,0.52],[0,4305,395.52],[0,4306,38390.9],[0,4307,637.3],[0,4308,233.63],[0,4309,3.57],[0,4310,0.47],[0,6102,0]]}
2020-12-27 10:00:47.047 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Sensor data {"G":[[0,9103,0],[0,1101,0],[0,4105,559.92],[0,4106,162398.9],[0,4107,108987.4],[0,4108,232.97],[0,4109,3.93],[0,4110,0.61],[0,4205,415.92],[0,4206,79413.2],[0,4207,97461.9],[0,4208,239.59],[0,4209,3.35],[0,4210,0.52],[0,4305,395.52],[0,4306,38390.9],[0,4307,637.3],[0,4308,233.63],[0,4309,3.57],[0,4310,0.47],[0,6102,0]]} (serial=33818)
2020-12-27 10:00:47.049 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: 21 CoAP sensor updates received
2020-12-27 10:01:02.051 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Message from /192.168.178.212:5683 (MID=16250): {"G":[[0,9103,0],[0,1101,0],[0,4105,556.57],[0,4106,162408.2],[0,4107,108987.4],[0,4108,234.14],[0,4109,3.93],[0,4110,0.60],[0,4205,423.70],[0,4206,79420.2],[0,4207,97461.9],[0,4208,239.12],[0,4209,3.38],[0,4210,0.52],[0,4305,391.35],[0,4306,38397.3],[0,4307,637.3],[0,4308,232.73],[0,4309,3.54],[0,4310,0.47],[0,6102,0]]}
2020-12-27 10:01:02.054 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Sensor data {"G":[[0,9103,0],[0,1101,0],[0,4105,556.57],[0,4106,162408.2],[0,4107,108987.4],[0,4108,234.14],[0,4109,3.93],[0,4110,0.60],[0,4205,423.70],[0,4206,79420.2],[0,4207,97461.9],[0,4208,239.12],[0,4209,3.38],[0,4210,0.52],[0,4305,391.35],[0,4306,38397.3],[0,4307,637.3],[0,4308,232.73],[0,4309,3.54],[0,4310,0.47],[0,6102,0]]} (serial=33818)
2020-12-27 10:01:02.057 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: 21 CoAP sensor updates received
2020-12-27 10:01:17.056 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Message from /192.168.178.212:5683 (MID=16251): {"G":[[0,9103,0],[0,1101,0],[0,4105,561.40],[0,4106,162408.2],[0,4107,108987.4],[0,4108,233.84],[0,4109,3.93],[0,4110,0.61],[0,4205,417.29],[0,4206,79420.2],[0,4207,97461.9],[0,4208,239.35],[0,4209,3.37],[0,4210,0.52],[0,4305,395.24],[0,4306,38397.3],[0,4307,637.3],[0,4308,233.04],[0,4309,3.59],[0,4310,0.47],[0,6102,0]]}
2020-12-27 10:01:17.058 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Sensor data {"G":[[0,9103,0],[0,1101,0],[0,4105,561.40],[0,4106,162408.2],[0,4107,108987.4],[0,4108,233.84],[0,4109,3.93],[0,4110,0.61],[0,4205,417.29],[0,4206,79420.2],[0,4207,97461.9],[0,4208,239.35],[0,4209,3.37],[0,4210,0.52],[0,4305,395.24],[0,4306,38397.3],[0,4307,637.3],[0,4308,233.04],[0,4309,3.59],[0,4310,0.47],[0,6102,0]]} (serial=33818)
2020-12-27 10:01:17.061 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: 21 CoAP sensor updates received
2020-12-27 10:01:32.066 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Message from /192.168.178.212:5683 (MID=16252): {"G":[[0,9103,0],[0,1101,0],[0,4105,560.68],[0,4106,162408.2],[0,4107,108987.4],[0,4108,233.88],[0,4109,3.93],[0,4110,0.61],[0,4205,416.28],[0,4206,79420.2],[0,4207,97461.9],[0,4208,239.20],[0,4209,3.34],[0,4210,0.52],[0,4305,390.91],[0,4306,38397.3],[0,4307,637.3],[0,4308,233.00],[0,4309,3.56],[0,4310,0.47],[0,6102,0]]}
2020-12-27 10:01:32.069 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Sensor data {"G":[[0,9103,0],[0,1101,0],[0,4105,560.68],[0,4106,162408.2],[0,4107,108987.4],[0,4108,233.88],[0,4109,3.93],[0,4110,0.61],[0,4205,416.28],[0,4206,79420.2],[0,4207,97461.9],[0,4208,239.20],[0,4209,3.34],[0,4210,0.52],[0,4305,390.91],[0,4306,38397.3],[0,4307,637.3],[0,4308,233.00],[0,4309,3.56],[0,4310,0.47],[0,6102,0]]} (serial=33818)
2020-12-27 10:01:32.072 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: 21 CoAP sensor updates received
2020-12-27 10:01:47.074 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Message from /192.168.178.212:5683 (MID=16253): {"G":[[0,9103,0],[0,1101,0],[0,4105,568.23],[0,4106,162408.2],[0,4107,108987.4],[0,4108,233.54],[0,4109,3.95],[0,4110,0.62],[0,4205,409.79],[0,4206,79420.2],[0,4207,97461.9],[0,4208,239.44],[0,4209,3.35],[0,4210,0.51],[0,4305,397.63],[0,4306,38397.3],[0,4307,637.3],[0,4308,233.63],[0,4309,3.63],[0,4310,0.47],[0,6102,0]]}
2020-12-27 10:01:47.077 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Sensor data {"G":[[0,9103,0],[0,1101,0],[0,4105,568.23],[0,4106,162408.2],[0,4107,108987.4],[0,4108,233.54],[0,4109,3.95],[0,4110,0.62],[0,4205,409.79],[0,4206,79420.2],[0,4207,97461.9],[0,4208,239.44],[0,4209,3.35],[0,4210,0.51],[0,4305,397.63],[0,4306,38397.3],[0,4307,637.3],[0,4308,233.63],[0,4309,3.63],[0,4310,0.47],[0,6102,0]]} (serial=33818)
2020-12-27 10:01:47.079 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: 21 CoAP sensor updates received
2020-12-27 10:01:58.230 [vent.ItemStateChangedEvent] - Shelly_EM3_Watts3 changed from NULL to 385.1
2020-12-27 10:01:58.249 [.ItemChannelLinkAddedEvent] - Link 'Shelly_EM3_Watts3-shelly:shellyem3:84cca8ad12a6:meter3#currentWatts' has been added.
2020-12-27 10:02:02.082 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Message from /192.168.178.212:5683 (MID=16254): {"G":[[0,9103,0],[0,1101,0],[0,4105,574.84],[0,4106,162417.6],[0,4107,108987.4],[0,4108,234.89],[0,4109,3.97],[0,4110,0.62],[0,4205,408.69],[0,4206,79427.2],[0,4207,97461.9],[0,4208,239.50],[0,4209,3.31],[0,4210,0.52],[0,4305,386.64],[0,4306,38403.8],[0,4307,637.3],[0,4308,233.50],[0,4309,3.62],[0,4310,0.46],[0,6102,0]]}
2020-12-27 10:02:02.085 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Sensor data {"G":[[0,9103,0],[0,1101,0],[0,4105,574.84],[0,4106,162417.6],[0,4107,108987.4],[0,4108,234.89],[0,4109,3.97],[0,4110,0.62],[0,4205,408.69],[0,4206,79427.2],[0,4207,97461.9],[0,4208,239.50],[0,4209,3.31],[0,4210,0.52],[0,4305,386.64],[0,4306,38403.8],[0,4307,637.3],[0,4308,233.50],[0,4309,3.62],[0,4310,0.46],[0,6102,0]]} (serial=33818)
2020-12-27 10:02:02.089 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: 21 CoAP sensor updates received
2020-12-27 10:02:02.108 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellyem3-84cca8ad12a6: Channel meter3#currentWatts updated with 386.6 W (type class org.eclipse.smarthome.core.library.types.QuantityType).
2020-12-27 10:02:02.118 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: 1 channels updated from CoIoT status, serial=33818
2020-12-27 10:02:02.114 [vent.ItemStateChangedEvent] - Shelly_EM3_Watts3 changed from 385.1 to 386.6
2020-12-27 10:02:03.105 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellyem3-84cca8ad12a6: Channel meter3#currentWatts updated with 386.3 W (type class org.eclipse.smarthome.core.library.types.QuantityType).
2020-12-27 10:02:03.120 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellyem3-84cca8ad12a6: Channel device#accumulatedWatts updated with 1368.8 W (type class org.eclipse.smarthome.core.library.types.QuantityType).
2020-12-27 10:02:03.141 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellyem3-84cca8ad12a6: Channel device#accumulatedWTotal updated with 280.249 kWh (type class org.eclipse.smarthome.core.library.types.QuantityType).
2020-12-27 10:02:03.111 [vent.ItemStateChangedEvent] - Shelly_EM3_Watts3 changed from 386.6 to 386.3
2020-12-27 10:02:03.151 [vent.ItemStateChangedEvent] - Shelly_EM3_accWatts changed from 1374.1 W to 1368.8 W
2020-12-27 10:02:03.155 [vent.ItemStateChangedEvent] - Shelly_EM3_accTotal changed from 280.180 to 280.249
2020-12-27 10:02:03.568 [vent.ItemStateChangedEvent] - Shelly_EM3_consumption changed from 0.023 to 0.069
2020-12-27 10:02:12.390 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellyem3-84cca8ad12a6: Channel meter3#currentWatts updated with 390.6 W (type class org.eclipse.smarthome.core.library.types.QuantityType).
2020-12-27 10:02:12.400 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellyem3-84cca8ad12a6: Channel device#accumulatedWatts updated with 1371.0 W (type class org.eclipse.smarthome.core.library.types.QuantityType).
2020-12-27 10:02:12.399 [vent.ItemStateChangedEvent] - Shelly_EM3_Watts3 changed from 386.3 to 390.6
2020-12-27 10:02:12.424 [vent.ItemStateChangedEvent] - Shelly_EM3_accWatts changed from 1368.8 W to 1371.0 W
2020-12-27 10:02:17.085 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Message from /192.168.178.212:5683 (MID=16255): {"G":[[0,9103,0],[0,1101,0],[0,4105,563.13],[0,4106,162417.6],[0,4107,108987.4],[0,4108,235.33],[0,4109,3.94],[0,4110,0.61],[0,4205,416.74],[0,4206,79427.2],[0,4207,97461.9],[0,4208,238.97],[0,4209,3.35],[0,4210,0.52],[0,4305,385.48],[0,4306,38403.8],[0,4307,637.3],[0,4308,232.73],[0,4309,3.57],[0,4310,0.46],[0,6102,0]]}
2020-12-27 10:02:17.089 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: CoIoT Sensor data {"G":[[0,9103,0],[0,1101,0],[0,4105,563.13],[0,4106,162417.6],[0,4107,108987.4],[0,4108,235.33],[0,4109,3.94],[0,4110,0.61],[0,4205,416.74],[0,4206,79427.2],[0,4207,97461.9],[0,4208,238.97],[0,4209,3.35],[0,4210,0.52],[0,4305,385.48],[0,4306,38403.8],[0,4307,637.3],[0,4308,232.73],[0,4309,3.57],[0,4310,0.46],[0,6102,0]]} (serial=33818)
2020-12-27 10:02:17.091 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: 21 CoAP sensor updates received
2020-12-27 10:02:17.104 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellyem3-84cca8ad12a6: Channel meter3#currentWatts updated with 385.5 W (type class org.eclipse.smarthome.core.library.types.QuantityType).
2020-12-27 10:02:17.110 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellyem3-84cca8ad12a6: 1 channels updated from CoIoT status, serial=33818
2020-12-27 10:02:17.111 [vent.ItemStateChangedEvent] - Shelly_EM3_Watts3 changed from 390.6 to 385.5
2020-12-27 10:02:18.643 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellyem3-84cca8ad12a6: Channel meter3#currentWatts updated with 388.2 W (type class org.eclipse.smarthome.core.library.types.QuantityType).
2020-12-27 10:02:18.655 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellyem3-84cca8ad12a6: Channel device#accumulatedWatts updated with 1370.0 W (type class org.eclipse.smarthome.core.library.types.QuantityType).
2020-12-27 10:02:18.649 [vent.ItemStateChangedEvent] - Shelly_EM3_Watts3 changed from 385.5 to 388.2
2020-12-27 10:02:18.676 [vent.ItemStateChangedEvent] - Shelly_EM3_accWatts changed from 1371.0 W to 1370.0 W

ok, the value was computed, but the channel only updated when currentWatts was updated too
please check, should work now.

Keep in mind the accumulated* channels are computed once a minute on every status check (usually once a minute), whereas the currentWatt channel gets updated by CoAP.

@markus7017 will the “Local interface IP to listen for CoIoT messages” setting be implemented in a future official release of the binding (for OH 2.5)?

This is already in, check the binding settings (Host Interface IP); and yes, this included in the PR

i should probably update something ?
i have the binding from paperui (2.5.11)…

No, you need to move to the DEV build

Latest DEV build: 2.5.12 - 3.1.0 - README - Installation - Bugs/Features - Firmware Index - Firmware Archive - API Doc
Note: The binding version included in the final OH 3.0 distro is significantly older than the DEV build. I can’t make it in-time. Make sure you deleted older versions of the binding when installing the 2.5.12-SNAPSHOT or 3.1.0-SNAPSHOT if you are already on OH 3.

uninstalled binding from paperui.
followed instructions (stopped oh, copied files, restarted, copied binding.jar) but nothing pops up with list -s
removed the files from addons folder and dropped californium-core-2.0.0.jar again (while openhab running):

2020-12-27 19:51:30.230 [WARN ] [org.apache.felix.fileinstall        ] - Error while starting bundle: file:/usr/share/openhab2/addons/californium-core-2.0.0.jar
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.californium.core [289]
  Unresolved requirement: Import-Package: org.eclipse.californium.elements; version="[2.0.0,3.0.0)"
        at org.eclipse.osgi.container.Module.start(Module.java:444) ~[org.eclipse.osgi-3.12.100.jar:?]
        at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) ~[org.eclipse.osgi-3.12.100.jar:?]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [bundleFile:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [bundleFile:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:520) [bundleFile:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [bundleFile:3.6.4]
        at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [bundleFile:3.6.4]

all this happenend on openhab 2.5.11.

obviously you forgot org.eclipse.californium.elements.jar
follow the instructions

here ?
i found only info for these two jars:

  • copy californium-core-2.0.0.jar to OH’s addons folder
  • copy element-connector-2.0.0.jar to OH’s addons folder

what in *** am i missing? :face_with_raised_eyebrow:

copy both Californium jars to the addons folder, wait a bit and then the binding jar, check the logfile for errors

oh boi, i’m sorry… i was looking for the bindings via list -s | grep Californium and got no results.
with list -s i got 'em:

290 │ Active │  80 │ 2.0.0                   │ org.eclipse.californium.element-connector
291 │ Active │  80 │ 2.0.0                   │ org.eclipse.californium.core

dev binding is now running, too! and [thing]:device#accumulatedWatts gets updates as expected! thank you very much! (and sorry again for the “trouble”)!

np, that‘s what the community is made for

1 Like

hey @markus7017

just installed OH3 from scratch. Every shelly is configured to ask for http credentials which have been configured in the Binding. However, on auto discovery I see log entries like:

2020-12-30 08:09:42.079 [INFO ] [discovery.ShellyDiscoveryParticipant] - shelly1-93a99a: Das Gerät mit der IP-Adresse 192.168.2.64 ist zugriffsgeschützt und keine Zugangsdaten konfiguriert.

and once I add the Thing I got a hint about missing configuration. What am I missing? see screenshot

This is what I see if I open the Binding config:

best regards

Stefan

BEFORE running the discovery go to the binding settings and set the credentials then start the discovery. If you have already things in the Inbox delete them. Make sire the devices are not of type shellyprotected or shellydevice.

UPDATE: I was able to fix it after I entered some dummy credential data in the binding configuration (I actually changed the admin to adminBLA). Then I saved it, changed it back to the correct username and saved again.

OLD POST:

thanks for your super fast reply. this raises more questions :wink:

In deed I first scanned for the shellies BEFORE I set the credentials in the binding. Then I went back, configured the binding, deleted everything from the inbox, re-scanned, same issue.

Now I see - after your hint - that my Shelly1 devices are of type “shellydevice”. What does that mean and how can I change it?

This is what I see after I remove everything from the inbox and then hit the scan button:

Thanks

Stefan

The binding uses the credentials from the binding settings to access the device. If that works it get‘s the thing type from the device‘s mdns name, e.g. shelly1. In this case it creates a thing of type shelly1.

If the http access fails it creates a thing of type shellydevice. This is a placeholder so the user see a thing, which needs additional information. Otherwise the device won‘t show up anywhere. If you edit the thing and enter the correct credentials the binding will re-initialize and change the thing type to the detected one. However, I can‘t change the name of the thing anymore so it stays shelly:shellydevice.

If you still see shellydevice after deleting and re-discovering the thing:

  • the binding should now be able to access the device so the thing should become online
  • nevertheless the name might stay the same, because OH keeps the old record in the JSON DB and if you re-discover the device it reuses that record. This is nice, if you really want to delete/re-add the same device, but prohibits reset to a clean status.

If you realy want to have a clean setup you need to clean-out the JSON-DB and remove all references/entries with shelly in the name. In this case all things get re-discovered and create clean entries in the DB. I know, a lot of details under the hood :wink:

1 Like

First of all happy new year and thanks for this great binding!
Initialisation of shelly binding in Openhab 3.1.0 takes quite long. As already described in the previous post the new openhab release 3.0 comes with a lot of changes under the hood and also in the way you interact with the bindings. I was able to get along with the new model based topology and was able to integrate my shellys quickly.
But as far my openhab restarts and the web app refreshes all shelly things are uninitialised and it takes several minutes (up to 5min) until they are online (shelly uni and shelly 1pm) So the startup procedure of the shelly binding for openhab 3.1 takes very long which can be problematic if you work with rules based on the shelly states… How is your experience?
An other inconsistency which i noticed is that the current item value like power consumption or temperature does not show up in the sites where all things are displayed according they semantic group (location, devices…) and only when i press analyse the values are displayed on the graph.

My setup is openhab 3.1 as a docker container on a Raspberry pi 4 with 4GB Ram.

Cheers

that must be specific to you installation. I never saw an issue that initialization takes 5 minutes. Check openhab.log to locate time delay.

I don’t get that, please explain

Thx for the fast reply. As follow two log series are postet which shows the exactly startup behaviour of my system. Sometimes the binding has up to 4 min until all shellies are online…
events_2.log (13.0 KB) events_1.log (7.8 KB)

I don’t get that, please explain

This is not related to the shelly binding as I could figure it out… The new UI which comes with OH 3 does not display the actual item’s state of my shelly devices only the trend line is displayed so far…