别着急，肯定是能搞定的。
你这样，找到灯的IP地址，然后直接运行命令 “telnet ip 55443"，看看什么反应
telnet 192.168.21.162 55443
Trying 192.168.21.162…
telnet: connect to address 192.168.21.162: Connection refused
telnet: Unable to connect to remote host
telnet 192.168.21.153 55443
Trying 192.168.21.153…
telnet: connect to address 192.168.21.153: Operation timed out
我开关了一次极客模式后，现在home app里可以读取灯泡的信息了，但是操作没有实际反映。
微信告诉我，我帮你看看。
weixin:lvxinyan1992
Thank you so much for creating this! Working perfectly first time around
Hi weiwei, Thank you for suport homebridge, I using this plugin very useful.
but, I have two problems.
-
first connecting time is long (turn on, turn off about 10 times. but, once connected, working immediately.)
I guess if there is no activity for some time, yeelight must reconnect to homebridge.
any other homebridge connected device is working always immediately
ex) connected smartthings zigbee device (xiaomi sensors, outlet), wi-fi connected logitech harmony.
connect : devices(zigbee, wifi) -> smartthings -> homebridge -> apple homekit <<< this connection is working immediately -
if set bulb color with homekit (can brighter than yeelight app’s max brightness), bulb irregularly blinking.
do you have solution this problems?
problem 2 is not important. but, 1 is important.
I use raspberryfi 3, 10 yeelight color bulb, 2 yeelight light strip. there connected on apple airport express.
and yeelight firmware updated lastest. connected singapore server.
I will link my problem on youtube.
sorry for bad english.
Hi llgnos,
Thanks for your feedback!
Could you do me a favor to capture homebridge’s log on your Pi when the 1st issue you mentioned happen again?
Meanwhile I will try to reproduce the issue by myself and do some debugging.
Thanks,
Wilson
Jun 3 11:58:41 raspberrypi homebridge[518]: {“id”:1,“method”:“set_power”,“params”:[“on”,“smooth”,500]}
Jun 3 11:58:41 raspberrypi homebridge[518]: socket error
Jun 3 11:58:41 raspberrypi homebridge[518]: failed to connect!
Jun 3 11:58:41 raspberrypi homebridge[518]: [6/3/2017, 11:58:41 AM] [homebridge-yeelight.yeelight] accesseory unreachable
Jun 3 11:58:41 raspberrypi homebridge[518]: [6/3/2017, 11:58:41 AM] [homebridge-yeelight.yeelight] dev disconnected 0x000000000334e7ce false
Jun 3 11:58:44 raspberrypi homebridge[518]: retry connect (0) …: 0x000000000334e7ce
Jun 3 11:58:45 raspberrypi homebridge[518]: connect ok!
Jun 3 11:58:45 raspberrypi homebridge[518]: [6/3/2017, 11:58:45 AM] [homebridge-yeelight.yeelight] accesseory reachable
Jun 3 11:58:45 raspberrypi homebridge[518]: [6/3/2017, 11:58:45 AM] [homebridge-yeelight.yeelight] dev connected 0x000000000334e7ce true
Jun 3 11:58:49 raspberrypi homebridge[518]: {“id”:1,“method”:“set_power”,“params”:[“off”,“smooth”,500]}
Jun 3 11:58:52 raspberrypi homebridge[518]: {“id”:1,“method”:“set_power”,“params”:[“on”,“smooth”,500]}
Jun 3 11:58:53 raspberrypi homebridge[518]: {“id”:1,“method”:“set_power”,“params”:[“off”,“smooth”,500]}
Jun 3 11:58:56 raspberrypi homebridge[518]: {“id”:1,“method”:“set_power”,“params”:[“on”,“smooth”,500]}
Jun 3 11:58:56 raspberrypi homebridge[518]: socket error
Jun 3 11:58:56 raspberrypi homebridge[518]: failed to connect!
Jun 3 11:58:56 raspberrypi homebridge[518]: [6/3/2017, 11:58:56 AM] [homebridge-yeelight.yeelight] accesseory unreachable
Jun 3 11:58:56 raspberrypi homebridge[518]: [6/3/2017, 11:58:56 AM] [homebridge-yeelight.yeelight] dev disconnected 0x00000000035ac169 false
Jun 3 11:58:59 raspberrypi homebridge[518]: retry connect (0) …: 0x00000000035ac169
Jun 3 11:58:59 raspberrypi homebridge[518]: connect ok!
Jun 3 11:58:59 raspberrypi homebridge[518]: [6/3/2017, 11:58:59 AM] [homebridge-yeelight.yeelight] accesseory reachable
Jun 3 11:58:59 raspberrypi homebridge[518]: [6/3/2017, 11:58:59 AM] [homebridge-yeelight.yeelight] dev connected 0x00000000035ac169 true
Jun 3 11:59:00 raspberrypi homebridge[518]: {“id”:1,“method”:“set_power”,“params”:[“off”,“smooth”,500]}
Jun 3 11:59:02 raspberrypi homebridge[518]: {“id”:1,“method”:“set_power”,“params”:[“on”,“smooth”,500]}
Jun 3 11:59:04 raspberrypi homebridge[518]: {“id”:1,“method”:“set_power”,“params”:[“off”,“smooth”,500]}
Jun 3 11:59:05 raspberrypi homebridge[518]: {“id”:1,“method”:“set_power”,“params”:[“on”,“smooth”,500]}
Jun 3 11:59:05 raspberrypi homebridge[518]: socket error
Jun 3 11:59:05 raspberrypi homebridge[518]: failed to connect!
Jun 3 11:59:05 raspberrypi homebridge[518]: [6/3/2017, 11:59:05 AM] [homebridge-yeelight.yeelight] accesseory unreachable
Jun 3 11:59:05 raspberrypi homebridge[518]: [6/3/2017, 11:59:05 AM] [homebridge-yeelight.yeelight] dev disconnected 0x000000000359f9e7 false
Jun 3 11:59:06 raspberrypi homebridge[518]: 0x000000000334e7ce property change: power value: 1
Jun 3 11:59:06 raspberrypi homebridge[518]: [6/3/2017, 11:59:06 AM] [homebridge-yeelight.yeelight] update accessory prop: powervalue: 1
Jun 3 11:59:06 raspberrypi homebridge[518]: 0x000000000334e7ce property change: power value: 0
Jun 3 11:59:06 raspberrypi homebridge[518]: [6/3/2017, 11:59:06 AM] [homebridge-yeelight.yeelight] update accessory prop: powervalue: 0
Jun 3 11:59:08 raspberrypi homebridge[518]: retry connect (0) …: 0x000000000359f9e7
Jun 3 11:59:08 raspberrypi homebridge[518]: connect ok!
Jun 3 11:59:08 raspberrypi homebridge[518]: [6/3/2017, 11:59:08 AM] [homebridge-yeelight.yeelight] accesseory reachable
Jun 3 11:59:08 raspberrypi homebridge[518]: [6/3/2017, 11:59:08 AM] [homebridge-yeelight.yeelight] dev connected 0x000000000359f9e7 true
Jun 3 11:59:14 raspberrypi homebridge[518]: {“id”:1,“method”:“set_power”,“params”:[“off”,“smooth”,500]}
Jun 3 11:59:16 raspberrypi homebridge[518]: {“id”:1,“method”:“set_power”,“params”:[“on”,“smooth”,500]}
Jun 3 11:59:16 raspberrypi homebridge[518]: 0x000000000359f9e7 property change: power value: 1
Jun 3 11:59:16 raspberrypi homebridge[518]: [6/3/2017, 11:59:16 AM] [homebridge-yeelight.yeelight] update accessory prop: powervalue: 1
Jun 3 11:59:17 raspberrypi homebridge[518]: {“id”:1,“method”:“set_power”,“params”:[“off”,“smooth”,500]}
Jun 3 11:59:17 raspberrypi homebridge[518]: 0x000000000359f9e7 property change: power value: 0
Jun 3 11:59:17 raspberrypi homebridge[518]: [6/3/2017, 11:59:17 AM] [homebridge-yeelight.yeelight] update accessory prop: powervalue: 0
Jun 3 11:59:18 raspberrypi homebridge[518]: {“id”:1,“method”:“set_power”,“params”:[“on”,“smooth”,500]}
Jun 3 11:59:19 raspberrypi homebridge[518]: socket error
Jun 3 11:59:19 raspberrypi homebridge[518]: failed to connect!
Jun 3 11:59:19 raspberrypi homebridge[518]: [6/3/2017, 11:59:19 AM] [homebridge-yeelight.yeelight] accesseory unreachable
Jun 3 11:59:19 raspberrypi homebridge[518]: [6/3/2017, 11:59:19 AM] [homebridge-yeelight.yeelight] dev disconnected 0x00000000035ad8fb false
Jun 3 11:59:20 raspberrypi homebridge[518]: connection brokenfalse
Jun 3 11:59:20 raspberrypi homebridge[518]: null
Jun 3 11:59:21 raspberrypi homebridge[518]: socket error
Jun 3 11:59:21 raspberrypi homebridge[518]: failed to connect!
Jun 3 11:59:21 raspberrypi homebridge[518]: [6/3/2017, 11:59:21 AM] [homebridge-yeelight.yeelight] accesseory unreachable
Jun 3 11:59:21 raspberrypi homebridge[518]: [6/3/2017, 11:59:21 AM] [homebridge-yeelight.yeelight] dev disconnected 0x00000000035ac169 false
Jun 3 11:59:22 raspberrypi homebridge[518]: retry connect (0) …: 0x00000000035ad8fb
Jun 3 11:59:22 raspberrypi homebridge[518]: connect ok!
Jun 3 11:59:22 raspberrypi homebridge[518]: [6/3/2017, 11:59:22 AM] [homebridge-yeelight.yeelight] accesseory reachable
Jun 3 11:59:22 raspberrypi homebridge[518]: [6/3/2017, 11:59:22 AM] [homebridge-yeelight.yeelight] dev connected 0x00000000035ad8fb true
Jun 3 11:59:24 raspberrypi homebridge[518]: retry connect (0) …: 0x00000000035ac169
Jun 3 11:59:25 raspberrypi homebridge[518]: connect ok!
Jun 3 11:59:25 raspberrypi homebridge[518]: [6/3/2017, 11:59:25 AM] [homebridge-yeelight.yeelight] accesseory reachable
Jun 3 11:59:25 raspberrypi homebridge[518]: [6/3/2017, 11:59:25 AM] [homebridge-yeelight.yeelight] dev connected 0x00000000035ac169 true
Jun 3 11:59:27 raspberrypi homebridge[518]: {“id”:1,“method”:“set_power”,“params”:[“on”,“smooth”,500]}
Jun 3 11:59:27 raspberrypi homebridge[518]: 0x00000000035ad8fb property change: power value: 1
Jun 3 11:59:27 raspberrypi homebridge[518]: [6/3/2017, 11:59:27 AM] [homebridge-yeelight.yeelight] update accessory prop: powervalue: 1
Jun 3 11:59:28 raspberrypi homebridge[518]: {“id”:1,“method”:“set_power”,“params”:[“off”,“smooth”,500]}
Jun 3 11:59:28 raspberrypi homebridge[518]: 0x00000000035ad8fb property change: power value: 0
Jun 3 11:59:28 raspberrypi homebridge[518]: [6/3/2017, 11:59:28 AM] [homebridge-yeelight.yeelight] update accessory prop: powervalue: 0
Jun 3 11:59:30 raspberrypi homebridge[518]: {“id”:1,“method”:“set_power”,“params”:[“on”,“smooth”,500]}
Jun 3 11:59:30 raspberrypi homebridge[518]: 0x00000000035ad8fb property change: power value: 1
Jun 3 11:59:30 raspberrypi homebridge[518]: [6/3/2017, 11:59:30 AM] [homebridge-yeelight.yeelight] update accessory prop: powervalue: 1
Jun 3 11:59:32 raspberrypi homebridge[518]: {“id”:1,“method”:“set_power”,“params”:[“off”,“smooth”,500]}
Jun 3 11:59:32 raspberrypi homebridge[518]: 0x00000000035ad8fb property change: power value: 0
Jun 3 11:59:32 raspberrypi homebridge[518]: [6/3/2017, 11:59:32 AM] [homebridge-yeelight.yeelight] update accessory prop: powervalue: 0
Jun 3 11:59:35 raspberrypi homebridge[518]: {“id”:1,“method”:“set_power”,“params”:[“on”,“smooth”,500]}
Jun 3 11:59:35 raspberrypi homebridge[518]: socket error
Jun 3 11:59:35 raspberrypi homebridge[518]: failed to connect!
Jun 3 11:59:35 raspberrypi homebridge[518]: [6/3/2017, 11:59:35 AM] [homebridge-yeelight.yeelight] accesseory unreachable
Jun 3 11:59:35 raspberrypi homebridge[518]: [6/3/2017, 11:59:35 AM] [homebridge-yeelight.yeelight] dev disconnected 0x00000000035b3ad9 false
Jun 3 11:59:38 raspberrypi homebridge[518]: retry connect (0) …: 0x00000000035b3ad9
Jun 3 11:59:38 raspberrypi homebridge[518]: connect ok!
Jun 3 11:59:38 raspberrypi homebridge[518]: [6/3/2017, 11:59:38 AM] [homebridge-yeelight.yeelight] accesseory reachable
Jun 3 11:59:38 raspberrypi homebridge[518]: [6/3/2017, 11:59:38 AM] [homebridge-yeelight.yeelight] dev connected 0x00000000035b3ad9 true
This is some logs. you can find socket error and retry connect.
reconnected then working fine. but 5minute after bulb occur socket error, need reconnect.
Thanks for your information, I will take a look ASAP.
I made a update on the script, could you help do a verification?
Download new script “yee.js” from https://s3.amazonaws.com/yeelight-images/yee.js and replace the one on your Pi /usr/lib/node_modules/homebridge-yeelight/lib/yee.js. Remember to restart the homebridge service after the repalcement.
Just let me know the result.
Thank you for update.
but I found solution. problem is Apple Airport Express.
I think yeelight and Apple Airport Express has unstable connection.
when I first connect to yeelight to Airport Express, I can’t connect to airport express.
but after firmware updated, I can connect to airport.
I guess Airport express and yeelight connection has something wrong.??
anyway, I will update new script. Thank you
sorry for bad english
你好，weiwei，我是一个小白，但是对于这方面很感兴趣，没有树莓，我想用我的mac搭建服务器，怎奈没有相关文章，我希望得到帮助，详细的帮助，谢谢
如果你能访问的了我的Blog。。。你可以看到如何在Mac上配置的教程，但服务器不在国内，比较慢:joy:
http://45.32.183.113:8001/?p=208
或者你的英语还可以的话，可以直接去homebridge的github wiki上看安装指南
我能访问，请问极客模式怎么打开，还有xcode是必须安装的吗
https://baijiahao.baidu.com/po/feed/share?wfr=spider&for=pc&context={"sourceFrom"%3A"bjh"%2C"nid"%3A"news_3436632283359127803"} 这遍文章中所说的和您说的有什么区别吗？不好意思不是很懂里面的专业术语
Xcode是必须要安装的，这个是homebridge官方教程里写的。你发的这篇文章用的插件不一样。简单的说，homebridge是个服务器软件，把我们这些不是homekit的设备伪装成支持homekit的设备。每种设备还需要相应的插件才可以使用，像yeelight和小米的aqara就有各自的插件，我是采用这些插件实现的。你发的文章采用的是另一个思路，将这些设备接入ha系统，也就是个第三方的智能家庭管理设备平台，然后用ha的插件，把这个平台接进homebridge。我没试过他这种，但是但从yeelight来看的话，我建议直接使用yeelight的插件
既然你可以访问我的Blog，那你看https://github.com/nfarina/homebridge/wiki/Install-Homebridge-on-macOS 这个比较直观，这是homebridge的文档里如何在Mac上安装的说明。
极客模式就在yeelight app的点开灯–设置–极客模式
有微信可以加一下吗，苹果yeelight是不是没有极客模式