Tradfri Binding: cannot create working gateway (bridge)

Add-ons Bindings
3

It seems my tradfri binding has also stopped functioning. Very strange. I do not get any new errors (it says the gateway doesn’t have an IP at startup, but this was never an issue before)

Wonder if it is related to TRADFRI - lost functionality

Just some info:
I’m on openhab 3.2 (which fixes gateway disconnect issue according to this Tradfri gateway not reachable after update to 1.17.19)
I have reinstalled the tradfri binding, which did not solve my problem. Maybe I should reinstall openhab, or try the testing build? Anyone who is on a similar config?

This is the events log:

[INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Outlet1_Power' received command ON
[INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'Outlet1_Power' predicted to become ON
[INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Outlet1_Power' changed from OFF to ON
[INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Outlet2_Power' received command ON
[INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'Outlet2_Power' predicted to become ON
[INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Outlet2_Power' changed from OFF to ON
[INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Outlet1_Power' received command OFF
[INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'Outlet1_Power' predicted to become OFF
[INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Outlet1_Power' changed from ON to OFF
[INFO ] [openhab.event.ItemCommandEvent      ] - Item 'Outlet2_Power' received command OFF
[INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'Outlet2_Power' predicted to become OFF
[INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Outlet2_Power' changed from ON to OFF

But the problem is the outlets don’t change from ON to OFF or from OFF to ON in the real world.

The weird thing is, it works fine with HASS (the nemesis :wink: ), and in the IKEA TRADFRI app. So we can safely assume that openhab is part of the problem

One thing I do notice, which I didn’t before: it seems the .ItemStatePredictedEvent log entry drops the first ‘o’. Might point to a missed typo in the code?