前言
虽然iobroker的入门难度比其他的开源平台要低一点，但是它毕竟还是来源于国外的并且刚进国内的新玩意。门槛还是有的，如果你感兴趣并愿意花心思去研究，先到的机友们是非常愿意分享自己的经验。
如果你遇到了困难，正确的步骤是：1.先看看自己有没有按照论坛的教程操作了；==》2.如果还不行，看看论坛里面有没有机友踩过同样的坑并提供了解决方案；==》3.如果都没有，那么你得学会自己看日志排除错误。==》4.自己无法解决的，请按照下面的提示，在论坛留言或者在qq群提问。
作为一个资深的抱大腿老油子，我给一点最实际的建议：
千万别在论坛或者qq群，直接一句，我的xx不行，这是什么原因。没有提供任何有价值的线索，在聪明的大神仙也帮不了你。
步骤
一、把实例的日志调成debug级别
二、查看日志里面指定实例的错误
| mihome.0 | 2019-12-26 11:33:47.159 | error | (7649) Error: bind EADDRINUSE 0.0.0.0:9898 |
|---|---|---|---|
| mihome.0 | 2019-12-26 11:33:47.156 | error | (7649) no key defined. Only read is possible |
| mihome.0 | 2019-12-26 11:33:17.152 | error | (7649) Error: bind EADDRINUSE 0.0.0.0:9898 |
| mihome.0 | 2019-12-26 11:33:17.133 | error | (7649) no key defined. Only read is possible |
这个什么毛病
端口占用 停了同一个机器上运行的hass
下载日志
日志大小 0.11 MB
时间
| host.aml | 2019-12-28 13:00:03.521 | info | Restart adapter system.adapter.ham.0 because enabled |
| host.aml | 2019-12-28 13:00:03.520 | info | instance system.adapter.ham.0 terminated with code 0 (NO_ERROR) |
| host.aml | 2019-12-28 13:00:03.520 | error | Caught by controller[1]: at process._tickCallback (internal/process/next_tick.js:63:19) |
| host.aml | 2019-12-28 13:00:03.519 | error | Caught by controller[1]: at endReadableNT (_stream_readable.js:1143:12) |
| host.aml | 2019-12-28 13:00:03.518 | error | Caught by controller[1]: at IncomingMessage.emit (events.js:198:13) |
| host.aml | 2019-12-28 13:00:03.517 | error | Caught by controller[1]: at HAPServer. (/opt/iobroker/node_modules/iobroker.ham/node_modules/hap-nodejs/lib/HAPServer.js:209:39) |
| host.aml | 2019-12-28 13:00:03.517 | error | Caught by controller[1]: at HAPServer._handlePair (/opt/iobroker/node_modules/iobroker.ham/node_modules/hap-nodejs/lib/HAPServer.js:315:10) |
| host.aml | 2019-12-28 13:00:03.516 | error | Caught by controller[1]: at HAPServer._handlePairStepThree (/opt/iobroker/node_modules/iobroker.ham/node_modules/hap-nodejs/lib/HAPServer.js:413:8) |
| host.aml | 2019-12-28 13:00:03.516 | error | Caught by controller[1]: at HAPServer._handlePairStepFour (/opt/iobroker/node_modules/iobroker.ham/node_modules/hap-nodejs/lib/HAPServer.js:439:8) |
| host.aml | 2019-12-28 13:00:03.515 | error | Caught by controller[1]: at HAPServer._handlePairStepFive (/opt/iobroker/node_modules/iobroker.ham/node_modules/hap-nodejs/lib/HAPServer.js:457:36) |
| host.aml | 2019-12-28 13:00:03.515 | error | Caught by controller[1]: at Function.nacl.sign.detached (/opt/iobroker/node_modules/iobroker.ham/node_modules/tweetnacl/nacl-fast.js:2276:24) |
| host.aml | 2019-12-28 13:00:03.514 | error | Caught by controller[1]: at Object.nacl.sign (/opt/iobroker/node_modules/iobroker.ham/node_modules/tweetnacl/nacl-fast.js:2257:11) |
| host.aml | 2019-12-28 13:00:03.512 | error | Caught by controller[1]: Error: bad secret key size |
| ham.0 | 2019-12-28 13:00:02.985 | info | (17850) Terminated (NO_ERROR): Without reason |
| ham.0 | 2019-12-28 13:00:02.983 | info | (17850) terminating |
| ham.0 | 2019-12-28 13:00:02.932 | warn | (17850) Exception: Error: bad secret key size |
| ham.0 | 2019-12-28 13:00:02.917 | info | (17850) cleaned everything up… |
| ham.0 | 2019-12-28 13:00:02.915 | error | (17850) Error: bad secret key size at Object.nacl.sign (/opt/iobroker/node_modules/iobroker.ham/node_modules/tweetnacl/nacl-fast.js:2257:11) at Function.nacl.sign.detached (/opt/iobroker/node_ |
| ham.0 | 2019-12-28 13:00:02.912 | error | (17850) uncaught exception: bad secret key size |
这个什么问题？能找到设备就是不能添加
bad secret key size token有误？
友情提示 你把你的iob后台地址发出来了， 而且没有设置密码
谢谢
没注意到反正也不重要，但是问题还没解决
重装一次试一下
Secret key 有问题 这个萝卜哥上一个回答已经提出来了
Error: ENOENT: no such file or directory, open ‘/opt/iobroker/node_modules/iobroker.admin/lib/…/src/configs.html’
at Object.openSync (fs.js:443:3)
at Object.readFileSync (fs.js:343:35)
at generateConfigPage (/opt/iobroker/node_modules/iobroker.admin/lib/web.js:213:20)
at Layer.handle [as handle_request] (/opt/iobroker/node_modules/express/lib/router/layer.js:95:5)
at next (/opt/iobroker/node_modules/express/lib/router/route.js:137:13)
at Route.dispatch (/opt/iobroker/node_modules/express/lib/router/route.js:112:3)
at Layer.handle [as handle_request] (/opt/iobroker/node_modules/express/lib/router/layer.js:95:5)
at /opt/iobroker/node_modules/express/lib/router/index.js:281:22
at Function.process_params (/opt/iobroker/node_modules/express/lib/router/index.js:335:12)
at next (/opt/iobroker/node_modules/express/lib/router/index.js:275:10
这个怎么解决
兄弟 ，我最好严格按照我上面的说明提供详细的截图，你这样提问，看不出啥来啊。
jsc 升级的教程论坛上找不到啊
大佬我的zigbee2mqttassistant 最近一直在报错 表现为报错时候zigbee2mqttassistant地图里连线就没有了 但是门磁等还有状态获取到 下面附上日志请大佬帮助谢谢 ！
ha:版本 108.5
zigbee2mqtt 1.122
fail: Zigbee2MqttAssistant.Services.MqttConnectionService[0]
Error processing MQTT message on topic ‘zigbee2mqtt/bridge/config/groups’
Newtonsoft.Json.JsonReaderException: Error reading JObject from JsonReader. Current JsonReader item is not an object: Integer. Path ‘’, line 1, position 13.
at Newtonsoft.Json.Linq.JObject.Load(JsonReader reader, JsonLoadSettings settings)
at Newtonsoft.Json.Linq.JObject.Parse(String json, JsonLoadSettings settings)
at Zigbee2MqttAssistant.Services.BridgeStateService.UpdateDevice(String friendlyName, String jsonPayload, Boolean& forceLastSeen) in d:\a\1\s\Zigbee2MqttAssistant\Services\BridgeStateService.cs:line 144
at Zigbee2MqttAssistant.Services.MqttConnectionService.DispatchZigbee2MqttMessage(MqttApplicationMessage msg) in d:\a\1\s\Zigbee2MqttAssistant\Services\MqttConnectionService.cs:line 503
at Zigbee2MqttAssistant.Services.MqttConnectionService.HandleApplicationMessageReceivedAsync(MqttApplicationMessageReceivedEventArgs eventArgs) in d:\a\1\s\Zigbee2MqttAssistant\Services\MqttConnectionService.cs:line 410
以上是日志
mihome.0 2020-07-23 23:30:40.696 error (665) no key defined. Only read is possible
你没有填写正确的key。另外你没有说清楚前因后果，这种有限的信息，解决不了问题。
