According to the code lastUpdate should get updated if any of the channel values has changed (device provided updated values). Please provide a log showing a sensor update. Keep in mind, same limitation: update means state / battery / temperature etc., no uptime, wifiSignal etc.
Many thanks i’ll give it a try,
to get the updated binding i run apt-get update && upgrade? or reinstall?
Cheers
No, you have to install the DEV build, see: https://github.com/markus7017/myfiles/blob/master/shelly/READMEbeta.md
download the jar here
don’t forget to deinstall the version, which comes in PaperUI
Sure. Here is a cycle of some changes OPEN/CLOSED as well as vibration ON/OFF. None update to the sensors#lastUpdate included:
2020-05-12 20:36:28.638 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellydw-tuer: CoIoT Message from /192.168.9.17:5683 (MID=25398): {"G":[[0,66,48],[0,55,0],[0,77,100],[0,88,-1],[0,99,0]]}
2020-05-12 20:36:28.641 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellydw-tuer: Duplicate serial 256 will be processed, because payload is different: {"G":[[0,66,48],[0,55,0],[0,77,100],[0,88,-1],[0,99,0]]} vs. {"G":[[0,66,48],[0,55,1],[0,77,100],[0,88,-1],[0,99,0]]}
2020-05-12 20:36:28.645 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellydw-tuer: CoIoT Sensor data {"G":[[0,66,48],[0,55,0],[0,77,100],[0,88,-1],[0,99,0]]}
2020-05-12 20:36:28.649 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellydw-tuer: 5 CoAP sensor updates received
2020-05-12 20:36:28.661 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellydw-tuer: Channel sensors#state updated with CLOSED (type class org.eclipse.smarthome.core.library.types.OpenClosedType).
2020-05-12 20:36:28.666 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellydw-tuer: 1 channels updated from CoIoT status
2020-05-12 20:36:28.686 [vent.ItemStateChangedEvent] - ShellyTuer changed from OPEN to CLOSED
2020-05-12 20:36:54.142 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellydw-tuer: CoIoT Message from /192.168.9.17:5683 (MID=63203): {"G":[[0,66,35],[0,55,0],[0,77,100],[0,88,-1],[0,99,1]]}
2020-05-12 20:36:54.146 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellydw-tuer: Duplicate serial 256 will be processed, because payload is different: {"G":[[0,66,35],[0,55,0],[0,77,100],[0,88,-1],[0,99,1]]} vs. {"G":[[0,66,48],[0,55,0],[0,77,100],[0,88,-1],[0,99,0]]}
2020-05-12 20:36:54.151 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellydw-tuer: CoIoT Sensor data {"G":[[0,66,35],[0,55,0],[0,77,100],[0,88,-1],[0,99,1]]}
2020-05-12 20:36:54.156 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellydw-tuer: 5 CoAP sensor updates received
2020-05-12 20:36:54.170 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellydw-tuer: Channel sensors#vibration updated with ON (type class org.eclipse.smarthome.core.library.types.OnOffType).
2020-05-12 20:36:54.176 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellydw-tuer: 1 channels updated from CoIoT status
2020-05-12 20:36:54.180 [vent.ItemStateChangedEvent] - ShellyTuer_vibration changed from OFF to ON
2020-05-12 20:37:51.081 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellydw-tuer: CoIoT Message from /192.168.9.17:5683 (MID=57768): {"G":[[0,66,20],[0,55,1],[0,77,100],[0,88,-1],[0,99,0]]}
2020-05-12 20:37:51.085 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellydw-tuer: Duplicate serial 256 will be processed, because payload is different: {"G":[[0,66,20],[0,55,1],[0,77,100],[0,88,-1],[0,99,0]]} vs. {"G":[[0,66,35],[0,55,0],[0,77,100],[0,88,-1],[0,99,1]]}
2020-05-12 20:37:51.088 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellydw-tuer: CoIoT Sensor data {"G":[[0,66,20],[0,55,1],[0,77,100],[0,88,-1],[0,99,0]]}
2020-05-12 20:37:51.092 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellydw-tuer: 5 CoAP sensor updates received
2020-05-12 20:37:51.112 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellydw-tuer: Channel sensors#state updated with OPEN (type class org.eclipse.smarthome.core.library.types.OpenClosedType).
2020-05-12 20:37:51.122 [vent.ItemStateChangedEvent] - ShellyTuer changed from CLOSED to OPEN
2020-05-12 20:37:51.133 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellydw-tuer: Channel sensors#vibration updated with OFF (type class org.eclipse.smarthome.core.library.types.OnOffType).
2020-05-12 20:37:51.136 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellydw-tuer: 2 channels updated from CoIoT status
2020-05-12 20:37:51.142 [vent.ItemStateChangedEvent] - ShellyTuer_vibration changed from ON to OFF
For reference, this is the current linking of the channels:
Group gShellyTuer
Contact ShellyTuer "Eingangstür [%s]" (gShellyTuer, gMapdb) {channel="shelly:shellydw:tuer:sensors#state" }
Switch ShellyTuer_vibration "Erschütterung" (gShellyTuer) {channel="shelly:shellydw:tuer:sensors#vibration" }
String ShellyTuer_reason "Aufwachgrund [%s]" (gShellyTuer) {channel="shelly:shellydw:tuer:device#wakeupReason" }
DateTime ShellyTuer_last "Lebenszeichen [%1$ta, %1$te. %1$tb %1$tk:%1$tM]" (gShellyTuer) {channel="shelly:shellydw:tuer:sensors#lastUpdate" }
String ShellyTuer_error "Letzter Fehler [%s]" (gShellyTuer) {channel="shelly:shellydw:tuer:sensors#lastError" }
Number ShellyTuer_batt "Batterie" (gShellyTuer) {channel="shelly:shellydw:tuer:battery#batteryLevel" }
Number ShellyTuer_uptime "Laufzeit [%d s]" <clock_grey> (gShellyTuer) {channel="shelly:shellydw:tuer:device#uptime"}
Number ShellyTuer_rssi "Signalstärke [%d]" <wifi> (gShellyTuer) {channel="shelly:shellydw:tuer:device#wifiSignal"}
ok, I could confirm a bug. The timestamp is set, but after the updates to the channels have been performed. I’ll provide a new build once I completed another change.
ok, new DEV build
- fix for sensors#lastUpdate
- Watt updates are filtered, diff must be > 1W
- KW/h updates are filtered, diff must be > 0.05 kw/h (50W)
Are the thresholds suitable? I want to prevent the logfile getting flooded by power updates, on the other side the threshold shouldn’t drop useful updates.
Feedback welcome.
1 Like
Thanks markus it is working fine even the rule fires correctly,
020-05-13 00:15:25.147 [INFO ] [y.internal.handler.ShellyBaseHandler] - shellyplug-7bcca9: Thing goes OFFLINE: message.offline.status-error-watchdog
==> /var/log/openhab2/events.log <==
2020-05-13 00:15:25.157 [hingStatusInfoChangedEvent] - 'shelly:shellyplug:7bcca9' changed from ONLINE to OFFLINE (COMMUNICATION_ERROR): Watchdog expired - device did not update status, going OFFLINE.
==> /var/log/openhab2/openhab.log <==
2020-05-13 00:15:25.290 [INFO ] [e.model.script.heating-control.rules] - Heating control failed while in mode OFFLINE
2020-05-13 00:16:36.567 [WARN ] [y.internal.handler.ShellyBaseHandler] - shellyplug-7bcca9: Event triggered: RESTARTED
==> /var/log/openhab2/events.log <==
2020-05-13 00:16:36.571 [me.event.ThingUpdatedEvent] - Thing 'shelly:shellyplug:7bcca9' has been updated.
2020-05-13 00:16:36.593 [vent.ChannelTriggeredEvent] - shelly:shellyplug:7bcca9:device#alarm triggered RESTARTED
2020-05-13 00:16:36.607 [me.event.ThingUpdatedEvent] - Thing 'shelly:shellyplug:7bcca9' has been updated.
2020-05-13 00:16:36.618 [hingStatusInfoChangedEvent] - 'shelly:shellyplug:7bcca9' changed from OFFLINE (COMMUNICATION_ERROR): Watchdog expired - device did not update status, going OFFLINE. to ONLINE
==> /var/log/openhab2/openhab.log <==
2020-05-13 00:16:36.642 [INFO ] [e.model.script.heating-control.rules] - Heating control failed while in mode ONLINE
Thanks for testing, but this sounds incorrect “Heating control failed while in mode ONLINE”. I assume is just a matter of your message?
Perfect - can confirm it’s now working as it expected:
2020-05-13 16:20:54.626 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellydw-tuer: CoIoT Sensor data {"G":[[0,66,260],[0,55,1],[0,77,97],[0,88,-1],[0,99,0]]}
2020-05-13 16:20:54.630 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellydw-tuer: 5 CoAP sensor updates received
2020-05-13 16:20:54.647 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellydw-tuer: Channel sensors#lastUpdate updated with 2020-05-13T16:20:54.000+0200 (type class org.eclipse.smarthome.core.library.types.DateTimeType).
2020-05-13 16:20:54.654 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellydw-tuer: Channel sensors#state updated with OPEN (type class org.eclipse.smarthome.core.library.types.OpenClosedType).
2020-05-13 16:20:54.658 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellydw-tuer: 2 channels updated from CoIoT status
2020-05-13 16:20:54.679 [vent.ItemStateChangedEvent] - ShellyTuer_last changed from 2020-05-13T16:18:14.000+0200 to 2020-05-13T16:20:54.000+0200
2020-05-13 16:20:54.683 [vent.ItemStateChangedEvent] - ShellyTuer changed from CLOSED to OPEN
So, sensors#lastUpdate now gets updated when any of the sensor values/states have changed.
Many thanks for your quick fix! Excellent!
Really aprecciate your responsiveness and continous improvement of this binding!
1 Like
it is just my message , it is working fine,
cheers
I added this to PR #7595, so gets into 2.5.5, latest 2.5.6
This will get into the next PR, won’t expect this for 2.5.5, but depends when this release is closed.
1 Like
Hi all,
After my first ShellyHT drained off may battery in about 2 weeks, I have got an replacement. I used same procedure to add this to my environment and can access WI once waked up. Status has been send this afternoon, than I hade to restart OpenHab and now Status is no longer updated, even when I wake device up. Any idea where this behaviour comes from??
I‘m not using (xxx) cloud, which has been disabled on all my Shelly devices as I only rely on this Binding to get values etc. 
In addition I recognised different behaviour when I wake device up. LED is flashing slowly (just as I remember this from my first device) but after 3 or 4 times, it‘s flashing faster. I have no clue why this is happening nor did I found anything at google :-/ while I trust this is not related to this binding, someone might help also on this?
1 Like
Hi Markus,
Sorry to trouble you again,
I am unable to get the temperature,humidity,battery,lastupdate,motion and lux from shelly sense despite that the trace shows some channels getting updated:
2020-05-14 11:00:08.785 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: CoIoT Sensor data {"G":[[0,11,0],[0,22,0],[0,33,26.223565],[0,44,75.096347],[0,66,35.064935],[0,77,100]]}
2020-05-14 11:00:08.787 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: 6 CoAP sensor updates received
2020-05-14 11:00:08.788 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: Sensor value[0]: id=11, Value=0.0 (Motion, Type=M, Range=0/1, Link=1: Sensors)
2020-05-14 11:00:08.790 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: Sensor value[1]: id=22, Value=0.0 (Charger, Type=S, Range=0/1, Link=1: Sensors)
2020-05-14 11:00:08.792 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: Sensor value[2]: id=33, Value=26.223565 (Temperature, Type=T, Range=-40/125, Link=1: Sensors)
2020-05-14 11:00:08.795 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: Sensor value[3]: id=44, Value=75.096347 (Humidity, Type=H, Range=0/100, Link=1: Sensors)
2020-05-14 11:00:08.798 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: Sensor value[4]: id=66, Value=35.064935 (Lux, Type=L, Range=0/1, Link=1: Sensors)
2020-05-14 11:00:08.801 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: Sensor value[5]: id=77, Value=100.0 (Battery, Type=B, Range=0/100, Link=1: Sensors)
2020-05-14 11:00:23.665 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: CoIoT Message from /10.0.0.11:5683 (MID=22491): {"G":[[0,11,0],[0,22,0],[0,33,26.185423],[0,44,75.186441],[0,66,33.766234],[0,77,100]]}
2020-05-14 11:00:23.667 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: CoIoT Sensor data {"G":[[0,11,0],[0,22,0],[0,33,26.185423],[0,44,75.186441],[0,66,33.766234],[0,77,100]]}
2020-05-14 11:00:23.669 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: 6 CoAP sensor updates received
2020-05-14 11:00:23.671 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: Sensor value[0]: id=11, Value=0.0 (Motion, Type=M, Range=0/1, Link=1: Sensors)
2020-05-14 11:00:23.672 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: Sensor value[1]: id=22, Value=0.0 (Charger, Type=S, Range=0/1, Link=1: Sensors)
2020-05-14 11:00:23.675 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: Sensor value[2]: id=33, Value=26.185423 (Temperature, Type=T, Range=-40/125, Link=1: Sensors)
2020-05-14 11:00:23.677 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: Sensor value[3]: id=44, Value=75.186441 (Humidity, Type=H, Range=0/100, Link=1: Sensors)
2020-05-14 11:00:23.679 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: Sensor value[4]: id=66, Value=33.766234 (Lux, Type=L, Range=0/1, Link=1: Sensors)
2020-05-14 11:00:23.681 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: Sensor value[5]: id=77, Value=100.0 (Battery, Type=B, Range=0/100, Link=1: Sensors)
2020-05-14 11:00:23.686 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellysense-4b3fa4: Channel sensors#humidity updated with 75.2 % (type class org.eclipse.smarthome.core.library.types.QuantityType).
2020-05-14 11:00:23.689 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellysense-4b3fa4: Channel sensors#lux updated with 33.8 lx (type class org.eclipse.smarthome.core.library.types.QuantityType).
2020-05-14 11:00:23.692 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: 2 channels updated from CoIoT status
2020-05-14 11:00:38.336 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: CoIoT Message from /10.0.0.11:5683 (MID=22492): {"G":[[0,11,0],[0,22,0],[0,33,26.204494],[0,44,75.210466],[0,66,35.064935],[0,77,100]]}
2020-05-14 11:00:38.338 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: CoIoT Sensor data {"G":[[0,11,0],[0,22,0],[0,33,26.204494],[0,44,75.210466],[0,66,35.064935],[0,77,100]]}
2020-05-14 11:00:38.341 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: 6 CoAP sensor updates received
2020-05-14 11:00:38.343 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: Sensor value[0]: id=11, Value=0.0 (Motion, Type=M, Range=0/1, Link=1: Sensors)
2020-05-14 11:00:38.346 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: Sensor value[1]: id=22, Value=0.0 (Charger, Type=S, Range=0/1, Link=1: Sensors)
2020-05-14 11:00:38.348 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: Sensor value[2]: id=33, Value=26.204494 (Temperature, Type=T, Range=-40/125, Link=1: Sensors)
2020-05-14 11:00:38.352 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: Sensor value[3]: id=44, Value=75.210466 (Humidity, Type=H, Range=0/100, Link=1: Sensors)
2020-05-14 11:00:38.355 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: Sensor value[4]: id=66, Value=35.064935 (Lux, Type=L, Range=0/1, Link=1: Sensors)
2020-05-14 11:00:38.358 [TRACE] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: Sensor value[5]: id=77, Value=100.0 (Battery, Type=B, Range=0/100, Link=1: Sensors)
2020-05-14 11:00:38.364 [DEBUG] [lly.internal.util.ShellyChannelCache] - shellysense-4b3fa4: Channel sensors#lux updated with 35.1 lx (type class org.eclipse.smarthome.core.library.types.QuantityType).
2020-05-14 11:00:38.366 [DEBUG] [elly.internal.coap.ShellyCoapHandler] - shellysense-4b3fa4: 1 channels updated from CoIoT status
2020-05-14 11:00:40.554 [TRACE] [y.internal.handler.ShellyBaseHandler] - shellysense-4b3fa4: Updating status
2020-05-14 11:00:40.556 [TRACE] [ng.shelly.internal.api.ShellyHttpApi] - shellysense-4b3fa4: HTTP GET for http://10.0.0.11/status
2020-05-14 11:00:40.718 [TRACE] [ng.shelly.internal.api.ShellyHttpApi] - shellysense-4b3fa4: HTTP Response 200: {"wifi_sta":{"connected":true,"ssid":"NickyGhz","ip":"10.0.0.11","rssi":-61},"cloud":{"enabled":true,"connected":true},"mqtt":{"connected":false},"time":"11:00","unixtime":1589454041,"serial":14,"has_update":false,"mac":"D436394B3FA4","motion":false,"charger":false,"tmp":{"value":26.185423,"is_valid":true,"units":"C"},"hum":{"value":75.225481,"is_valid":true},"lux":{"value":35.064935,"is_valid":true},"bat":{"value":100},"update":{"status":"idle","has_update":false,"new_version":"20200309-104151/v1.6.0@43056d58","old_version":"20200309-104151/v1.6.0@43056d58"},"ram_total":48020,"ram_free":23920,"fs_size":83081,"fs_free":21837,"uptime":1105}
2020-05-14 11:00:40.722 [DEBUG] [y.internal.handler.ShellyBaseHandler] - shellysense-4b3fa4: Updating sensor
2020-05-14 11:00:40.724 [TRACE] [ng.shelly.internal.api.ShellyHttpApi] - shellysense-4b3fa4: HTTP GET for http://10.0.0.11/status
2020-05-14 11:00:40.891 [TRACE] [ng.shelly.internal.api.ShellyHttpApi] - shellysense-4b3fa4: HTTP Response 200: {"wifi_sta":{"connected":true,"ssid":"NickyGhz","ip":"10.0.0.11","rssi":-59},"cloud":{"enabled":true,"connected":true},"mqtt":{"connected":false},"time":"11:00","unixtime":1589454041,"serial":14,"has_update":false,"mac":"D436394B3FA4","motion":false,"charger":false,"tmp":{"value":26.166352,"is_valid":true,"units":"C"},"hum":{"value":75.249506,"is_valid":true},"lux":{"value":35.064935,"is_valid":true},"bat":{"value":100},"update":{"status":"idle","has_update":false,"new_version":"20200309-104151/v1.6.0@43056d58","old_version":"20200309-104151/v1.6.0@43056d58"},"ram_total":48020,"ram_free":23916,"fs_size":83081,"fs_free":21837,"uptime":1105}
I noticed in paper ui only the following channels are discovered:
.Things declaration:
Thing shelly:shellysense:4b3fa4 "Shelly Sense (Temp/Humidity/IR)" @ "Elias Bedroom" [deviceIp="10.0.0.11", userId="", password="" , eventsSensorReport="true", eventsCoIoT="true" , updateInterval="60"]
.Items
Number Temperature_i "Temperature [%0.1f °C]" <temperature> (gTemperature, gElias) ["Temperature", "Measurement"] {channel="shelly:shellysense:4b3fa4:sensors#temperature"}
Number Humidity_i "Humidity [%0.1f %%]" <humidity> (gElias) ["Measurement"] {channel="shelly:shellysense:4b3fa4:sensors#humidity"}
Number Lux_i "Brightness [%0.1f Lux]" <lightbulb> (gElias) ["Measurement"] {channel="shelly:shellysense:4b3fa4:sensors#lux"}
Number Battery_i "Battery [%d %%]" <batterylevel> (gElias) ["Measurement"] {channel="shelly:shellysense:4b3fa4:battery#batterylevel"}
Switch Motion_i "Motion detected" <motion> (gElias) ["Measurement"] {channel="shelly:shellysense:4b3fa4:sensors#motion"}
String Lastupdate "LastUpdate: [%s]" <time> (gElias) ["Measurement"] {channel="shelly:shellysense:4b3fa4:sensors#lastUpdate"}
.Sitemap
Text label="Elias Room" icon="boy_2" {
Text item=Temperature_i
Switch item=Motion_i
Text item=Humidity_i
Text item=Lux_i
Text item=Battery_i
Text item=Lastupdate
}
{"wifi_sta":{"connected":true,"ssid":"NickyGhz","ip":"10.0.0.11","rssi":-61},"cloud":{"enabled":true,"connected":true},"mqtt":{"connected":false},"time":"11:31","unixtime":1589455864,"serial":33,"has_update":false,"mac":"D436394B3FA4","motion":false,"charger":false,"tmp":{"value":26.109139,"is_valid":true,"units":"C"},"hum":{"value":76.739057,"is_valid":true},"lux":{"value":40.259740,"is_valid":true},"bat":{"value":100},"update":{"status":"idle","has_update":false,"new_version":"20200309-104151/v1.6.0@43056d58","old_version":"20200309-104151/v1.6.0@43056d58"},"ram_total":48020,"ram_free":23956,"fs_size":83081,"fs_free":21837,"uptime":2928}
{"device":{"type":"SHSEN-1","mac":"xxxxxxx","hostname":"shellysense-4B3FA4"},"wifi_ap":{"enabled":false,"ssid":"shellysense-4B3FA4","key":""},"wifi_sta":{"enabled":true,"ssid":"NickyGhz","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},"mqtt": {"enable":false,"server":"192.168.33.3:1883","user":"","id":"shellysense-4B3FA4","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": {"update_period":15},"sntp":{"server":"time.google.com","enabled":true},"login":{"enabled":false,"unprotected":false,"username":"admin","password":"admin"},"pin_code":"","name":"","fw":"20200309-104151/v1.6.0@43056d58","discoverable":false,"build_info":{"build_id":"20200309-104151/v1.6.0@43056d58","build_timestamp":"2020-03-09T10:41:51Z","build_version":"1.0"},"cloud":{"enabled":true,"connected":true},"timezone":"Asia/Beirut","lat":33.893799,"lng":35.501801,"tzautodetect":true,"tz_utc_offset":10800,"tz_dst":true,"tz_dst_auto":true,"time":"11:32","unixtime":1589455920,"light_sensor":"NOA1305","schedule":false,"schedule_rules":[],"sensors":{"motion_duration":10,"motion_led":false,"temperature_unit":"C"}}
Can you please advise, many thanks,
Check if it is included in your network first as changing battery might reset it; Just a thought
Yes, it’s included in network and I can access device when I wake it up and if I do restart binding at same time, it’s getting all values properly. But than it stuck again.
wake up has been confgured to take place either 1 degree of temp. or 10% humidity change or once every 2 hours.
Try the dev build above from markus
Another question to the community here,
Does any one knows how can we implement an interlock rule to prevent a shelly rollershutter from processing a close command before an open command has finished?
i’m not good with rules but i think i should look into when roller#input1 changes to OFF and monitor the power consumption (current watts), can anyone help please with such a rule,
Many thanks,
OK, thanks for the hint.
- made a backup
- deinstalled integrated binding
- removed/comment out all Shelly items in *.items
- updated to 2.5.5-snapshot (just to be on latest and corresponding version to Dev Binding)
- copied binding to get installed
- after all was up I experienced same issue as reported => missing californium.core :-/
- found the solution and installed featues, install went through
- my Plug-s became online again, while shallyht was still offline
- pushed button on shellyht and restarted binding => shellyht becomes online
- added/un-comment all shelly items => all were updated, except shellyht
(LED was already off again) - pushed button again, restarted shelly binding and now also shellyht reports the values
Let’s see if it will continue to send those, I 'll watching this and report.
I can’t put down a rule right now…anyway I think that this kind of behavior requires a proxy item for the rollershutter, because you can’t prevent the default behavior when an item receive a command.
So I can guess the logic would be : ProxyRoller receive an up or down - > rule check the real state/power consumpiton of the RealRollerShutter -> do nothing or forward the command to the RealRollerShutter
Fine i wil try but how can i guarantee interlock when an up command is received for ex?