Thank you @markus7017 : can you check this?
https://shelly-api-docs.shelly.cloud/docs-ble/Devices/wall_us
looks like it is updated also for the other buttons.
Thank you
Any updates for Plus Uni
Oh? Itās the UNi not supported? Crap I wanted to use it in my door bellā¦
Just the āPlusā Uni. The regular Uni works very well ![]()
It is correct, the Shelly uni is working fine but the Shelly plus uni has a problem.
Considering ther is a shelly plus uni Iā would think to use it for new project as they probably not continuing generation 1 devices as the shelly uni.
Ha Markus,
Thanx for the reply and explaination.
Iām using the event trigger channel now, that one updates at every button press regardless of the prior press.
Best regards, Jesse
Hello, I have the same problem as already more people did ask an solution for it.
I will explain as much as i know and i hope for an solution .
I did ask Shelly, the answer was that the problem is in Openhap.
I did explain the problem already many, no answer
**Shelly Plus 2PM works fine (but i use Openhab! **
Openhab 4.2.0 the binding is not OK for the optie Cover used by Rollers
- I had over the years a raspberry PI4 with OpenHAB 3xx til 4.2.0 working fine for many years with plugwise plugs.
- Last year i did go to an PI5 with OpenHAB 4.2.0
- After install everything works fine again
- Then i started with Shelly moduleās. Many Plus i4, Dimmer2, Plus 2PM installed in my home.
- Most of the 2PM are for Rollers ( setup 2PM as Cover)
Final status for 1 month ago was that everything was working fine.
Then i saw that my 2PM did have FW 1.0.7 and I started with update for all Shellyās to the last stable version 1.4.2.
The most Shelly moduleās had no problem with it.
Only the Shelly Plus 2PM, the ones in the OH binding where not seen any more and the ones already working in OH :
But the one i did not update is still working fine
Then i started reading , asking but no result !
Then i started new with one Shelly Plus 2PM with FW 1.4.2
factory reset. as i was started for years ago.
- factory reset start IP 192.168.33.1
- By mobile I go to Wifi and set my static IP (192.168.0.36), Sub, GW and DNS SAVE !
- I dit go to the webpage off the 2PM on 192.168.0.36 and seem OK.
- Settings : only Wifi !

So after factory reset the 2PM is seen in the web and in the OH binding !
- The 2PM is standard setting on Switch.
- all the testings for the 2PM as Switch, seen in the openhab binding , seen in Openhab by things scrips and scheduls are working everything looks fine for me.
BUT THEN : i have to change from Switch to Cover for my Rollers.
I did the changing 2 times again from factory reset because i can change directly in the webpage from the 2PM or later on when it is imported in OH.
1 - Factory reset and the standard settings !
-
2PM OK in the web
-
Before i changed to Cover, the 2PM is seen in OH binding

-
then i switched the 2PM to Cover and directly the 2PM is disappeared in de OH binding.
after new scan it stil is disappeared
2 - Factory reset and the standard settings !
The same happen 's if you do not Factory setting but you go back chancing from Cover to switch.
- 2PM OK in the web
- Seen in OH , import in OH everything goes fine

But stil it is an switch ! Relay mode


I can not change it to Cover in OH
If i change it in the web than noting happenās in OH it still is a Switch for OH
The one with FW 1.0.7 is still working that what i need,
Hi everyone,
I just got a new Shelly Pro 2. After setting it up and trying to include it in openhab 4.2.2, I figured out, that auto discovery isnāt able to find the correct device type and the thing is not usable.
CONFIGURATION_ERROR
The IP address of the Shelly device is not configured.
Thing Type:
Unknown Shelly Device
But, I am able to set it up manually by choosing Shelly Pro 2 as Device. So I am able to use the device. But auto discovery is shown that unknown device. After reading some documentations, I figured out, that the Vendor ID of my Device is SPSW-202XE12UL which is not in the documentation and perhaps is not in the list of device for the pro 2 in the bindings code.
I am using the latest firmware 1.4.2 on the Pro 2 in Relay mode and I am using the included binding version from openhab 4.2.2.
Perhaps this issue is related to the 2PM problem and firmware 1.4.2?
Same problem here, since I updated a ShellyPlus2PM today to Firmware 1.4.2 when used as cover. I have several ohter ShellyPlus2PM in use as Switch with Firmware 1.4.2, they work as expected. As far as I know a firmware downgrad is not possible, so I have to change the ShellyPlus2PM to an old Shelly 2.5
Never touch a running systemā¦
I did give up Openhab !
I do not know whatās the problem is in this community to answer an questions wat already many people were asking for over more then 2 month.
I did after many years switch to Home Assistant. ![]()
The problem with the 2PM as cover was also there but solved in a few days.
It is working fine there..
In 3 hours I had al my Shelly moduleās working in HA as normal ![]()
So i am now learning scripting in HA but that will also be good and nice i think.
??? Congratulations�
I did ask this al ready 2 month and no answer ? Did you get an answer from somebody to solve the problem ?
Openhab is developed entirely by volunteers. If the developer for this binding (Markus) is currently not reacting then he has his own reason for this. All you (and others) can do is being patient. I am sure he will come back and fix the problems. Meanwhile it would be good if you can provide more details like a debug log.
If you cannot wait then revert back to the last combination (firmware version and openhab version) where you know it has been working.
If it is a new device, then downgrade from v 1.4.2 as this version is known to have problems as the API (I think) changed.
Just to let you all know, I am using about 9 Shelly Plus 2PM, all with latest 1.4.2 firmware and in roller shutter mode. I am using openhab 4.2.2 with included shelly binding version.
I do not have any issues with that setup. Perhaps the issue is related to the hardware revision of the device?
@Oliver2 ,
Thanks for the answer .
Thatās what many people who are new hier wanted to know. only 1 answer to know what is going on.
Many asking for the same problem but no one did get an answer dan i and the others do believe there is no one to help. And they wil ask again.
So for now we know we have to wait with a reason smile:
For me : I did already give all the things you ask for with a lot af pictures and an i did write a letter from starting with a new module Plus P2PM FW 1.0.7 (working fine) till after update to 1.4.2( working fine as Switch but not working anymore as Cover for Roller) witten the who going on till end. Written everything what goes write and were it goes wrong. I did also test an older version 1.3.3 the only version i did get from Shelly but also not working. I like to have back the version 1.0.7 for the time being . But Shelly tolt me not to have that one ?
I did tel this many times on many forums in about 2 months already.but no answer.
You are the first who did given an answer.
I have PI5 with Openhab but did already install Home Assistant on the old PI4 and test it there . Itās working fine there. But i have many (45) plugwise plugs in my home and the binding in Openhab works already many years very good and de binding in Home Assistant is not working and still an beta version.
So i will stay on with Openhab as already many many years.
@alaub81 Hello good to know . I am happy with your answer I have Openhab 4.2.0 Maybe you can tell us what you do to install the Plus 2PM and maybe i see what is go wrong or what maybe i do wrong.
Itās a long time since I installed the 2pms. But I think I did in that order:
- Set it up in the shelly app
- Firmware Update to the latest version, I can not remember which version that was
- configure the shelly 2pm as roller shutter in the shelly app
- added it in openHAB, normally the auto discovery is working fine there, so it was just in the inbox
after that I updated openHAB a few times until now and also, normally I do upgrades on my Shelly devices, too, if there are new versions.
If you need more details, just ask me.
No. I changed the shelly and wait until the problem ist solved
Excellent choice ![]()
I didnāt reply earlier because I thought that all users who had problems with 1.4.2 managed to get it workng anyway. I also have 3 shellyplus 2 and they are working fine in roller shutter mode.
In the end, you get it working either in the way Andreas described or you need to remove the thing, clean cache (channel links will be deleted, too, and you have to re-link the items), reboot pi, restart shelly.
After openhab is up and running wait a few minutes and watch the inbox. Typically the binding detects new devices pretty fast.
First i am very happy with answers
![]()
@momo90
OK, Yes thatās the way āOliver2ā told us !
Wait and there will be coming an answer soon.
@alaub81
Thank you for the answer , I did this many times the same as you.
The last change i made was change from PI4 with openhab 3.x to an PI5 with openhab 4.2.0
Everything started and was back in to the air all working.fine.
So also the Shelly Plus 2PM was working on FW 1.0.7 everything fine.
Then i saw an Final FW 1.4.2 for some Shelly modules also for the Shelly Plus 2PM and i installed it.
After that everything was working fine except for Shelly Plus 2PM use as Cover for Roller.
Shelly Plus 2PM is working fine as switch.
So the difference we have is the openhab version ! I have 4.2.0 and you have 4.2.2
So can you tell me is it difficult to change to 4.2.0 I am not that good with Openhab installing.
@Oliver2
No if you look around for problems with the Plus 2PM but only used for Cover for Roller ! As switch it working fine.
What you do say that all i have don and i did write all for everyone to read..
except clean cache , i do not know where.
It was al working till after Shelly update for the 2PM from 1.07 over 1.3.3 to 1.4.2.
And Yes openhab binding is fast also for Plugwise i am very happy with openhab .
The Home Assistant people are toking for an plugwire binding startup from some hours .
Start ssh session and execute the following commands:
sudo systemctl stop openhab
sudo openhab-cli clean-cache
sudo systemctl start openhab
but follow the order described as above.
I guess you have a snapshot binding installed?
In this case you need to wait until openhab is running and then reinstall coap services:
sudo openhab-cli console
password is habopen
then:
feature:install openhab-transport-coap
It is worth a try. There are many who got it working. Also try to run through the whole procedure 2 or 3 times.




