www.homeseer.com    
 

Go Back   HomeSeer Message Board > HomeSeer Products & Services > HomeSeer Software > HS3 / HS3PRO > HS3 Plug-In Development

HS3 Plug-In Development Discussions related to developing plugins for HS3.

Reply
 
Thread Tools Display Modes
  #1  
Old December 1st, 2017, 05:17 PM
mrhappy mrhappy is offline
OverSeer
 
Join Date: Nov 2007
Location: W.Mids, UK
Posts: 7,314
Yeelight Plugin (Beta) - Testers Wanted

Dear All

I know there has been the odd mention around here of the ability to control the Yeelight brand of WiFi bulbs (https://www.yeelight.com/ - available on places like DX/Banggood) in HS. I've written a plugin that is still a bit rough around the edges I am interested in beta testers for, I only have a single Yeelight bulb so it is difficult for me to know how it behaves with multiple devices and more complicated setups.

It is ridiculously simple to set up and only needs to be dropped into the HS directory and enabled as it will find everything else out from the discovery methods on the network, it does however have a couple of known issues which are detailed in the help file (you also MUST enable LAN control in the Yeelight app before you have control over the device else it will appear invisible).

Documentation is here - http://s652164905.websitehome.co.uk/....aspx#Yeelight 3P

Plugin is downloadable from here - http://s652164905.websitehome.co.uk/...t_0_0_0_11.zip

Please note that there are a couple of odd design decisions in the Yeelight API that I'm still not sure why they are in there, hence I might have had to make workarounds to get things working.

If you test it and either way it works or does not work I would still appreciate to know,

Thanks
Attached Images
 

Last edited by mrhappy; April 21st, 2018 at 05:58 AM.
Reply With Quote
  #2  
Old December 4th, 2017, 09:03 AM
jfla jfla is offline
Seer Deluxe
 
Join Date: Apr 2004
Location: ROUEN, France
Posts: 213
Hi, MrHappy
I have two Yeelight LedStrip:

https://www.gearbest.com/smart-lighting/pp_424884.html

Work Basically with Google Home , and Plugin drhsIpPlugIn (On, OFF, Change color)


I have installed your plugin for my yeeliht LedStrip and i have this message :

déc.-04 13:55:41 Plug-In Finished initializing plug-in Yeelight 3P
déc.-04 13:55:41 Yeelight 3P Connection Worker Thread Completed
déc.-04 13:55:41 Yeelight 3P Start Discovery Timer
déc.-04 13:55:41 Yeelight 3P UDP RX Thread Started
déc.-04 13:55:41 Yeelight 3P Yeelight LED Startup
déc.-04 13:55:41 Info Plugin Yeelight 3P has connected. IP:127.0.0.1:64404

No other information, no device created, no plugin in manage plugin

My config:

Current Date/Time: 04/12/2017 14:02:55
HomeSeer Version: HS3 Pro Edition 3.0.0.372
Operating System: Microsoft Windows 10 Famille - Work Station
System Uptime: 0 Days 9 Hours 50 Minutes 29 Seconds
IP Address: 192.168.50.53
Number of Devices: 416
Number of Events: 141
Available Threads: 200

Enabled Plug-Ins
2.0.38.0: BLLAN
1.0.3.0: BLShutdown
4.8.6.0: BULLET
3.0.0.64: mcsXap
3.0.0.14: NetCAM
3.0.1.109: PHLocation
30.0.0.36: RFXCOM
5.0.2.0: SCREPOSITORY
4.0.0.4: THERMOSTAT
3.0.0.44: X10
0.0.0.1: Yeelight 3P
3.0.1.130: Z-Wave

Jean-Francois.
Reply With Quote
  #3  
Old December 4th, 2017, 11:35 AM
jfla jfla is offline
Seer Deluxe
 
Join Date: Apr 2004
Location: ROUEN, France
Posts: 213
Hi, MrHappy

If i start it Manually, i get this log:

Quote:
Connecting to server at 127.0.0.1...
Connected, Waiting to be initialized...
[04/12/2017 16:32:38] - Yeelight LED Startup
[04/12/2017 16:32:38] - StartThread Entered
[04/12/2017 16:32:38] - --> Receive Thread Started
[04/12/2017 16:32:38] - -> Start Discovery Timer - Two Seconds To Start
[04/12/2017 16:32:38] - Connection Worker Thread Completed
[04/12/2017 16:32:38] - ---> Start Of Block
[04/12/2017 16:32:40] - ---> Discovery Timer Elapsed
[04/12/2017 16:32:40] - SendDiscovery Called
[04/12/2017 16:32:40] - Discovery Packet Sent: True
[04/12/2017 16:32:40] - HandleDiscovery Called

Exception non gérée*: System.Net.Sockets.SocketException: Une connexion existante a dû être fermée par l'hôte distant
à System.Net.Sockets.Socket.ReceiveFrom(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, EndPoint& remoteEP)
à System.Net.Sockets.UdpClient.Receive(IPEndPoint& remoteEP)
à HSPI_YEELIGHT3P.plugin.ThreadRX()
à System.Threading.ThreadHelper.ThreadStart_Context(Object state)
à System.Threading.ExecutionContext.RunInternal(ExecutionConte xt executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
à System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
à System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
à System.Threading.ThreadHelper.ThreadStart()
No other log in HS3

Jean-Francois.
Reply With Quote
  #4  
Old December 4th, 2017, 01:50 PM
mrhappy mrhappy is offline
OverSeer
 
Join Date: Nov 2007
Location: W.Mids, UK
Posts: 7,314
First thank you for testing the plugin, second you should not see that error and it should not cause the plugin to crash so I have now fixed that. Could I ask if you can try this version please;

(see first post)

And see what comes up, I hope that at least it does not crash and hopefully starts sending the packets out to the network.

Last edited by mrhappy; April 21st, 2018 at 05:58 AM.
Reply With Quote
  #5  
Old December 4th, 2017, 06:43 PM
jfla jfla is offline
Seer Deluxe
 
Join Date: Apr 2004
Location: ROUEN, France
Posts: 213
Hi, MrHappy

Discovery don't work:

Quote:
Connecting to server at 127.0.0.1...
Connected, Waiting to be initialized...
[04/12/2017 23:38:04] - Yeelight LED Startup
[04/12/2017 23:38:04] - StartThread Entered
[04/12/2017 23:38:04] - --> Receive Thread Started
[04/12/2017 23:38:04] - ---> Start Of Block
[04/12/2017 23:38:04] - -> Start Discovery Timer - Two Seconds To Start
[04/12/2017 23:38:04] - Connection Worker Thread Completed
[04/12/2017 23:38:06] - ---> Discovery Timer Elapsed
[04/12/2017 23:38:06] - SendDiscovery Called
[04/12/2017 23:38:06] - Discovery Packet Sent: True
[04/12/2017 23:38:06] - HandleDiscovery Called: M-SEARCH * HTTP/1.1 HOST: 239.255.255.250:1982 MAN: "ssdp:discover" ST: wifi_bulb
[04/12/2017 23:38:06] - ---> Loopback Packet - False
[04/12/2017 23:38:06] - ---> Thread RX Exception: Une connexion existante a dû être fermée par l'hôte distant
Jean-Francois.
Reply With Quote
  #6  
Old December 5th, 2017, 09:12 AM
jfla jfla is offline
Seer Deluxe
 
Join Date: Apr 2004
Location: ROUEN, France
Posts: 213
Hi,MrHappy

I know the ip adress of my LedStrip.

How work plugin and devices ?

may be i put Ip adress on an .ini ?

Jean-Francois
Reply With Quote
  #7  
Old December 5th, 2017, 01:03 PM
mrhappy mrhappy is offline
OverSeer
 
Join Date: Nov 2007
Location: W.Mids, UK
Posts: 7,314
Quote:
Originally Posted by jfla View Post
Hi,MrHappy

I know the ip adress of my LedStrip.

How work plugin and devices ?

may be i put Ip adress on an .ini ?

Jean-Francois
Unfortunately I did not add this option as when you discover a device it appears differently and provides all of the information to the plugin about the type of device, current settings, IP address, ID details etc. Those are not available by any other means, there does not appear to be an option to get those details from the device any other way. I guess I can look at enabling you to see this (you would need to get details for the ID number, IP address and device type at least) but ideally I would like to fix the auto detection.

In the Zip file I have included a file called Yeelight_Control.exe - this is an app written by someone else to discover devices on your network - if you load this does it find any of your bulbs?
Reply With Quote
  #8  
Old December 5th, 2017, 04:07 PM
jfla jfla is offline
Seer Deluxe
 
Join Date: Apr 2004
Location: ROUEN, France
Posts: 213
Hi, MrHappy

I get this error when i start Yeelight_Control.exe

This ddl are in System32, the path are OK
Attached Images
  
Reply With Quote
  #9  
Old December 5th, 2017, 04:35 PM
jfla jfla is offline
Seer Deluxe
 
Join Date: Apr 2004
Location: ROUEN, France
Posts: 213
Hi, MrHappy


Every hour, my ledstrip send this to HS3 log via drhsIpPlugIn

Quote:
déc.-05 21:21:39

Pass-thru
There are 477 bytes of binary data.
déc.-05 21:21:39

Pass-thru
NOTIFY * HTTP/1.1 Host: 239.255.255.250:1982 Cache-Control: max-age=3600 Location: yeelight://192.168.xx.33:55443 NTS: ssdp:alive Server: POSIX, UPnP/1.0 YGLC/1 id: 0x00000000031aac13 model: stripe fw_ver: 40 support: get_prop set_default set_power toggle set_bright start_cf stop_cf set_scene cron_add cron_get cron_del set_ct_abx set_rgb set_hsv set_adjust set_music set_name power: off bright: 100 color_mode: 1 ct: 1700 rgb: 3680511 hue: 0 sat: 100 name:
déc.-05 21:21:39

Pass-thru
192.168.xx.33:1982
déc.-05 21:21:39

Pass-thru
Yeelight Discover
Jean-francois.
Attached Images
 
Reply With Quote
  #10  
Old December 5th, 2017, 06:13 PM
jfla jfla is offline
Seer Deluxe
 
Join Date: Apr 2004
Location: ROUEN, France
Posts: 213
Hi, MrHappy

I found a correct version of VCruntime140.dll and msvcp140.dll (Visual studio 2015), i put it on the folder than Yeelight_control

I can run Yeelight_Control

Jean-Francois.
Attached Images
 
Reply With Quote
  #11  
Old December 7th, 2017, 07:13 AM
mrhappy mrhappy is offline
OverSeer
 
Join Date: Nov 2007
Location: W.Mids, UK
Posts: 7,314
Quote:
Originally Posted by jfla View Post
Hi, MrHappy

I found a correct version of VCruntime140.dll and msvcp140.dll (Visual studio 2015), i put it on the folder than Yeelight_control

I can run Yeelight_Control

Jean-Francois.
OK I think I can see what might be the issue, do you have multiple network interfaces or something similar? The packet is being sent through 169.254.x but the bulb is on 192.168.x, I imagine that might be throwing the plugin off and it not capturing the return packet for some reason. I will have a think and post back here but I do appreciate you testing.
Reply With Quote
  #12  
Old December 7th, 2017, 07:53 AM
TeleFragger's Avatar
TeleFragger TeleFragger is offline
OverSeer
 
Join Date: Jun 2004
Location: Williamstown, NJ
Posts: 4,794
thought I replied...
so I'm clueless on what is needed for this.
I want to get 2x A19 led color bulbs..

can you give me an example of what I need to buy to use this plugin? very interested so I can replace bulbs and not change them every holiday to colored bulbs...
thx
Jeff
__________________
HW - i5 4570T @2.9ghz runs @11w | 8gb ram | 128gb ssd OS - Win10 x64

HS - HS3 Pro Edition 3.0.0.435

Plugins - BLRF 2.0.94.0 | Concord 4 3.1.13.10 | HSBuddy 3.9.605.5 | HSTouch Server 3.0.0.68 | RFXCOM 30.0.0.36 | X10 3.0.0.36 | Z-Wave 3.0.1.190

Hardware - EdgePort/4 DB9 Serial | RFXCOM 433MHz USB Transceiver | Superbus 2000 for Concord 4 | TI103 X-10 Interface | WGL Designs W800 RF | Z-Net Z-Wave Interface
Reply With Quote
  #13  
Old December 7th, 2017, 08:29 AM
mrhappy mrhappy is offline
OverSeer
 
Join Date: Nov 2007
Location: W.Mids, UK
Posts: 7,314
Quote:
Originally Posted by TeleFragger View Post
thought I replied...
so I'm clueless on what is needed for this.
I want to get 2x A19 led color bulbs..

can you give me an example of what I need to buy to use this plugin? very interested so I can replace bulbs and not change them every holiday to colored bulbs...
thx
Jeff
If you wanted to use the Yeelight bulbs then all you need to buy is two bulbs because they are wifi devices so there is no need to buy hubs etc. They are available on eBay/DealExtreme/BangGood and the like, retail for $20 each on DX.com.
Reply With Quote
  #14  
Old December 7th, 2017, 09:46 AM
langenet's Avatar
langenet langenet is offline
OverSeer
 
Join Date: May 2003
Location: Ottawa, Ontario, Canada
Posts: 2,640
Adam,

Great to know. I was just having a conversation with a buddy about Lifx bulbs yesterday and didn't even know about these. Seems nicely priced...
May need to expand my HS yet again..

So can I assume your plugin is completely event controllable?

Dumb question but have to ask, do these require a cloud service or being TCP totally locally controllable? - sorry short on this morning's coffee.

Robert
__________________
HS3PRO 3.0.0.435 as a Fire Daemon service, Windows 2016 Server Std Intel Core i5 PC HTPC Slim SFF 4GB, 120GB SSD drive, WLG800, RFXCom, TI103,NetCam, UltraNetcam3, BLBackup, CurrentCost 3P Rain8Net, MCsSprinker, HSTouch, Ademco Security plugin/AD2USB, various Oregon Scientific temp/humidity sensors, Z-Net, Zsmoke, Aeron Labs micro switches, Amazon Echo Dot, WS+, WD+ ... on and on.
Reply With Quote
  #15  
Old December 7th, 2017, 02:45 PM
mrhappy mrhappy is offline
OverSeer
 
Join Date: Nov 2007
Location: W.Mids, UK
Posts: 7,314
Quote:
Originally Posted by langenet View Post
Adam,

Great to know. I was just having a conversation with a buddy about Lifx bulbs yesterday and didn't even know about these. Seems nicely priced...
May need to expand my HS yet again..

So can I assume your plugin is completely event controllable?

Dumb question but have to ask, do these require a cloud service or being TCP totally locally controllable? - sorry short on this morning's coffee.

Robert
Providing I can resolve the issue with the auto discovery (or provide the facility to manually add a bulb the plugin) then it should be good to go. The options to control these bulbs is available from the events page if this is what you mean?? The more complex options (pattern flows) are available by event action and further enhancements might also help with this.

In terms of the plugin then it completely is locally connecting to the bulbs and does not rely on a cloud service. I've been looking at the traffic in wireshark which I've not seen any odd connections to dubious services etc, the only issue is I think to originally link your bulb to the network you do have to have the app on your phone to link it. The app does need you to sign up but you can always use a burner email and password for this.
Reply With Quote
  #16  
Old December 7th, 2017, 02:55 PM
langenet's Avatar
langenet langenet is offline
OverSeer
 
Join Date: May 2003
Location: Ottawa, Ontario, Canada
Posts: 2,640
This is great. After seeing this today I bought one to test.

Thanks for answering all my questions.

Robert
Reply With Quote
  #17  
Old December 7th, 2017, 05:30 PM
jfla jfla is offline
Seer Deluxe
 
Join Date: Apr 2004
Location: ROUEN, France
Posts: 213
Hi, MrHappy

I have only one network in my home :192.168.xx.xx connected by wifi and DHCP

My laptop is connected to wifi

network with adress 169.254.xx.xx is a self attrib network adress

Quote:
Originally Posted by mrhappy View Post
OK I think I can see what might be the issue, do you have multiple network interfaces or something similar? The packet is being sent through 169.254.x but the bulb is on 192.168.x, I imagine that might be throwing the plugin off and it not capturing the return packet for some reason. I will have a think and post back here but I do appreciate you testing.
I don't know why the program Yeelight_Control use adress 169.254.xx.xx

Now, I can't find my lesdstrip with Yeelight_control

it's conneted to yeelight android application and i can see in drhsIpPlugIn all change to ledstrip

This is the network trame send by Yeelight_control

Quote:
déc.-07 22:12:21 Pass-thru Yeelight Discover
déc.-07 22:12:21 Pass-thru 192.168.xx.12:61098
déc.-07 22:12:21 Pass-thru M-SEARCH * HTTP/1.1 HOST: 239.255.255.250:1982 MAN: "ssdp:discover" ST: wifi_bulb
déc.-07 22:12:21 Pass-thru There are 83 bytes of binary data.
My change in ledstrip from Android application:

Quote:

déc.-07 22:11:46 Pass-thru Yeelight-1
déc.-07 22:11:46 Pass-thru 192.168.xx.33:55443
déc.-07 22:11:46 Pass-thru {"method":"props","params":{"bright":50}}
déc.-07 22:11:46 Pass-thru There are 42 bytes of binary data.
déc.-07 22:11:45 Pass-thru 192.168.xx.33:55443
déc.-07 22:11:45 Pass-thru {"method":"props","params":{"color_mode":1}}
déc.-07 22:11:45 Pass-thru There are 45 bytes of binary data.
déc.-07 22:11:45 Pass-thru Yeelight-1
déc.-07 22:11:24 Pass-thru There are 52 bytes of binary data.
déc.-07 22:11:24 Pass-thru Yeelight-1
déc.-07 22:11:24 Pass-thru 192.168.xx.33:55443
déc.-07 22:11:24 Pass-thru {"method":"props","params":{"bright":80,"ct":3200}}
déc.-07 22:11:23 Pass-thru Yeelight-1
déc.-07 22:11:23 Pass-thru 192.168.xx.33:55443
déc.-07 22:11:23 Pass-thru {"method":"props","params":{"color_mode":2}}
déc.-07 22:11:23 Pass-thru There are 45 bytes of binary data.
déc.-07 22:10:40 Pass-thru Yeelight-1
déc.-07 22:10:40 Pass-thru 192.168.xx.33:55443
déc.-07 22:10:40 Pass-thru {"method":"props","params":{"bright":50}}
déc.-07 22:10:40 Pass-thru There are 42 bytes of binary data.
déc.-07 22:10:39 Pass-thru Yeelight-1
déc.-07 22:10:39 Pass-thru 192.168.xx.33:55443
déc.-07 22:10:39 Pass-thru {"method":"props","params":{"rgb":1315890}}
déc.-07 22:10:39 Pass-thru There are 44 bytes of binary data.
déc.-07 22:10:07 Pass-thru {"method":"props","params":{"rgb":4066559}}
déc.-07 22:10:07 Pass-thru There are 44 bytes of binary data.
déc.-07 22:10:07 Pass-thru Yeelight-1
déc.-07 22:10:07 Pass-thru 192.168.xx.33:55443
déc.-07 22:10:06 Pass-thru Yeelight-1
déc.-07 22:10:06 Pass-thru 192.168.xx.33:55443
déc.-07 22:10:06 Pass-thru {"method":"props","params":{"rgb":5834495}}
déc.-07 22:10:06 Pass-thru There are 44 bytes of binary data.
déc.-07 22:10:04 Pass-thru There are 45 bytes of binary data.
déc.-07 22:10:04 Pass-thru Yeelight-1
déc.-07 22:10:04 Pass-thru 192.168.xx.33:55443
déc.-07 22:10:04 Pass-thru {"method":"props","params":{"rgb":16754439}}
déc.-07 22:10:00 Pass-thru Yeelight-1
déc.-07 22:10:00 Pass-thru 192.168.xx.33:55443
déc.-07 22:10:00 Pass-thru {"method":"props","params":{"color_mode":1}}
déc.-07 22:10:00 Pass-thru There are 45 bytes of binary data.
déc.-07 22:09:46 Pass-thru Yeelight-1
déc.-07 22:09:46 Pass-thru 192.168.xx.33:55443
déc.-07 22:09:46 Pass-thru {"method":"props","params":{"ct":6049}}
déc.-07 22:09:46 Pass-thru There are 40 bytes of binary data.
déc.-07 22:09:45 Pass-thru Yeelight-1
déc.-07 22:09:45 Pass-thru 192.168.xx.33:55443
déc.-07 22:09:45 Pass-thru {"method":"props","params":{"ct":6066}}
déc.-07 22:09:45 Pass-thru There are 40 bytes of binary data.
déc.-07 22:09:43 Pass-thru Yeelight-1
déc.-07 22:09:43 Pass-thru 192.168.xx.33:55443
déc.-07 22:09:43 Pass-thru {"method":"props","params":{"ct":3186}}
déc.-07 22:09:43 Pass-thru There are 40 bytes of binary data.
déc.-07 22:09:42 Pass-thru Yeelight-1
déc.-07 22:09:42 Pass-thru 192.168.xx.33:55443
déc.-07 22:09:42 Pass-thru {"method":"props","params":{"color_mode":2}}
déc.-07 22:09:42 Pass-thru There are 45 bytes of binary data.
déc.-07 22:09:04 Pass-thru 192.168.xx.33:55443
déc.-07 22:09:04 Pass-thru {"method":"props","params":{"bright":58}}
déc.-07 22:09:04 Pass-thru There are 42 bytes of binary data.
déc.-07 22:09:04 Pass-thru Yeelight-1
déc.-07 22:08:54 Pass-thru Yeelight-1
déc.-07 22:08:54 Pass-thru 192.168.xx.33:55443
déc.-07 22:08:54 Pass-thru {"method":"props","params":{"bright":1,"rgb":16750848}}
déc.-07 22:08:54 Pass-thru There are 56 bytes of binary data.
déc.-07 22:08:52 Pass-thru {"method":"props","params":{"flowing":0}}
déc.-07 22:08:52 Pass-thru There are 42 bytes of binary data.
déc.-07 22:08:52 Pass-thru Yeelight-1
déc.-07 22:08:52 Pass-thru 192.168.xx.33:55443
déc.-07 22:08:06 Pass-thru Yeelight-1
déc.-07 22:08:06 Pass-thru 192.168.xx.33:55443
déc.-07 22:08:06 Pass-thru {"method":"props","params":{"flowing":1}}
déc.-07 22:08:06 Pass-thru There are 42 bytes of binary data.
déc.-07 22:07:35 Pass-thru Yeelight-1
déc.-07 22:07:35 Pass-thru 192.168.xx.33:55443
déc.-07 22:07:35 Pass-thru {"method":"props","params":"bright":50,"rgb":1315890,"flowin g":0}}
déc.-07 22:07:35 Pass-thru There are 68 bytes of binary data.
déc.-07 22:07:34 Pass-thru Yeelight-1
déc.-07 22:07:34 Pass-thru 192.168.xx.33:55443
déc.-07 22:07:34 Pass-thru {"method":"props","params":{"color_mode":1}}
déc.-07 22:07:34 Pass-thru There are 45 bytes of binary data.
Jean-francois.
Reply With Quote
  #18  
Old December 31st, 2017, 06:10 PM
mrhappy mrhappy is offline
OverSeer
 
Join Date: Nov 2007
Location: W.Mids, UK
Posts: 7,314
jfla

Could you please try this - (see first post)

It appears that .net is sending out the UDP discovery packets on interfaces that may not always be the correct one (who knows how it makes the decision), as such the packets get lost. There is no great method to determine which is the right network interface to send them out of because even my VirtualBox has a virtual NIC that supports the multicast address so it is not correct to check whether or not they support that address.

I have left it to make it's own mind up about the interfaces and default to interface 0. This may still however be wrong in certain setups and as such I do have a method to jump that if needed but I would prefer to try this first. If this still does not allow the devices to be discovered then please attach a screenshot of the start of the plugin. I am interested in the names of the interfaces that you see in the red boxes like here;

Last edited by mrhappy; April 21st, 2018 at 06:00 AM.
Reply With Quote
  #19  
Old January 2nd, 2018, 07:40 AM
jfla jfla is offline
Seer Deluxe
 
Join Date: Apr 2004
Location: ROUEN, France
Posts: 213
Hi, MrHappy

I'm not at home .I test it when i return.

Happy NewYear

Jean-Francois.
Reply With Quote
  #20  
Old January 3rd, 2018, 04:45 AM
jfla jfla is offline
Seer Deluxe
 
Join Date: Apr 2004
Location: ROUEN, France
Posts: 213
Hello, MrHappy

I tested last night,

Before i stopped drhsplugin for this

this is the startup log:

Quote:
Connecting to server at 127.0.0.1...
Connected, waiting to be initialized...
[02/01/2018 22:41:27] - Yeelight LED Startup
[02/01/2018 22:41:27] - StartThread Entered
[02/01/2018 22:41:27] - --> Receive Thread Started
[02/01/2018 22:41:27] - -> NameOfInterface: ethernet
[02/01/2018 22:41:27] - ---> Start Of Block
[02/01/2018 22:41:27] - --> Multicast Adapter Discovered: Connexion au réseau local
[02/01/2018 22:41:27] - --> MCA Count: 11
[02/01/2018 22:41:27] - ---> MCA Item Address: ff01::1%2
[02/01/2018 22:41:27] - ---> MCA Item Address: ff02::1%2
[02/01/2018 22:41:27] - ---> MCA Item Address: ff02::c%2
[02/01/2018 22:41:27] - ---> MCA Item Address: ff02::fb%2
[02/01/2018 22:41:27] - ---> MCA Item Address: ff02::1:3%2
[02/01/2018 22:41:27] - ---> MCA Item Address: ff02::1:ffcd:edb7%2
[02/01/2018 22:41:27] - ---> MCA Item Address: 224.0.0.1
[02/01/2018 22:41:27] - ---> MCA Item Address: 224.0.0.251
[02/01/2018 22:41:27] - ---> MCA Item Address: 224.0.0.252
[02/01/2018 22:41:27] - ---> MCA Item Address: 239.255.255.250
[02/01/2018 22:41:27] - ---> MCA Item Address: 239.255.255.251
[02/01/2018 22:41:27] - --> Multicast Operational Status: 1
[02/01/2018 22:41:27] - ---> Index: 2
[02/01/2018 22:41:27] - --> Multicast Adapter Discovered: Connexion réseau sans fil
[02/01/2018 22:41:27] - --> MCA Count: 4
[02/01/2018 22:41:27] - ---> MCA Item Address: ff01::1%7
[02/01/2018 22:41:27] - ---> MCA Item Address: ff02::1%7
[02/01/2018 22:41:27] - ---> MCA Item Address: ff02::1:ff93:d06%7
[02/01/2018 22:41:27] - ---> MCA Item Address: 224.0.0.1
[02/01/2018 22:41:27] - --> Multicast Operational Status: 2
[02/01/2018 22:41:27] - ---> Index: 7
[02/01/2018 22:41:27] - --> Multicast Adapter Discovered: Connexion au réseau local* 3
[02/01/2018 22:41:27] - --> MCA Count: 4
[02/01/2018 22:41:27] - ---> MCA Item Address: ff01::1%6
[02/01/2018 22:41:27] - ---> MCA Item Address: ff02::1%6
[02/01/2018 22:41:27] - ---> MCA Item Address: ff02::1:ff79:912d%6
[02/01/2018 22:41:27] - ---> MCA Item Address: 224.0.0.1
[02/01/2018 22:41:27] - --> Multicast Operational Status: 2
[02/01/2018 22:41:27] - ---> Index: 6
[02/01/2018 22:41:27] - --> Multicast Adapter Discovered: Connexion réseau Bluetooth 2
[02/01/2018 22:41:27] - --> MCA Count: 4
[02/01/2018 22:41:27] - ---> MCA Item Address: ff01::1%5
[02/01/2018 22:41:27] - ---> MCA Item Address: ff02::1%5
[02/01/2018 22:41:27] - ---> MCA Item Address: ff02::1:ff98:3387%5
[02/01/2018 22:41:27] - ---> MCA Item Address: 224.0.0.1
[02/01/2018 22:41:27] - --> Multicast Operational Status: 2
[02/01/2018 22:41:27] - ---> Index: 5
[02/01/2018 22:41:27] - --> Multicast Adapter Discovered: Loopback Pseudo-Interface 1
[02/01/2018 22:41:27] - --> MCA Count: 2
[02/01/2018 22:41:27] - ---> MCA Item Address: ff02::c%1
[02/01/2018 22:41:27] - ---> MCA Item Address: 239.255.255.250
[02/01/2018 22:41:27] - --> Multicast Operational Status: 1
[02/01/2018 22:41:27] - ---> Index: 1
[02/01/2018 22:41:27] - -> Index Of Interface: 0
[02/01/2018 22:41:27] - -> Start Discovery Timer - Five Seconds To Start
[02/01/2018 22:41:32] - Discovery Packet Sent: True
[02/01/2018 22:41:32] - HandleDiscovery Called: M-SEARCH * HTTP/1.1 HOST: 239.255.255.250:1982 MAN: "ssdp:discover" ST: wifi_bulb
[02/01/2018 22:41:32] - ---> Loopback Packet - False
[02/01/2018 22:42:02] - HandleDiscovery Called: M-SEARCH * HTTP/1.1 HOST: 239.255.255.250:1982 MAN: "ssdp:discover" ST: wifi_bulb
[02/01/2018 22:42:02] - ---> Loopback Packet - False
[02/01/2018 22:42:02] - Discovery Packet Sent: True
[02/01/2018 22:42:02] - ---> Thread RX Exception: Une connexion existante a dû être fermée par l'hôte distant
[02/01/2018 22:42:32] - Discovery Packet Sent: True
[02/01/2018 22:43:02] - Discovery Packet Sent: True
[02/01/2018 22:43:32] - Discovery Packet Sent: True
[02/01/2018 22:44:02] - Discovery Packet Sent: True
No reponse to discovery the ledstrip

Jean-Francois.
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Beta Testers Wanted CFGuy WeatherXML 0 February 3rd, 2016 11:40 PM
Arduino For HS3 Beta testers Wanted..... enigmatheatre HS3 Plug-In Development 25 January 11th, 2014 06:39 AM
InControl For Windows Phone 7.5 Mango - Beta Testers Wanted lamanmi InControl Windows Store / Windows Phone 7 December 22nd, 2011 09:22 AM
IRTrans .net Plugin BETA Testers Wanted YoYo Plug-In Development 0 March 25th, 2006 05:56 PM
Beta testers wanted for HomeSeer plug-in ChrisG Script & Plug-In Library Discussion 9 March 9th, 2002 06:03 PM


All times are GMT -4. The time now is 12:11 PM.


Copyright HomeSeer Technologies, LLC