IKEA STYRBAR pairing issues

I've been using IKEA Styrbar remotes for some time wihtout issue. I've recently upgraded a couple with new firmware (V-1.0.024 to V-2.4.5) - and this seems to affect pairing. The previous version paired, altmatically picking up the STYRBAR driver [Beta] [Release] Ikea Styrbar. The new version pairs as a DEVICE, and does not recognise button presses.

Has anyone expereinced the same, or found a workaround/fix?

Many thanks,

Logs of the new firmware

dev:164402023-02-09 11:59:11.651 AMdebuggetting info for unknown Zigbee device...

dev:164402023-02-09 11:58:49.307 AMinfofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0003,0020,1000,FC57,FC7C", outClusters:"0003,0005,0006,0008,0019,1000", model:"Remote Control N2", manufacturer:"IKEA of Sweden"

dev:164402023-02-09 11:58:48.369 AMtraceZCL version:08

dev:164402023-02-09 11:58:48.362 AMtraceSoftware Build Id:2.4.5

dev:164402023-02-09 11:58:48.360 AMtraceModel:Remote Control N2

dev:164402023-02-09 11:58:48.354 AMtraceManufacturer:IKEA of Sweden

dev:164402023-02-09 11:58:47.750 AMdebuggetting info for unknown Zigbee device...

dev:164402023-02-09 11:58:46.986 AMinfoZigbee parsed:[raw:catchall: 0104 0003 01 FF 0040 00 864F 01 00 0000 01 00 , profileId:0104, clusterId:0003, clusterInt:3, sourceEndpoint:01, destinationEndpoint:FF, options:0040, messageType:00, dni:864F, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]

dev:164402023-02-09 11:58:45.642 AMdebugconfigure() called...

DEVICE just means unrecognized fingerprint. Can you change the driver to the one your other ones are using, click save, then click configure? Then open a live log and start pressing buttons after a few mins. It should work.

1 Like

No button presses are being logged. Same driver on earlier firmware register button presses instantly, as soon as the device is configured.

dev:164402023-02-09 12:04:15.783 PMwarnConfiguring Reporting and Bindings.

dev:164402023-02-09 11:59:11.651 AMdebuggetting info for unknown Zigbee device...

dev:164402023-02-09 11:58:49.307 AMinfofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0003,0020,1000,FC57,FC7C", outClusters:"0003,0005,0006,0008,0019,1000", model:"Remote Control N2", manufacturer:"IKEA of Sweden"

dev:164402023-02-09 11:58:48.369 AMtraceZCL version:08

dev:164402023-02-09 11:58:48.362 AMtraceSoftware Build Id:2.4.5

dev:164402023-02-09 11:58:48.360 AMtraceModel:Remote Control N2

dev:164402023-02-09 11:58:48.354 AMtraceManufacturer:IKEA of Sweden

dev:164402023-02-09 11:58:47.750 AMdebuggetting info for unknown Zigbee device...

dev:164402023-02-09 11:58:46.986 AMinfoZigbee parsed:[raw:catchall: 0104 0003 01 FF 0040 00 864F 01 00 0000 01 00 , profileId:0104, clusterId:0003, clusterInt:3, sourceEndpoint:01, destinationEndpoint:FF, options:0040, messageType:00, dni:864F, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]

dev:164402023-02-09 11:58:45.642 AMdebugconfigure() called...

Did you press configure on the device page?

yes.
dev:164402023-02-09 12:04:15.783 PMwarnConfiguring Reporting and Bindings.

1 Like

@mike.maxwell any thoughts?

I would add the new fingerprint to the existing driver, then reset, re join the device.
If that doesn't work you're going to have to reach out to the original driver author to see if he has an update that works with the new device firmware.

The device joins, it just doesn't work any longer with the OP's driver.

3 Likes

Thanks Both for your suggestions,

I ammended the new fingerprint into the existing driver. The new firmware devices join as Styrbars, but still no joy on capturing button presses (except once, as shown - very strange)

dev:164412023-02-10 09:07:00.783 AMinfoButton 4 pushed - Bottom button

dev:164412023-02-10 09:07:00.780 AMdebugCatchall: 0, 6, 0, [2, 253, 255, 4, 1, 1, 25, 0, 0]

dev:164412023-02-10 09:07:00.775 AMdebugcatchall: 0000 0006 00 00 0040 00 228D 00 00 0000 00 00 02FDFF040101190000

dev:164412023-02-10 09:07:00.774 AMdebugParse returned [:]

dev:164412023-02-10 09:07:00.772 AMdebugParse description catchall: 0000 0006 00 00 0040 00 228D 00 00 0000 00 00 02FDFF040101190000

dev:164412023-02-10 09:04:36.554 AMdebug[[he raw 0x228D 1 0x01 0x0001 {10 00 00 20 00}, delay 2000], [he raw 0x228D 1 0x01 0x0001 {10 00 00 21 00}, delay 2000]]

dev:164412023-02-10 09:04:36.547 AMinfoRefresh pushed... Attempting to read battery

dev:164412023-02-10 09:04:36.542 AMwarnConfiguring Reporting and Bindings.

dev:164412023-02-10 09:04:20.731 AMdebugCatchall: 1, 3, 1, []

dev:164412023-02-10 09:04:20.728 AMdebugcatchall: 0104 0003 01 FF 0040 00 228D 01 00 0000 01 00

dev:164412023-02-10 09:04:20.727 AMdebugParse returned [:]

dev:164412023-02-10 09:04:20.725 AMdebugParse description catchall: 0104 0003 01 FF 0040 00 228D 01 00 0000 01 00

dev:164412023-02-10 09:04:17.703 AMdebug[[he raw 0x228D 1 0x01 0x0001 {10 00 00 20 00}, delay 2000], [he raw 0x228D 1 0x01 0x0001 {10 00 00 21 00}, delay 2000]]

dev:164412023-02-10 09:04:17.698 AMinfoRefresh pushed... Attempting to read battery

dev:164412023-02-10 09:04:17.692 AMwarnConfiguring Reporting and Bindings.

dev:164412023-02-10 09:04:17.603 AMwarndescription logging is: true

dev:164412023-02-10 09:04:17.602 AMwarndebug logging is: true

dev:164412023-02-10 09:04:17.600 AMinfoupdated...

dev:164412023-02-10 09:04:17.588 AMdebug[[he raw 0x228D 1 0x01 0x0001 {10 00 00 20 00}, delay 2000], [he raw 0x228D 1 0x01 0x0001 {10 00 00 21 00}, delay 2000]]

dev:164412023-02-10 09:04:17.582 AMinfoRefresh pushed... Attempting to read battery

dev:164412023-02-10 09:04:17.574 AMwarnConfiguring Reporting and Bindings.

dev:164412023-02-10 09:04:17.570 AMwarnCan't parse SmartShield(text: null, manufacturerId: 0x0000, direction: 0x00, data: [0x05, 0x00, 0x42, 0x11, 0x52, 0x65, 0x6d, 0x6f, 0x74, 0x65, 0x20, 0x43, 0x6f, 0x6e, 0x74, 0x72, 0x6f, 0x6c, 0x20, 0x4e, 0x32], number: null, isManufacturerSpecific: false, messageType: 0x00, senderShortId: 0x228d, isClusterSpecific: false, sourceEndpoint: 0x01, profileId: 0x0000, command: 0x01, clusterId: 0x0000, destinationEndpoint: 0x00, options: 0x0000)

I'll post in the original driver thread, and have a play myself.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.