Zigbee2mqtt: IKEA Fyrtur Kadrilj Blinds

Created on 19 Jan 2019  ·  140Comments  ·  Source: Koenkk/zigbee2mqtt

Hey. In a few days These new devices will be Released.
Will it be possible to Support Them. Because will be the First zigbee blinds? Or do you add code to Support blinds ?
Thx

stale

Most helpful comment

Device is supported in the dev branch now, credit go to @syphernl :smile;

All 140 comments

We can check when somebody gets their hands on one of them.

I will definitiv Buy as Soon as avaiable in Germany

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.

They are now available:

And promising for DIY: https://www.youtube.com/watch?v=tfJn6oNGF74

Please reopen

If somebody owns this device and wants to add support for it, we can reopen it.

Ok. A friend bought a couple of these.
We are going to add them to zigbee2mqtt asap.

However, looking through you website, I do not understand how to find out which commands are available to control and create the "toZigBee" converters.

Please provide some pointers.

There is some information about these blinds in this thread. It may be useful -> https://github.com/dresden-elektronik/deconz-rest-plugin/issues/1121

Two issues.

  1. Getting Ikea E1766 remote (Open/Close Remote) working.

Pairing as usual. 4 short pushed on the reset button on the back. Paired by holding close to signal repeater.

It reveals itself as model = modelID = "TRADFRI open/close remote"

Added to devices.js:

   {
        zigbeeModel: ['TRADFRI open/close remote'],
        model: 'TRADFRI open/close remote',
        vendor: 'IKEA',
        description: 'TRADFRI open/close remote',
        supports: 'up, down, release',
        fromZigbee: [ fz.genOnOff_cmdOn, fz.genOnOff_cmdOff, fz.TRADFRI_open_close_stop ],
        toZigbee: [],
        configure: (ieeeAddr, shepherd, coordinator, callback) => {
            const device = shepherd.find(ieeeAddr, 1);
            const cfg = {
                direction: 0, attrId: 33, dataType: 32, minRepIntval: 0, maxRepIntval: repInterval.MAX, repChange: 0,
            };

            const actions = [
                (cb) => device.bind('genPowerCfg', coordinator, cb),
                (cb) => device.foundation('genPowerCfg', 'configReport', [cfg], foundationCfg, cb),
            ];

            execute(device, actions, callback);
        },
    },

and into fromZigBee.js:

   TRADFRI_open_close_stop: {
        cid: 'closuresWindowCovering',
        type: 'cmdStop',
        convert: (model, msg, publish, options) => {
            return {click: 'closure_stop'};
        },
    },

However, I do not get any events nor warnings for regular button push. The stop function is activated by long-press any button.

Seems supported by deconz: https://github.com/dresden-elektronik/deconz-rest-plugin/blob/dc0d508d6a8c49d4cf59a3b72791f31f726d801b/sensor.cpp#L146

  1. FYRTUR blinds.

Pairing easy.:
Hold both buttons on blind for 5 seconds, release and hold close to repeater.

Reveals itself as:

Device with modelID 'FYRTUR block-out roller blind' is not supported.

Working on getting it working.

Any help on both appreciated.

I've installed two Fyrtur blinds this morning. After installing the blinds i've tried to add them to zigbee2mqtt but i experience the same issues as @osos.

Pairing was very easy but afterwards i didn't receive any event in zigbee2mqtt.

The Remote has a client Window Covering cluster, to send comands to the blind. This means that it can only control (directly) the blind, and that the blind cannot be controlled (directly) by the other control devices. Not too happy about the 0xFC7C cluster, which is probably used for some IKEA-specific configuration.
We need to sniff the specific configuration.

The remote reporting its battery percentage (cluster 0x0001, attribute 0x0021).

The FYRTUR does support attribute reporting for Battery Percentage Remaining (0x0001/0x0021) and, for Current Position Lift Percentage (0x0102/0x0008).
For this we also need configure reporting to see the actually lift state.

We could use also SW Build ID (0x0000/0x4000).

From what I see their should be a group ID where they act like we see from other ikea remotes.

@osos please share your database file content.

From database.db:

Open/Close remote:

{"id":8,"type":"EndDevice","ieeeAddr":"0x000d6ffffee3c176","nwkAddr":56685,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Battery","modelId":"TRADFRI open/close remote","epList":[1],"zclVersion":3,"appVersion":34,"stackVersion":98,"hwVersion":1,"swBuildId":"2.2.008","status":"offline","joinTime":null,"endpoints":{"1":{"profId":260,"epId":1,"devId":515,"inClusterList":[0,1,3,9,32,4096,64636],"outClusterList":[3,4,6,8,25,258,4096],"clusters":{"64636":{"dir":{"value":1},"attrs":{}},"genBasic":{"dir":{"value":1},"attrs":{"9":226,"10":{},"11":"","65533":1,"zclVersion":3,"appVersion":34,"stackVersion":98,"hwVersion":1,"manufacturerName":"IKEA of Sweden","modelId":"TRADFRI open/close remote","dateCode":"20190311","powerSource":3,"appProfileVersion":1,"swBuildId":"2.2.008"}},"genPowerCfg":{"dir":{"value":1},"attrs":{"65533":1,"batteryVoltage":29,"batteryPercentageRemaining":74}},"genIdentify":{"dir":{"value":3},"attrs":{"65533":1,"identifyTime":0}},"genGroups":{"dir":{"value":2},"attrs":{}},"genOnOff":{"dir":{"value":2},"attrs":{}},"genLevelCtrl":{"dir":{"value":2},"attrs":{}},"genAlarms":{"dir":{"value":1},"attrs":{"65533":1}},"genOta":{"dir":{"value":2},"attrs":{}},"genPollCtrl":{"dir":{"value":1},"attrs":{"65533":1,"checkinInterval":172800,"longPollInterval":1160,"shortPollInterval":4,"fastPollTimeout":40}},"closuresWindowCovering":{"dir":{"value":2},"attrs":{}},"lightLink":{"dir":{"value":3},"attrs":{"65533":1}}}}},"dateCode":"20190311","_id":"RcCUQl89Wv8qZqH2"}

Fyrtur:

{"id":9,"type":"EndDevice","ieeeAddr":"0x000d6ffffe2dea2f","nwkAddr":58822,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Battery","modelId":"FYRTUR block-out roller blind","epList":[1],"zclVersion":3,"appVersion":34,"stackVersion":99,"hwVersion":1,"swBuildId":"2.2.007","status":"online","joinTime":1567257368,"endpoints":{"1":{"profId":260,"epId":1,"devId":514,"inClusterList":[0,1,3,4,5,32,258,4096,64636],"outClusterList":[25,4096],"clusters":{"64636":{"dir":{"value":1},"attrs":{}},"genBasic":{"dir":{"value":1},"attrs":{"9":255,"10":{},"11":"","65533":1,"zclVersion":3,"appVersion":34,"stackVersion":99,"hwVersion":1,"manufacturerName":"IKEA of Sweden","modelId":"FYRTUR block-out roller blind","dateCode":"20190311","powerSource":3,"appProfileVersion":0,"swBuildId":"2.2.007"}},"genPowerCfg":{"dir":{"value":1},"attrs":{"65533":1,"batteryVoltage":0,"batteryPercentageRemaining":0}},"genIdentify":{"dir":{"value":1},"attrs":{"65533":1,"identifyTime":168}},"genGroups":{"dir":{"value":1},"attrs":{}},"genScenes":{"dir":{"value":1},"attrs":{}},"genOta":{"dir":{"value":2},"attrs":{}},"genPollCtrl":{"dir":{"value":1},"attrs":{}},"closuresWindowCovering":{"dir":{"value":1},"attrs":{}},"lightLink":{"dir":{"value":3},"attrs":{}}}}},"dateCode":"20190311","_id":"jrVKz4IB9fT3m443"}
{"id":9,"type":"EndDevice","ieeeAddr":"0x000d6ffffe2dea2f","nwkAddr":58822,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Battery","modelId":"FYRTUR block-out roller blind","epList":[1],"zclVersion":3,"appVersion":34,"stackVersion":99,"hwVersion":1,"swBuildId":"2.2.007","status":"offline","joinTime":null,"endpoints":{"1":{"profId":260,"epId":1,"devId":514,"inClusterList":[0,1,3,4,5,32,258,4096,64636],"outClusterList":[25,4096],"clusters":{"64636":{"dir":{"value":1},"attrs":{}},"genBasic":{"dir":{"value":1},"attrs":{"9":255,"10":{},"11":"","65533":1,"zclVersion":3,"appVersion":34,"stackVersion":99,"hwVersion":1,"manufacturerName":"IKEA of Sweden","modelId":"FYRTUR block-out roller blind","dateCode":"20190311","powerSource":3,"appProfileVersion":0,"swBuildId":"2.2.007"}},"genPowerCfg":{"dir":{"value":1},"attrs":{"65533":1,"batteryVoltage":0,"batteryPercentageRemaining":0}},"genIdentify":{"dir":{"value":1},"attrs":{"65533":1,"identifyTime":168}},"genGroups":{"dir":{"value":1},"attrs":{}},"genScenes":{"dir":{"value":1},"attrs":{}},"genOta":{"dir":{"value":2},"attrs":{}},"genPollCtrl":{"dir":{"value":1},"attrs":{}},"closuresWindowCovering":{"dir":{"value":1},"attrs":{}},"lightLink":{"dir":{"value":3},"attrs":{}}}}},"dateCode":"20190311","_id":"jrVKz4IB9fT3m443"}

@tb-killa, the blinds can be controlled via the Ikea App and google/youtube shows that the blinds can be connected to Philips Hue bridge, thus it should be possible to control without Ikea specifics. Right?

Inspiration may be found in deConz support for both the Open/Close remote and the blinds.

See pull request:
https://github.com/dresden-elektronik/deconz-rest-plugin/pull/1774
https://github.com/dresden-elektronik/deconz-rest-plugin/pull/1783
https://github.com/dresden-elektronik/deconz-rest-plugin/pull/1785

I do not know where to go from here. I am able to sniff the traffic, but do not know how to use the information.
From traffic sniffing I see the open/close remote send 3 different commands, 0x00 (Up/Open), 0x01 (Down/close) and 0x02 (Stop). However, only the Stop triggered output in zigbee2mqtt.

@osos How's it going? Any status update?

@osos How's it going? Any status update?

Not good. Don't know how to continue with this.

were you able to get the open close remote working?

Can somebody try with the following configuration for the blinds:

{
        zigbeeModel: ['FYRTUR block-out roller blind'],
        model: 'TODO',
        vendor: 'IKEA',
        description: 'Blinds',
        supports: 'open/close',
        fromZigbee: [fz.cover_position_report, fz.cover_position, fz.cover_state_change, fz.cover_state_report],
        toZigbee: [tz.cover_position, tz.cover_open_close],
    },

It should then work with zigbee2mqtt/[DEVICE_ID]/set {"state": "OPEN"} (and CLOSE)

@Koenkk Close but... not yet I'm afraid (at least not here)

I've added the code to devices.js and paired one of my freshly cut blinds:

9/24/2019, 5:30:48 PM - info: New device 'FYRTUR block-out roller blind' with address 0x000dXXXXXXXXX connected!
9/24/2019, 5:30:48 PM - info: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_connected","message":"0x000dXXXXXXXXX","meta":{"modelID":"FYRTUR block-out roller blind"}}'

The model for the FYTRUR is E1757 and its description on the device label states: Wireless/battery operated roller blind

~It didn't show up in HomeAssistant yet but it probably requires an entry in homeassistant.js for that?~
I've added this to homeassistant.js:

'E1757': [configurations.cover_position],

It shows up in HomeAssistant, but the arrows are inverted and it reports state "Closed", however it is fully opened. Seems like the status needs to be inverted.

Issuing the open/close state via MQTT results in:

9/24/2019, 5:34:51 PM - info: Zigbee publish to device '0x000dXXXXXXXXX ', genLevelCtrl - moveToLevelWithOnOff - {"level":"255","transtime":0} - {"manufSpec":0,"disDefaultRsp":0} - 1
9/24/2019, 5:34:51 PM - info: MQTT publish: topic 'zigbee2mqtt/0x000dXXXXXXXXX ', payload '{"position":100,"device":{"ieeeAddr":"0x000dXXXXXXXXX ","friendlyName":"0x000dXXXXXXXXX ","type":"EndDevice","nwkAddr":15308,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Battery","modelId":"FYRTUR block-out roller blind","hwVersion":1,"swBuildId":"2.2.007","dateCode":"20190311","status":"online"}}'

9/24/2019, 5:34:59 PM - info: Zigbee publish to device '0x000dXXXXXXXXX ', genLevelCtrl - moveToLevelWithOnOff - {"level":"0","transtime":0} - {"manufSpec":0,"disDefaultRsp":0} - 1
9/24/2019, 5:35:01 PM - info: MQTT publish: topic 'zigbee2mqtt/0x000dXXXXXXXXX ', payload '{"position":0,"device":{"ieeeAddr":"0x000dXXXXXXXXX ","friendlyName":"0x000dXXXXXXXXX ","type":"EndDevice","nwkAddr":15308,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Battery","modelId":"FYRTUR block-out roller blind","hwVersion":1,"swBuildId":"2.2.007","dateCode":"20190311","status":"online"}}'

But nothing happens yet. The blind remains opened.

Can you try with

{
        zigbeeModel: ['FYRTUR block-out roller blind'],
        model: 'TODO',
        vendor: 'IKEA',
        description: 'Blinds',
        supports: 'open/close',
        fromZigbee: [fz.cover_position_report, fz.cover_position, fz.cover_state_change, fz.cover_state_report],
        toZigbee: [tz.cover_control],
    },

And home assistant configuration configurations.cover (dont forgot to also restart home assistant after changing the configuration). Position wont work after this but atleast open close and stop should work.

Can you try with

{
        zigbeeModel: ['FYRTUR block-out roller blind'],
        model: 'TODO',
        vendor: 'IKEA',
        description: 'Blinds',
        supports: 'open/close',
        fromZigbee: [fz.cover_position_report, fz.cover_position, fz.cover_state_change, fz.cover_state_report],
        toZigbee: [tz.cover_control],
    },

And home assistant configuration configurations.cover (dont forgot to also restart home assistant after changing the configuration). Position wont work after this but atleast open close and stop should work.

Awesome! It is opening, stopping and closing perfectly right now. The arrows work as they should, state reports "open" when it is open.

From what I understand it should be capable of sending its position and receiving a specific position, but for that some more work is required probably?

Great, I've improved the naming over the cover converters a bit. Can you update to the latest dev brach and zigbee-herdsman-converters?

I expect it will fully work with the following configuration (including position):

devices.js

{
    zigbeeModel: ['FYRTUR block-out roller blind'],
    model: 'E1757',
    vendor: 'IKEA',
    description: 'FYRTUR smart blinds',
    supports: 'open, close, stop, position, tilt',
    fromZigbee: [fz.cover_position_tilt],
    toZigbee: [tz.cover_state, tz.cover_position_tilt],
},

homeassistant.js

'E1757': [cfg.cover_position_tilt],

Great, I've improved the naming over the cover converters a bit. Can you update to the latest dev brach and zigbee-herdsman-converters?

I expect it will fully work with the following configuration (including position):

devices.js

{
    zigbeeModel: ['FYRTUR block-out roller blind'],
    model: 'E1757',
    vendor: 'IKEA',
    description: 'FYRTUR smart blinds',
    supports: 'open, close, stop, position, tilt',
    fromZigbee: [fz.cover_position_tilt],
    toZigbee: [tz.cover_state, tz.cover_position_tilt],
},

homeassistant.js

'E1757': [cfg.cover_position_tilt],

With the dev version/herdsman and the changes above the position does work however:

  • 100% is 100% open, not 100% closed (what you'd expect).
  • When the blind is opened fully (position: 100%) the up arrow shows instead of the down arrow (which is greyed out). The only way to get the blind down is by changing the position slider from 100 to 95 for instance. However, the down arrow still remains greyed out.
  • The cover status is "closed" while it is opened. Likely due to the previous two points.
  • It shows tilting options but this has no effect on this type of blind.

Can you:

Can you:

I moved the slider (since the buttons are not working) to 0% and 100% but it doesn't log anything (or it logs at a level that is below the one npm start uses by default?)

Great, I've improved the naming over the cover converters a bit. Can you update to the latest dev brach and zigbee-herdsman-converters?

I expect it will fully work with the following configuration (including position):

devices.js

{
    zigbeeModel: ['FYRTUR block-out roller blind'],
    model: 'E1757',
    vendor: 'IKEA',
    description: 'FYRTUR smart blinds',
    supports: 'open, close, stop, position, tilt',
    fromZigbee: [fz.cover_position_tilt],
    toZigbee: [tz.cover_state, tz.cover_position_tilt],
},

homeassistant.js

'E1757': [cfg.cover_position_tilt],

I made it also work with the Kadrilj blinds (E1926):

    {
    zigbeeModel: ['KADRILJ roller blind'],
    model: 'E1926',
    vendor: 'IKEA',
    description: 'KADRILJ roller blind',
    supports: 'open, close, stop, position, tilt',
    fromZigbee: [fz.cover_position_tilt],
    toZigbee: [tz.cover_state, tz.cover_position_tilt],
},
'E1926': [cfg.cover_position_tilt],

Using HomeKit (through home-assistant) it actually works to set percentages, but the slider in home-assistant does not

@syphernl can you try changing https://github.com/Koenkk/zigbee-shepherd-converters/blob/zigbee-herdsman-converters/converters/fromZigbee.js#L2368 to result.position = liftPercentage <= 100 ? liftPercentage : null;

I will definitiv Buy as Soon as avaiable in Germany

I've bought mine in Netherlands. But some days later i've seen Fyrtur blinds at IKEA in Düsseldorf (GER) also. Even though the blinds are not offically listet online in the store.

result.position = liftPercentage <= 100 ? liftPercentage : null;

Open / Close works fine (open = up, close = down as it should).
However its state is unknown in HomeAssistant.

The tilt buttons do not work and neither does setting a specific position.
Whether I set it to 0, 100, 50 or anywhere in between it won't move.


I have been fiddling a bit around in the code, to get rid of the tilting (which does not work)
There is something odd going on though. I have 3 blinds. Two of them show state "unknown", have no position slider and the arrows make sense. Up = up, down = down.

The third one is a bit different, it shows state (Closed). This blind has a position slider.
When set to 0, the blind is fully closed. Set to 100, it is opened. However, the state always remains "Closed" even if its fully open. The current_position also never updates. The arrows appear to be inversed as well.

@syphernl could you perhaps contact me on telegram (koenkk), in this way we can iterate faster.

@syphernl could you perhaps contact me on telegram (koenkk), in this way we can iterate faster.

On it!

Device is supported in the dev branch now, credit go to @syphernl :smile;

Device is supported in the dev branch now, credit go to @syphernl :smile;

Note that, next to the model ID, the Zigbee model naming between the two is actually different so I think you need to add 'KADRILJ roller blind' to the zigbeeModel array as well :)

@dsbaars good catch, also added that one, both KADRILJI and FYRTUR are supported in the dev branch now.

@syphernl @Koenkk Thank you so much! My blinds are working like a charm with OpenHAB.

Is this already available in a docker images? (koenkk/zigbee2mqtt:/latest-dev)

Yes

Hmmm couldn't get it to work. 😔

What are the steps to get the blinds, signal repeater and open-close button work?

Hmmm couldn't get it to work. 😔

What are the steps to get the blinds, signal repeater and open-close button work?

Signal repeater: See https://www.zigbee2mqtt.io/devices/E1746.html
Blinds: Enable join mode in Z2M. Hold both buttons (~5 seconds) on the blind until the leds start flashing / turn on. After some time it should show up.
Remote: https://www.zigbee2mqtt.io/devices/E1743.html. I haven't used this one yet. IIUC it should be pairable directly to the blinds while they are part of the Zigbee network but haven't yet tried this. Otherwise you can bind the remote to your coordinator and use it from there.

The blinds work fine here without the repeater. I however do have some TRADFRI Bulbs and a power socket on that floor that they use as hop to my coordinator.

@syphernl, thanks for your reply! Would you be available for a chat?

[√] Signal repeater: successfully paired following E1746
[√] Blinds: successfully paired following your description.
[ X ] Remote: tradfri-open-close-remote-1 (0x086bd7fffe57f940): Not supported (EndDevice)

A json to open the blinds, published to zigbee2mqtt/<device_id_or_friendly_name>/set:

{
    "state": "open"
}

A json to close the blinds, published to zigbee2mqtt/<device_id_or_friendly_name>/set:

{
    "state": "close"
}

A json to position the blinds, published to zigbee2mqtt/<device_id_or_friendly_name>/set:

{
    "position": 50
}

I've bought an Ikea blind today, and I'll try to connect to Z2M, but I've a question, is the Signal Repeater mandatory for the blinds to work?

Regards!

@abmantis, no it's not.

@abmantis, no it's not.

Thanks! With the remote (even quite near to the blind) I wasn't able to operate it without the SR connected... :S

Thanks! With the remote (even quite near to the blind) I wasn't able to operate it without the SR connected... :S

Well while pairing the blind, I had it as close as possible (could be close) to the coordinator. Since the SR came with the packages, I've added them as well to Z2M :)

Unfortunately, I wasn't able to add the open/close remote :(

tradfri-open-close-remote-1 (0x086bd7fffe57f940): Not supported (EndDevice)

@RaymondMouthaan as you have paired the remote, could you start zigbee2mqtt with DEBUG=zigbee-herdsman* npm start) (I assume you use docker so set the DEBUG=zigbee-herdsman* environment variable inside the container). Can you provide the logging when pressing the buttons?

This is the debug logging you requested:

2019-09-29T19:58:24.363Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-29T19:58:24.364Z zigbee-herdsman:controller:zStack:startZnp Item 'networkKeyDistribute' is valid

2019-09-29T19:58:24.367Z zigbee-herdsman:znp:SREQ --> SAPI - readConfiguration - {"id":98,"configid":98,"len":16,"offset":0,"value":{"type":"Buffer","data":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13]}}

2019-09-29T19:58:24.369Z zigbee-herdsman:unpi:writer --> frame [254,1,38,4,98,65]

2019-09-29T19:58:24.393Z zigbee-herdsman:unpi:parser <-- [254,19,102,4,0,98,16,1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13,0]

2019-09-29T19:58:24.394Z zigbee-herdsman:unpi:parser --- parseNext [254,19,102,4,0,98,16,1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13,0]

2019-09-29T19:58:24.395Z zigbee-herdsman:unpi:parser --> parsed 19 - 3 - 6 - 4 - [b    





] - 0

2019-09-29T19:58:24.396Z zigbee-herdsman:znp:SRSP <-- SAPI - readConfiguration - {"status":0,"configid":98,"len":16,"value":{"type":"Buffer","data":[1,3,5,7,9,11,13,15,0,2,4,6,8,10,12,13]}}

2019-09-29T19:58:24.397Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-29T19:58:24.398Z zigbee-herdsman:controller:zStack:startZnp Item 'networkKey' is valid

2019-09-29T19:58:24.400Z zigbee-herdsman:znp:SREQ --> SYS - osalNvRead - {"id":131,"len":2,"offset":0,"value":{"type":"Buffer","data":[98,26]}}

2019-09-29T19:58:24.402Z zigbee-herdsman:unpi:writer --> frame [254,3,33,8,131,0,0,169]

2019-09-29T19:58:24.410Z zigbee-herdsman:unpi:parser <-- [254,4,97,8,0,2,98,26,23]

2019-09-29T19:58:24.411Z zigbee-herdsman:unpi:parser --- parseNext [254,4,97,8,0,2,98,26,23]

2019-09-29T19:58:24.412Z zigbee-herdsman:unpi:parser --> parsed 4 - 3 - 1 - 8 - [b] - 23

2019-09-29T19:58:24.412Z zigbee-herdsman:znp:SRSP <-- SYS - osalNvRead - {"status":0,"len":2,"value":{"type":"Buffer","data":[98,26]}}

2019-09-29T19:58:24.413Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-29T19:58:24.413Z zigbee-herdsman:controller:zStack:startZnp Item 'panID' is valid

2019-09-29T19:58:24.415Z zigbee-herdsman:znp:SREQ --> SYS - osalNvRead - {"id":45,"len":8,"offset":0,"value":{"type":"Buffer","data":[221,221,221,221,221,221,221,221]}}

2019-09-29T19:58:24.415Z zigbee-herdsman:unpi:writer --> frame [254,3,33,8,45,0,0,7]

2019-09-29T19:58:24.424Z zigbee-herdsman:unpi:parser <-- [254,10,97,8,0,8,221,221,221,221,221,221,221,221,107]

2019-09-29T19:58:24.425Z zigbee-herdsman:unpi:parser --- parseNext [254,10,97,8,0,8,221,221,221,221,221,221,221,221,107]

2019-09-29T19:58:24.426Z zigbee-herdsman:unpi:parser --> parsed 10 - 3 - 1 - 8 - [��������] - 107

2019-09-29T19:58:24.427Z zigbee-herdsman:znp:SRSP <-- SYS - osalNvRead - {"status":0,"len":8,"value":{"type":"Buffer","data":[221,221,221,221,221,221,221,221]}}

2019-09-29T19:58:24.428Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-29T19:58:24.429Z zigbee-herdsman:controller:zStack:startZnp Item 'extendedPanID' is valid

2019-09-29T19:58:24.432Z zigbee-herdsman:znp:SREQ --> UTIL - getDeviceInfo - {}

2019-09-29T19:58:24.433Z zigbee-herdsman:unpi:writer --> frame [254,0,39,0,39]

2019-09-29T19:58:24.443Z zigbee-herdsman:unpi:parser <-- [254,30,103,0,0,96,172,54,25,0,75,18,0,0,0,7,9,8,217,38,137,214,214,218,64,75,163,165,178,33,91,207,252,45,178]

2019-09-29T19:58:24.444Z zigbee-herdsman:unpi:parser --- parseNext [254,30,103,0,0,96,172,54,25,0,75,18,0,0,0,7,9,8,217,38,137,214,214,218,64,75,163,165,178,33,91,207,252,45,178]

2019-09-29T19:58:24.445Z zigbee-herdsman:unpi:parser --> parsed 30 - 3 - 7 - 0 - [`�6K   �&����@K���![��-] - 178

2019-09-29T19:58:24.449Z zigbee-herdsman:znp:SRSP <-- UTIL - getDeviceInfo - {"status":0,"ieeeaddr":"0x00124b001936ac60","shortaddr":0,"devicetype":7,"devicestate":9,"numassocdevices":8,"assocdeviceslist":[9945,54921,56022,19264,42403,8626,53083,11772]}

2019-09-29T19:58:24.450Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-29T19:58:24.451Z zigbee-herdsman:controller:zStack:startZnp ZNP is already started as coordinator

2019-09-29T19:58:24.455Z zigbee-herdsman:znp:SREQ --> ZDO - activeEpReq - {"dstaddr":0,"nwkaddrofinterest":0}

2019-09-29T19:58:24.457Z zigbee-herdsman:unpi:writer --> frame [254,4,37,5,0,0,0,0,36]

2019-09-29T19:58:24.465Z zigbee-herdsman:unpi:parser <-- [254,1,101,5,0,97]

2019-09-29T19:58:24.465Z zigbee-herdsman:unpi:parser --- parseNext [254,1,101,5,0,97]

2019-09-29T19:58:24.466Z zigbee-herdsman:unpi:parser --> parsed 1 - 3 - 5 - 5 - [] - 97

2019-09-29T19:58:24.466Z zigbee-herdsman:znp:SRSP <-- ZDO - activeEpReq - {"status":0}

2019-09-29T19:58:24.467Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-29T19:58:24.471Z zigbee-herdsman:unpi:parser <-- [254,14,69,133,0,0,0,0,0,8,11,8,6,5,4,3,2,1,194]

2019-09-29T19:58:24.471Z zigbee-herdsman:unpi:parser --- parseNext [254,14,69,133,0,0,0,0,0,8,11,8,6,5,4,3,2,1,194]

2019-09-29T19:58:24.472Z zigbee-herdsman:unpi:parser --> parsed 14 - 2 - 5 - 133 - [
] - 194

2019-09-29T19:58:24.474Z zigbee-herdsman:znp:AREQ <-- ZDO - activeEpRsp - {"srcaddr":0,"status":0,"nwkaddr":0,"activeepcount":8,"activeeplist":[11,8,6,5,4,3,2,1]}

2019-09-29T19:58:24.475Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-29T19:58:24.476Z zigbee-herdsman:controller:zStack:startZnp Endpoint '1' already registered

2019-09-29T19:58:24.477Z zigbee-herdsman:controller:zStack:startZnp Endpoint '2' already registered

2019-09-29T19:58:24.477Z zigbee-herdsman:controller:zStack:startZnp Endpoint '3' already registered

2019-09-29T19:58:24.478Z zigbee-herdsman:controller:zStack:startZnp Endpoint '4' already registered

2019-09-29T19:58:24.478Z zigbee-herdsman:controller:zStack:startZnp Endpoint '5' already registered

2019-09-29T19:58:24.478Z zigbee-herdsman:controller:zStack:startZnp Endpoint '6' already registered

2019-09-29T19:58:24.478Z zigbee-herdsman:controller:zStack:startZnp Endpoint '8' already registered

2019-09-29T19:58:24.478Z zigbee-herdsman:controller:zStack:startZnp Endpoint '11' already registered

2019-09-29T19:58:24.479Z zigbee-herdsman:controller:log Started with result 'resumed'

2019-09-29T19:58:24.480Z zigbee-herdsman:controller:log Injected database: true, adapter: true

zigbee2mqtt:info  2019-09-29T19:58:24: zigbee-herdsman started

zigbee2mqtt:info  2019-09-29T19:58:24: Coordinator firmware version: '{"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190608}}'

2019-09-29T19:58:24.494Z zigbee-herdsman:znp:SREQ --> ZDO - extNwkInfo - {}

2019-09-29T19:58:24.495Z zigbee-herdsman:unpi:writer --> frame [254,0,37,80,117]

2019-09-29T19:58:24.500Z zigbee-herdsman:unpi:parser <-- [254,24,101,80,0,0,9,98,26,0,0,221,221,221,221,221,221,221,221,0,0,0,0,0,0,0,0,11,87]

2019-09-29T19:58:24.501Z zigbee-herdsman:unpi:parser --- parseNext [254,24,101,80,0,0,9,98,26,0,0,221,221,221,221,221,221,221,221,0,0,0,0,0,0,0,0,11,87]

2019-09-29T19:58:24.501Z zigbee-herdsman:unpi:parser --> parsed 24 - 3 - 5 - 80 - [ b��������
] - 87

2019-09-29T19:58:24.502Z zigbee-herdsman:znp:SRSP <-- ZDO - extNwkInfo - {"shortaddr":0,"devstate":9,"panid":6754,"parentaddr":0,"extendedpanid":"0xdddddddddddddddd","parentextaddr":"0x0000000000000000","channel":11}

2019-09-29T19:58:24.503Z zigbee-herdsman:unpi:parser --- parseNext []

zigbee2mqtt:debug 2019-09-29T19:58:24: Zigbee network parameters: {"panID":6754,"extendedPanID":"0xdddddddddddddddd","channel":11}

zigbee2mqtt:info  2019-09-29T19:58:24: Currently 8 devices are joined:

zigbee2mqtt:info  2019-09-29T19:58:24: hue-dimmer-1 (0x0017880106b736ad): 324131092621 - Philips Hue dimmer switch (EndDevice)

zigbee2mqtt:info  2019-09-29T19:58:24: tradfri-remote-1 (0x90fd9ffffee6e4c0): E1524/E1810 - IKEA TRADFRI remote control (EndDevice)

zigbee2mqtt:info  2019-09-29T19:58:24: tradfri-remote-2 (0x90fd9ffffee8ea42): E1524/E1810 - IKEA TRADFRI remote control (EndDevice)

zigbee2mqtt:info  2019-09-29T19:58:24: tradfri-window-blind-2 (0x000d6ffffea940f2): E1926 - IKEA KADRILJ roller blind (EndDevice)

zigbee2mqtt:info  2019-09-29T19:58:24: tradfri-window-blind-1 (0x000d6ffffe9d5e34): E1926 - IKEA KADRILJ roller blind (EndDevice)

zigbee2mqtt:info  2019-09-29T19:58:24: tradfri-signal-repeater-1 (0x000d6ffffea9402f): E1746 - IKEA TRADFRI signal repeater (Router)

zigbee2mqtt:info  2019-09-29T19:58:24: tradfri-signal-repeater-2 (0x000d6ffffea1f2f2): E1746 - IKEA TRADFRI signal repeater (Router)

zigbee2mqtt:info  2019-09-29T19:58:24: tradfri-open-close-remote-1 (0x086bd7fffe57f940): Not supported (EndDevice)

zigbee2mqtt:info  2019-09-29T19:58:24: Zigbee: disabling joining new devices.

2019-09-29T19:58:24.525Z zigbee-herdsman:controller:log Disable joining

2019-09-29T19:58:24.528Z zigbee-herdsman:znp:SREQ --> ZDO - mgmtPermitJoinReq - {"addrmode":15,"dstaddr":65532,"duration":0,"tcsignificance":0}

2019-09-29T19:58:24.529Z zigbee-herdsman:unpi:writer --> frame [254,5,37,54,15,252,255,0,0,26]

zigbee2mqtt:info  2019-09-29T19:58:24: Connecting to MQTT server at mqtt://mqtt.indonesia:1883

zigbee2mqtt:debug 2019-09-29T19:58:24: Using MQTT client ID: 'zigbee2mqtt'

2019-09-29T19:58:24.964Z zigbee-herdsman:unpi:parser <-- [254,1,101,54,0,82,254,3,69,182,0,0,0,240]

2019-09-29T19:58:24.966Z zigbee-herdsman:unpi:parser --- parseNext [254,1,101,54,0,82,254,3,69,182,0,0,0,240]

2019-09-29T19:58:24.967Z zigbee-herdsman:unpi:parser --> parsed 1 - 3 - 5 - 54 - [] - 82

2019-09-29T19:58:24.970Z zigbee-herdsman:znp:SRSP <-- ZDO - mgmtPermitJoinReq - {"status":0}

2019-09-29T19:58:24.971Z zigbee-herdsman:unpi:parser --- parseNext [254,3,69,182,0,0,0,240]

2019-09-29T19:58:24.972Z zigbee-herdsman:unpi:parser --> parsed 3 - 2 - 5 - 182 - [] - 240

2019-09-29T19:58:24.974Z zigbee-herdsman:znp:AREQ <-- ZDO - mgmtPermitJoinRsp - {"srcaddr":0,"status":0}

2019-09-29T19:58:24.975Z zigbee-herdsman:unpi:parser --- parseNext []

zigbee2mqtt:info  2019-09-29T19:58:25: Connected to MQTT server

zigbee2mqtt:info  2019-09-29T19:58:25: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'

zigbee2mqtt:info  2019-09-29T19:58:25: MQTT publish: topic 'zigbee2mqtt/hue-dimmer-1', payload '{"counter":1,"linkquality":107,"brightness":223}'

zigbee2mqtt:info  2019-09-29T19:58:25: MQTT publish: topic 'zigbee2mqtt/tradfri-remote-1', payload '{"linkquality":84}'

zigbee2mqtt:info  2019-09-29T19:58:25: MQTT publish: topic 'zigbee2mqtt/tradfri-remote-2', payload '{"linkquality":113}'

zigbee2mqtt:info  2019-09-29T19:58:25: MQTT publish: topic 'zigbee2mqtt/tradfri-window-blind-2', payload '{"position":0,"linkquality":28,"battery":30}'

zigbee2mqtt:info  2019-09-29T19:58:25: MQTT publish: topic 'zigbee2mqtt/tradfri-window-blind-1', payload '{"position":0,"linkquality":28,"battery":49}'

zigbee2mqtt:info  2019-09-29T19:58:25: MQTT publish: topic 'zigbee2mqtt/tradfri-signal-repeater-1', payload '{"linkquality":178}'

zigbee2mqtt:info  2019-09-29T19:58:25: MQTT publish: topic 'zigbee2mqtt/tradfri-signal-repeater-2', payload '{"linkquality":173}'

zigbee2mqtt:info  2019-09-29T19:58:25: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.6.0","commit":"99ebc46","coordinator":{"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190608}},"log_level":"debug","permit_join":false}'

2019-09-29T20:00:00.122Z zigbee-herdsman:unpi:parser <-- [254,23,68,129,0,0,2,1,252,45,1,1,0,63,0,235,27,218,0,0,3,1,6,1,252,45,11,202]

2019-09-29T20:00:00.123Z zigbee-herdsman:unpi:parser --- parseNext [254,23,68,129,0,0,2,1,252,45,1,1,0,63,0,235,27,218,0,0,3,1,6,1,252,45,11,202]

2019-09-29T20:00:00.124Z zigbee-herdsman:unpi:parser --> parsed 23 - 2 - 4 - 129 - [�-?���-
] - 202

2019-09-29T20:00:00.127Z zigbee-herdsman:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":258,"srcaddr":11772,"srcendpoint":1,"dstendpoint":1,"wasbroadcast":0,"linkquality":63,"securityuse":0,"timestamp":14293995,"transseqnumber":0,"len":3,"data":{"type":"Buffer","data":[1,6,1]}}

�2019-09-29T20:00:00.141Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":false},"transactionSequenceNumber":6,"manufacturerCode":null,"commandIdentifier":1},"Payload":{},"Cluster":{"ID":258,"attributes":{"windowCoveringType":{"ID":0,"type":48,"name":"windowCoveringType"},"physicalClosedLimitLiftCm":{"ID":1,"type":33,"name":"physicalClosedLimitLiftCm"},"physicalClosedLimitTiltDdegree":{"ID":2,"type":33,"name":"physicalClosedLimitTiltDdegree"},"currentPositionLiftCm":{"ID":3,"type":33,"name":"currentPositionLiftCm"},"currentPositionTiltDdegree":{"ID":4,"type":33,"name":"currentPositionTiltDdegree"},"numOfActuationsLift":{"ID":5,"type":33,"name":"numOfActuationsLift"},"numOfActuationsTilt":{"ID":6,"type":33,"name":"numOfActuationsTilt"},"configStatus":{"ID":7,"type":24,"name":"configStatus"},"currentPositionLiftPercentage":{"ID":8,"type":32,"name":"currentPositionLiftPercentage"},"currentPositionTiltPercentage":{"ID":9,"type":32,"name":"currentPositionTiltPercentage"},"operationalStatus":{"ID":10,"type":24,"name":"operationalStatus"},"installedOpenLimitLiftCm":{"ID":16,"type":33,"name":"installedOpenLimitLiftCm"},"installedClosedLimitLiftCm":{"ID":17,"type":33,"name":"installedClosedLimitLiftCm"},"installedOpenLimitTiltDdegree":{"ID":18,"type":33,"name":"installedOpenLimitTiltDdegree"},"installedClosedLimitTiltDdegree":{"ID":19,"type":33,"name":"installedClosedLimitTiltDdegree"},"velocityLift":{"ID":20,"type":33,"name":"velocityLift"},"accelerationTimeLift":{"ID":21,"type":33,"name":"accelerationTimeLift"},"decelerationTimeLift":{"ID":22,"type":33,"name":"decelerationTimeLift"},"windowCoveringMode":{"ID":23,"type":24,"name":"windowCoveringMode"},"intermediateSetpointsLift":{"ID":24,"type":65,"name":"intermediateSetpointsLift"},"intermediateSetpointsTilt":{"ID":25,"type":65,"name":"intermediateSetpointsTilt"},"ubisysTurnaroundGuardTime":{"ID":4096,"type":32,"manufacturerCode":4338,"name":"ubisysTurnaroundGuardTime"},"ubisysLiftToTiltTransitionSteps":{"ID":4097,"type":33,"manufacturerCode":4338,"name":"ubisysLiftToTiltTransitionSteps"},"ubisysTotalSteps":{"ID":4098,"type":33,"manufacturerCode":4338,"name":"ubisysTotalSteps"},"ubisysLiftToTiltTransitionSteps2":{"ID":4099,"type":33,"manufacturerCode":4338,"name":"ubisysLiftToTiltTransitionSteps2"},"ubisysTotalSteps2":{"ID":4100,"type":33,"manufacturerCode":4338,"name":"ubisysTotalSteps2"},"ubisysAdditionalSteps":{"ID":4101,"type":32,"manufacturerCode":4338,"name":"ubisysAdditionalSteps"},"ubisysInactivePowerThreshold":{"ID":4102,"type":33,"manufacturerCode":4338,"name":"ubisysInactivePowerThreshold"},"ubisysStartupSteps":{"ID":4103,"type":33,"manufacturerCode":4338,"name":"ubisysStartupSteps"}},"name":"closuresWindowCovering","commands":{"upOpen":{"ID":0,"parameters":[],"name":"upOpen"},"downClose":{"ID":1,"parameters":[],"name":"downClose"},"stop":{"ID":2,"parameters":[],"name":"stop"},"goToLiftValue":{"ID":4,"parameters":[{"name":"liftvalue","type":33}],"name":"goToLiftValue"},"goToLiftPercentage":{"ID":5,"parameters":[{"name":"percentageliftvalue","type":32}],"name":"goToLiftPercentage"},"goToTiltValue":{"ID":7,"parameters":[{"name":"tiltvalue","type":33}],"name":"goToTiltValue"},"goToTiltPercentage":{"ID":8,"parameters":[{"name":"percentagetiltvalue","type":32}],"name":"goToTiltPercentage"}},"commandsResponse":{}}},"networkAddress":11772,"endpoint":1,"linkquality":63,"groupID":0}'

2019-09-29T20:00:00.144Z zigbee-herdsman:controller:log Skipping command 'downClose' because it is missing from the lookup

2019-09-29T20:00:00.156Z zigbee-herdsman:znp:SREQ --> AF - dataRequest - {"dstaddr":11772,"destendpoint":1,"srcendpoint":1,"clusterid":258,"transid":1,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[24,6,11,1,0]}}

2019-09-29T20:00:00.159Z zigbee-herdsman:unpi:writer --> frame [254,15,36,1,252,45,1,1,2,1,1,0,30,5,24,6,11,1,0,246]

2019-09-29T20:00:00.160Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-29T20:00:00.170Z zigbee-herdsman:unpi:parser <-- [254,1,100,1,0,100]

2019-09-29T20:00:00.171Z zigbee-herdsman:unpi:parser --- parseNext [254,1,100,1,0,100]

2019-09-29T20:00:00.172Z zigbee-herdsman:unpi:parser --> parsed 1 - 3 - 4 - 1 - [] - 100

2019-09-29T20:00:00.173Z zigbee-herdsman:znp:SRSP <-- AF - dataRequest - {"status":0}

2019-09-29T20:00:00.174Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-29T20:00:01.162Z zigbee-herdsman:unpi:parser <-- [254,3,68,128,0,1,1,199]

2019-09-29T20:00:01.162Z zigbee-herdsman:unpi:parser --- parseNext [254,3,68,128,0,1,1,199]

2019-09-29T20:00:01.163Z zigbee-herdsman:unpi:parser --> parsed 3 - 2 - 4 - 128 - [] - 199

2019-09-29T20:00:01.164Z zigbee-herdsman:znp:AREQ <-- AF - dataConfirm - {"status":0,"endpoint":1,"transid":1}

2019-09-29T20:00:01.165Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-29T20:00:17.178Z zigbee-herdsman:unpi:parser <-- [254,27,68,129,0,0,1,0,178,33,1,1,0,52,0,49,236,218,0,0,7,8,24,10,33,0,32,59,178,33,29,214]

2019-09-29T20:00:17.179Z zigbee-herdsman:unpi:parser --- parseNext [254,27,68,129,0,0,1,0,178,33,1,1,0,52,0,49,236,218,0,0,7,8,24,10,33,0,32,59,178,33,29,214]

2019-09-29T20:00:17.180Z zigbee-herdsman:unpi:parser --> parsed 27 - 2 - 4 - 129 - [�!41��

! ;�!
] - 214

2019-09-29T20:00:17.181Z zigbee-herdsman:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":1,"srcaddr":8626,"srcendpoint":1,"dstendpoint":1,"wasbroadcast":0,"linkquality":52,"securityuse":0,"timestamp":14347313,"transseqnumber":0,"len":7,"data":{"type":"Buffer","data":[8,24,10,33,0,32,59]}}

2019-09-29T20:00:17.190Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false},"transactionSequenceNumber":24,"manufacturerCode":null,"commandIdentifier":10},"Payload":[{"attrId":33,"dataType":32,"attrData":59}],"Cluster":{"ID":1,"attributes":{"mainsVoltage":{"ID":0,"type":33,"name":"mainsVoltage"},"mainsFrequency":{"ID":1,"type":32,"name":"mainsFrequency"},"mainsAlarmMask":{"ID":16,"type":24,"name":"mainsAlarmMask"},"mainsVoltMinThres":{"ID":17,"type":33,"name":"mainsVoltMinThres"},"mainsVoltMaxThres":{"ID":18,"type":33,"name":"mainsVoltMaxThres"},"mainsVoltageDwellTripPoint":{"ID":19,"type":33,"name":"mainsVoltageDwellTripPoint"},"batteryVoltage":{"ID":32,"type":32,"name":"batteryVoltage"},"batteryPercentageRemaining":{"ID":33,"type":32,"name":"batteryPercentageRemaining"},"batteryManufacturer":{"ID":48,"type":66,"name":"batteryManufacturer"},"batterySize":{"ID":49,"type":48,"name":"batterySize"},"batteryAHrRating":{"ID":50,"type":33,"name":"batteryAHrRating"},"batteryQuantity":{"ID":51,"type":32,"name":"batteryQuantity"},"batteryRatedVoltage":{"ID":52,"type":32,"name":"batteryRatedVoltage"},"batteryAlarmMask":{"ID":53,"type":24,"name":"batteryAlarmMask"},"batteryVoltMinThres":{"ID":54,"type":32,"name":"batteryVoltMinThres"},"batteryVoltThres1":{"ID":55,"type":32,"name":"batteryVoltThres1"},"batteryVoltThres2":{"ID":56,"type":32,"name":"batteryVoltThres2"},"batteryVoltThres3":{"ID":57,"type":32,"name":"batteryVoltThres3"},"batteryPercentMinThres":{"ID":58,"type":32,"name":"batteryPercentMinThres"},"batteryPercentThres1":{"ID":59,"type":32,"name":"batteryPercentThres1"},"batteryPercentThres2":{"ID":60,"type":32,"name":"batteryPercentThres2"},"batteryPercentThres3":{"ID":61,"type":32,"name":"batteryPercentThres3"},"batteryAlarmState":{"ID":62,"type":27,"name":"batteryAlarmState"}},"name":"genPowerCfg","commands":{},"commandsResponse":{}}},"networkAddress":8626,"endpoint":1,"linkquality":52,"groupID":0}'

zigbee2mqtt:debug 2019-09-29T20:00:17: Received Zigbee message from 'tradfri-window-blind-2' of type 'attributeReport' with data '{"batteryPercentageRemaining":59}' from endpoint 1 with groupID 0

zigbee2mqtt:info  2019-09-29T20:00:17: MQTT publish: topic 'zigbee2mqtt/tradfri-window-blind-2', payload '{"position":0,"linkquality":52,"battery":29.5}'

2019-09-29T20:00:17.208Z zigbee-herdsman:znp:SREQ --> AF - dataRequest - {"dstaddr":8626,"destendpoint":1,"srcendpoint":1,"clusterid":1,"transid":2,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[24,24,11,10,0]}}

2019-09-29T20:00:17.210Z zigbee-herdsman:unpi:writer --> frame [254,15,36,1,178,33,1,1,1,0,2,0,30,5,24,24,11,10,0,160]

2019-09-29T20:00:17.210Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-29T20:00:17.221Z zigbee-herdsman:unpi:parser <-- [254,1,100,1,0,100]

2019-09-29T20:00:17.222Z zigbee-herdsman:unpi:parser --- parseNext [254,1,100,1,0,100]

2019-09-29T20:00:17.222Z zigbee-herdsman:unpi:parser --> parsed 1 - 3 - 4 - 1 - [] - 100

2019-09-29T20:00:17.223Z zigbee-herdsman:znp:SRSP <-- AF - dataRequest - {"status":0}

2019-09-29T20:00:17.223Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-29T20:00:18.150Z zigbee-herdsman:unpi:parser <-- [254,3,68,128,0,1,2,196]

2019-09-29T20:00:18.150Z zigbee-herdsman:unpi:parser --- parseNext [254,3,68,128,0,1,2,196]

2019-09-29T20:00:18.151Z zigbee-herdsman:unpi:parser --> parsed 3 - 2 - 4 - 128 - [] - 196

2019-09-29T20:00:18.152Z zigbee-herdsman:znp:AREQ <-- AF - dataConfirm - {"status":0,"endpoint":1,"transid":2}

2019-09-29T20:00:18.153Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-29T20:00:24.231Z zigbee-herdsman:unpi:parser <-- [254,23,68,129,0,0,2,1,252,45,1,1,0,110,0,58,66,219,0,0,3,1,7,0,252,45,11,18]

2019-09-29T20:00:24.232Z zigbee-herdsman:unpi:parser --- parseNext [254,23,68,129,0,0,2,1,252,45,1,1,0,110,0,58,66,219,0,0,3,1,7,0,252,45,11,18]

2019-09-29T20:00:24.233Z zigbee-herdsman:unpi:parser --> parsed 23 - 2 - 4 - 129 - [�-n:B��-
] - 18

2019-09-29T20:00:24.235Z zigbee-herdsman:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":258,"srcaddr":11772,"srcendpoint":1,"dstendpoint":1,"wasbroadcast":0,"linkquality":110,"securityuse":0,"timestamp":14369338,"transseqnumber":0,"len":3,"data":{"type":"Buffer","data":[1,7,0]}}

�2019-09-29T20:00:24.238Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":false},"transactionSequenceNumber":7,"manufacturerCode":null,"commandIdentifier":0},"Payload":{},"Cluster":{"ID":258,"attributes":{"windowCoveringType":{"ID":0,"type":48,"name":"windowCoveringType"},"physicalClosedLimitLiftCm":{"ID":1,"type":33,"name":"physicalClosedLimitLiftCm"},"physicalClosedLimitTiltDdegree":{"ID":2,"type":33,"name":"physicalClosedLimitTiltDdegree"},"currentPositionLiftCm":{"ID":3,"type":33,"name":"currentPositionLiftCm"},"currentPositionTiltDdegree":{"ID":4,"type":33,"name":"currentPositionTiltDdegree"},"numOfActuationsLift":{"ID":5,"type":33,"name":"numOfActuationsLift"},"numOfActuationsTilt":{"ID":6,"type":33,"name":"numOfActuationsTilt"},"configStatus":{"ID":7,"type":24,"name":"configStatus"},"currentPositionLiftPercentage":{"ID":8,"type":32,"name":"currentPositionLiftPercentage"},"currentPositionTiltPercentage":{"ID":9,"type":32,"name":"currentPositionTiltPercentage"},"operationalStatus":{"ID":10,"type":24,"name":"operationalStatus"},"installedOpenLimitLiftCm":{"ID":16,"type":33,"name":"installedOpenLimitLiftCm"},"installedClosedLimitLiftCm":{"ID":17,"type":33,"name":"installedClosedLimitLiftCm"},"installedOpenLimitTiltDdegree":{"ID":18,"type":33,"name":"installedOpenLimitTiltDdegree"},"installedClosedLimitTiltDdegree":{"ID":19,"type":33,"name":"installedClosedLimitTiltDdegree"},"velocityLift":{"ID":20,"type":33,"name":"velocityLift"},"accelerationTimeLift":{"ID":21,"type":33,"name":"accelerationTimeLift"},"decelerationTimeLift":{"ID":22,"type":33,"name":"decelerationTimeLift"},"windowCoveringMode":{"ID":23,"type":24,"name":"windowCoveringMode"},"intermediateSetpointsLift":{"ID":24,"type":65,"name":"intermediateSetpointsLift"},"intermediateSetpointsTilt":{"ID":25,"type":65,"name":"intermediateSetpointsTilt"},"ubisysTurnaroundGuardTime":{"ID":4096,"type":32,"manufacturerCode":4338,"name":"ubisysTurnaroundGuardTime"},"ubisysLiftToTiltTransitionSteps":{"ID":4097,"type":33,"manufacturerCode":4338,"name":"ubisysLiftToTiltTransitionSteps"},"ubisysTotalSteps":{"ID":4098,"type":33,"manufacturerCode":4338,"name":"ubisysTotalSteps"},"ubisysLiftToTiltTransitionSteps2":{"ID":4099,"type":33,"manufacturerCode":4338,"name":"ubisysLiftToTiltTransitionSteps2"},"ubisysTotalSteps2":{"ID":4100,"type":33,"manufacturerCode":4338,"name":"ubisysTotalSteps2"},"ubisysAdditionalSteps":{"ID":4101,"type":32,"manufacturerCode":4338,"name":"ubisysAdditionalSteps"},"ubisysInactivePowerThreshold":{"ID":4102,"type":33,"manufacturerCode":4338,"name":"ubisysInactivePowerThreshold"},"ubisysStartupSteps":{"ID":4103,"type":33,"manufacturerCode":4338,"name":"ubisysStartupSteps"}},"name":"closuresWindowCovering","commands":{"upOpen":{"ID":0,"parameters":[],"name":"upOpen"},"downClose":{"ID":1,"parameters":[],"name":"downClose"},"stop":{"ID":2,"parameters":[],"name":"stop"},"goToLiftValue":{"ID":4,"parameters":[{"name":"liftvalue","type":33}],"name":"goToLiftValue"},"goToLiftPercentage":{"ID":5,"parameters":[{"name":"percentageliftvalue","type":32}],"name":"goToLiftPercentage"},"goToTiltValue":{"ID":7,"parameters":[{"name":"tiltvalue","type":33}],"name":"goToTiltValue"},"goToTiltPercentage":{"ID":8,"parameters":[{"name":"percentagetiltvalue","type":32}],"name":"goToTiltPercentage"}},"commandsResponse":{}}},"networkAddress":11772,"endpoint":1,"linkquality":110,"groupID":0}'

2019-09-29T20:00:24.238Z zigbee-herdsman:controller:log Skipping command 'upOpen' because it is missing from the lookup

2019-09-29T20:00:24.241Z zigbee-herdsman:znp:SREQ --> AF - dataRequest - {"dstaddr":11772,"destendpoint":1,"srcendpoint":1,"clusterid":258,"transid":3,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[24,7,11,0,0]}}

2019-09-29T20:00:24.242Z zigbee-herdsman:unpi:writer --> frame [254,15,36,1,252,45,1,1,2,1,3,0,30,5,24,7,11,0,0,244]

2019-09-29T20:00:24.243Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-29T20:00:24.252Z zigbee-herdsman:unpi:parser <-- [254,1,100,1,0,100]

2019-09-29T20:00:24.253Z zigbee-herdsman:unpi:parser --- parseNext [254,1,100,1,0,100]

2019-09-29T20:00:24.254Z zigbee-herdsman:unpi:parser --> parsed 1 - 3 - 4 - 1 - [] - 100

2019-09-29T20:00:24.254Z zigbee-herdsman:znp:SRSP <-- AF - dataRequest - {"status":0}

2019-09-29T20:00:24.255Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-29T20:00:25.272Z zigbee-herdsman:unpi:parser <-- [254,3,68,128,0,1,3,197]

2019-09-29T20:00:25.273Z zigbee-herdsman:unpi:parser --- parseNext [254,3,68,128,0,1,3,197]

2019-09-29T20:00:25.274Z zigbee-herdsman:unpi:parser --> parsed 3 - 2 - 4 - 128 - [] - 197

2019-09-29T20:00:25.275Z zigbee-herdsman:znp:AREQ <-- AF - dataConfirm - {"status":0,"endpoint":1,"transid":3}

2019-09-29T20:00:25.276Z zigbee-herdsman:unpi:parser --- parseNext []

@RaymondMouthaan added the missing commands, please update to the latest dev branch and you should see the No converter available.. messages when pressing buttons.

@Koenkk, not sure if I captured all the logs you need, but this is what I got:

2019-09-30T21:56:10.628Z zigbee-herdsman:controller:device Interview - got simple descriptor for endpoint '1' device '0x086bd7fffe57f940'

2019-09-30T21:56:10.646Z zigbee-herdsman:znp:SREQ --> AF - dataRequest - {"dstaddr":58205,"destendpoint":1,"srcendpoint":1,"clusterid":0,"transid":4,"options":0,"radius":30,"len":9,"data":{"type":"Buffer","data":[16,2,0,5,0,4,0,7,0]}}

2019-09-30T21:56:10.647Z zigbee-herdsman:unpi:writer --> frame [254,19,36,1,93,227,1,1,0,0,4,0,30,9,16,2,0,5,0,4,0,7,0,143]

2019-09-30T21:56:10.657Z zigbee-herdsman:unpi:parser <-- [254,1,100,1,0,100]

2019-09-30T21:56:10.657Z zigbee-herdsman:unpi:parser --- parseNext [254,1,100,1,0,100]

2019-09-30T21:56:10.658Z zigbee-herdsman:unpi:parser --> parsed 1 - 3 - 4 - 1 - [] - 100

2019-09-30T21:56:10.658Z zigbee-herdsman:znp:SRSP <-- AF - dataRequest - {"status":0}

2019-09-30T21:56:10.659Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-30T21:56:11.645Z zigbee-herdsman:unpi:parser <-- [254,3,68,128,0,1,4,194]

2019-09-30T21:56:11.645Z zigbee-herdsman:unpi:parser --- parseNext [254,3,68,128,0,1,4,194]

2019-09-30T21:56:11.646Z zigbee-herdsman:unpi:parser --> parsed 3 - 2 - 4 - 128 - [] - 194

2019-09-30T21:56:11.646Z zigbee-herdsman:znp:AREQ <-- AF - dataConfirm - {"status":0,"endpoint":1,"transid":4}

2019-09-30T21:56:11.647Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-30T21:56:11.667Z zigbee-herdsman:unpi:parser <-- [254,77,68,129,0,0,0,0,93,227,1,1,0,178,0,94,50,216,0,0,57,24,2,1,5,0,0,66,25,84,82,65,68,70,82,73,32,111,112,101,110,47,99,108,111,115,101,32,114,101,109,111,116,101,4,0,0,66,14,73,75,69,65,32,111,102,32,83,119,101,100,101,110,7,0,0,48,3,93,227,29,165]

2019-09-30T21:56:11.668Z zigbee-herdsman:unpi:parser --- parseNext [254,77,68,129,0,0,0,0,93,227,1,1,0,178,0,94,50,216,0,0,57,24,2,1,5,0,0,66,25,84,82,65,68,70,82,73,32,111,112,101,110,47,99,108,111,115,101,32,114,101,109,111,116,101,4,0,0,66,14,73,75,69,65,32,111,102,32,83,119,101,100,101,110,7,0,0,48,3,93,227,29,165]

2019-09-30T21:56:11.669Z zigbee-herdsman:unpi:parser --> parsed 77 - 2 - 4 - 129 - []��^2�9BTRADFRI open/close remoteBIKEA of Sweden0]�] - 165

2019-09-30T21:56:11.669Z zigbee-herdsman:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":0,"srcaddr":58205,"srcendpoint":1,"dstendpoint":1,"wasbroadcast":0,"linkquality":178,"securityuse":0,"timestamp":14168670,"transseqnumber":0,"len":57,"data":{"type":"Buffer","data":[24,2,1,5,0,0,66,25,84,82,65,68,70,82,73,32,111,112,101,110,47,99,108,111,115,101,32,114,101,109,111,116,101,4,0,0,66,14,73,75,69,65,32,111,102,32,83,119,101,100,101,110,7,0,0,48,3]}}

2019-09-30T21:56:11.675Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true},"transactionSequenceNumber":2,"manufacturerCode":null,"commandIdentifier":1},"Payload":[{"attrId":5,"status":0,"dataType":66,"attrData":"TRADFRI open/close remote"},{"attrId":4,"status":0,"dataType":66,"attrData":"IKEA of Sweden"},{"attrId":7,"status":0,"dataType":48,"attrData":3}],"Cluster":{"ID":0,"attributes":{"zclVersion":{"ID":0,"type":32,"name":"zclVersion"},"appVersion":{"ID":1,"type":32,"name":"appVersion"},"stackVersion":{"ID":2,"type":32,"name":"stackVersion"},"hwVersion":{"ID":3,"type":32,"name":"hwVersion"},"manufacturerName":{"ID":4,"type":66,"name":"manufacturerName"},"modelId":{"ID":5,"type":66,"name":"modelId"},"dateCode":{"ID":6,"type":66,"name":"dateCode"},"powerSource":{"ID":7,"type":48,"name":"powerSource"},"appProfileVersion":{"ID":8,"type":48,"name":"appProfileVersion"},"swBuildId":{"ID":16384,"type":66,"name":"swBuildId"},"locationDesc":{"ID":16,"type":66,"name":"locationDesc"},"physicalEnv":{"ID":17,"type":48,"name":"physicalEnv"},"deviceEnabled":{"ID":18,"type":16,"name":"deviceEnabled"},"alarmMask":{"ID":19,"type":24,"name":"alarmMask"},"disableLocalConfig":{"ID":20,"type":24,"name":"disableLocalConfig"}},"name":"genBasic","commands":{"resetFactDefault":{"ID":0,"parameters":[],"name":"resetFactDefault"}},"commandsResponse":{}}},"networkAddress":58205,"endpoint":1,"linkquality":178,"groupID":0}'

2019-09-30T21:56:11.684Z zigbee-herdsman:unpi:parser --- parseNext []


qtt:debug 2019-09-30T21:56:11: Received Zigbee message from 'tradfri-open-close-remote-1' of type 'readResponse' with data '{"modelId":"TRADFRI open/close remote","manufacturerName":"IKEA of Sweden","powerSource":3}' from endpoint 1 with groupID 0

zigbee2mqtt:warn  2019-09-30T21:56:11: Received message from unsupported device with Zigbee model 'TRADFRI open/close remote'

zigbee2mqtt:warn  2019-09-30T21:56:11: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.

2019-09-30T21:56:11.747Z zigbee-herdsman:controller:device Interview - got 'modelId,manufacturerName,powerSource' for device '0x086bd7fffe57f940'

2019-09-30T21:56:11.757Z zigbee-herdsman:znp:SREQ --> AF - dataRequest - {"dstaddr":58205,"destendpoint":1,"srcendpoint":1,"clusterid":0,"transid":5,"options":0,"radius":30,"len":9,"data":{"type":"Buffer","data":[16,3,0,0,0,1,0,2,0]}}

2019-09-30T21:56:11.758Z zigbee-herdsman:unpi:writer --> frame [254,19,36,1,93,227,1,1,0,0,5,0,30,9,16,3,0,0,0,1,0,2,0,138]

2019-09-30T21:56:11.767Z zigbee-herdsman:unpi:parser <-- [254,1,100,1,0,100]

2019-09-30T21:56:11.768Z zigbee-herdsman:unpi:parser --- parseNext [254,1,100,1,0,100]

2019-09-30T21:56:11.769Z zigbee-herdsman:unpi:parser --> parsed 1 - 3 - 4 - 1 - [] - 100

2019-09-30T21:56:11.769Z zigbee-herdsman:znp:SRSP <-- AF - dataRequest - {"status":0}

2019-09-30T21:56:11.770Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-30T21:56:13.719Z zigbee-herdsman:unpi:parser <-- [254,3,68,128,0,1,5,195]

2019-09-30T21:56:13.720Z zigbee-herdsman:unpi:parser --- parseNext [254,3,68,128,0,1,5,195]

2019-09-30T21:56:13.720Z zigbee-herdsman:unpi:parser --> parsed 3 - 2 - 4 - 128 - [] - 195

2019-09-30T21:56:13.721Z zigbee-herdsman:znp:AREQ <-- AF - dataConfirm - {"status":0,"endpoint":1,"transid":5}

2019-09-30T21:56:13.722Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-30T21:56:13.736Z zigbee-herdsman:unpi:parser <-- [254,38,68,129,0,0,0,0,93,227,1,1,0,178,0,170,75,216,0,0,18,24,3,1,0,0,0,32,3,1,0,0,32,34,2,0,0,32,98,93,227,29,29]

2019-09-30T21:56:13.737Z zigbee-herdsman:unpi:parser --- parseNext [254,38,68,129,0,0,0,0,93,227,1,1,0,178,0,170,75,216,0,0,18,24,3,1,0,0,0,32,3,1,0,0,32,34,2,0,0,32,98,93,227,29,29]

2019-09-30T21:56:13.737Z zigbee-herdsman:unpi:parser --> parsed 38 - 2 - 4 - 129 - []���K�  " b]�] - 29

2019-09-30T21:56:13.738Z zigbee-herdsman:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":0,"srcaddr":58205,"srcendpoint":1,"dstendpoint":1,"wasbroadcast":0,"linkquality":178,"securityuse":0,"timestamp":14175146,"transseqnumber":0,"len":18,"data":{"type":"Buffer","data":[24,3,1,0,0,0,32,3,1,0,0,32,34,2,0,0,32,98]}}

2019-09-30T21:56:13.739Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true},"transactionSequenceNumber":3,"manufacturerCode":null,"commandIdentifier":1},"Payload":[{"attrId":0,"status":0,"dataType":32,"attrData":3},{"attrId":1,"status":0,"dataType":32,"attrData":34},{"attrId":2,"status":0,"dataType":32,"attrData":98}],"Cluster":{"ID":0,"attributes":{"zclVersion":{"ID":0,"type":32,"name":"zclVersion"},"appVersion":{"ID":1,"type":32,"name":"appVersion"},"stackVersion":{"ID":2,"type":32,"name":"stackVersion"},"hwVersion":{"ID":3,"type":32,"name":"hwVersion"},"manufacturerName":{"ID":4,"type":66,"name":"manufacturerName"},"modelId":{"ID":5,"type":66,"name":"modelId"},"dateCode":{"ID":6,"type":66,"name":"dateCode"},"powerSource":{"ID":7,"type":48,"name":"powerSource"},"appProfileVersion":{"ID":8,"type":48,"name":"appProfileVersion"},"swBuildId":{"ID":16384,"type":66,"name":"swBuildId"},"locationDesc":{"ID":16,"type":66,"name":"locationDesc"},"physicalEnv":{"ID":17,"type":48,"name":"physicalEnv"},"deviceEnabled":{"ID":18,"type":16,"name":"deviceEnabled"},"alarmMask":{"ID":19,"type":24,"name":"alarmMask"},"disableLocalConfig":{"ID":20,"type":24,"name":"disableLocalConfig"}},"name":"genBasic","commands":{"resetFactDefault":{"ID":0,"parameters":[],"name":"resetFactDefault"}},"commandsResponse":{}}},"networkAddress":58205,"endpoint":1,"linkquality":178,"groupID":0}'

2019-09-30T21:56:13.748Z zigbee-herdsman:unpi:parser --- parseNext []

zigbee2mqtt:debug 2019-09-30T21:56:13: Received Zigbee message from 'tradfri-open-close-remote-1' of type 'readResponse' with data '{"zclVersion":3,"appVersion":34,"stackVersion":98}' from endpoint 1 with groupID 0

zigbee2mqtt:warn  2019-09-30T21:56:13: Received message from unsupported device with Zigbee model 'TRADFRI open/close remote'

zigbee2mqtt:warn  2019-09-30T21:56:13: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.

2019-09-30T21:56:13.806Z zigbee-herdsman:controller:device Interview - got 'zclVersion,appVersion,stackVersion' for device '0x086bd7fffe57f940'

2019-09-30T21:56:13.815Z zigbee-herdsman:znp:SREQ --> AF - dataRequest - {"dstaddr":58205,"destendpoint":1,"srcendpoint":1,"clusterid":0,"transid":6,"options":0,"radius":30,"len":9,"data":{"type":"Buffer","data":[16,4,0,3,0,6,0,0,64]}}

2019-09-30T21:56:13.816Z zigbee-herdsman:unpi:writer --> frame [254,19,36,1,93,227,1,1,0,0,6,0,30,9,16,4,0,3,0,6,0,0,64,200]

2019-09-30T21:56:13.824Z zigbee-herdsman:unpi:parser <-- [254,1,100,1,0,100]

2019-09-30T21:56:13.825Z zigbee-herdsman:unpi:parser --- parseNext [254,1,100,1,0,100]

2019-09-30T21:56:13.825Z zigbee-herdsman:unpi:parser --> parsed 1 - 3 - 4 - 1 - [] - 100

2019-09-30T21:56:13.826Z zigbee-herdsman:znp:SRSP <-- AF - dataRequest - {"status":0}

2019-09-30T21:56:13.827Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-30T21:56:15.797Z zigbee-herdsman:unpi:parser <-- [254,3,68,128,0,1,6,192]

2019-09-30T21:56:15.798Z zigbee-herdsman:unpi:parser --- parseNext [254,3,68,128,0,1,6,192]

2019-09-30T21:56:15.798Z zigbee-herdsman:unpi:parser --> parsed 3 - 2 - 4 - 128 - [] - 192

2019-09-30T21:56:15.799Z zigbee-herdsman:znp:AREQ <-- AF - dataConfirm - {"status":0,"endpoint":1,"transid":6}

2019-09-30T21:56:15.800Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-30T21:56:15.822Z zigbee-herdsman:unpi:parser <-- [254,53,68,129,0,0,0,0,93,227,1,1,0,178,0,29,101,216,0,0,33,24,4,1,3,0,0,32,1,6,0,0,66,8,50,48,49,57,48,51,49,49,0,64,0,66,7,50,46,50,46,48,48,56,93,227,29,153]

2019-09-30T21:56:15.823Z zigbee-herdsman:unpi:parser --- parseNext [254,53,68,129,0,0,0,0,93,227,1,1,0,178,0,29,101,216,0,0,33,24,4,1,3,0,0,32,1,6,0,0,66,8,50,48,49,57,48,51,49,49,0,64,0,66,7,50,46,50,46,48,48,56,93,227,29,153]

2019-09-30T21:56:15.824Z zigbee-herdsman:unpi:parser --> parsed 53 - 2 - 4 - 129 - []��e�! B20190311@B2.2.008]�] - 153

2019-09-30T21:56:15.825Z zigbee-herdsman:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":0,"srcaddr":58205,"srcendpoint":1,"dstendpoint":1,"wasbroadcast":0,"linkquality":178,"securityuse":0,"timestamp":14181661,"transseqnumber":0,"len":33,"data":{"type":"Buffer","data":[24,4,1,3,0,0,32,1,6,0,0,66,8,50,48,49,57,48,51,49,49,0,64,0,66,7,50,46,50,46,48,48,56]}}

2019-09-30T21:56:15.827Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true},"transactionSequenceNumber":4,"manufacturerCode":null,"commandIdentifier":1},"Payload":[{"attrId":3,"status":0,"dataType":32,"attrData":1},{"attrId":6,"status":0,"dataType":66,"attrData":"20190311"},{"attrId":16384,"status":0,"dataType":66,"attrData":"2.2.008"}],"Cluster":{"ID":0,"attributes":{"zclVersion":{"ID":0,"type":32,"name":"zclVersion"},"appVersion":{"ID":1,"type":32,"name":"appVersion"},"stackVersion":{"ID":2,"type":32,"name":"stackVersion"},"hwVersion":{"ID":3,"type":32,"name":"hwVersion"},"manufacturerName":{"ID":4,"type":66,"name":"manufacturerName"},"modelId":{"ID":5,"type":66,"name":"modelId"},"dateCode":{"ID":6,"type":66,"name":"dateCode"},"powerSource":{"ID":7,"type":48,"name":"powerSource"},"appProfileVersion":{"ID":8,"type":48,"name":"appProfileVersion"},"swBuildId":{"ID":16384,"type":66,"name":"swBuildId"},"locationDesc":{"ID":16,"type":66,"name":"locationDesc"},"physicalEnv":{"ID":17,"type":48,"name":"physicalEnv"},"deviceEnabled":{"ID":18,"type":16,"name":"deviceEnabled"},"alarmMask":{"ID":19,"type":24,"name":"alarmMask"},"disableLocalConfig":{"ID":20,"type":24,"name":"disableLocalConfig"}},"name":"genBasic","commands":{"resetFactDefault":{"ID":0,"parameters":[],"name":"resetFactDefault"}},"commandsResponse":{}}},"networkAddress":58205,"endpoint":1,"linkquality":178,"groupID":0}'

2019-09-30T21:56:15.837Z zigbee-herdsman:unpi:parser --- parseNext []

zigbee2mqtt:debug 2019-09-30T21:56:15: Received Zigbee message from 'tradfri-open-close-remote-1' of type 'readResponse' with data '{"hwVersion":1,"dateCode":"20190311","swBuildId":"2.2.008"}' from endpoint 1 with groupID 0

zigbee2mqtt:warn  2019-09-30T21:56:15: Received message from unsupported device with Zigbee model 'TRADFRI open/close remote'

zigbee2mqtt:warn  2019-09-30T21:56:15: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.

2019-09-30T21:56:15.888Z zigbee-herdsman:controller:device Interview - got 'hwVersion,dateCode,swBuildId' for device '0x086bd7fffe57f940'

2019-09-30T21:56:15.897Z zigbee-herdsman:controller:device Interview - completed for device '0x086bd7fffe57f940'

2019-09-30T21:56:15.907Z zigbee-herdsman:controller:log Succesfully interviewed '0x086bd7fffe57f940'

zigbee2mqtt:info  2019-09-30T21:56:15: Successfully interviewed 'tradfri-open-close-remote-1', device has successfully been paired

zigbee2mqtt:warn  2019-09-30T21:56:15: Device 'tradfri-open-close-remote-1' with Zigbee model 'TRADFRI open/close remote' is NOT supported, please follow https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html

zigbee2mqtt:info  2019-09-30T21:56:15: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_successful","meta":{"friendly_name":"tradfri-open-close-remote-1","supported":false}}'

Pressing the close button:

2019-09-30T22:03:18.738Z zigbee-herdsman:unpi:parser <-- [254,23,68,129,0,0,2,1,115,139,1,1,0,152,0,89,143,236,0,0,3,1,5,1,115,139,11,126]

2019-09-30T22:03:18.738Z zigbee-herdsman:unpi:parser --- parseNext [254,23,68,129,0,0,2,1,115,139,1,1,0,152,0,89,143,236,0,0,3,1,5,1,115,139,11,126]

2019-09-30T22:03:18.739Z zigbee-herdsman:unpi:parser --> parsed 23 - 2 - 4 - 129 - [s��Y��s�] - 126

2019-09-30T22:03:18.740Z zigbee-herdsman:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":258,"srcaddr":35699,"srcendpoint":1,"dstendpoint":1,"wasbroadcast":0,"linkquality":152,"securityuse":0,"timestamp":15503193,"transseqnumber":0,"len":3,"data":{"type":"Buffer","data":[1,5,1]}}

�2019-09-30T22:03:18.742Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":false},"transactionSequenceNumber":5,"manufacturerCode":null,"commandIdentifier":1},"Payload":{},"Cluster":{"ID":258,"attributes":{"windowCoveringType":{"ID":0,"type":48,"name":"windowCoveringType"},"physicalClosedLimitLiftCm":{"ID":1,"type":33,"name":"physicalClosedLimitLiftCm"},"physicalClosedLimitTiltDdegree":{"ID":2,"type":33,"name":"physicalClosedLimitTiltDdegree"},"currentPositionLiftCm":{"ID":3,"type":33,"name":"currentPositionLiftCm"},"currentPositionTiltDdegree":{"ID":4,"type":33,"name":"currentPositionTiltDdegree"},"numOfActuationsLift":{"ID":5,"type":33,"name":"numOfActuationsLift"},"numOfActuationsTilt":{"ID":6,"type":33,"name":"numOfActuationsTilt"},"configStatus":{"ID":7,"type":24,"name":"configStatus"},"currentPositionLiftPercentage":{"ID":8,"type":32,"name":"currentPositionLiftPercentage"},"currentPositionTiltPercentage":{"ID":9,"type":32,"name":"currentPositionTiltPercentage"},"operationalStatus":{"ID":10,"type":24,"name":"operationalStatus"},"installedOpenLimitLiftCm":{"ID":16,"type":33,"name":"installedOpenLimitLiftCm"},"installedClosedLimitLiftCm":{"ID":17,"type":33,"name":"installedClosedLimitLiftCm"},"installedOpenLimitTiltDdegree":{"ID":18,"type":33,"name":"installedOpenLimitTiltDdegree"},"installedClosedLimitTiltDdegree":{"ID":19,"type":33,"name":"installedClosedLimitTiltDdegree"},"velocityLift":{"ID":20,"type":33,"name":"velocityLift"},"accelerationTimeLift":{"ID":21,"type":33,"name":"accelerationTimeLift"},"decelerationTimeLift":{"ID":22,"type":33,"name":"decelerationTimeLift"},"windowCoveringMode":{"ID":23,"type":24,"name":"windowCoveringMode"},"intermediateSetpointsLift":{"ID":24,"type":65,"name":"intermediateSetpointsLift"},"intermediateSetpointsTilt":{"ID":25,"type":65,"name":"intermediateSetpointsTilt"},"ubisysTurnaroundGuardTime":{"ID":4096,"type":32,"manufacturerCode":4338,"name":"ubisysTurnaroundGuardTime"},"ubisysLiftToTiltTransitionSteps":{"ID":4097,"type":33,"manufacturerCode":4338,"name":"ubisysLiftToTiltTransitionSteps"},"ubisysTotalSteps":{"ID":4098,"type":33,"manufacturerCode":4338,"name":"ubisysTotalSteps"},"ubisysLiftToTiltTransitionSteps2":{"ID":4099,"type":33,"manufacturerCode":4338,"name":"ubisysLiftToTiltTransitionSteps2"},"ubisysTotalSteps2":{"ID":4100,"type":33,"manufacturerCode":4338,"name":"ubisysTotalSteps2"},"ubisysAdditionalSteps":{"ID":4101,"type":32,"manufacturerCode":4338,"name":"ubisysAdditionalSteps"},"ubisysInactivePowerThreshold":{"ID":4102,"type":33,"manufacturerCode":4338,"name":"ubisysInactivePowerThreshold"},"ubisysStartupSteps":{"ID":4103,"type":33,"manufacturerCode":4338,"name":"ubisysStartupSteps"}},"name":"closuresWindowCovering","commands":{"upOpen":{"ID":0,"parameters":[],"name":"upOpen"},"downClose":{"ID":1,"parameters":[],"name":"downClose"},"stop":{"ID":2,"parameters":[],"name":"stop"},"goToLiftValue":{"ID":4,"parameters":[{"name":"liftvalue","type":33}],"name":"goToLiftValue"},"goToLiftPercentage":{"ID":5,"parameters":[{"name":"percentageliftvalue","type":32}],"name":"goToLiftPercentage"},"goToTiltValue":{"ID":7,"parameters":[{"name":"tiltvalue","type":33}],"name":"goToTiltValue"},"goToTiltPercentage":{"ID":8,"parameters":[{"name":"percentagetiltvalue","type":32}],"name":"goToTiltPercentage"}},"commandsResponse":{}}},"networkAddress":35699,"endpoint":1,"linkquality":152,"groupID":0}'

zigbee2mqtt:debug 2019-09-30T22:03:18: Received Zigbee message from 'tradfri-open-close-remote-1' of type 'commandDownClose' with data '{}' from endpoint 1 with groupID 0

zigbee2mqtt:warn  2019-09-30T22:03:18: Received message from unsupported device with Zigbee model 'TRADFRI open/close remote'

zigbee2mqtt:warn  2019-09-30T22:03:18: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.

2019-09-30T22:03:18.750Z zigbee-herdsman:znp:SREQ --> AF - dataRequest - {"dstaddr":35699,"destendpoint":1,"srcendpoint":1,"clusterid":258,"transid":27,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[24,5,11,1,0]}}

2019-09-30T22:03:18.751Z zigbee-herdsman:unpi:writer --> frame [254,15,36,1,115,139,1,1,2,1,27,0,30,5,24,5,11,1,0,198]

2019-09-30T22:03:18.754Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-30T22:03:18.763Z zigbee-herdsman:unpi:parser <-- [254,1,100,1,0,100]

2019-09-30T22:03:18.764Z zigbee-herdsman:unpi:parser --- parseNext [254,1,100,1,0,100]

2019-09-30T22:03:18.764Z zigbee-herdsman:unpi:parser --> parsed 1 - 3 - 4 - 1 - [] - 100

2019-09-30T22:03:18.765Z zigbee-herdsman:znp:SRSP <-- AF - dataRequest - {"status":0}

2019-09-30T22:03:18.765Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-30T22:03:19.774Z zigbee-herdsman:unpi:parser <-- [254,3,68,128,0,1,27,221]

2019-09-30T22:03:19.775Z zigbee-herdsman:unpi:parser --- parseNext [254,3,68,128,0,1,27,221]

2019-09-30T22:03:19.775Z zigbee-herdsman:unpi:parser --> parsed 3 - 2 - 4 - 128 - [] - 221

2019-09-30T22:03:19.776Z zigbee-herdsman:znp:AREQ <-- AF - dataConfirm - {"status":0,"endpoint":1,"transid":27}

2019-09-30T22:03:19.776Z zigbee-herdsman:unpi:parser --- parseNext []

Pressing the open button:

2019-09-30T22:05:51.774Z zigbee-herdsman:unpi:parser <-- [254,23,68,129,0,0,2,1,115,139,1,1,0,139,0,94,219,243,0,0,3,1,6,0,115,139,11,35]

2019-09-30T22:05:51.775Z zigbee-herdsman:unpi:parser --- parseNext [254,23,68,129,0,0,2,1,115,139,1,1,0,139,0,94,219,243,0,0,3,1,6,0,115,139,11,35]

2019-09-30T22:05:51.775Z zigbee-herdsman:unpi:parser --> parsed 23 - 2 - 4 - 129 - [s��^��s�] - 35

2019-09-30T22:05:51.776Z zigbee-herdsman:znp:AREQ <-- AF - incomingMsg - {"groupid":0,"clusterid":258,"srcaddr":35699,"srcendpoint":1,"dstendpoint":1,"wasbroadcast":0,"linkquality":139,"securityuse":0,"timestamp":15981406,"transseqnumber":0,"len":3,"data":{"type":"Buffer","data":[1,6,0]}}

�2019-09-30T22:05:51.779Z zigbee-herdsman:controller:log Received 'zcl' data '{"frame":{"Header":{"frameControl":{"frameType":1,"manufacturerSpecific":false,"direction":0,"disableDefaultResponse":false},"transactionSequenceNumber":6,"manufacturerCode":null,"commandIdentifier":0},"Payload":{},"Cluster":{"ID":258,"attributes":{"windowCoveringType":{"ID":0,"type":48,"name":"windowCoveringType"},"physicalClosedLimitLiftCm":{"ID":1,"type":33,"name":"physicalClosedLimitLiftCm"},"physicalClosedLimitTiltDdegree":{"ID":2,"type":33,"name":"physicalClosedLimitTiltDdegree"},"currentPositionLiftCm":{"ID":3,"type":33,"name":"currentPositionLiftCm"},"currentPositionTiltDdegree":{"ID":4,"type":33,"name":"currentPositionTiltDdegree"},"numOfActuationsLift":{"ID":5,"type":33,"name":"numOfActuationsLift"},"numOfActuationsTilt":{"ID":6,"type":33,"name":"numOfActuationsTilt"},"configStatus":{"ID":7,"type":24,"name":"configStatus"},"currentPositionLiftPercentage":{"ID":8,"type":32,"name":"currentPositionLiftPercentage"},"currentPositionTiltPercentage":{"ID":9,"type":32,"name":"currentPositionTiltPercentage"},"operationalStatus":{"ID":10,"type":24,"name":"operationalStatus"},"installedOpenLimitLiftCm":{"ID":16,"type":33,"name":"installedOpenLimitLiftCm"},"installedClosedLimitLiftCm":{"ID":17,"type":33,"name":"installedClosedLimitLiftCm"},"installedOpenLimitTiltDdegree":{"ID":18,"type":33,"name":"installedOpenLimitTiltDdegree"},"installedClosedLimitTiltDdegree":{"ID":19,"type":33,"name":"installedClosedLimitTiltDdegree"},"velocityLift":{"ID":20,"type":33,"name":"velocityLift"},"accelerationTimeLift":{"ID":21,"type":33,"name":"accelerationTimeLift"},"decelerationTimeLift":{"ID":22,"type":33,"name":"decelerationTimeLift"},"windowCoveringMode":{"ID":23,"type":24,"name":"windowCoveringMode"},"intermediateSetpointsLift":{"ID":24,"type":65,"name":"intermediateSetpointsLift"},"intermediateSetpointsTilt":{"ID":25,"type":65,"name":"intermediateSetpointsTilt"},"ubisysTurnaroundGuardTime":{"ID":4096,"type":32,"manufacturerCode":4338,"name":"ubisysTurnaroundGuardTime"},"ubisysLiftToTiltTransitionSteps":{"ID":4097,"type":33,"manufacturerCode":4338,"name":"ubisysLiftToTiltTransitionSteps"},"ubisysTotalSteps":{"ID":4098,"type":33,"manufacturerCode":4338,"name":"ubisysTotalSteps"},"ubisysLiftToTiltTransitionSteps2":{"ID":4099,"type":33,"manufacturerCode":4338,"name":"ubisysLiftToTiltTransitionSteps2"},"ubisysTotalSteps2":{"ID":4100,"type":33,"manufacturerCode":4338,"name":"ubisysTotalSteps2"},"ubisysAdditionalSteps":{"ID":4101,"type":32,"manufacturerCode":4338,"name":"ubisysAdditionalSteps"},"ubisysInactivePowerThreshold":{"ID":4102,"type":33,"manufacturerCode":4338,"name":"ubisysInactivePowerThreshold"},"ubisysStartupSteps":{"ID":4103,"type":33,"manufacturerCode":4338,"name":"ubisysStartupSteps"}},"name":"closuresWindowCovering","commands":{"upOpen":{"ID":0,"parameters":[],"name":"upOpen"},"downClose":{"ID":1,"parameters":[],"name":"downClose"},"stop":{"ID":2,"parameters":[],"name":"stop"},"goToLiftValue":{"ID":4,"parameters":[{"name":"liftvalue","type":33}],"name":"goToLiftValue"},"goToLiftPercentage":{"ID":5,"parameters":[{"name":"percentageliftvalue","type":32}],"name":"goToLiftPercentage"},"goToTiltValue":{"ID":7,"parameters":[{"name":"tiltvalue","type":33}],"name":"goToTiltValue"},"goToTiltPercentage":{"ID":8,"parameters":[{"name":"percentagetiltvalue","type":32}],"name":"goToTiltPercentage"}},"commandsResponse":{}}},"networkAddress":35699,"endpoint":1,"linkquality":139,"groupID":0}'

zigbee2mqtt:debug 2019-09-30T22:05:51: Received Zigbee message from 'tradfri-open-close-remote-1' of type 'commandUpOpen' with data '{}' from endpoint 1 with groupID 0

zigbee2mqtt:warn  2019-09-30T22:05:51: Received message from unsupported device with Zigbee model 'TRADFRI open/close remote'

zigbee2mqtt:warn  2019-09-30T22:05:51: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.

2019-09-30T22:05:51.787Z zigbee-herdsman:znp:SREQ --> AF - dataRequest - {"dstaddr":35699,"destendpoint":1,"srcendpoint":1,"clusterid":258,"transid":28,"options":0,"radius":30,"len":5,"data":{"type":"Buffer","data":[24,6,11,0,0]}}

2019-09-30T22:05:51.788Z zigbee-herdsman:unpi:writer --> frame [254,15,36,1,115,139,1,1,2,1,28,0,30,5,24,6,11,0,0,195]

2019-09-30T22:05:51.789Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-30T22:05:51.797Z zigbee-herdsman:unpi:parser <-- [254,1,100,1,0,100]

2019-09-30T22:05:51.798Z zigbee-herdsman:unpi:parser --- parseNext [254,1,100,1,0,100]

2019-09-30T22:05:51.798Z zigbee-herdsman:unpi:parser --> parsed 1 - 3 - 4 - 1 - [] - 100

2019-09-30T22:05:51.798Z zigbee-herdsman:znp:SRSP <-- AF - dataRequest - {"status":0}

2019-09-30T22:05:51.799Z zigbee-herdsman:unpi:parser --- parseNext []

2019-09-30T22:05:52.814Z zigbee-herdsman:unpi:parser <-- [254,3,68,128,0,1,28,218]

2019-09-30T22:05:52.815Z zigbee-herdsman:unpi:parser --- parseNext [254,3,68,128,0,1,28,218]

2019-09-30T22:05:52.815Z zigbee-herdsman:unpi:parser --> parsed 3 - 2 - 4 - 128 - [] - 218

2019-09-30T22:05:52.816Z zigbee-herdsman:znp:AREQ <-- AF - dataConfirm - {"status":0,"endpoint":1,"transid":28}

2019-09-30T22:05:52.817Z zigbee-herdsman:unpi:parser --- parseNext []

@RaymondMouthaan thanks, exactly what I needed, please try with the following branch: https://github.com/Koenkk/zigbee-shepherd-converters/tree/E1766

@RaymondMouthaan thanks, exactly what I needed, please try with the following branch: https://github.com/Koenkk/zigbee-shepherd-converters/tree/E1766

@Koenkk. can you explain in a few steps how to do that in conjunction with a running docker container? Should i install git, clone the repo and check out the branch? In which dir?

@RaymondMouthaan https://www.zigbee2mqtt.io/information/docker.html#support-new-devices

For the git clone, check out the E17661 branch and instead of -v $(pwd)/data/zigbee-shepherd-converters:/app/node_modules/zigbee-shepherd-converters \ do -v $(pwd)/data/zigbee-shepherd-converters:/app/node_modules/zigbee-herdsman-converters \

@Koenkk, can we have a chat on telegram or discord? Not sure if i do the right thing here

Yes, (koenkk)

Great work. When will the blinds be officially supported? Running Hassio with the official Z2M addon - can't wait to control my blinds in HA.

@simonriskjaer they are already in the edge version of the addon.

@koenkk I get this error:

zigbee2mqtt:error 2019-10-02T18:13:13: Publish 'set' 'position' to 'tradfri-window-blind-2' failed: 'Error: Data request failed with error: 'MAC transaction expired' (240)'

How can I fix this?

@Koenkk i know. The edge version fails to launch on my system, so I reverted back to the main addon. Just wondering what the release-cycle is for Z2M.

I also have the same issue...
After my ikea blinds were paired they worked for some hours until I tried to open them in the morning.
From there on I periodically got a zigbee_publish_error ('MAC transaction expired' (240)').
In this state I wanted to pair the repeater to improve and test the blinds again, but it was impossible. Only after I removed the blinds from the configuration and database, I have been able to pair the repeater on the first try.

Unfortunately I still have the problem with the blinds :(

When you got the MAC error, try to remove the battery from the blind for about 30 seconds and add it back in.

I had this issue before and @Koenkk advised to place the blind close(r) to the coordinator (or visaversa). This helped to control the blinds again.

After that I've paired the repeater(s) with z2m and moved the coordinator to its original location and removed the battery again and re-added back in. Hoping that the blind connects via the repeater to the coordinator. Not sure if it does, but up to now I have no more MAC issues and the blinds are perfectly controlled.

You might want to create a network map see for details this page

FYI - all of my devices:

zigbee2mqtt:info  2019-10-22T18:14:52: hue-dimmer-1 (0x0017880106b736ad): 324131092621 - Philips Hue dimmer switch (EndDevice)

zigbee2mqtt:info  2019-10-22T18:14:52: tradfri-remote-1 (0x90fd9ffffee6e4c0): E1524/E1810 - IKEA TRADFRI remote control (EndDevice)

zigbee2mqtt:info  2019-10-22T18:14:52: tradfri-remote-2 (0x90fd9ffffee8ea42): E1524/E1810 - IKEA TRADFRI remote control (EndDevice)

zigbee2mqtt:info  2019-10-22T18:14:52: tradfri-window-blind-2 (0x000d6ffffea940f2): E1926 - IKEA KADRILJ roller blind (EndDevice)

zigbee2mqtt:info  2019-10-22T18:14:52: tradfri-window-blind-1 (0x000d6ffffe9d5e34): E1926 - IKEA KADRILJ roller blind (EndDevice)

zigbee2mqtt:info  2019-10-22T18:14:52: tradfri-signal-repeater-1 (0x000d6ffffea9402f): E1746 - IKEA TRADFRI signal repeater (Router)

zigbee2mqtt:info  2019-10-22T18:14:52: tradfri-signal-repeater-2 (0x000d6ffffea1f2f2): E1746 - IKEA TRADFRI signal repeater (Router)

zigbee2mqtt:info  2019-10-22T18:14:52: tradfri-open-close-remote-1 (0x086bd7fffe57f940): E1766 - IKEA TRADFRI open/close remote (EndDevice)

zigbee2mqtt:info  2019-10-22T18:14:52: tradfri-open-close-remote-2 (0x086bd7fffe21aca4): E1766 - IKEA TRADFRI open/close remote (EndDevice)

zigbee2mqtt:info  2019-10-22T18:14:52: tradfri-window-blind-3 (0x086bd7fffe5be1c5): E1757 - IKEA FYRTUR roller blind (EndDevice)

zigbee2mqtt:info  2019-10-22T18:14:52: tradfri-window-blind-4 (0x086bd7fffe56a5b1): E1757 - IKEA FYRTUR roller blind (EndDevice)

zigbee2mqtt:info  2019-10-22T18:14:52: tradfri-window-blind-5 (0x086bd7fffe57e708): E1757 - IKEA FYRTUR roller blind (EndDevice)

zigbee2mqtt:info  2019-10-22T18:14:52: tradfri-window-blind-6 (0x086bd7fffe56b0bc): E1757 - IKEA FYRTUR roller blind (EndDevice)

zigbee2mqtt:info  2019-10-22T18:14:52: tradfri-open-close-remote-3 (0x086bd7fffe2c49de): E1766 - IKEA TRADFRI open/close remote (EndDevice)

zigbee2mqtt:info  2019-10-22T18:14:52: tradfri-open-close-remote-4 (0x086bd7fffe57f7fa): E1766 - IKEA TRADFRI open/close remote (EndDevice)

zigbee2mqtt:info  2019-10-22T18:14:52: tradfri-signal-repeater-3 (0x000d6ffffe8e8619): E1746 - IKEA TRADFRI signal repeater (Router)

zigbee2mqtt:info  2019-10-22T18:14:52: tradfri-signal-repeater-4 (0x000d6ffffe9cbc04): E1746 - IKEA TRADFRI signal repeater (Router)

zigbee2mqtt:info  2019-10-22T18:14:52: tradfri-open-close-remote-5 (0x086bd7fffe22a4ba): E1766 - IKEA TRADFRI open/close remote (EndDevice)

zigbee2mqtt:info  2019-10-22T18:14:52: tradfri-open-close-remote-6 (0x086bd7fffe599a4a): E1766 - IKEA TRADFRI open/close remote (EndDevice)

Mine aren't working 100% either. I have 3, with sufficient repeaters nearby.

Only one them reports its current status when it is changing state, pretty chatty when its going fully-open or fully-closed. The other's are opening and closing just fine, except that their status is always "open" in HASS.

I did have some connectivity issues before, but I switched my coordinator to other firmware (source-routing) which resolved those issues for me.

@syphernl for those who are always open, can you provide the debug log when closing and opening the curtain? Please post the log on pastebin.com and link it here.

To enable debug logging set in configuration.yaml:

advanced:
  log_level: debug

My blinds are working fine since 25 days. I had only one issue in the morning opening the blinds.

The blinds are connected to the repeater and coordinator. The first two days i had minimal issues and poor linkquality, i think it took some days to switch from a direct connection to the repeater.

@Koenkk It's actually pretty straightforward. CLOSE is sent to all blinds, but only one reports its status.

As requested, a pastebin:
https://pastebin.com/GCU1g18N

@RaymondMouthaan,

removing the battery and restarting the blinds did the trick! So far they work as expected!
Great!!!

@syphernl it looks that indeed the other blinds don't reports it status. This is also the reason why they stay open in HASS.

  • Did they never work?
  • Did you see a successfully configured for this device? This is necessary as it configures the reporting of the position. If you can share your database.db we can check this.

@Koenkk I don't recall seeing the actual position work for those two. But you are right, there is a difference in regards to reporting. The one that works differs from the others in the database:

{"id":2,"type":"EndDevice","ieeeAddr":"0x000d6ffffe96666","nwkAddr":45265,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Battery","modelId":"FYRTUR block-out roller blind","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":514,"inClusterList":[0,1,3,4,5,32,258,4096,64636],"outClusterList":[25,4096],"clusters":{"genBasic":{"attributes":{"modelId":"FYRTUR block-out roller blind","manufacturerName":"IKEA of Sweden","powerSource":3,"zclVersion":3,"appVersion":34,"stackVersion":99,"hwVersion":1,"dateCode":"20190311","swBuildId":"2.2.007"}},"closuresWindowCovering":{"attributes":{"currentPositionLiftPercentage":15}},"genPowerCfg":{"attributes":{"batteryPercentageRemaining":78}}}}},"appVersion":34,"stackVersion":99,"hwVersion":1,"dateCode":"20190311","swBuildId":"2.2.007","zclVersion":3,"interviewCompleted":true,"meta":{"configured":2}}
{"id":23,"type":"EndDevice","ieeeAddr":"0x000d6ffffe30555f","nwkAddr":15308,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Battery","modelId":"FYRTUR block-out roller blind","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":514,"inClusterList":[0,1,3,4,5,32,258,4096,64636],"outClusterList":[25,4096],"clusters":{"genBasic":{"attributes":{"modelId":"FYRTUR block-out roller blind","manufacturerName":"IKEA of Sweden","powerSource":3,"zclVersion":3,"appVersion":34,"stackVersion":99,"hwVersion":1,"dateCode":"20190311","swBuildId":"2.2.007"}},"genPowerCfg":{"attributes":{"batteryPercentageRemaining":91}},"closuresWindowCovering":{"attributes":{"currentPositionLiftPercentage":100}}}}},"appVersion":34,"stackVersion":99,"hwVersion":1,"dateCode":"20190311","swBuildId":"2.2.007","zclVersion":3,"interviewCompleted":true,"meta":{"configured":2}}
{"id":24,"type":"EndDevice","ieeeAddr":"0x000d6ffffe2b7772","nwkAddr":36483,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Battery","modelId":"FYRTUR block-out roller blind","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":514,"inClusterList":[0,1,3,4,5,32,258,4096,64636],"outClusterList":[25,4096],"clusters":{"genBasic":{"attributes":{"modelId":"FYRTUR block-out roller blind","manufacturerName":"IKEA of Sweden","powerSource":3,"zclVersion":3,"appVersion":34,"stackVersion":99,"hwVersion":1,"dateCode":"20190311","swBuildId":"2.2.007"}},"genPowerCfg":{"attributes":{"batteryPercentageRemaining":94}},"closuresWindowCovering":{"attributes":{"currentPositionLiftPercentage":36}}}}},"appVersion":34,"stackVersion":99,"hwVersion":1,"dateCode":"20190311","swBuildId":"2.2.007","zclVersion":3,"interviewCompleted":true,"meta":{"configured":2,"reporting":1}}

The last one has "reporting":1 while the others don't. But they all seem "configured"?

Can you stop zigbee2mqtt, set the configured value from 2 to 1 and start zigbee2mqtt; you should see the values changing from 1 to 2 again, do they all work after this?

Can you stop zigbee2mqtt, set the configured value from 2 to 1 and start zigbee2mqtt; you should see the values changing from 1 to 2 again, do they all work after this?

@Koenkk, I have the same issue as @syphernl and changing the configured value did not work for me.

Working blind (the one that reports position):
{"id":10,"type":"EndDevice","ieeeAddr":"0xd0cf5efffef55d26","nwkAddr":57552,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Battery","modelId":"FYRTUR block-out roller blind","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":514,"inClusterList":[0,1,3,4,5,32,258,4096,64636],"outClusterList":[25,4096],"clusters":{"genBasic":{"attributes":{"modelId":"FYRTUR block-out roller blind","manufacturerName":"IKEA of Sweden","powerSource":3,"zclVersion":3,"appVersion":34,"stackVersion":99,"hwVersion":1,"dateCode":"20190311","swBuildId":"2.2.007"}},"closuresWindowCovering":{"attributes":{"currentPositionLiftPercentage":0}},"genPowerCfg":{"attributes":{"batteryPercentageRemaining":98}}},"binds":[{"cluster":1,"type":"endpoint","deviceIeeeAddress":"0x00124b001936dcce","endpointID":1},{"cluster":258,"type":"endpoint","deviceIeeeAddress":"0x00124b001936dcce","endpointID":1}]}},"appVersion":34,"stackVersion":99,"hwVersion":1,"dateCode":"20190311","swBuildId":"2.2.007","zclVersion":3,"interviewCompleted":true,"meta":{"configured":2}}

Non-working blind (the one that doesn't report position):
{"id":14,"type":"EndDevice","ieeeAddr":"0xd0cf5efffecb6878","nwkAddr":55777,"manufId":4476,"manufName":"IKEA of Sweden","powerSource":"Battery","modelId":"FYRTUR block-out roller blind","epList":[1],"endpoints":{"1":{"profId":260,"epId":1,"devId":514,"inClusterList":[0,1,3,4,5,32,258,4096,64636],"outClusterList":[25,4096],"clusters":{"genBasic":{"attributes":{"modelId":"FYRTUR block-out roller blind","manufacturerName":"IKEA of Sweden","powerSource":3,"zclVersion":3,"appVersion":34,"stackVersion":99,"hwVersion":1,"dateCode":"20190311","swBuildId":"2.2.007"}},"closuresWindowCovering":{"attributes":{"currentPositionLiftPercentage":0}}},"binds":[{"cluster":1,"type":"endpoint","deviceIeeeAddress":"0x00124b001936dcce","endpointID":1},{"cluster":258,"type":"endpoint","deviceIeeeAddress":"0x00124b001936dcce","endpointID":1}]}},"appVersion":34,"stackVersion":99,"hwVersion":1,"dateCode":"20190311","swBuildId":"2.2.007","zclVersion":3,"interviewCompleted":true,"meta":{"configured":2}}

Update: Strangely the blind started reporting its position after a while. Now both the blinds are working well.

Can you stop zigbee2mqtt, set the configured value from 2 to 1 and start zigbee2mqtt; you should see the values changing from 1 to 2 again, do they all work after this?

2 out of 3 are reporting fine now. But the third one seems to refuse to move towards that state.

Edit: The fix was to remove the battery for ~30 seconds. Now it seems to be reporting its status properly.

Is anybody else experience large delays from calling a service to the blinds starting to move? I've even had cases where the blinds would get confused and it would continue going "down" until the blinds start climbing and then goes the wrong way.

Do you happen to know if there's anything technical behind the "holding devices close together" habit of Tradfri?

I have a CC2531 stick with external antenna, so holding stuff close to the antenna seems a little... weird. Still, Fyrtur and now also the repeater fail to pair with zigbee2mqtt for me.

The first time I used the repeater I could just pair it with z2m and it showed up in Home Assistant as expected. Pairing the blind, it didn't seem to talk to z2m at all. Nothing in the logs. So I re-paired remote, Fyrtur and repeater together to check if they work at all. They do.

Now I'm starting from a standalone remote-repeater-blind chain. Starting with the repeater I held the pairing/reset button. It started to breathe the white LED. It does not trigger any reaction from z2m though.
The same goes for Fyrtur. Holding both buttons it starts to breathe as well but "nothing happens". 🤦‍♂️

I can hold both devices close to the antenna, close to the stick, somewhere else, no reaction. Did you do anything else to make them pair with z2m? (Maybe a rain dance?)

zigbee2mqtt: 1.7.1
Firmware: 20190608
Vendor photo of the cc2531 stick including antenna.

@tanuva,

maybe you made the same mistake as I did?
These are only supported in the dev branch, read zigbee2mqtt.io on how to switch to it.

@Kiwifranky Good catch, indeed I was on master instead of dev. (didn't expect master to be the stable branch. :) )
Sadly, switching to dev didn't change the observed behavior at all. I still fail to pair the receiver as well as the blind to z2m.

Oh, and yes, I do see

2019-11-22 17:59:57: `permit_join` set to  `true` in configuration.yaml.

in the log. That would've been too easy...

Woot. After a few days not thinking about this at all I managed to pair the repeater again and the first Fyrtur. o/ It struck me that I should maybe try rebooting the Pi (that usually fixes Windows issues, Unix ones more rarely...) and, ta-dah, after that I was able to pair the repeater and the blind. Without issues, just as I expected things to work in the first place.

I would love to know what the actual issue was. Since I never saw anything looking like an error at all there won't be a lot look for I guess.

Great job by adding this device :). I have a few questions about how it works when you pair Fyrtur to zigbee2mqtt:

  • Does the repeater work as a zigbee router?
  • Can you pair the blind to report its state to the network while preserving the remote switch to work independently of my zigbee network?

The blind works very well out of the box with the remote switch. So I would like to preserve that (without need to automate the switch to control the blind) but also be able to see the blind's state and control it via my zigbee network.

  • Can you pair the blind to report its state to the network while preserving the remote switch to work independently of my zigbee network?

The blind works very well out of the box with the remote switch. So I would like to preserve that (without need to automate the switch to control the blind) but also be able to see the blind's state and control it via my zigbee network.

I would also like to know that.

Another question I have is about the battery reported. I have fully charged the battery and reported value is 50%, how is that possible?

Another question I have is about the battery reported. I have fully charged the battery and reported value is 50%, how is that possible?

I set mine up over the last few days, and gave one of the batteries a full charge - it's also showing as 50%. I wonder if the scale being used is wrong?

@pplucky the change linked above this comment should fix the 50% issue.

Can you please check if the position set on your blinds is being reported back to HA?

In HA, for me, position is always 100 and state is always Open. If I change the position manually in HA, physically it works, but position is temporarily changed and then goes back to 100.

If I control the blinds manually with the buttons near the battery lid, nothing is reported back to HA (position always 100 and State Open).

My zigbee2mqtt config for the cover:

devices:
  '0xd0cf5efffe6ed3e9':
    friendly_name: ikea_estore_80_cozinha
    retain: true

My Home Assistant cover config:

cover:
  - platform: "mqtt"
    name: 'Estore pequeno cozinha'
    availability_topic: "zigbee2mqtt/bridge/state"
    command_topic: "zigbee2mqtt/ikea_estore_80_cozinha/set"
    position_topic: "zigbee2mqtt/ikea_estore_80_cozinha"
    set_position_topic: "zigbee2mqtt/ikea_estore_80_cozinha/set"
    set_position_template: "{ \"position\": {{ position }} }"
    value_template: "{{ value_json.position }}"

I've read above, but could not find an actual answer on what the issue/fix is.

Thanks in advance for your help.

Can you please check if the position set on your blinds is being reported back to HA?

Position is reported for me, though on one, it didn't work initially and I had to remove and re-pair it.

Just got a new Fyrtur blind installed and paired with zigbee2mqtt. I also paired the remote successfully to zigbee2mqtt. I'm not planning to use home-assistant, but rather various homebridge MQTT plugins. But I can't find a complete list of the MQTT commands for opening, closing, querying and setting position, querying battery state, etc.

I have figured out how to command position of the blind, ala:

"zigbee2mqtt/ikea_blind_famroom_30in_N/set" -m '{"position": 100}'

and if I use the buttons on the blind to operate it, I get updates like {"position":55,"linkquality":78}, but I haven't managed to figure out the rest, since the docs are mentioning only HA config. How to I ask the device for its state, for example? Are open and close just positions 100 and 0 (or whatever lower limit you set)?

I also have the open/close remote paired, and receive messages on topic zigbee2mqtt/ikea_updown_remote_1 like {"linkquality":89,"click":"open|close|release"}. I presume release gets translated to a stop command when paired directly to the blinds. Is there any way to have the remote paired to zigbee2mqtt and have it also control the blinds? Or is it an either/or situation?

Thanks for your work on this!

Could really use some help with this, all. How can you bind a Fyrtur to zigbee2mqtt and bind the remote to the blinds at the same time?. For me I can only do one or the other...

I can pair the up/down remote via the Repeater to the blinds. Fine (though sometimes I have to repair to the repeater). Then I follow zigbee2mqtt's Fyrtur advice and press both buttons for 5s.

This _resets_ the Fyrtur device, and severs the blind's pairing to the remote. But then zigbee2mqtt finds and pairs with the blinds. Then I go to pair the remote to the blinds again, by short-pressing both buttons. This results in both the remote and the blind leaving the network right away:

payload '{"type":"device_removed","message":"left_network","meta":{"friendly_name":"0xIDOFBLINDS"}}'
payload '{"type":"device_removed","message":"left_network","meta":{"friendly_name":"0xIDOFREMOTE"}}'

and now the remote won't then pair with the blinds, either. So then I repair the remote to the repeater, reset the blinds with a 5s press, and start the process all over again! I've tried every combination I can think of...

So I can EITHER have the remote or Zigbee2mqtt paired to the blinds. How can I achieve both?!?!

EDIT: I can't even FOOL it by stopping zigbee2mqtt and unplugging my sniffer while re-pairing the remote to the blind. While that prevents the "left network" sadness, now when I restart zigbee2mqtt, I get the following error when trying to control the blinds with MQTT:

Error: Data request failed with error: 'MAC transaction expired' (240)'

@syphernl can you expand on this?

Remote: https://www.zigbee2mqtt.io/devices/E1743.html. I haven't used this one yet. IIUC it should be pairable directly to the blinds while they are part of the Zigbee network but haven't yet tried this. Otherwise you can bind the remote to your coordinator and use it from there.

I am so far unable to have the remote paired to the blind at the same time the blind is paired to z2m. I am able to pair both to z2m... what approach to this setup did you envision?

Thanks

I paired two E1926 (CC2530, Raspberry). Both reacting to {"state": "ON"} or {"state": "OPEN"}.
(also close, position, stop). "zigbee2mqtt/balkon_rollo-rechts_ikea/set"
I grouped both in configuration.yaml cause both a covering big window. When I send one of these orders to friendly_group_name nothing happens. "zigbee2mqtt/rolladen_wohnzimmer_gruppe/set"

Using {"state": "ON"} blind is responding: {"state":"OFF","brightness":0}
Using {"position": "60"} log gives: No converter available for 'position'

Does that mean, It's not possible to group blinds

thanks
Kay

Does that mean, It's not possible to group blinds

If you update to the head of the dev branch, you should be able to eliminate the "No converter" error for position. Be sure to follow the full directions for switching to the dev branch.

For me, however, group-based MQTT blinds commands now just silently fail. Has anybody got group commands working for blinds?

Hi, i tried yesterday to add my KADRILJ blinds to zigbee2mqtt. The blinds themself are connected but don't report a status. All statuses are 'unknown'. I use a CC2531 router and a CC2531 Coordinator with the latest source-routing flashed to it, to connect the blind to. Anyone can help me? Or do I have to use the repeater and open/close remote from Ikea to get it done? Many thanks

Info:
I have a CC2531 coordinator with source routing 20190619 flashed to it. And a CC2531 router with .bin from 201902 flashed to it.

The blind is connecting to the router.

For those still having issue with these blinds, #3015 suggested to pair the blinds directly to the TRADFRI signal repeater. Pairing instructions have been updated: https://www.zigbee2mqtt.io/devices/E1757.html#pairing

Does this method allow blinds to be grouped and addressed through a single MQTT call? I have no trouble controlling blinds individually with no repeater in the picture. Just can't get groups of blinds to behave (either with zigbee2mqtt/ikea_blind_group/set/position or fully with a remote bound to the group). Obviously if your controller is far from the blinds a repeater will help (mine are ~3-5m away).

Just a ping — is anyone having full success with a group of these blinds? By that I mean:

  1. Blinds stay reliably attached to network. (_I have experienced spontaneous “device leaving network” every few days._)
  2. Up/Down remote bound to a group of blinds, controls them quickly and can interrupt movements (e.g. stop, reverse), and stays bound. (_When I bind up/down remote, it can move group of blinds, but not interrupt motion, when z2m is running_).
  3. Can control a group of blinds directly via MQTT. (_commanding zigbee2mqtt/group/set/position fails silently for me_).

From other discussions with @Koenkk, it sounds like the next step would be to sniff the traffic from the remote to the repeater and blinds when working in "directly paired mode", so that z2m can reliably mimic that. I don't have a separate sniffer. Does anyone with a group of the blinds have one available?

Anyone got any hints on how to pair the Kadrilj and remote? I can pair the remote to the repeater and then the remote to the blind but holding the remote pair button down with pairing mode on in z2m shows nothing in the logs with pairing mode on. I've also tried pairing a blind by holding it next to the usb stick, pairing the repeater and factory resetting everything and trying again. Tried also pairing the remote to the repeater next to z2m

@jdtsmith Just wondering if you made any progress in grouping the blinds and the remote together. I tried to create a group, but unfortunately it does not allow me to control all the blinds in one room at once either.
The remote is also not working directly yet (ofcourse I can get it to work by adding some automation in Home Assistant, but it would be nice if it could be done within the ZigBee network).

I use two blinds and grouped them with z2m. They are directly connected to CC2530 without IKEA Repeater (same room). Newest z2m Version.

If i send commands to each single, all commands are recognized and will be fullfilled.
If I send commands to group, nothing ist happening.
I have a workarround in nodered, but group reacting in z2m would be nice.

kay

@itavero I can group them fine, but like @kaykoch, group commands silently fail. I also have had limited success binding the remote to the group (partially works, but can't interrupt moves). And lately the blinds seem to disappear from the network. So sadly not much progress to report.

Apparently the way to make progress is to sniff traffic to the group, since our dev does not have these blinds. For that you need another sniffer stick. If anyone is in the position to do this please let us know!

I do have some ZigBee sniffers somewhere. I reckon the idea is to capture the traffic when they are connected to the IKEA bridge and/or remote directly?

I think that's right. And see what happens when a group set command tries but fails. @Koenkk what should @itavero look for?

It's been several years since I did some Zigbee communication debugging. I should still have the tools so I can capture the traffic and analyze it with Wireshark.
Not sure how soon I'll be able to do that though, given that I still have to get the tools from underneath a pile of dust and my "test environment" is also my production environment (my users [read: girlfriend] just want things to work 😉).

Thanks @Koenkk. I had to "dust off" my Windows VM as well, but I got the sniffer working in the end.
I might have some time this Saturday to do some tests with a single remote and two blinds (let's hope I don't accidentally reset the height setting on the blinds this time).

@itavero @Koenkk awesome. Do you have the repeater as well? Might be good to put it into the mix.

Things I'd be very glad to see some progress on, that sniffed logs might be helpful for:

  1. getting zigbee2mqtt/group_of_blinds/set/position and the like working.
  2. getting the remote bound to blind groups such that it can stop and reversed moves (this has worked very occasionally, but usually doesn't).
  3. seeing why blinds sometimes drop from network or stop responding with error Error: AREQ - AF - dataConfirm after 5000ms.

I'll create the bare minimum as per the IKEA instructions first (that might already include the repeater), working towards a setup with multiple blinds and the Tradfri gateway.
Of course I'll be making logs along the way of actions like closing, opening and interrupting the blinds.

Any luck with the sniffing @itavero? Thanks for your work.

Can you please check if the position set on your blinds is being reported back to HA?

In HA, for me, position is always 100 and state is always Open. If I change the position manually in HA, physically it works, but position is temporarily changed and then goes back to 100.

If I control the blinds manually with the buttons near the battery lid, nothing is reported back to HA (position always 100 and State Open).

My zigbee2mqtt config for the cover:

devices:
  '0xd0cf5efffe6ed3e9':
    friendly_name: ikea_estore_80_cozinha
    retain: true

My Home Assistant cover config:

cover:
  - platform: "mqtt"
    name: 'Estore pequeno cozinha'
    availability_topic: "zigbee2mqtt/bridge/state"
    command_topic: "zigbee2mqtt/ikea_estore_80_cozinha/set"
    position_topic: "zigbee2mqtt/ikea_estore_80_cozinha"
    set_position_topic: "zigbee2mqtt/ikea_estore_80_cozinha/set"
    set_position_template: "{ \"position\": {{ position }} }"
    value_template: "{{ value_json.position }}"

I've read above, but could not find an actual answer on what the issue/fix is.

Thanks in advance for your help.

Did it work fine for you? What have you done?

@jdtsmith Unfortunately I haven't come around to it yet. As soon as I have, I'll report back here. ;)

@4sag For me this works just fine, but I'm using MQTT Discovery (so not manually configuring the device). The only thing that I ran into is that they don't respond via the HomeKit integration of HA, but that is unrelated to this piece of software. I think it probably ignores it due to the fact that the "last seen" is a long time ago, but I have yet to check if such logic is actually in the HomeKit integration and if there is a way to circumvent it.

@itavero Everything worked for me too, then it was updated, and now it always shows position 42, it answers buttons. Homekit works.

I'll throw my experience in this as well. I am able to join my blinds (4 total) to z2m - 3x paired directly to the coordinator and 1x going through an Ikea repeater. They are all controllable individually via z2m and HomeAssistant (via MQTT discovery). I am unable to control the group of them, it silently fails no matter what values I provide for position/state/etc.

As part of my debugging I have gone from ZHA (in HomeAssistant) to Zigbee2MQTT and while playing around with ZHA I tried to bind the remote included directly to the Level Control cluster and was able to get 2x of the 4 blinds working that way - so not 100% success but I am unable to recreate that success with Zigbee2MQTT.

@Koenkk I see when trying to bind it in z2m it is binding to closuresWindowCovering - I know it sounds like the correct one but I'm wondering if the level control cluster would work? I assume I could try this by overriding the device line here https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/devices.js#L1453 to include/replace with genLevelCtrl?

I am just starting to dig in on this and do not have a second device to sniff with yet.

Don't have an idea of the first place to look regarding the group issue not doing anything though.

Meta discussion: should this ticket be reopended?

Thanks, @mrardon. Do your blinds stay attached to the network for weeks or more? When you have the remote bound with the 2 of yours that work with it, can you stop/and reverse moves already in motion? What version of sniffer firmware and z2m are you running?

@jdtsmith I just received the blinds 2 days ago so haven't been able to experience your issue with them disconnecting from the network.

Unfortunately, the only time I got the remote to work with the 2 blinds by binding was in ZHA. In ZHA you can bind to arbitrary clusters. The level control cluster of the 2 blinds worked exactly as they should with the remote (open/close/hold then release/press to stop). I did forget to mention in ZHA I was using a Conbee II stick not a CC2531. I re-paired them to work with z2m when I switched and can no longer bind them to specific clusters (just allows closuresWindowCovering cluster for me). I know this is just anecdotal but I hope to get an additional sniffer to see whats going on.

I'm currently running z2m 1.13.0-dev on a CC2531 w/ zstack 1.2 20190608.

@mrardon I guess you are talking about binding the remote via https://www.zigbee2mqtt.io/information/binding.html?

If yes, could you share me your database.db entry of both the blinds and the remote that you bound.

Ignore what I said about the Level Control vs Window Closure, both clusters appear to control the blinds in ZHA.

@Koenkk Yes, I have been trying to bind it that way but it doesn't work, nor do the groups work with my blinds in Z2M.

Maybe I'm doing something wrong but this is how I tried everything:

Z2M

  1. Put in Pairing Mode (permit_join = true)
  2. Factory reset blinds (hold down up/down buttons on blinds for about 10 secs)
  3. Wait until blinds connects
  4. Put remote into pairing mode (pairing button on back press 4x rapidly)
  5. Wait until remote connects
  6. Create a blind_group with the blinds (Following steps here https://www.zigbee2mqtt.io/information/groups.html)
  7. Bind Remote to group

    • zigbee2mqtt/bridge/bind/blind_remote with payload blind_group (Follow steps here: https://www.zigbee2mqtt.io/information/binding.html)

    • Bind doesn't fail but nothing works

    • Attempting the binding with single blind instead of group has same outcome

To test out this idea I did everything in ZHA as well (using a Conbee II stick and then trying the CC2531) and have the desired outcome only with the Conbee II device. I can reliably control the blinds with the Conbee II via HA or the remote using bindings to the group.

ZHA (Conbee II) - Works

  1. Enable pairing mode in ZHA (HA-> Configuration -> ZHA -> Add Devices)
  2. Factory reset blinds (hold down up/down buttons on blinds for about 10 secs)
  3. Wait until blinds connects
  4. Put remote into pairing mode (pairing button on back press 4x rapidly)
  5. Wait until remote connects
  6. Create a ZHA group with the blinds (HA -> Configuration -> ZHA -> Groups -> + and add the blinds)
  7. Bind remote to Level Control or Window Covering cluster (both seem to work)

    • goto remote in ZHA and scroll down to Group Bindings

    • select the Group we added in step 6

    • select Level Control or Window Covering (both appear to work for me)

    • click 'Bind Group'

    • immediately after clicking Bind Group wake up the remote by pressing a button

  8. Remote works properly and control via HA works as well

ZHA (CC2531) - Cannot Bind Remote to Group properly

I tried the same thing in ZHA with my CC2531 and it was unable to continue after step 6 above. I just get a Bind_req failed when trying to do the group bind for level control or window closure.

I know there are a lot of variables here and not sure if any of this is related to the issues in Z2M but I find it odd that I'm running into similar issues with the CC2531 being the common piece right now.

_TLDR_:

  • Z2M - Individual blinds work via single command but unable to operate blinds as a group, nor can I use the remote bound to a group or single blind through Z2M.
  • ZHA with CC2531 - Individual blinds work via single command but unable to operate blinds as a group, nor can I use the remote bound to a group or single blind through ZHA with CC2531.
  • ZHA with Conbee II - Individual blinds work, group of blinds work, and binding remote to group works.

I am going to keep tinkering around but I am a real noob with Zigbee debugging and learning how Z2M works. I'll let you know if I find anything else.

If you could provide me 2 sniffs, one with ZHA + Conbee and one with z2m + cc2531 I can probably figure out why this doesnt work. (https://www.zigbee2mqtt.io/how_tos/how_to_sniff_zigbee_traffic.html)

@Koenkk Should have a separate sniffer cc2531 in a few days will try to get those sniffs to you once it arrives.

@Koenkk I got the additional sniffer and I was able to get the binding working. I am still unable to get the groups working. I've tried grouping them via the config approach and via adding them via the mqtt topic approach. When data is published to the group set topics the blinds do not react. The blinds do appear to group successfully just not respond to position/open/close commands.

I've pulled some frames for you - I'm not certain they are very helpful but here they are:

If you need something else let me know.

Could you share the pcapng files?

@Koenkk attached. It's the entire session I did that afternoon.
zigbee-blinds-binding-etc-capture.pcapng.zip

I've found out the issue. The remote has destination 0xFFFF while the command from z2m has destination 0xFFFD. 0xFFFF = all devices, 0xFFFD = all devices except sleeping end devices.

I've read the Z-Stack documentation/source code on how we can control this destination but I believe it's not possible. I've asked Texas Instruments for assistance: https://e2e.ti.com/support/wireless-connectivity/zigbee-and-thread/f/158/t/908663

Sounds like progress. Is that the same issue which prevents group-of-blinds commands from executing? @mrardon did you also sniff your Conbee II working with this? Might be interesting to see if it uses the 0xFFFF address. It could explain the sporadic behavior with the remote I have experienced depending on the blinds' sleep state.

Unfortunately it's not possible to send groups messages to 0xFFFF from Z-Stack (details: http://e2e.ti.com/support/wireless-connectivity/zigbee-and-thread/f/158/p/908663/3359326#3359326)

Does this also not work when the blind is connected through the bundled TRADFRI repeater? (https://www.zigbee2mqtt.io/devices/E1757.html#pairing)

That is disappointing.

The pairing instructions are unclear to me. This is procedure I just followed based where I'm at now for pairing:

  1. Remove the blind from z2m to start over basically
  2. Pair the repeater to z2m
  3. Momentary push the 2 buttons on the blind to pair to the repeater.

Does the blind never need to pair directly to z2m in this scenario? I currently just see the repeater in z2m. I'll be able to test more this weekend but trying that so far didn't seem to work for me.

And the goal is after pairing this way I should be able to control through Z2M groups since the repeater is always "awake"?

@jdtsmith Is this the method you used when pairing?

That's unfortunate. Is the 0xFFFF the confirmed culprit or just an educated guess?

Following those pairing instructions with the repeater doesn't really change anything. I did manage some (likely temporary) success through the following long sequence of steps:

  • Paired a new spare repeater.
  • Paired 2 blinds to the repeater at 1cm range.
  • Mounted blinds in their location (1-2m away from repeat, 2-3m from coordinator).
  • Checked if both blinds were connected to the repeater using graphviz. They had both reverted to direct connection to the coordinator.
  • Grouped both blinds:
:~ $ mosquitto_pub -t "zigbee2mqtt/bridge/group/famroom_blinds/add" -m "ikea_blind_famroom_30in_N"
:~ $ mosquitto_pub -t "zigbee2mqtt/bridge/group/famroom_blinds/add" -m "ikea_blind_famroom_30in_S"

which succeeds.

  • Send a group command:
$ mosquitto_pub -t "zigbee2mqtt/famroom_blinds/set/position" -m 20

which silently fails. This has never once worked.

  • Pair a remote to the same signal repeater.
  • While holding remote button to make sure it's awake, bind remote to the group:
$ mosquitto_pub -t "zigbee2mqtt/bridge/bind/ikea_updown_remote_2" -m famroom_blinds

which succeeds with clusters genOnOff, genLevelCtrl, and closuresWindowCovering.

  • Click remote down button once. Both blinds start dropping.
  • Click again. _One_ blind stops, the other continues. Click up to bring them back open.
  • Click and hold remote down button for 5s, then release button. Same blind stops on "release" event, other continues. Why does one blind in the group work and the other not? No idea.
  • Remove the repeater to which the blinds were bound. Re-pair misbehaving blind and re-add to group. Same behavior (one works correctly with remote, one doesn't).
  • Noticed that the blind that _is_ behaving is not publishing position messages even when commanded via MQTT. Re-pair and re-add to group. Now it behaves correctly and reports position. Both blinds have same firmware.
  • Noticed that 2 of my paired remote operates the blind group in the same manner, despite binding only one.
  • Removed battery on misbehaving blind for 2 minutes and reinstalled. Tried remote again. Both blinds now work correctly with either remote!!!

I will leave it like this for some time and see how stable it is. In the past, the blinds would drop off the network after a few days, setting you back to the start.

UPDATE: After 10 min, both blinds are now unreachable on the network with error 'No network route' (205))'. Sigh.

Using:

{
  "version": "1.12.2",
  "commit": "911cd58",
  "coordinator": {
    "type": "zStack30x",
    "meta": {
      "transportrev": 2,
      "product": 2,
      "majorrel": 2,
      "minorrel": 7,
      "maintrel": 2,
      "revision": 20190425
    }
  },
  "log_level": "info",
  "permit_join": true
}

That is disappointing.

The pairing instructions are unclear to me. This is procedure I just followed based where I'm at now for pairing:

  1. Remove the blind from z2m to start over basically
  2. Pair the repeater to z2m
  3. Momentary push the 2 buttons on the blind to pair to the repeater.

Does the blind never need to pair directly to z2m in this scenario? I currently just see the repeater in z2m. I'll be able to test more this weekend but trying that so far didn't seem to work for me.

And the goal is after pairing this way I should be able to control through Z2M groups since the repeater is always "awake"?

@jdtsmith Is this the method you used when pairing?

I'm taking blinds down, holding both buttons on blind for 10s to begin the pulsing white light, and holding it very close to the repeater (like 1cm) until the interview completes. So the blind certainly pairs to z2m, just via the repeater. Once I re-installed them, however, they reverted to my coordinator (which is just as close).

Sadly, as updated in my other post, both blinds have just stopped responding, with 'No network route' (205))'. Do your blinds drop off like this? If not, what firmware/z2m version are you using?

@jdtsmith Ok, that is what I was doing originally. The way the link describes pairing on z2m page is how you setup a stand alone pairing like when they originally come out of the box. I was unable to get anything to connect doing it that way.

I am pairing the repeater to z2m (paper clip in reset hole on repeater). I then factory reset the blinds - by holding both buttons for 10s. Everything shows up on the network and based on my network graph I currently have 2 on the coordinator and 2 going through the repeater. No real difference in functionality noticed except maybe a slight delay in sending commands to the ones on the repeater but I've also noticed them move around throughout the last few weeks. They seem to be staying on the network though, every once in a while I've had to send the command again (guessing just because device was asleep) to make it work but they are not falling off like you describe.

Coordinator:

{
  "type": "zStack12",
  "meta": {
    "transportrev": 2,
    "product": 0,
    "majorrel": 2,
    "minorrel": 6,
    "maintrel": 3,
    "revision": 20190608
  }
}

Z2M Version: 1.13.0-dev via HomeAssistant (zigbee2mqtt-edge) and it's just a random cc2531 dongle off of Amazon.

@Koenkk I've seen that you are working with the Conbee II implementation for Z2M, do you know if it has the same limitation?

@jdtsmith Ok, that is what I was doing originally. The way the link describes pairing on z2m page is how you setup a stand alone pairing like when they originally come out of the box. I was unable to get anything to connect doing it that way.

I agree. The IKEA pairing instructions and z2m are mutually exclusive. So "pairing to the repeater" as mentioned on that page is kind of meaningless, unless you want to go the IKEA way and have no z2m connection.

I am pairing the repeater to z2m (paper clip in reset hole on repeater). I then factory reset the blinds - by holding both buttons for 10s. Everything shows up on the network and based on my network graph I currently have 2 on the coordinator and 2 going through the repeater. No real difference in functionality noticed except maybe a slight delay in sending commands to the ones on the repeater but I've also noticed them move around throughout the last few weeks. They seem to be staying on the network though, every once in a while I've had to send the command again (guessing just because device was asleep) to make it work but they are not falling off like you describe.

OK good, I'll downgrade my firmware to 1.2 stack and try again. I had upgrade to ZStack3 in the hopes of improved functionality, but I think for basic connectivity it was better before. I don't use HA.

Unless something changes, I'm likely going to abandon group and remote bind functionality, and just run my logic as HomeKit automations. If that fails, I'll probably scrap this long experiment with z2m and get the Tradfri gateway, whose HomeKit support is apparently now flawless.

For what it's worth, my blinds have been paired since Dec 2019 (thankfully I had a comment here to remember the date :D) and other than charging the batteries, they work just fine. There was maybe a handful of times where 1 blind didn't respond to a command, but it's probably less than 5 times over that period.

I have the repeater and a bulb in the room with the 3 blinds. I have 2 open/close remotes paired + bound to the ZigBee group of blinds. I have home assistant setup to control them too, however, it has to address the blinds individually (via a Home Assistant group).

They even survived migrating from an older ZigBee stick to a newer one without needing anything.

No guarantees, despite being locked at home, time is still incredibly short, but I'll see if I can pcap the remotes issuing an open command to the group Vs Z2M issuing an open command. And - I doubt it'll help with all the other issues people are having, as I just don't have those issues.

@kiall I agree, seems to be Home Assistant group is all that works for me when it comes to groups. I was trying to get the z2m group working but as you can see doesn't work. While HA groups aren't perfect they give the best result currently for multiple blinds in a room.

For what it's worth, my blinds have been paired since Dec 2019 (thankfully I had a comment here to remember the date :D) and other than charging the batteries, they work just fine. There was maybe a handful of times where 1 blind didn't respond to a command, but it's probably less than 5 times over that period.

I have the repeater and a bulb in the room with the 3 blinds. I have 2 open/close remotes paired + bound to the ZigBee group of blinds. I have home assistant setup to control them too, however, it has to address the blinds individually (via a Home Assistant group).

They even survived migrating from an older ZigBee stick to a newer one without needing anything.

No guarantees, despite being locked at home, time is still incredibly short, but I'll see if I can pcap the remotes issuing an open command to the group Vs Z2M issuing an open command. And - I doubt it'll help with all the other issues people are having, as I just don't have those issues.

Thanks for the good experience report. What version of the firmware do you use on your controller? Your remote is bound using z2m binding? Or are you using HA groups to make that "binding"?

.

Thanks for the good experience report. What version of the firmware do you use on your controller?

The ZigBee 3 firmware - No idea offhand on the exact version 🤣 I tend to update it whenever I see a new version.

Your remote is bound using z2m binding? Or are you using HA groups to make that "binding"?

The remotes are bound to a ZigBee group. The binding was done using Zigbee2mqtt. I.e., when I turn home assistant off, the remotes and blinds continue to work just fine.

The remotes are bound to a ZigBee group.

@kiall Are your remotes able to reliably interrupt moves which are underway (stop and then reverse direction?). Can I also ask what version firmware your blinds are running? And one more quick one: do MQTT commands of the _group_ work (e.g. zigbee2mqtt/blind_group/set/position 20) work? Thanks.

@kiall Are your remotes able to reliably interrupt moves which are underway (stop and then reverse direction?).

Yes, this works just fine.

Can I also ask what version firmware your blinds are running?

The latest - 2.2.009 for the blinds, and 2.2.010 for the open/close remotes.

do MQTT commands of the group work (e.g. zigbee2mqtt/blind_group/set/position 20) work?

No, the ZigBee groups only work from other Zigbee devices - like the Open/Close remote. Calling those groups from Zigbee2Mqtt does nothing.

@kiall Are your remotes able to reliably interrupt moves which are underway (stop and then reverse direction?).

Yes, this works just fine.

Very surprising. I _occasionally_ get this working, but not for long. You have a standard CC2531 stick?

Can I also ask what version firmware your blinds are running?

The latest - 2.2.009 for the blinds, and 2.2.010 for the open/close remotes.

Same here, thanks.

do MQTT commands of the group work (e.g. zigbee2mqtt/blind_group/set/position 20) work?

No, the ZigBee groups only work from other Zigbee devices - like the Open/Close remote. Calling those groups from Zigbee2Mqtt does nothing.

That's consistent with everyone's experiences AFAIK.

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.

Has there been any progress on controlling groups from z2m?
I've got 9 blinds in 1 room. I had no issues creating the group and binding the button to the group. I created the group in HA per the instructions since they're not automatically discovered. When I try to control the group in HA I get the following in the logs, but none of the blinds move.

Zigbee2MQTT:info 2020-09-03 19:02:26: MQTT publish: topic 'zigbee2mqtt/side_window_blinds', payload '{"brightness":0,"position":0,"state":"OFF"}'

No issues controlling the individual entities and no issues controlling the group with the button.

Hi! I have paired brand new fyrtur blinds to z2m, but I have problem with save maximal opening length. The blinds react properly for double click (swing a bit up and down), but afterwards, the max opening is not saved - the blinds will go all the way down. Do you had this issue?

Additional question to blinds pilot - how do you handle it? Do you connect it directly to blinds or to z2m and make some automations in i.e. node-red?

Hi! I have paired brand new fyrtur blinds to z2m, but I have problem with save maximal opening length. The blinds react properly for double click (swing a bit up and down), but afterwards, the max opening is not saved - the blinds will go all the way down. Do you had this issue?

Just double checking, you need to press the up or down button the blinds itself and not the remote. The end position is saved in the blinds and not in z2m.

Additional question to blinds pilot - how do you handle it? Do you connect it directly to blinds or to z2m and make some automations in i.e. node-red?

In my case, the blinds, remote and repeater are connected to z2m. Which is then connected to Mosquitto and I use my own rule sets in OpenHAB to automatically open/close the blinds (halfway or completely), or by google voice command. All in Docker of course 😇

Thanks for feedback! Answers below:

Just double checking, you need to press the up or down button the blinds itself and not the remote. The end position is saved in the blinds and not in z2m.

Correct, I had using buttons from the blind. Another interesting fact - I had some error with blind positioning. I discovered that when I push button to put down, the blind was not ever stopping, but still turning. Eventually the fabric was wrapping the opposite way. I've made factory reset, removed blinds from Z2M and configure them from the scratch. The "non-stop" bug is gone, they stop correctly at the end.

However, I still cannot set maximal permitted extension - it rolls every time to the end.

Other strange behavior I've discovered - when I send blinds to the top, they wrap completely and stop moving, there is no motor stress etc. which seems fine However, the buttons act as the movement was still active - next push of either buttons act as a "stop". Of course the blind was already stopped before, therefore nothing is happening. Then, after "stopping", the next button push i.e. down acts as a new order to move.
Do you have the same or only I have such strange behavior? As if the top level was not recognized and blinds software was still wanting to finish task. I wonder if this is connected to no possibility of setting maximal length.

FYI, when I set position as a value from Z2M, i.e. "50", the available range is the full range of the blinds -> so the blind movement is correct, under consideration that no length limit was properly set.

In my case, the blinds, remote and repeater are connected to z2m. Which is then connected to Mosquitto and I use my own rule sets in OpenHAB to automatically open/close the blinds (halfway or completely), or by google voice command. All in Docker of course 😇

For now I've made very simple flow in Node-Red for remote. Basically it acts as passthrough for "OPEN" and "CLOSE" buttons. Works fine :).

Hi! I have paired brand new fyrtur blinds to z2m, but I have problem with save maximal opening length. The blinds react properly for double click (swing a bit up and down), but afterwards, the max opening is not saved - the blinds will go all the way down. Do you had this issue?

Just double checking, you need to press the up or down button the blinds itself and not the remote. The end position is saved in the blinds and not in z2m.

Additional question to blinds pilot - how do you handle it? Do you connect it directly to blinds or to z2m and make some automations in i.e. node-red?

In my case, the blinds, remote and repeater are connected to z2m. Which is then connected to Mosquitto and I use my own rule sets in OpenHAB to automatically open/close the blinds (halfway or completely), or by google voice command. All in Docker of course 😇

Hi!

@dietah
I am currently trying to integrate the blinds,repeater,remote to z2m.
Could you please share the exact steps you did, so I can replicate them?

Furthermore I want to integrate them to my openhab server aswell.
Do you mind sharing your .items .things contents for the blinds,repeater,remote ?

Hi!

I am currently trying to integrate the blinds,repeater,remote to z2m.
Could you please share the exact steps you did, so I can replicate them?

Furthermore I want to integrate them to my openhab server aswell.
Do you mind sharing your .items .things contents for the blinds,repeater,remote ?

Hi!
Thanks for reply! I have already solved my issue - as it turned out, the problem was not in z2m, but in my particular blinds, they were broken. I had to replace them, since they were draining battery like crazy (2-3 days and recharge was needed). With the new unit I have no issues - the battry is ok and the blinds remember maximal opening. I did not tried to pair remote with the blinds, since I have already made automation in node-RED which also contains adjusting length to the sun position, but I guess it would also work as in blinds of other members.

Hi!

@dietah
I am currently trying to integrate the blinds,repeater,remote to z2m.
Could you please share the exact steps you did, so I can replicate them?

Hi @gelsas ,

To be honest it was a bit trial and error to get them paired.
If I remember, I think I first paired the repeater to z2m.
Next I can recall sitting on the floor with my blinds so I could bring the repeater as close to the housing as possible as suggested in the pairing instructions. I think it only works when paired to the repeater and not directly to your zigbee endpoint.
The remote is the easiest to do so I kept it as the last.

Believe it or not but I did the whole process twice as I resetted my Pi at some point and one of my file mounts that backed up the z2m database was not doing its job properly. I noticed in that second time that starting from scratch was better than trying to manually fix the database.db file of z2m.

After pairing new devices I manually update the configuration.yaml with a friendly_name. And in our case you have to add invert_cover: true for the blinds itself. (see https://github.com/Koenkk/zigbee-herdsman-converters/issues/1447)

Furthermore I want to integrate them to my openhab server as well.
Do you mind sharing your .items .things contents for the blinds,repeater,remote ?

Sure thing,

mqtt.things:

Bridge mqtt:broker:mosquitto "Mosquitto" [ host="X.X.X.X", port="1883", secure=false ]
{
...
    Thing topic bedroomWindowBlinds "Window blinds" @ "Bedroom" {
    Channels:
        Type number         : battery       "battery"       [ stateTopic="zigbee2mqtt/tradfri_fyrtur_bedroom/battery", unit="%" ]
        Type number         : linkquality   "linkquality"   [ stateTopic="zigbee2mqtt/tradfri_fyrtur_bedroom/linkquality" ]
        Type number         : position      "position"      [ stateTopic="zigbee2mqtt/tradfri_fyrtur_bedroom/position", commandTopic="zigbee2mqtt/tradfri_fyrtur_bedroom/set/position" ]
        Type string         : state         "state"         [ commandTopic="zigbee2mqtt/tradfri_fyrtur_bedroom/set/state" ]
    }

    Thing topic bedroomWindowBlindsRemote "Window blinds remote" @ "Bedroom" {
    Channels:
        Type number         : battery       "battery"       [ stateTopic="zigbee2mqtt/tradfri_openclose_remote_bedroom/battery", unit="%" ]
        Type number         : linkquality   "linkquality"   [ stateTopic="zigbee2mqtt/tradfri_openclose_remote_bedroom/linkquality" ]
        Type string         : action        "action"        [ stateTopic="zigbee2mqtt/tradfri_openclose_remote_bedroom/click" ]
    }

    Thing topic utilitiesRepeater "Tradfri repeater" @ "Utilities Room" {
    Channels:
        Type number         : linkquality   "linkquality"   [ stateTopic="zigbee2mqtt/tradfri_signal_repeater_utilities/linkquality" ]
    }
...
}
  • The repeater is not essential for functionality in OpenHAB here, I just like to see/get all the values

bedroom.items: (indentation in vscode should look ok)

// Tradfri Window Blinds
Number:Dimensionless    BEDROOMWINDOWBLINDS_LINKQUALITY             "Link Quality [%d]"     <network>       (gTradfri) { channel="mqtt:topic:mosquitto:bedroomWindowBlinds:linkquality" }
Number:Dimensionless    BEDROOMWINDOWBLINDS_BATTERY                 "Battery"               <batterylevel>  (gTradfri) { channel="mqtt:topic:mosquitto:bedroomWindowBlinds:battery" }
Number:Dimensionless    BEDROOMWINDOWBLINDS_POSTITION               "Position [%d]"         <blinds>        (gTradfri) { channel="mqtt:topic:mosquitto:bedroomWindowBlinds:position" }
Number:Dimensionless    BEDROOMWINDOWBLINDS_SWITCH                  "Switch [%d]"           <blinds>
String                  BEDROOMWINDOWBLINDS_STATE                   "State"                 <blinds>        (gTradfri) { channel="mqtt:topic:mosquitto:bedroomWindowBlinds:state" }
Rollershutter           BEDROOMWINDOWBLINDS_SHUTTER                 "Blinds"                <blinds>                   { ga="Blinds" }

// Tradfri Window Blinds Remote
Number:Dimensionless    BEDROOMWINDOWBLINDSREMOTE_LINKQUALITY       "Link Quality [%d]"     <network>       (gTradfri) { channel="mqtt:topic:mosquitto:bedroomWindowBlindsRemote:linkquality" }
Number:Dimensionless    BEDROOMWINDOWBLINDSREMOTE_BATTERY           "Battery"               <batterylevel>  (gTradfri) { channel="mqtt:topic:mosquitto:bedroomWindowBlindsRemote:battery" }
String                  BEDROOMWINDOWBLINDSREMOTE_ACTION            "Action"                <batterylevel>  (gTradfri) { channel="mqtt:topic:mosquitto:bedroomWindowBlindsRemote:action" }
  • BEDROOMWINDOWBLINDS_SHUTTER here with { ga="Blinds" } is used to connect the Google Assistant command, in the .rules I use a received update and execute my own rule to then sendCommand to the BEDROOMWINDOWBLINDS_SWITCH which is then a reusable mapping to BEDROOMWINDOWBLINDS_POSTITION.sendCommand() 😅

In my .sitemap you can also find:

    Frame label="Bedroom" {
        Text        item=BEDROOMWINDOWBLINDS_POSTITION          icon="rollershutter"    label="Shutter Position"
        Switch      item=BEDROOMWINDOWBLINDS_SWITCH             icon="rollershutter"    label="Shutter Control []"     mappings=[0="Open", 1="Halfway", 2="Closed", 3="↑", 4="↓", 5="Stop"]
    }

    Frame label="Battery levels" {
        Text        item=BEDROOMWINDOWBLINDSREMOTE_BATTERY          icon="batterylevel"     label="Tradfri Remote"
        Text        item=BEDROOMWINDOWBLINDS_BATTERY                icon="batterylevel"     label="Tradfri Fyrtur"
    }

I think my most important rule for the blinds is:

rule "Fyrtur - Sitemap buttons"
when
    Item BEDROOMWINDOWBLINDS_SWITCH received update
then
    switch ((newState as Number).intValue) {
        case 0: {
            logInfo("fyrtur", "Virtual switched pressed, opening fyrtur")
            BEDROOMWINDOWBLINDS_POSTITION.sendCommand(FYRTUR_OPEN)
        }

        case 1: {
            logInfo("fyrtur", "Virtual switched pressed, opening fyrtur halfway")
            BEDROOMWINDOWBLINDS_POSTITION.sendCommand(FYRTUR_HALFWAY)
        }

        case 2: {
            logInfo("fyrtur", "Virtual switched pressed, closing fyrtur")
            BEDROOMWINDOWBLINDS_POSTITION.sendCommand(FYRTUR_CLOSED)
        }

        case 3: {
            logInfo("fyrtur", "Virtual switched pressed, moving fyrtur up")
            BEDROOMWINDOWBLINDS_STATE.sendCommand("OPEN")
        }

        case 4: {
            logInfo("fyrtur", "Virtual switched pressed, moving fyrtur down")
            BEDROOMWINDOWBLINDS_STATE.sendCommand("CLOSE")
        }

        case 5: {
            logInfo("fyrtur", "Virtual switched pressed, stopping fyrtur")
            BEDROOMWINDOWBLINDS_STATE.sendCommand("STOP")
        }
    }
end
  • FYRTUR_OPEN, FYRTUR_HALFWAY and FYRTUR_CLOSED are global variables that I re-use. I use these to tweak the positions a bit, open for me is 2 and halfway is 45, it has to do with the position the blind is mounted on the wall and the height of my window. Closed is set to 100 as the end position can be programmed on the blinds themselves.
  • I only have one of those blinds, so if you have more it could use some improvements. You can also use groups to send commands to if I remember correctluy.

Hope this helps! Let me know if you need more information, it has been a while since I did any updates on these (lockdown # 1)

Was this page helpful?
0 / 5 - 0 ratings

Related issues

jeroenterheerdt picture jeroenterheerdt  ·  3Comments

andreasbrett picture andreasbrett  ·  3Comments

mpuff picture mpuff  ·  3Comments

Koenkk picture Koenkk  ·  3Comments

Courty40 picture Courty40  ·  4Comments