Same issue here after upgrading to OS 4.8 nothing works. Tried setting to /dev/ttyS0 but it reconnects every few seconds…does somebody have the same issue?
Have you tried integrate it again?
How does that work?
I noticed that from time to time the Firmware jumps from “not connected” to “00000000” and then it wants tu upgrade the firmware in phoscon app.
Can you see it in hardware?
I was using AMA0 before, now i tried to use it with S0 but that doesnt work.
Hardware is a Raspberry 3B and RaspBee (first version)
So you cant reach deconz in HA either? Try with dev/ttyS0 ord dev/ttyAMA0 and restart deconz, then try to enter deconz, go to setting and authenticate app, then integrate deconz again in HA
will there a fix before its dark, my whole house is now without lights?
How to downgrade HassOs to a working deconz?
DeConz is reachable with Phoscon App:
When trying to connect with VNC it connects for a short time an also displays my ZigBee network but then it looses connection again…
I reintegrated it but that doesnt change anything… the problem lies below, it is not the connection between HA and DeConz but between the gateway and DeConz
can you tell the exact steps
Is conbee connected direct in usb? Or do you use an extension cable?
If it helps: my conbee 2 is directly in USB (3.0). I can reach deconz from home assistant. However, within deconz I don’t see status change if a door opens or closes. So indeed the problem seems to be there.
It worked perfectly before updating.
So changing to USB 2.0 and again reintegrating did not work either. I migrated to ZHA and that works.
Thank you,
changed from /dev/ttyAMA0 to /dev/ttyS0 and reboot system did the tricks and now my RaspBee works again.
It worked also for me! Many thanks! Just for curiosity, how did you retrieve the new RaspBee device address?
You can look up the serial devices on the Supervisor -> System -> Host system -> Hardware page.
1 Like
Today i lost my Fyrtur… i have done no changes since yesterday… I saw it was an new update, so i tried that. But no luck, any one now whats going on?
Talking to myself! Fixed it again…
This might help? Happened to me again after 4.8 update.
For me everything is working agaein after the kernel downgrade. 