FNB56-SKT1EHG1.2 #177
Comments
|
What did you add to |
|
Trying to not reinvent the wheel I copied what seemed a similar device and renamed it:
{
zigbeeModel: ['FNB56-SKT1EHG1.2'],
model: 'Z809A',
vendor: 'Netvox',
description: 'Power socket',
supports: 'on/off',
fromZigbee: [fz.ignore_onoff_change, fz.generic_state],
toZigbee: [tz.on_off],
// configure: (ieeeAddr, shepherd, coordinator, callback) => {
// const device = shepherd.find(ieeeAddr, 3);
// const cfg = {direction: 0, attrId: 0, dataType: 16, minRepIntval: 0, maxRepIntval: 1000, repChange: 0};
// const actions = [
// (cb) => device.bind('genOnOff', coordinator, cb),
// (cb) => device.foundation('genOnOff', 'configReport', [cfg], foundationCfg, cb),
// ];
//
// execute(device, actions, callback);
// },
},
From: Koen Kanters <notifications@github.com>
Sent: 29 December 2018 23:37
To: Koenkk/zigbee-shepherd-converters <zigbee-shepherd-converters@noreply.github.com>
Cc: arcsyst <git-hub@TheITboat.co.uk>; Author <author@noreply.github.com>
Subject: Re: [Koenkk/zigbee-shepherd-converters] FNB56-SKT1EHG1.2 (#177)
What did you add to devices.js?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#177 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AFJnVIq629Dd40EHWies4MNXsY2ARANtks5u9_yggaJpZM4ZkoNK>.
|
|
That looks good, |
|
I can’t explain it, it’s like it’s not referencing the correct bit of code.
I can send you anything, not sure what you want so have included the three most recent logs.
zigbee2mqtt:debug 2018-12-30 20:16:13 Received MQTT message on 'zigbee2mqtt/0x00158d0002a85038/set' with data '"ON"'
zigbee2mqtt:error 2018-12-30 20:16:13 No converter available for '0' (O)
zigbee2mqtt:error 2018-12-30 20:16:13 No converter available for '1' (N)
zigbee2mqtt:debug 2018-12-30 20:16:27 Received MQTT message on 'zigbee2mqtt/0x00158d0002a85038/set' with data 'ON'
zigbee2mqtt:error 2018-12-30 20:16:27 No converter available for 'state' (ON)
zigbee2mqtt:debug 2018-12-30 20:17:22 Received MQTT message on 'zigbee2mqtt/0x00158d0002a85038/set' with data 'on'
zigbee2mqtt:error 2018-12-30 20:17:22 No converter available for 'state' (on)
From: Koen Kanters <notifications@github.com>
Sent: 30 December 2018 19:18
To: Koenkk/zigbee-shepherd-converters <zigbee-shepherd-converters@noreply.github.com>
Cc: arcsyst <git-hub@TheITboat.co.uk>; Author <author@noreply.github.com>
Subject: Re: [Koenkk/zigbee-shepherd-converters] FNB56-SKT1EHG1.2 (#177)
That looks good, tz.on_off should catch the {"state":"on"} message. Could you provide the complete log? Could you also try just sending "ON" instead of {"state":"on"}.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#177 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AFJnVAOCnFJWKEmP8C9hJ_GiP131_02oks5u-RFdgaJpZM4ZkoNK>.
|
|
On which zigbee2mqtt version are you? |
|
***@***.*** start /opt/zigbee2mqtt
node index.js
Zigbee2mqtt requires node version >=8.11 10, you are running v8.14.0!
From: Koen Kanters <notifications@github.com>
Sent: 30 December 2018 21:49
To: Koenkk/zigbee-shepherd-converters <zigbee-shepherd-converters@noreply.github.com>
Cc: arcsyst <git-hub@TheITboat.co.uk>; Author <author@noreply.github.com>
Subject: Re: [Koenkk/zigbee-shepherd-converters] FNB56-SKT1EHG1.2 (#177)
On which zigbee2mqtt version are you?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#177 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AFJnVHpTkYQegJeo1hFMWoA2xlIZBQSpks5u-TTNgaJpZM4ZkoNK>.
|
|
Can you update to zigbee2mqtt 1.0.1 and try again? |
|
Thank you that seems to have fixed it. Simply sending on or off is sufficient. |
|
Hi Koenkk, zigbee2mqtt:debug 2019-1-3 20:36:33 Received zigbee message of type 'devInterview' with data '"0x00158d000202bb30"' Seems to have paired ok so then activate it: zigbee2mqtt:debug 2019-1-3 20:38:28 Received zigbee message of type 'statusChange' with data '{"cid":"ssIasZone","zoneStatus":32}' of device 'undefined' (0x00124b0018ed35a7) TypeError: Cannot read property 'cid' of undefined npm ERR! A complete log of this run can be found in: Ii seems to be picking up a different device address somehow. |
|
Did you do a |
|
I deleted the whole zigbee2mqtt folder and started again |
|
Did you make some manual changes afterwards? |
|
TBH I was struggling getting anything to pair and flailed around a bit, I now have a smart socket acting as a router could that affect anything? Happy to start over, what's the best way to proceed? Presumably I keep my devices.js? |
|
Tha shouldnt be a problem, can you start over? (without manual changes) |
|
Yes no problem, how would you recommend, just blow the whole thing away and pull from git then npm install, copy back my devices. js? |
|
The problem probably is your devices.js, how does the section look that you added? |
|
Support for this device has been added in #198 |
|
Appears to be the same hardware but different model/brand name.... As more of these start appearing it might be easy to use the same handlers once they are finalised. |
|
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. |
* Don't throw promise.reject() when permit joins fails. But try again. * Set network paramters according to configuration.yaml * Speed up command queues * Retry reset watchdog if it fails once * Force RaspBee and ConBee to use 16bit NWK addr in data indications * Fix wrong handling of 64bit src addresses in received data responses * Remove unnecessary debug output * Use given zclFrame.toBuffer() function instead of own implementation * Don't throw error when unknown parameter is received * Added writeparameter request to permit join request * Removed unnecessary console.log * Start on conbee * Updates. * conbee -> deconz. Koenkk/zigbee-herdsman#72 * Initial suppport for reading parameters - Add basic frame parser - Handle slip protocol and crc calculation - Add queue for read and write parameters * Add dummy function DeconzAdapter.supportsLED() * Start working on write parameters * supportsLED() returns false * Implemented getCoordinator() * Added deCONZ adapter dummy functions * Implemented getCoordinatorVersion() * Implemented getNetworkParameters() * Added constants for APS layer * Startet APS layer Added readReceivedStateRequest, deviceStateRequest, deviceStateResponse, readReceivedDataRequest * Added APS layer parser functions parseDeviceStateResponse, parseReadReceivedDataResponse, parseReceivedDataNotification, * Added parser for APS responses * Refactored some deCONZ adapter functions * Added sendZclFrameNetworkAddress, sendZclFrameNetworkAddressWithResponse and sendZclFrameGroup * Added constants for deCONZ adapter * Added deCONZ driver functions for sending APS commands * Added discoverRoute, supportsDiscoverRoute dummy functions * Implemented NodeDescriptor * Added constants * Reworked debug messages and fixed send unnecessary device state requests * Some smal fixes * Implemented permit join * Fixed check DeviceStatus variables * implemented Active Endpoint request * Implemented simple descriptor * Removed reading request_id if data confirm fail * Fixed reading payload of data indication * Fix nodedescriptor devicetype * Added waitFor dummy function * Implemented lqi() * Implemented routingTable() * implemented bind() * implmented unbind() * Implemented removeDevice() * Changes at driver.ts * Fix for resolve aps request error * ieeeAddr to String now add '0x' prefix * Get correct APS data payload * Fixes for some adapter functions * Delete old code * Added constant * Added support of timeout for aps requests * Refactored deCONZ adapter functions * Added constants * Refactored driver functions and debug logs * Refactored frameparser debug logs * Updated deCONZ adapter to newest adapter version * Added device state intervall wand tweaked watchdog * Removed unused code * Removed unused code * Added received msg event, removed discoverRoute * Added catch for devicestaterequest * Handle default response when sending zcl message * Refactored debug print * Added /* istanbul ignore file */ * Fixed/ implemented zclFrame.payload to Array (for dim and color commands) * Implemented waitFor() and some changes for OTA update * Update deconzAdapter.ts * Fixed sending manufacturere specific commands * Added some attributes to zclpayloadToArray conversion needed for e.g. configure reporting TODO: this has to be reworked completely * Fixed zclPayload to array function (used by configureReporting) handle arrays of objects correctly Co-authored-by: Koen Kanters <koenkanters94@gmail.com>
Trying to get this 'Smart Socket' to work by myself but failing. I can receive the device status if I press the button on the socket but am failing due to mis-configuration or stupidity to send any commands to it. This is what I'm getting:
zigbee2mqtt:debug 2018-12-29 16:08:40 Received MQTT message on 'zigbee2mqtt/0x00158d0002a85038/set' with data '{"state":"on"}'
zigbee2mqtt:error 2018-12-29 16:08:40 No converter available for 'state' (on)
Pressing the manual on/off on the device generates:
zigbee2mqtt:debug 2018-12-29 16:13:42 Received zigbee message of type 'attReport' with data '{"cid":"genOnOff","data":{"onOff":0}}' of device 'FNB56-SKT1EHG1.2' (0x00158d0002a85038)
zigbee2mqtt:info 2018-12-29 16:13:42 MQTT publish, topic: 'zigbee2mqtt/0x00158d0002a85038', payload: '{"state":"OFF","linkquality":120}'
zigbee2mqtt:debug 2018-12-29 16:13:42 Received zigbee message of type 'devChange' with data '{"cid":"genOnOff","data":{"onOff":0}}' of device 'FNB56-SKT1EHG1.2' (0x00158d0002a85038)
zigbee2mqtt:debug 2018-12-29 16:13:44 Received zigbee message of type 'attReport' with data '{"cid":"genOnOff","data":{"onOff":1}}' of device 'FNB56-SKT1EHG1.2' (0x00158d0002a85038)
zigbee2mqtt:info 2018-12-29 16:13:44 MQTT publish, topic: 'zigbee2mqtt/0x00158d0002a85038', payload: '{"state":"ON","linkquality":128}'
zigbee2mqtt:debug 2018-12-29 16:13:44 Received zigbee message of type 'devChange' with data '{"cid":"genOnOff","data":{"onOff":1}}' of device 'FNB56-SKT1EHG1.2' (0x00158d0002a85038)
Using current versions of evices.js, fromZigbbe.js and toZigbee.js
The text was updated successfully, but these errors were encountered: