Hi, I have the same problem with Shelly3em. Independant from Interval setting and AutoCoIoT there are every second a new messurement in the logfile. Did you found solution for the logging interval?
OH has an integrated feature to filter the event log, see the discussion here 1
The configuration is added as a new section to openhab2-userdata/etc/org.ops4j.pax.logging.cfg
Based on this you could use the following config:
# custom filtering rules
log4j2.appender.event.filter.uselessevents.type = RegexFilter
log4j2.appender.event.filter.uselessevents.regex = .*(heartBeat|LastUpdate|lastUpdate|LetzteAktualisierung|Uptime|Laufzeit|ZuletztGesehen).*
log4j2.appender.event.filter.uselessevents.onMatch = DENY
log4j2.appender.event.filter.uselessevents.onMisMatch = NEUTRAL
This filters events for items heartBeat, lastUpdate, LetzteAktualisierung, Uptime, Laufzeit, ZuletztGesehen. Replace those strings with the items you want to filter. Use a list of items to reduce logging.
Please note: Once events are filtered they are “lost”, you can’t find them later.
you need to use the DEV build
Latest DEV build: 2.5.10 - 3.0.0 - README - Installation - Firmware Index - Firmware Archive - API Doc
thy markus7017, but I do not want to exclude the events, I only want to reduce the events, like every two minutes. I want to setup a rule, which runs on everyChange, but only every two minutes.
Has someone an other idea, why the setting “Update Interval” in the Shelly3EM thing is not working?
In my setup, the update interval works with the 3EM, I get an update every 5 minutes like I configured. I’m not using any dev release.
that’s strange @wars . Which OH-Release, shelly firmware and shelly update interval you have; or have you acticated MQTT in shelly settings?
In the shelly thing properties, I found “devUpdatePeriod”, which could not be changed:
| coapDeviceDescr | {“blk”:[{“I”:1,“D”:“relay_0”},{“I”:2,“D”:“emeter_0”},{“I”:3,“D”:“emeter_1”},{“I”:4,“D”:“emeter_2”},{“I”:5,“D”:“device”}],“sen”:[{“I”:9103,“T”:“EVC”,“D”:“cfgChanged”,“R”:“U16”,“L”:5},{“I”:1101,“T”:“S”,“D”:“output”,“R”:“0/1”,“L”:1},{“I”:4105,“T”:“P”,“D”:“power”,“U”:“W”,“R”:[“0/31800”,"-1"],“L”:2},{“I”:4106,“T”:“E”,“D”:“energy”,“U”:“Wh”,“R”:[“U32”,"-1"],“L”:2},{“I”:4107,“T”:“E”,“D”:“energyReturned”,“U”:“Wh”,“R”:[“U32”,"-1"],“L”:2},{“I”:4108,“T”:“V”,“D”:“voltage”,“U”:“V”,“R”:[“0/265”,"-1"],“L”:2},{“I”:4109,“T”:“I”,“D”:“current”,“U”:“A”,“R”:[“0/120”,"-1"],“L”:2},{“I”:4110,“T”:“S”,“D”:“powerFactor”,“R”:[“0/1”,"-1"],“L”:2},{“I”:4205,“T”:“P”,“D”:“power”,“U”:“W”,“R”:[“0/31800”,"-1"],“L”:3},{“I”:4206,“T”:“E”,“D”:“energy”,“U”:“Wh”,“R”:[“U32”,"-1"],“L”:3},{“I”:4207,“T”:“E”,“D”:“energyReturned”,“U”:“Wh”,“R”:[“U32”,"-1"],“L”:3},{“I”:4208,“T”:“V”,“D”:“voltage”,“U”:“V”,“R”:[“0/265”,"-1"],“L”:3},{“I”:4209,“T”:“I”,“D”:“current”,“U”:“A”,“R”:[“0/120”,"-1"],“L”:3},{“I”:4210,“T”:“S”,“D”:“powerFactor”,“R”:[“0/1”,"-1"],“L”:3},{“I”:4305,“T”:“P”,“D”:“power”,“U”:“W”,“R”:[“0/31800”,"-1"],“L”:4},{“I”:4306,“T”:“E”,“D”:“energy”,“U”:“Wh”,“R”:[“U32”,"-1"],“L”:4},{“I”:4307,“T”:“E”,“D”:“energyReturned”,“U”:“Wh”,“R”:[“U32”,"-1"],“L”:4},{“I”:4308,“T”:“V”,“D”:“voltage”,“U”:“V”,“R”:[“0/265”,"-1"],“L”:4},{“I”:4309,“T”:“I”,“D”:“current”,“U”:“A”,“R”:[“0/120”,"-1"],“L”:4},{“I”:4310,“T”:“S”,“D”:“powerFactor”,“R”:[“0/1”,"-1"],“L”:4},{“I”:6102,“T”:“A”,“D”:“overpower”,“R”:[“0/1”,"-1"],“L”:1}]} |
|---|---|
| coapVersion | 2 |
| coiotAutoEnable | true |
| coiotAutoRefresh | true |
| deviceHwBatch | 1 |
| deviceHwRev | prod-2020-1 |
| deviceMode | |
| deviceName | Shelly3em |
| deviceType | shellyem3 |
| devUpdatePeriod | 70 |
| macAddress | 40F52000EFE4 |
| modelId | SHEM-3 |
| numberMeters | 3 |
| numberRelays | 1 |
| numberRollers | 0 |
| serviceName | shellyem3-40f52000efe4 |
| statsTimeoutErrors | 4 |
| statsTimeoutsRecovered | 4 |
| updateAvailable | no |
| updateCurrentVersion | 20200813-140420/v1.8.1@1b2a49be |
| updateNewVersion | 20200813-140420/v1.8.1@1b2a49be |
| updateStatus | idle |
| vendor | Shelly |
| wifiNetwork | keller |
I found a solution. It seems, that “update interval” is only working, when CoIoT is disabled.
I thought I disabled CoIoT, but it automatically is activated, when in the shelly binding configuration the parameter “autoCoIoT” is on (what is the default).
Now I switched “autoCoIoT” (in binding config) and “CoIoT” (in thing config) to “off”. Now the “update interval” of 60 is working
Hello,
In OH version 2.5.8 (openhabian on RP4), with the shelly binding version 2.5.8 installed via PaperUI, the newer things Shelly Button and Shelly Gas are not appearing in the list of things under Configuration/Bindings/Shelly Binding.
I uninstalled the binding and reinstalled, however, this did not correct.
Thanks in advance for any assistance
you need to install the latest version (yes it runs on 2.5.8) or upgrade OH 2.5.10
—
Latest DEV build: 2.5.10 - 3.0.0 - README - Installation - Firmware Index - Firmware Archive - API Doc
Hi,
I have the Shelly UNI (https://shelly.cloud/products/shelly-uni-smart-home-automation-device/)
But it shows up as unsupported by the Shelly Binding, how can we make it work with the binding?
the UNI is currently not supported. I have it on my desk, but didn’t had the time so far to work on it, maybe within the next 2 weeks
1 Like
Upgrading the binding to the dev version corrected the issue. Thanks!
@markus7017 did one of the newer releases or dev of the shelly binding has the config option “Local IP”?
I am curious if I could update to the Shelly binding included in openHAB 2.5.10 without loosing the config option “Local IP”.
I am still running you test binding.
No, this is not yet merged to the 2.5.x distro nor 3.0. I’m pretty sure that this will not go into 2.5.x, because this 2.5.x. will only receive cherry picked fixes, everything else will only go into 3.0. I didn’t had the time to create another PR for 3.0, but it’s on the list
@markus7017 I do not plan to migrate to 3.0 soon - maybe mid 2021. So I plan to live with this test build of the shelly binding .
No worries, I’ll continue to provide 2.5.x updates
Hi,
my shelly binding (DEV) is not visible on binding list in UI.
openHAB version: 3.0.0.M2-docker
Shelly binding version: 3.0.0.202010031637
I’ve instaled it as per instruction:
- OH container stop
- cleared cache and tmp
-
californium-core-2.0.0.jarandelement-connector-2.0.0.jarcopied into addons folder - OH container start
- waiting when OH is fully started
-
org.openhab.binding.shelly-3.0.0-SNAPSHOT.jarinto addons folder
Even if I see shelly binding on the list in karaf console:
253 x Active x 80 x 3.0.0.202010031637 x org.openhab.binding.shelly
Binding is not visible in UI
BTW how to switch on TRACE logging in OH3? Is it enough to add below code to log4j2.xml?
<Logger level="DEBUG" name="org.openhab.binding.shelly"/>
you should use the OH console to set logging, it’s not in the xml file
check openhab.log for any errors
in openhab.log I see:
2020-11-16 21:09:50.304 [WARN ] [org.apache.felix.fileinstall ] - Error while starting bundle: file:/openhab/addons/org.openhab.binding.shelly-3.0.0-SNAPSHOT.jar
org.osgi.framework.BundleException: Could not resolve module: org.openhab.binding.shelly [208]
Unresolved requirement: Import-Package: org.apache.commons.lang.time