I would even suggest to always use the dev-binding. It always includes the latest bug fixes and supports new devices earlier than the release version.
I just remember once when there was a bug fix included in the release version of the binding and not in the dev-version. The reason was that a different developer than Markus did a quick bug fix for a fresh openhab release.
Recently a PR of mine was merged into the main branch. I do wonder what will happen to my contribution after Markus pushes his new version 
It will still be thereâŚ
I tried mvn clean install after cherry-picking your commit, but encountered a lot of errors. Maybe your changes are incompatible with OH 4.3.x? I couldnât figure it out in the limited time I hadâŚ
Is this only for OH 5?
I run into this issue with OH 4.3.5. What can I do to get the shelly back work?
Do you plan to implement the fix also for OH 4.3.5?
Harald
Iâve just added a Shelly Plus Uni with 5 temp sensors (DS18B20) so I can automate my domestic hot water heating.
The Shelly binding can discover the device but there is a communication error. (I think it is looking for a /settings page)
What do I need to do to get this working - Iâm new to OpenHAB.
This is the authentication of the shelly device and not specific to API calls. If you havenât configured a password for your device, leave it blank in the dialog you posted.
In case you are using the same user/password for all your devices go to addon settings and enter details there. Then you can leave this dialog box empty.
I have a password thatâs clear but no user idâŚwhere do I finde the user on Shelly?
This is only optional.
If you don`t have set a restricted access to your shelly, you do not need to fill the fields out.
I you have set a username and password to you shelly, please use this also in the thing setting
in you OH installation.
This username and password is depending from your shelly.
Older model like the shelly 1 has username and password, newer gerneration only have password.
So please check, if you have the latest binding installed, and if you have choosen the right shelly product by adding them to OH.
New:
Old:
i am using the version on github
this is my configuration
Thing shelly:shellyplus1pm:d4d4da7cbde0 "Shelly One" @ "Bedroom" [deviceIp="xxxxx", password="xxxxx"]
but I canât find the channels any more
The thing Status is probably âNot yet readyâ
If you are using Shelly binding 4.3.6-snapshot, replace it by the release version of the binding.
4.3.6 was not working at all on my system
I am on Oh 5.x snapshot build
@falkena, I now realize I didnât address the actual author⌠Is there a reason I failed at making a jar for 4.3.x?
1 Like
I updated the Dev Build
â˘â â Fix for Plus2PM Discovery im Roller-/Cover-Mode
â˘â Support â â Shelly 1/1PM Gen4
â˘â â â Support Shelly Mini 1/1PM Gen4 und EM
â˘â â â New channel meter#frequency (advanced)
â˘â â â Bugfix for firmware 1.6.1 (id not set on status updates)
I did only general testing, keep an backup of your current version.
Check READMEbeta to learn how to install the DEV build.
Please help testing.
5.0.0-DEV | 4.3.6-DEV | README | READMEbeta
Avdanced Users | Shelly Manager | Bugs/Features | API Doc
Note: The DEV build is always newer than the version in the official Distro or Milestone builds..
DO NOT USE THE 5.x build on 4.3 nor mix versions - this is a good source for side effects.
4 Likes
Minor issue: Those two links seem to be swapped
And one hint for those who donât want to (repeatedly) install californium manually: Just install the tradfri binding. It needs coap and therefore automatically installs californium. As tradfri is a release binding californium keeps being installed after updates or cache cleaning.
good catch 
I fixed them
any test results so far?
yes: v4.3.6 working flawlessly since a week with a lot of:
Shelly Plus 1
Shelly Plus 2PM
Shelly TRV
All on firmware 1.5.1 except TRV on 2.2.4
Can you check, when you try to add a new thing via the UI, if all devicetyps are listed?
For me it look only 20% of the Typs are listedâŚ
1 Like
