Osram Smart+ Plugs cannot be switched on/off in V2_05_66

[Markkuuss]

Yesterday I updated to the latest version V2_05_66. Since then, my two Osram Smart+ Plugs no longer work correctly. A timeout occurs when switching via the on/off cluster. That goes so far that the devices lose their zigbee connection afterwards. I can only switch on the devices by switching on the group they are in.

I have read on the Internet that newer firmware versions of Osram Plugs can cause problems. My plugs have versions 1.04.12 and 1.04.90.

Can anybody reproduce a similar problem with the Osram Smart+ Plugs?

[manup]

Which firmware version are you using?

When using the On/Off cluster directly it should always work, since the commands will be send directly to the plug. I'll check later if I can reproduce this with my OSRAM Smart+ plug.

[Markkuuss]

I am using firmware version 26330500.

It is also not possible to read the attributes of the OTAU cluster.

Can you please tell me which firmware your Smart+ Plugs have?

[manup]

It's the European version V1.04.12.
I can currently just control it remotely from the office but this seems to work.

[manup]

Have you tried to power-cycle the plugs?
Do the other lights in the network work?

[Markkuuss]

Have you tried to power-cycle the plugs?

Yes, without success.

Do the other lights in the network work?

Yes, several of dresden elektronik, ubisys, philips, ... They all work. Only the two Osram plugs cause problems.

I just reset one of the two nodes with F5 in deconz. Normally the node acts as a ZLL. Now it is displayed as follows:

[Markkuuss]

It's the European version V1.04.12.

So the same version as me.

What about deconz? Do you also use the latest version and the latest firmware of the Raspbee?

[Philje123]

I also had a problem with my Osram Plug. I couldn't control it anymore after updated deconz to 2.05.66.

My plug has firmware version V1.05.11.

I deleted it and re-added and it's been fine since.

[Markkuuss]

I'm now back at 2.05.65. That didn't help at first. Then I reloaded the firmware (according to the description), now the Osram plugs are reachable as usual.

@Philje123: What do you mean by "deleted"?
This one:

Or did you set the plug to factory settings?

[pergolafabio]

i am also on 1.04.12 (eu)
i see newer versions here like 1.04.90 1.05.11

how to update those osrams? i have issues with it if my xiaomi sensors are connected to it

[Philje123]

I deleted the plug via the phoscon web page.

I have an Osram lightify Hub so updated my osram products via that before pairing with deconz.

[pergolafabio]

ah ok , you saw some release notes in there ? , so 1.05.11 is latest one?

[Markkuuss]

1.04.90 is on my Osram Smart+ Outdoor Plug. But I think that is the same hardware as the indoor only in a different case.

An update is probably only possible via the Osram Hub, since the firmware files are only available for download as encrypted .bin files. Or is anyone familiar with another solution?

[pergolafabio]

i hope for another solution :)
dont want to buy a hub, only for upgrading :)

[pergolafabio]

i dropped osram a support mail, but not hoping for a good reply anyway :)

[Philje123]

Yeah I only got the hub as my local supermarket were selling a load of Osram stuff off cheap and only paid £12 for it. It's come in handy as I have quite a few Osram bulbs etc.

[pergolafabio]

you also have xiaomi motion sensors? seems there are issues with it in combination with osram , so maybe firmwares can help

[Markkuuss]

But isn't the update procedure very complicated? Could you explain it shortly, @Philje123 ? Do you have to set the Osram devices to factory defaults? You'll have to somehow remove them from the deconz network and then reinsert them? Do the Osram devices get a new ID after they have been reinserted into the deconz network after the update?

[Markkuuss]

i dropped osram a support mail, but not hoping for a good reply anyway :)

Please tell us the answer here.

[pergolafabio]

Yeah, once I receive a reply ;)

[pergolafabio]

with googling i was able to find the directory to those encrypted bin files :)
http://s3-eu-west-1.amazonaws.com/lightify-osram-firmware/
and here is the link to the release notes for that 1.04.90 and 1.05.10

http://s3-eu-west-1.amazonaws.com/lightify-osram-firmware/firmware/release/Cloud/Release_notes/Plug%2001.txt

[pergolafabio]

also, got response from lightify, already asked if possible to send me the unecrypted files :)

thank you for your request. Unfortunately the LIGHTIFY devices can be updated only via the LIGHTIFY Gateway with the LIGHTIFY App.

[pergolafabio]

and another reply from another osram team :-)

**The firmware of SMART + products can also be updated via the third-party systems from Qivicon and Samsung Smart Things. Please ask for the possibility and the necessary steps at the respective manufacture**r.

[Markkuuss]

These are exactly the answers that can also be found in the Osram FAQs. Maybe you should ask Qivicon and Samsung Smart Things? ;-)

[pergolafabio]

:-)

i dont have that hardware , so its a nogo anyway

[timbru31]

I've sent a support request to SmartThings. 🤞

---

Edit: SmartThings told me to buy/use their hub. 🙄
I've asked Qivicon/Telekom now

——

Edit2: Telekom Community is just like: stop whining, by their gateway... 🙄
No official response yet

[manup]

By looking at the firmware files I figure these just need to be extended with the proper Zigbee OTA header. Normally it doesn't matter if OTA files are encrypted since the data is only passed through and handled by the receiving device.

[pergolafabio]

ok, i can try to update one of my osrams, but never done this before
ist there a guide? can it be done with then GUI application or command line like upgrading conbee stick ?
i am using marthoc addon

[timbru31]

By looking at the firmware files I figure these just need to be extended with the proper Zigbee OTA header. Normally it doesn't matter if OTA files are encrypted since the data is only passed through and handled by the receiving device.

I've tried to load the file in the OTAU Plugin, but it did not load correctly.
Would you shed some light on the proper Zigbee OTA header? (I'm too lazy to dig up the Zigbee spec again)

[alp-by]

Btw... sometimes my osram plug is getting gray and not available (it doesn't work from domoticz)
Physically it's located quite close to my server with Conbee II stick.

Is it because of device or is it an issue with Conbee II ?

[alp-by]

just FYI. I had to play with location of my zigbee stick.

As soon as I took it out from backside of the server (it was installed there, near Zwave stick) and put more in the front - the signal quality became much better!
Pay a lot attention of your Conbee stick location.

At the moment I am in the testing mode: 6 hours - works quite fine

[kugelkopf123]

just FYI. I had to play with location of my zigbee stick.

As soon as I took it out from backside of the server (it was installed there, near Zwave stick) and put more in the front - the signal quality became much better!
Pay a lot attention of your Conbee stick location.

At the moment I am in the testing mode: 6 hours - works quite fine

As far as i know, deconz suggest a usb extension cable for the conbee stick. And you should have look at your WiFi Network. On witch channel it is, to find a good channel for your Zigbee Signals.

[Adminiuga]

And preferably on USB2 port without any USB3.0 devices nearby.

[alp-by]

just FYI. I had to play with location of my zigbee stick.
As soon as I took it out from backside of the server (it was installed there, near Zwave stick) and put more in the front - the signal quality became much better!
Pay a lot attention of your Conbee stick location.
At the moment I am in the testing mode: 6 hours - works quite fine

As far as i know, deconz suggest a usb extension cable for the conbee stick. And you should have look at your WiFi Network. On witch channel it is, to find a good channel for your Zigbee Signals.

yes, firstly I tried with USB extension cable, but it wasn't long enough :)

And preferably on USB2 port without any USB3.0 devices nearby.

Correct, also read about it. I use esxi with usb2.0 emulation ... not sure if it switches the physical port to USB2.

[alp-by]

well... additional test showed me that sometimes I take about 140-150 mins timeout from my xiaomi temperature sensors :(

[kugelkopf123]

Afaik it sends only changes. Perhaps there wasn’t any changes in temperature within this time?
Never had any problems with osram and Aqara multisensors. Only when the battery got a bit to low. Then I got wrong values.

_{Sent with GitHawk}

[alp-by]

Afaik it sends only changes. Perhaps there wasn’t any changes in temperature within this time?
Never had any problems with osram and Aqara multisensors. Only when the battery got a bit to low. Then I got wrong values.

Sent with GitHawk

By now: 650 mins with no update ... it should be the changes with temperature

[kugelkopf123]

Ever checked the lqi in the deconz gui? Perhaps it is not in range?

_{Sent with GitHawk}

[alp-by]

Ever checked the lqi in the deconz gui? Perhaps it is not in range?

Sent with GitHawk

how to do it?

[kugelkopf123]

https://flemmingss.com/wp-content/uploads/2019/08/deconz_gui_in_vnc_viewer.jpg on the top bar next to CRE.
Than you can see the quality of the connection. But you can also see it by the Color of the lines. If it is red, it’s bad...

_{Sent with GitHawk}

[alp-by]

https://flemmingss.com/wp-content/uploads/2019/08/deconz_gui_in_vnc_viewer.jpg on the top bar next to CRE.
Than you can see the quality of the connection. But you can also see it by the Color of the lines. If it is red, it’s bad...

Sent with GitHawk

well...that's my case:
The sensor where I receive no data has no line :(

[kugelkopf123]

https://flemmingss.com/wp-content/uploads/2019/08/deconz_gui_in_vnc_viewer.jpg on the top bar next to CRE.
Than you can see the quality of the connection. But you can also see it by the Color of the lines. If it is red, it’s bad...
Sent with GitHawk

well...that's my case:
The sensor where I receive no data has no line :(

Too far away from one of the routers? You should pair the sensors at the place where they are going to stay. Do not pair them next to your conbee and take the Sensor afterwards away to another place. The Aqara sensors are really bad in making new connection ways.
So if the osram plug is your nearest router to your sensor, then try to rejoin the sensor there.

[alp-by]

https://flemmingss.com/wp-content/uploads/2019/08/deconz_gui_in_vnc_viewer.jpg on the top bar next to CRE.
Than you can see the quality of the connection. But you can also see it by the Color of the lines. If it is red, it’s bad...
Sent with GitHawk

well...that's my case:
The sensor where I receive no data has no line :(

Too far away from one of the routers? You should pair the sensors at the place where they are going to stay. Do not pair them next to your conbee and take the Sensor afterwards away to another place. The Aqara sensors are really bad in making new connection ways.
So if the osram plug is your nearest router to your sensor, then try to rejoin the sensor there.

Too far away from one of the routers? - it shouldn't - in my eyes. That's why I bought osram + plug and put it in between .... in order to have additional repeater.

I didn't know about the paring at the place where they are going to stay. I paired it near the router and than brought away from it to the "right" location place. But it worked before ... I mean several days ago it worked quite good with getting update quite regular. I will also try to replace the battery, but the previous battery status (that I saw) was more that 50-60%.

[Adminiuga]

Xiaomi are picky about their parent device. Osram would not hold xiaomi sensor as they don't check in often enough. See https://community.hubitat.com/t/xiaomi-aqara-devices-pairing-keeping-them-connected/623

[kugelkopf123]

Yes. Good link! Really try replace the battery. Would be bad if you try so much and later on was the only problem a low battery.

_{Sent with GitHawk}

[alp-by]

Xiaomi are picky about their parent device. Osram would not hold xiaomi sensor as they don't check in often enough. See https://community.hubitat.com/t/xiaomi-aqara-devices-pairing-keeping-them-connected/623

well... according to this info it should work with "OSRAM/Sylvania LIGHTIFY" OSRAM Smart+ Outlet - model AB3257001NJ (UK & EU only) ... that's exactly what I have.

Yes. Good link! Really try replace the battery. Would be bad if you try so much and later on was the only problem a low battery.

Sent with GitHawk

Didn't work. With new battery the same issue - no connection.

[kugelkopf123]

Then I have no idea. The combination of Raspbee with 8x Osram smart+ Plugs and 8x Aqara Multisensors and Window / Doorsensors works for me.
60% of the sensors are not in the area of the Raspbee.
Never had any problems with it, no matter which deconz firmware.

Due to the fact that the Aqara sensors do not like to reconnect after restarting the Raspbee it may be necessary to short press the button on the sensor 1-2 times so that it reconnects.
Thats it.

[alp-by]

Due to the fact that the Aqara sensors do not like to reconnect after restarting the Raspbee it may be necessary to short press the button on the sensor 1-2 times so that it reconnects.
Thats it.

did it .... got it connected and saw updated data.... will check how it goes afterwards

The distance between my osram +plug (repeater) and my "problem" Aqara sensor is 5 meters with glass and wood construction between.
The distance between the same plug (repeater) and my "good" Aqara sensor (regular updating from it) is about 3 meters and concrete wall between

[alp-by]

well...I put my osram+plug (repeater) quite close to my "problem" sensor. 2 meters distance with a window between only :) ... let's see. Osram+plug works good at this location

[alp-by]

well... closing location to "problem" sensor gave me regular updates from it. But now I get some missing info from prev-'good' sensor. Sometimes I get the timeout from it.
So, I can make the conclusion that Aqara sensors don't have strong enough translation and need help in passive repeaters.

[alp-by]

well... small update: 1 week test. ("bad" sensor located near passive repeater)
Sometimes I still lose the connection with my "bad" sensor and get timeouts ...
I have a feeling that my Osram +Plug just goes in sleep mode after N hours and/or stops resending signals from "bad" sensor.

I will try to make the regular check (1 time in 2-3 hours) in order to "activate" Osram +Plug i.e. switch in On\Off.

[kugelkopf123]

Would also suggest to add more active items to your mesh. Such as lightbulbs and more outlets.

_{Sent with GitHawk}

[alp-by]

Would also suggest to add more active items to your mesh. Such as lightbulbs and more outlets.

Sent with GitHawk

Ok. At the moment my current OSRAM +Plug sometimes getting "grey" at Phoscon application.

I have already ordered additional OSRAM + Plug to integrate it on my network. So... I will have more "active" devices there.
Also thinking to make router on CC2531 (https://www.zigbee2mqtt.io/how_tos/how_to_create_a_cc2530_router.html)
or will try to replace my conbee II with CC2531 device with the corresponding flashware.

[alp-by]

I will try to make the regular check (1 time in 2-3 hours) in order to "activate" Osram +Plug i.e. switch in On\Off.

1 day testing (I did it so: every hour my domoticz changed the state of it i.e. switch it ON and OFF). Didn't worked for 100%. After several hours it's getting "grey" in Phoscon.... very strange behaviour

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[mhristache]

Was there a conclusion? I am having similar issue with an Osram outdoor plug. Thanks

[Adminiuga]

Sometimes osram plugs do that. Power cycle them.