-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ikea Tradfri repeater no quality link value reported #1417
Comments
I am seeing the same behavior. Coordinator firmware: 20190425 and zigbee2mqtt: 1.4.0 I have three repeaters that show as joined devices but never report linkquality values. |
The reason for this is that the TRADFRI repeater doesn't send any messages. Perhaps we could configure this so that it does, please try with the following configuration (guidance: http://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html): devices.js {
zigbeeModel: ['TRADFRI signal repeater'],
model: 'E1746',
description: 'TRADFRI signal repeater',
supports: 'linkquality',
vendor: 'IKEA',
fromZigbee: [fz.ignore_basic_change, fz.ignore_diagnostic_change],
toZigbee: [],
configure: (ieeeAddr, shepherd, coordinator, callback) => {
const device = shepherd.find(ieeeAddr, 1);
const actions = [
(cb) => device.report('genBasic', 'modelId', 0, 3, 0, cb),
];
execute(device, actions, callback);
},
}, fromZigbee.js E1746_linkquality: {
cid: 'genBasic',
type: ['attReport', 'readRsp'],
convert: (model, msg, publish, options) => {
return {linkquality: msg.linkquality};
},
}, |
I may have not done this correctly. I am getting this warning:
|
I forgot something, please try with: devices.js {
zigbeeModel: ['TRADFRI signal repeater'],
model: 'E1746',
description: 'TRADFRI signal repeater',
supports: 'linkquality',
vendor: 'IKEA',
fromZigbee: [fz.ignore_basic_change, fz.ignore_diagnostic_change, fz.E1746_linkquality],
toZigbee: [],
configure: (ieeeAddr, shepherd, coordinator, callback) => {
const device = shepherd.find(ieeeAddr, 1);
const actions = [
(cb) => device.report('genBasic', 'modelId', 0, 3, 0, cb),
];
execute(device, actions, callback);
},
}, fromZigbee.js E1746_linkquality: {
cid: 'genBasic',
type: ['attReport', 'readRsp'],
convert: (model, msg, publish, options) => {
return {linkquality: msg.linkquality};
},
}, |
I tried the modification as well - my three IKEA repeaters are reporting their linkquality now. |
@3DIRK the code above was for testing purposes, I would recommend changing to (cb) => device.report('genBasic', 'modelId', 3600, 14400, 0, cb), which would result in linkquality reported somewhere between every 1 till 4 hours. |
Okay, I have made the changes and am now receiving linkquality reports from each repeater! Thank you! Do you need anything from my end? |
Nope, will be available in the dev branch soon, thanks! |
Hi @Koenkk, |
@joseal it's already in for a long time (+ 1 year), if it doesn't work you can try to reconfigure: https://www.zigbee2mqtt.io/information/mqtt_topics_and_message_structure.html#zigbee2mqttbridgeconfigure |
Hi @Koenkk, thanks for the quick reply! |
@joseal I have the same problem. What do you mean with "rebuild the container"? |
@soenkegissel, in my case I had to rebuild the docker container (you can do it by simple removed the addon and added it again). Also, validate if your repeater is running the latest firmware (check for OTA updates) and do a reconfirgure after detected (mine became more stable after the reconfigure... don't ask me why :) ). What are you using as coordinator? |
USB zigbee dongle CC2538+CC2592 |
I never tested with that device, but I've 3 CC2531 and one with the RF Amp running without any issues. Are you using Raspberry Pi 4? |
Yes. With 2 meter extension. My very close wall plug is reporting linkquality to coordinator without problems. |
Can you bring one device plus the repeater close to the coordinator, just for testing? |
Bug Report
What happened
No link quality reported on devices connected to this repeater
What did you expect to happen
How to reproduce it (minimal and precise)
Debug Info
zigbee2mqtt version: 1.3.0
CC253X firmware version: March 29, 2019
The text was updated successfully, but these errors were encountered: