Domoticz

Of cource you can't, but I cant find any log file. What should I do to get a log file?

Also try to use the button as activator to a scene/group to see if that works
And maybe upgrade to Zigbee2MQTT?

What do you have in the Domoticz logs ?

In the Zigbee for Domoticz Plugin home directory, could you kindly do the following command and share it in the post
You can also try that as I think you have installed Z2M. It might be good to stop it (thanks for @gizmocuz to pointed out that)

gizmocuz wrote: ↑Sunday 05 February 2023 15:24 Also try to use the button as activator to a scene/group to see if that works
And maybe upgrade to Zigbee2MQTT?

There is no difference in behavior of a ikea Tradfri button behavior between zigbee2mqtt or ZigbeeforDomoticz plugin... You need to add it into a Zigbee group.

Now I've got even more problems. I took the RPi down clean to check what version of Zigate I really have. Took out the Zigate board and it says Ver 1.2.
When I start up the RPi again, it says "failed to load overlay pi3 = disable-bt" and very low screen resolution. It has never done that before. Clean restart again and now it starts with full resolution, but still the error message about overlay.

I will post a log as soon as it starts as it should again. About Z2M. I have never installed anything with Z2M. I have just followed the Wiki installation guide for Zigate on RPi3.

try updating your system (and firmware). Could be you updated your system some time ago, and just rebooted, and now facing this issue

Updated Raspian. Still error code on boot. This feels like something with Raspian, not Domoticz or Zigate. The error code comes when booting the RPi and mentions overlay that was changed to turn off Bluetooth according to Wiki guide. I can't see how this could have anything to do with Zigate firmware. The firmware worked before and isn't changed since.

gizmocuz wrote: ↑Monday 06 February 2023 9:03 Could be you updated your system some time ago, and just rebooted, and now facing this issue

Do you mean that the problem was really inserted with the update and then showed up on reboot?

Then no, I don't think so. The RPi was rebooted several times between last update and when it went sour.

Thanx anyway for the suggtions. I'm greatfull to all people who cares to help.