Skip to content
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

Failed to call 'DeviceReceive' 'onZigbeeEvent' #3107

Closed
ccorderod opened this issue Mar 11, 2020 · 7 comments
Closed

Failed to call 'DeviceReceive' 'onZigbeeEvent' #3107

ccorderod opened this issue Mar 11, 2020 · 7 comments

Comments

@ccorderod
Copy link

Bug Report

What happened

Using Z2M dev, cc1352-P2 firmware dev 20200306 on pi4.

Log is full of:
error 2020-03-11 19:20:59: Failed to call 'DeviceReceive' 'onZigbeeEvent' (TypeError: Cannot read property 'debounce' of null at DeviceReceive.onZigbeeEvent (/opt/zigbee2mqtt/lib/extension/deviceReceive.js:119:82) at Controller.callExtensionMethod (/opt/zigbee2mqtt/lib/controller.js:340:44) at Controller.onZigbeeEvent (/opt/zigbee2mqtt/lib/controller.js:230:14) at Zigbee.emit (events.js:311:20) at Controller.<anonymous> (/opt/zigbee2mqtt/lib/zigbee.js:57:52) at Controller.emit (events.js:311:20) at Controller.<anonymous> (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/controller/controller.js:466:22) at Generator.next (<anonymous>) at /opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/controller/controller.js:8:71 at new Promise (<anonymous>))

No ZB messages are proccesed by Z2M.

What did you expect to happen

How to reproduce it (minimal and precise)

Rebooting pi or disconnecting/reconnecting the controller does not fix the problem

Debug Info

zigbee2mqtt version: dev - latest commit
CC253X firmware version: 20200306

@Koenkk
Copy link
Owner

Koenkk commented Mar 11, 2020

Could you provide the debug logging of this and your configuration.yaml?

To enable debug logging set in configuration.yaml:

advanced:
  log_level: debug

@ccorderod
Copy link
Author

Sure. May I send both to you by PM through discord?

@Koenkk
Copy link
Owner

Koenkk commented Mar 11, 2020

yes

@ccorderod
Copy link
Author

Done. Log, config, devices & groups

@Koenkk
Copy link
Owner

Koenkk commented Mar 11, 2020

In your configuration.yaml device_options: null is set which is invalid. Either remove it completely from configuration.yaml or change it to device_options: {}.

I've added an additional check so Zigbee2mqtt refuses to start now when this is set:

> zigbee2mqtt@1.11.0-dev start /Users/Koenkk/Git/zigbee2mqtt
> node index.js

zigbee2mqtt:info  2020-03-11 20:16:55: Logging to console and directory: '/Users/Koenkk/Git/zigbee2mqtt/data/log/2020-03-11.20-16-55' filename: log.txt
zigbee2mqtt:error 2020-03-11 20:16:55: Refusing to start, configuration.yaml is not valid, found the following errors:
zigbee2mqtt:error 2020-03-11 20:16:55:   - device_options should be object
zigbee2mqtt:error 2020-03-11 20:16:55: If you don't know how to solve this, read https://www.zigbee2mqtt.io/configuration/configuration.html

Thanks for reporting! Fixed in latest dev branch.

@LukeHandle
Copy link

Weirdly also had the same issue (upgrading from 1.8.0).

The doc URL might need an adjustment to https://www.zigbee2mqtt.io/information/configuration.html ?

Also, the doc there shows the following which still seems to throw the error:

# Optional: Device specific options
device_options:
  # See 'Device specific configuration' below

Deleting the key per your advice works fine though.

Koenkk added a commit to Koenkk/zigbee2mqtt.io that referenced this issue Apr 14, 2020
@Koenkk
Copy link
Owner

Koenkk commented Apr 14, 2020

Updated the docs, thanks!

Koenkk added a commit to Koenkk/zigbee2mqtt.io that referenced this issue Apr 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants