thank you @markus7017. But, maybe a basic question, if I know how to install manually a binding, how do I switch from a binding installed from the web interface to a manual one ? Should I uninstall the “web” binding then install the DEV one ? Or is there another way ?
For the record, I’ve deleted my request on GitHub, sorry about that.
Yes that’s exactly the way to do it. Remove the binding via the UI first and then deploy the new one in the addon folder.
Again me I’m sorry.
I’ve removed the “official” binding, stopped OH, downloaded 4.1.0-DEV, restarted OH.
From the bundle list, I get this:
272 │ Resolved │ 80 │ 4.1.0.202308122203 │ openHAB Add-ons :: Bundles :: Shelly Binding Gen1+2
I go back to Openhab, in my inbox I see my Gateway, I had it as thing, then I go back to the list of things, and I have the exact same problem as before: the thing is offline with a CONFIGURATION_ERROR “IP/MAC Address of the Shelly device is missing.” In thing properties however, deviceIp is set to the correct address.
What am I missing ?
ups, sorry, you are right, the BLU gateway is not supported yet; as I said to move forward with the PRs (current one is almost done) before adding new stuff
It has been a while since the last time someone said it, so, thank you Markus for your work!
Having some 30shellies i highly dependend on. Do you have a “Buy me a coffee” or something like that?
I have “I appreciate your work” and it’s free of charge 
I highly appreciate feedback, if you want to contribute be active here helping to support the community:hugs: or help testing or enhancing the documentation. Or just hints how to improve documentation or add a feature that make it easier for others or implementing use cases.
Ling time ago I invited to contribute use case descriptions (like I did for Shelly rollers using favorites). Some combination of Shelly function, rules or just a step-by-step implementation guide for more complex scenarios than “installed a Shelly”. This creates ideas for creative setups using Shellys for others. So I you have something like an irrigation controller, weather dependent, alarm system or something else just create a draft in MD format or plain text and I’ll include this as part of the dist (as part of the doc folder). So @MajorTwip if you save “I heavily depend on my Shellys and the binding”
, this smells like a use case others are interested 
And of course anyone else is invited too:innocent:
One the current PR (critical fixed preventing IH to run into out-of-memory) the next one (enhanced security and improved discovery) I’ll start working on new features. Thanks @Lolodomo and and the team doing the reviews.
@markus7017 Absolutely no problem! Just back to square one, it’s anyway an opportunity to fiddle with shelly scripting.
Two questions:
If someone is interested, I have created a widget, popup and rules to manage shellies
Will take some time to clean up the code and do translation, that‘s why I am suggesting this first.
Solved the operational side by switching to MQTT - all functions work well (but manually). Added bonus is it works with 2.5 too 
When the Shelly binding gets the fix might revert.
Worked well for one week.
But it seems that coap feature gets lost by clean-cache?!
I had t install it again.
Is there any way to keep it?
Yes, that‘s part of the clean cache to remove not required components.
Best way is to use a batch/sh file which cleans the cache and reinstalls the components
/usr/bin/ssh -p 8101 openhab@localhost feature:install openhab-transport-coap
Im using this file in the /bin/ share
#!/bin/bash
echo '###########################################'
echo '###### openHAB CACHE/TMP loeschen #####'
echo '###########################################'
date "+%A %d/%m/%Y %H:%M:%S"
echo '###########################################'
# openHAB Service stoppen
echo 'Stoppe openhab-Service'
sudo systemctl stop openhab.service
# CACHE und TMP löschen
echo 'CACHE und TMP loeschen'
sudo yes | openhab-cli clean-cache
# openHAB Service starten
echo 'Starte openhab-Service'
sudo systemctl start openhab.service
How do I have do handle your command? Do I have to use „sudo“ as well?
Add the command after starting openhab.service
I don‘t think you need sudo.
Yes, my question was not related to the position in the script but as it is a command of the karaf console I am not sure how this command must look like in a shell script.
I added my first Shelly BLU button to openHAB (3.4.5 + DEV Binding 3.4.5.202308121445). Following the docs from the binding everything went fine after some trial and error.
[INFO ] [el.core.internal.ModelRepositoryImpl] - Loading model 'shelly_button.things'
[WARN ] [core.thing.internal.ThingManagerImpl] - The model of shelly:shellyblubutton:BLUETOOTH_MACADDRESS is inconsistent [thing.getHandler().getThing() != thing]
==> /var/log/openhab/events.log <==
[INFO ] [ab.event.ThingStatusInfoChangedEvent] - Thing 'shelly:shellyblubutton:BLUETOOTH_MACADDRESS' changed from UNINITIALIZED (HANDLER_CONFIGURATION_PENDING): {deviceAddress=The parameter is required.} to INITIALIZING
Didn’t find a text file example, so here is one:
Thing shelly:shellyblubutton:BLUETOOTH_MACADDRESS "Shelly BLU button Red" @ "Zolder" [deviceAddress="BLUETOOTH_MACADDRESS"]
Gives a warning about an inconsistent model though? But is working fine:
shelly:shellyblubutton:BLUETOOTH_MACADDRESS:status#button triggered SHORT_PRESSED
Things seems to be silent, but we are working in the background.
Short update on PRs
We need 2 more PRs to get the list up to the DEV level before I continue implementing new features
Said that:
The best thing you could contribute is testing. I’ll update the DEV build to include the changes from the review process and let you know.
Thanks a lot for your effort and also to @Lolodomo!
Hello Markus,
thank you for your efforts.
If you have time, could you please also check the following error.
Yesterday I installed a shellyplus1 with the plus-addon. According to the documentation 5 temperature sensors are supported.
This also works in the Shelly app, but in Openhab I can add a maximum of 3 temperature sensors.
Yes, I have read that I could integrate sensors 3 and 4 via MQQT, but I don’t think that’s a clean solution.
Maybe you can fix this error please.
Thank you!
I updated the DEV build for 4.1-SNAPSHOT. Due to changed package dependencies this will no longer work on 4.0.
This version includes the latest functions and changes from PR review. It would be great to get some feedback = testing to make sure having a solid basis moving forward.
WD users fyi: I’m still investigating the Wall Display with @igi Even with firmware 1.2.5 we see tons of mDNS advertisements, which are processed by the binding without NPEs or resource leaks (which is great), but also creates a lot of useless traffic. Who else has a WD with 1.2.5 and wants to share observations (run Wireshark and check frequency of mDNS traffic)?
which version of the binding are you using? DEV build?