-
Notifications
You must be signed in to change notification settings - Fork 22
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
v15 firmware, no TARIFPERIOD available #318
Comments
I think it's linked to this issue : Koenkk/zigbee-herdsman#1310 (comment) |
That clearly explains the issue yes. |
Thanks a lot to give a look. |
Hello everyone, @fairecasoimeme: I recently opened an issue on the Zigbee2MQTT GitHub regarding the Lixee Zlinky _TIC: Koenkk/zigbee2mqtt#26146. I am also experiencing an issue with the current_price (LTARF) value, which no longer updates. Thanks! Let me know if you need more details or if I can help in any way. |
@KipK Same as you : I'm currently looking at the code base but I've strictly no idea what is expected between zigbee-herdsman and zigbee-herdsman-converters in terms of class/methods contracts. |
same issue for me. |
There is no reason that LTARF value no longer update with the new firmware. |
@KipK , I tried this but I don't know how to test : |
Had the same problem yesterday :) you'll need to remove the lixeePrivate from cluster.js while testing as they have the same name. But the thing I haven't found yet, is how to compile the .ts to .js to have them in the node_modules dir. edit: was probably tired yesterday, it's just written in the zhc zh readme:
|
I saw you've added this new attribute on latest v15 update.
I've tried it with z2m ( just updated it before to new 2.1.0 ), forced the update using localota as still not available yet.
OTA succeed, everything seems ok but I can't get this new tariff_period.
I've already added it to Tic command whitelist using 'TARIFPERIOD' as it seems to be in LixeeCluster.h ( E_CLD_LINKY_TARIFPERIOD = 0x0010, ) , tried also using Tariff ( as it is in the lixee.js converter )
Also when configuring the device, z2m reports an error on this attribute:
z2m: Failed to configure 'Linky', attempt 1 (Error: ZCL command 0x00158d000638e0dc/1 liXeePrivate.configReport([{"attribute":"tariffPeriod","minimumReportInterval":60,"maximumReportInterval":900,"reportableChange":1}], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"manufacturerCode":null,"writeUndiv":false}) failed (Don't know value type for 'undefined') at Object.getDataTypeClass (/opt/zigbee2mqtt/node_modules/.pnpm/zigbee-herdsman@3.2.5/node_modules/zigbee-herdsman/src/zspec/zcl/utils.ts:76:15) at Function.conditionsValid (/opt/zigbee2mqtt/node_modules/.pnpm/zigbee-herdsman@3.2.5/node_modules/zigbee-herdsman/src/zspec/zcl/zclFrame.ts:307:35) at ZclFrame.writePayloadGlobal (/opt/zigbee2mqtt/node_modules/.pnpm/zigbee-herdsman@3.2.5/node_modules/zigbee-herdsman/src/zspec/zcl/zclFrame.ts:95:35) at ZclFrame.toBuffer (/opt/zigbee2mqtt/node_modules/.pnpm/zigbee-herdsman@3.2.5/node_modules/zigbee-herdsman/src/zspec/zcl/zclFrame.ts:77:18) at EmberAdapter.sendZclFrameToEndpoint (/opt/zigbee2mqtt/node_modules/.pnpm/zigbee-herdsman@3.2.5/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1961:31) at Request.func (/opt/zigbee2mqtt/node_modules/.pnpm/zigbee-herdsman@3.2.5/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:298:36) at Request.send (/opt/zigbee2mqtt/node_modules/.pnpm/zigbee-herdsman@3.2.5/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:82:31) at Endpoint.sendRequest (/opt/zigbee2mqtt/node_modules/.pnpm/zigbee-herdsman@3.2.5/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:324:34) at Endpoint.zclCommand (/opt/zigbee2mqtt/node_modules/.pnpm/zigbee-herdsman@3.2.5/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:949:39) at Endpoint.configureReporting (/opt/zigbee2mqtt/node_modules/.pnpm/zigbee-herdsman@3.2.5/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:686:20))
The text was updated successfully, but these errors were encountered: