+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: Add-on Support (https://forum.kodi.tv/forumdisplay.php?fid=27)
+---- Forum: Service Add-ons (https://forum.kodi.tv/forumdisplay.php?fid=152)
+---- Thread: Broken YeeMee - (Control Yeelight Smart Bulb + Ambi from Kodi) (/showthread.php?tid=313197)
RE: YeeMee - (Control Yeelight Smart Bulb + Ambi from Kodi) - paokoutsa - 2018-01-07
(2018-01-07, 13:40)DaLanik Wrote: There is probably another process listening on the port, can you a) restart Kodi and try again b) disable addons/services which might use the same ports... Doesn't seem like addon error, more like your local config.Indeed, not getting an error in kodi log after uninstalling Addon, restarting kodi and reconfiguring. But there is no response from Yeelight strip when starting a video. Testing it works normally.
RE: YeeMee - (Control Yeelight Smart Bulb + Ambi from Kodi) - User 325245 - 2018-01-07
Well yes, - because then the other process would be "alone" and can listen on the port. Lights work in normal mode because it works differently from Ambi mode. In ambi mode, you need to listen on the port.... What other addons do you use?
RE: YeeMee - (Control Yeelight Smart Bulb + Ambi from Kodi) - paokoutsa - 2018-01-07
(2018-01-07, 15:17)DaLanik Wrote: Well yes, - because then the other process would be "alone" and can listen on the port. Lights work in normal mode because it works differently from Ambi mode. In ambi mode, you need to listen on the port.... What other addons do you use?
Mostly some mainstream video add-ons. Nothing really special because that is a fresh install. I had the same problems with my old one using YeeMee add-on, that's why I reinstalled LibreElec.
What port is the add-on using for the server it tries to start? Is that possible that other apps (for example Yeti in my Android phone) prevent YeeMee from accessing the strip?
RE: YeeMee - (Control Yeelight Smart Bulb + Ambi from Kodi) - User 325245 - 2018-01-07
It's using port 55440.
RE: YeeMee - (Control Yeelight Smart Bulb + Ambi from Kodi) - User 325245 - 2018-01-08
OMG, just realized I'll have to redo the addon to support new Moon ceiling light (Yeelight JIAOYUE 650) which has both white and color LEDs... real horror show for settings....
RE: YeeMee - (Control Yeelight Smart Bulb + Ambi from Kodi) - plenkske - 2018-01-08
Hi there @"DaLanik" , first of all great work on your addon !
I'm having some troubles though.
What I want to do:
I have 2 yeelight strips behind my tv , and I want to use them for ambilight with your addon in Kodi.
Using Kodi on a Windows HTPC. Its Kodi 17.6
Using your latest repo/addon version.
The 2 yeelight strips have developer/LAN enabled, and they have a static IP through my router. They both work fine in the app and in Domoticz (I disable it in domoticz when I test the addon).
The main problem is: ambilight does not work. The stripes turn on but dont change in color.
I was able to add the stripes and test them, they also worked on video play/stop. But they never did anything with ambilight.
What I tried:
- Multiple reinstallations of the addon
- Multiple deletions of the userdata
- Disabling hardware acceleration
- Discovery of the stripes never worked
- Manually adding the stripes worked, tried to add in multiple orders and changing settings in multiple ways.
- Tried only ambi service on and no yeemee service on. Seemed promosing in the log but ambilight still didnt work. Saw no errors,
- Tried the rendercapture thing but that gave some buffer error in the log.
- Checked the log sometimes, at one point I thought the exception about "screensaver.video" was it. But I checked your python code and it seems you dont need it ?
- I downloaded the repo again and reinstalled it all.
- A lot of Kodi reboots.
- Some Windows reboots. After the last 2 reboots the stripes dont work at all with the yeemee addon. After adding and testing they dont work.
Current status: nothing seems to work anymore after adding bulbs. Testing also fails, and after testing fails it keeps showing the loading screen so I have to kill Kodi. Maybe you can fix that
This is the current log when testing:
normal log
debug loglog:21:29:24.253 T:4432 WARNING: CPythonInvoker(11): Script invoked without an addon. Adding all addon modules installed to python path as fallback. This behaviour will be removed in future version.
21:29:46.794 T:4292 ERROR: EXCEPTION: Unknown addon id 'screensaver.video'.
21:29:47.702 T:4432 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <type 'exceptions.TypeError'>
Error Contents: expected string or buffer
Traceback (most recent call last):
File "C:\Users\admin\AppData\Roaming\Kodi\addons\service.yeemee\standalone.py", line 438, in <module>
testbulb(1)
File "C:\Users\admin\AppData\Roaming\Kodi\addons\service.yeemee\standalone.py", line 233, in testbulb
mmm1 = bulbone.testTurnOn()
File "C:\Users\admin\AppData\Roaming\Kodi\addons\service.yeemee\service.py", line 1055, in testTurnOn
a1 = json.loads(result)["error"]["message"]
File "C:\Program Files (x86)\Kodi\system\python\Lib\json\__init__.py", line 339, in loads
return _default_decoder.decode(s)
File "C:\Program Files (x86)\Kodi\system\python\Lib\json\decoder.py", line 364, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
TypeError: expected string or buffer
-->End of Python script error report<--
21:29:55.710 T:4884 NOTICE: Storing total System Uptime
21:29:55.710 T:4884 NOTICE: Saving settings
21:29:55.714 T:4884 NOTICE: Saving skin settings
21:29:55.715 T:4884 NOTICE: stop all
21:29:55.715 T:4884 NOTICE: stop player
21:29:55.715 T:4884 NOTICE: ES: Stopping event server
21:29:55.715 T:4884 NOTICE: stopping upnp
21:29:55.868 T:4884 NOTICE: CWebServer[8080]: Stopped
21:29:55.902 T:3144 NOTICE: ES: UDP Event server stopped
21:29:56.103 T:4884 NOTICE: clean cached files!
21:30:01.142 T:4884 ERROR: CPythonInvoker(3, C:\Users\admin\AppData\Roaming\Kodi\addons\service.yeemee\service.py): script didn't stop in 5 seconds - let's kill it
21:30:01.237 T:4884 NOTICE: closing down remote control service
21:30:01.237 T:4884 NOTICE: stopped
21:30:01.438 T:4884 NOTICE: destroy
21:30:01.438 T:4884 NOTICE: unload skin
After this I uninstalled the addon again and deleted the userdata,log:21:31:08.603 T:4788 INFO: initializing python engine.
21:31:08.603 T:4788 DEBUG: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): start processing
21:31:08.612 T:2624 DEBUG: Keyboard: scancode: 0x1c, sym: 0x000d, unicode: 0x0000, modifier: 0x0
21:31:08.746 T:4260 DEBUG: YEEMEE >> YEMME - AMBI PRIORITY >> 1
21:31:08.746 T:4260 DEBUG: YEEMEE >> LOWER BRIGHTNESS ON AMBI PAUSE >> 0
21:31:08.746 T:4260 DEBUG: YEEMEE >> AMBI SMOOTHEN (MS) >> 0
21:31:08.746 T:4260 DEBUG: YEEMEE >> YEMME - AMBI PRECISION >> 0
21:31:08.746 T:4260 DEBUG: YEEMEE >> REPORT ERRORS >> True
21:31:08.746 T:4260 DEBUG: YEEMEE >> NUMBER OF BULBS >> 1
21:31:08.746 T:4260 DEBUG: YEEMEE >> ON AT START >> 0
21:31:08.746 T:4260 DEBUG: YEEMEE >> DISABLE FOR SHORT FILMS >>FALSE<<
21:31:08.746 T:4260 DEBUG: YEEMEE >> ACTIVATION TIME >>OFF<<
21:31:08.746 T:4260 DEBUG: YEEMEE >> MAX BRIGHT DAY >> 100
21:31:08.746 T:4260 DEBUG: YEEMEE >> MAX BRIGHT CIVIL TW >> 100
21:31:08.746 T:4260 DEBUG: YEEMEE >> MAX BRIGHT NAUTIC TW >> 100
21:31:08.746 T:4260 DEBUG: YEEMEE >> MAX BRIGTH NIGHT >> 100
21:31:08.746 T:4260 DEBUG: YEEMEE >> INIT BULB NUM: 1, IP ADDR: 192.168.1.77, MODEL: stripe
21:31:08.746 T:4260 DEBUG: YEEMEE >> NUMBER OF ACTIVE BULBS >> 1
21:31:08.746 T:4260 DEBUG: YEEMEE >> Number Act Int Color Eff Duration
21:31:08.746 T:4260 DEBUG: YEEMEE >> BULB 0 PLAY : >> 0 20 #BA2B2B 0 500
21:31:08.746 T:4260 DEBUG: YEEMEE >> BULB 0 STOP : >> 0 20 #BA2B2B 0 500
21:31:08.746 T:4260 DEBUG: YEEMEE >> BULB 0 PAUSE: >> 0 20 #BA2B2B 0 500
21:31:08.746 T:4260 DEBUG: YEEMEE >> BULB 0 AMBI: >> 1 BIAS: 0
21:31:08.746 T:4260 DEBUG: YEEMEE >> NUMBER OF AMBI BULBS >> 1
21:31:08.746 T:4260 DEBUG: YEEMEE >> NUMBER OF CONTROLLERS >> 0
21:31:08.817 T:4788 DEBUG: -->Python Interpreter Initialized<--
21:31:08.817 T:4788 DEBUG: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): the source file to load is "special://home/addons/service.yeemee/standalone.py" ("C:\Users\admin\AppData\Roaming\Kodi\addons\service.yeemee\standalone.py")
21:31:08.817 T:4788 WARNING: CPythonInvoker(6): Script invoked without an addon. Adding all addon modules installed to python path as fallback. This behaviour will be removed in future version.
21:31:08.824 T:4788 DEBUG: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): setting the Python path to C:\Users\admin\AppData\Roaming\Kodi\addons\service.yeemee;C:\Program Files (x86)\Kodi\addons\script.module.pil\lib;C:\Users\admin\AppData\Roaming\Kodi\addons\script.module.httplib2\lib;C:\Users\admin\AppData\Roaming\Kodi\addons\script.module.six\lib;C:\Users\admin\AppData\Roaming\Kodi\addons\script.module.uritemplate\lib;C:\Users\admin\AppData\Roaming\Kodi\addons\script.module.oauth2client\lib;C:\Users\admin\AppData\Roaming\Kodi\addons\script.module.googleapi\lib;C:\Users\admin\AppData\Roaming\Kodi\addons\script.module.certifi\lib;C:\Users\admin\AppData\Roaming\Kodi\addons\script.module.chardet\lib;C:\Users\admin\AppData\Roaming\Kodi\addons\script.module.idna\lib;C:\Users\admin\AppData\Roaming\Kodi\addons\script.module.urllib3\lib;C:\Users\admin\AppData\Roaming\Kodi\addons\script.module.requests\lib;C:\Users\admin\AppData\Roaming\Kodi\addons\script.module.yaml\lib;C:\Users\admin\AppData\Roaming\Kodi\addons\script.module.beautifulsoup\lib;C:\Users\admin\AppData\Roaming\Kodi\addons\script.module.xbmcswift2\lib;C:\Users\admin\AppData\Roaming\Kodi\addons\plugin.video.youtube\resources\lib\;C:\Program Files (x86)\Kodi\system\python\DLLs;C:\Program Files (x86)\Kodi\system\python\Lib;C:\Program Files (x86)\Kodi\python27.zip;C:\Program Files (x86)\Kodi\system\python\lib\plat-win;C:\Program Files (x86)\Kodi\system\python\lib\lib-tk;C:\Program Files (x86)\Kodi;C:\Program Files (x86)\Kodi\system\python;C:\Program Files (x86)\Kodi\system\python\lib\site-packages
21:31:08.824 T:4788 DEBUG: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): entering source directory C:\Users\admin\AppData\Roaming\Kodi\addons\service.yeemee
21:31:08.841 T:2624 DEBUG: ------ Window Deinit (DialogAddonSettings.xml) ------
21:31:08.860 T:4476 DEBUG: YEEMEE >> STANDALONE FINISHED
21:31:08.860 T:4476 INFO: CPythonInvoker(5, C:\Users\admin\AppData\Roaming\Kodi\addons\service.yeemee\standalone.py): script successfully run
21:31:08.930 T:4476 INFO: Python script stopped
21:31:08.930 T:4476 DEBUG: Thread LanguageInvoker 4476 terminating
21:31:09.596 T:4788 DEBUG: YEEMEE >> STANDALONE STARTED VERSION 4.2 - TEST LIGHTS
21:31:09.598 T:2624 DEBUG: ------ Window Init (DialogConfirm.xml) ------
21:31:09.598 T:2624 INFO: Loading skin file: DialogConfirm.xml, load type: KEEP_IN_MEMORY
21:31:10.583 T:2624 DEBUG: Keyboard: scancode: 0x1c, sym: 0x000d, unicode: 0x000d, modifier: 0x0
21:31:10.733 T:2624 DEBUG: CInputManager::OnKey: return (0xf00d) pressed, action is Select
21:31:10.733 T:2624 DEBUG: Keyboard: scancode: 0x1c, sym: 0x000d, unicode: 0x0000, modifier: 0x0
21:31:10.968 T:2624 DEBUG: ------ Window Deinit (DialogConfirm.xml) ------
21:31:11.030 T:4788 DEBUG: [Warning] CGUITextureManager::GetTexturePath: could not find texture 'media\YEE02.png'
21:31:11.034 T:4788 DEBUG: [Warning] CGUITextureManager::GetTexturePath: could not find texture 'media\yee_color.png'
21:31:11.064 T:4788 DEBUG: YEEMEE STANDALONE >> INITIALIZING OVERLAY
21:31:11.065 T:4788 DEBUG: YEEMEE >> TEST BULB NR 1
21:31:11.065 T:4788 DEBUG: YEEMEE >> TEST BULB ON
21:31:11.084 T:2624 DEBUG: Activating window ID: 10138
21:31:11.084 T:2624 DEBUG: ------ Window Init (DialogBusy.xml) ------
21:31:27.484 T:2624 DEBUG: CWinEventsWin32::WndProcWindow is active
21:31:27.667 T:2624 DEBUG: CInputManager:rocessMouse: trying mouse action leftclick
21:31:27.916 T:2624 DEBUG: Keyboard: scancode: 0x01, sym: 0x001b, unicode: 0x001b, modifier: 0x0
21:31:28.034 T:2624 DEBUG: CInputManager::OnKey: escape (0xf01b) pressed, action is PreviousMenu
21:31:28.034 T:2624 DEBUG: Keyboard: scancode: 0x01, sym: 0x001b, unicode: 0x0000, modifier: 0x0
21:31:28.035 T:2624 DEBUG: ------ Window Deinit (Pointer.xml) ------
21:31:28.118 T:2624 DEBUG: Keyboard: scancode: 0x01, sym: 0x001b, unicode: 0x001b, modifier: 0x0
21:31:28.233 T:2624 DEBUG: CInputManager::OnKey: escape (0xf01b) pressed, action is PreviousMenu
21:31:28.233 T:2624 DEBUG: Keyboard: scancode: 0x01, sym: 0x001b, unicode: 0x0000, modifier: 0x0
21:31:28.816 T:2624 DEBUG: Keyboard: scancode: 0x1c, sym: 0x000d, unicode: 0x000d, modifier: 0x0
21:31:28.933 T:2624 DEBUG: CInputManager::OnKey: return (0xf00d) pressed, action is Select
21:31:28.933 T:2624 DEBUG: Keyboard: scancode: 0x1c, sym: 0x000d, unicode: 0x0000, modifier: 0x0
21:31:29.366 T:2624 DEBUG: Keyboard: scancode: 0x1c, sym: 0x000d, unicode: 0x000d, modifier: 0x0
21:31:29.466 T:2624 DEBUG: CInputManager::OnKey: return (0xf00d) pressed, action is Select
21:31:29.467 T:2624 DEBUG: Keyboard: scancode: 0x1c, sym: 0x000d, unicode: 0x0000, modifier: 0x0
21:31:29.567 T:2624 DEBUG: Keyboard: scancode: 0x1c, sym: 0x000d, unicode: 0x000d, modifier: 0x0
21:31:29.650 T:2624 DEBUG: CInputManager::OnKey: return (0xf00d) pressed, action is Select
21:31:29.650 T:2624 DEBUG: Keyboard: scancode: 0x1c, sym: 0x000d, unicode: 0x0000, modifier: 0x0
21:31:29.717 T:2624 DEBUG: Keyboard: scancode: 0x1c, sym: 0x000d, unicode: 0x000d, modifier: 0x0
21:31:29.800 T:2624 DEBUG: CInputManager::OnKey: return (0xf00d) pressed, action is Select
21:31:29.800 T:2624 DEBUG: Keyboard: scancode: 0x1c, sym: 0x000d, unicode: 0x0000, modifier: 0x0
21:31:29.866 T:2624 DEBUG: Keyboard: scancode: 0x1c, sym: 0x000d, unicode: 0x000d, modifier: 0x0
21:31:29.966 T:2624 DEBUG: CInputManager::OnKey: return (0xf00d) pressed, action is Select
21:31:29.966 T:2624 DEBUG: Keyboard: scancode: 0x1c, sym: 0x000d, unicode: 0x0000, modifier: 0x0
21:31:30.649 T:2624 DEBUG: Keyboard: scancode: 0x4b, sym: 0x0114, unicode: 0x0000, modifier: 0x0
21:31:30.650 T:2624 DEBUG: CInputManager::OnKey: left (0xf082) pressed, action is Left
21:31:30.784 T:2624 DEBUG: Keyboard: scancode: 0x4b, sym: 0x0114, unicode: 0x0000, modifier: 0x0
21:31:30.900 T:2624 DEBUG: Keyboard: scancode: 0x4d, sym: 0x0113, unicode: 0x0000, modifier: 0x0
21:31:30.900 T:2624 DEBUG: CInputManager::OnKey: right (0xf083) pressed, action is Right
21:31:31.050 T:2624 DEBUG: Keyboard: scancode: 0x4d, sym: 0x0113, unicode: 0x0000, modifier: 0x0
21:31:31.050 T:2624 DEBUG: Keyboard: scancode: 0x4b, sym: 0x0114, unicode: 0x0000, modifier: 0x0
21:31:31.051 T:2624 DEBUG: CInputManager::OnKey: left (0xf082) pressed, action is Left
21:31:31.167 T:2624 DEBUG: Keyboard: scancode: 0x4b, sym: 0x0114, unicode: 0x0000, modifier: 0x0
21:31:31.250 T:2624 DEBUG: Previous line repeats 1 times.
21:31:31.250 T:2624 DEBUG: CInputManager::OnKey: left (0xf082) pressed, action is Left
21:31:31.333 T:2624 DEBUG: Keyboard: scancode: 0x4b, sym: 0x0114, unicode: 0x0000, modifier: 0x0
21:31:31.349 T:2624 DEBUG: Keyboard: scancode: 0x4d, sym: 0x0113, unicode: 0x0000, modifier: 0x0
21:31:31.349 T:2624 DEBUG: CInputManager::OnKey: right (0xf083) pressed, action is Right
21:31:31.500 T:2624 DEBUG: Keyboard: scancode: 0x4d, sym: 0x0113, unicode: 0x0000, modifier: 0x0
21:31:31.533 T:2624 DEBUG: Keyboard: scancode: 0x4b, sym: 0x0114, unicode: 0x0000, modifier: 0x0
21:31:31.533 T:2624 DEBUG: CInputManager::OnKey: left (0xf082) pressed, action is Left
21:31:31.600 T:2624 DEBUG: Keyboard: scancode: 0x48, sym: 0x0111, unicode: 0x0000, modifier: 0x0
21:31:31.601 T:2624 DEBUG: CInputManager::OnKey: up (0xf080) pressed, action is Up
21:31:31.650 T:2624 DEBUG: Keyboard: scancode: 0x4b, sym: 0x0114, unicode: 0x0000, modifier: 0x0
21:31:31.717 T:2624 DEBUG: Keyboard: scancode: 0x48, sym: 0x0111, unicode: 0x0000, modifier: 0x0
21:31:31.800 T:2624 DEBUG: Previous line repeats 1 times.
21:31:31.800 T:2624 DEBUG: CInputManager::OnKey: up (0xf080) pressed, action is Up
21:31:31.916 T:2624 DEBUG: Keyboard: scancode: 0x48, sym: 0x0111, unicode: 0x0000, modifier: 0x0
21:31:31.933 T:2624 DEBUG: Keyboard: scancode: 0x4d, sym: 0x0113, unicode: 0x0000, modifier: 0x0
21:31:31.933 T:2624 DEBUG: CInputManager::OnKey: right (0xf083) pressed, action is Right
21:31:32.067 T:2624 DEBUG: Keyboard: scancode: 0x4d, sym: 0x0113, unicode: 0x0000, modifier: 0x0
21:31:32.068 T:4788 DEBUG: YEEMEE >> CONNECT ERROR [Errno 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
21:31:32.072 T:4788 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <type 'exceptions.TypeError'>
Error Contents: expected string or buffer
Traceback (most recent call last):
File "C:\Users\admin\AppData\Roaming\Kodi\addons\service.yeemee\standalone.py", line 438, in <module>
testbulb(1)
File "C:\Users\admin\AppData\Roaming\Kodi\addons\service.yeemee\standalone.py", line 233, in testbulb
mmm1 = bulbone.testTurnOn()
File "C:\Users\admin\AppData\Roaming\Kodi\addons\service.yeemee\service.py", line 1055, in testTurnOn
a1 = json.loads(result)["error"]["message"]
File "C:\Program Files (x86)\Kodi\system\python\Lib\json\__init__.py", line 339, in loads
return _default_decoder.decode(s)
File "C:\Program Files (x86)\Kodi\system\python\Lib\json\decoder.py", line 364, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
TypeError: expected string or buffer
-->End of Python script error report<--
21:31:32.072 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 5112
21:31:32.083 T:2624 DEBUG: ------ Window Init (DialogNotification.xml) ------
21:31:32.084 T:2624 DEBUG: Keyboard: scancode: 0x4b, sym: 0x0114, unicode: 0x0000, modifier: 0x0
21:31:32.084 T:2624 DEBUG: CInputManager::OnKey: left (0xf082) pressed, action is Left
21:31:32.084 T:2624 DEBUG: Keyboard: scancode: 0x48, sym: 0x0111, unicode: 0x0000, modifier: 0x0
21:31:32.084 T:2624 DEBUG: CInputManager::OnKey: up (0xf080) pressed, action is Up
21:31:32.150 T:2624 DEBUG: Keyboard: scancode: 0x48, sym: 0x0111, unicode: 0x0000, modifier: 0x0
21:31:32.173 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 1584
21:31:32.200 T:2624 DEBUG: Keyboard: scancode: 0x4b, sym: 0x0114, unicode: 0x0000, modifier: 0x0
21:31:32.250 T:2624 DEBUG: Keyboard: scancode: 0x5b, sym: 0x0137, unicode: 0x0000, modifier: 0x10
21:31:32.250 T:2624 DEBUG: CInputManager::OnKey: win-leftwindows (0x10f0d6) pressed, action is
21:31:32.274 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3868
21:31:32.375 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 2672
21:31:32.402 T:2624 DEBUG: Keyboard: scancode: 0x5b, sym: 0x0137, unicode: 0x0000, modifier: 0x0
21:31:32.403 T:2624 DEBUG: CWinEventsWin32::WndProcWindow is active
21:31:32.403 T:2624 DEBUG: CWinEventsWin32::WndProc: Focus switched to process C:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\SearchUI.exe
21:31:32.478 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4668
21:31:32.579 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4864
21:31:32.680 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4484
21:31:32.781 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4832
21:31:32.802 T:2624 DEBUG: ------ Window Init (Pointer.xml) ------
21:31:32.882 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3620
21:31:32.983 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4312
21:31:33.083 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3648
21:31:33.184 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4552
21:31:33.198 T:860 DEBUG: Thread JobWorker 860 terminating (autodelete)
21:31:33.198 T:4224 DEBUG: Thread JobWorker 4224 terminating (autodelete)
21:31:33.198 T:4376 DEBUG: Thread JobWorker 4376 terminating (autodelete)
21:31:33.198 T:2940 DEBUG: Thread JobWorker 2940 terminating (autodelete)
21:31:33.285 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3940
21:31:33.386 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4384
21:31:33.487 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4044
21:31:33.588 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3880
21:31:33.689 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4272
21:31:33.790 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 5020
21:31:33.891 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3352
21:31:33.993 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3436
21:31:34.193 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3772
21:31:34.294 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3408
21:31:34.394 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 744
21:31:34.495 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4840
21:31:34.596 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 5040
21:31:34.700 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 1656
21:31:34.802 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 2996
21:31:34.903 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4760
21:31:35.005 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4512
21:31:35.106 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 2088
21:31:35.208 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3636
21:31:35.309 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 1804
21:31:35.410 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 2716
21:31:35.510 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 1568
21:31:35.611 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3736
21:31:35.712 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4948
21:31:35.813 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4492
21:31:35.913 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4776
21:31:36.014 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4692
21:31:36.078 T:2624 NOTICE: Storing total System Uptime
21:31:36.078 T:2624 NOTICE: Saving settings
21:31:36.083 T:2624 NOTICE: Saving skin settings
21:31:36.085 T:2624 NOTICE: stop all
21:31:36.085 T:2624 NOTICE: stop player
21:31:36.085 T:2624 DEBUG: CNetwork::NetworkMessage - Signaling network services to stop
21:31:36.085 T:2624 NOTICE: ES: Stopping event server
21:31:36.085 T:2624 DEBUG: CNetwork::NetworkMessage - Waiting for network services to stop
21:31:36.085 T:2624 NOTICE: stopping upnp
21:31:36.086 T:1604 DEBUG: CAnnouncementManager - Announcement: OnQuit from xbmc
21:31:36.087 T:1604 DEBUG: GOT ANNOUNCEMENT, type: 8, from xbmc, message OnQuit
21:31:36.115 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 2640
21:31:36.173 T:3008 NOTICE: ES: UDP Event server stopped
21:31:36.173 T:3008 DEBUG: Thread EventServer 3008 terminating
21:31:36.175 T:1136 DEBUG: Thread TCPServer 1136 terminating
21:31:36.216 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3928
21:31:36.291 T:2624 NOTICE: CWebServer[8080]: Stopped
21:31:36.291 T:4548 DEBUG: Thread PeripEventScanner 4548 terminating
21:31:36.292 T:4388 DEBUG: Thread PeripBusUSB 4388 terminating
21:31:36.316 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4672
21:31:36.416 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 5112
21:31:36.516 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4372
21:31:36.617 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4728
21:31:36.717 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 1584
21:31:36.785 T:1556 DEBUG: Thread PeripBusCEC 1556 terminating
21:31:36.785 T:4204 DEBUG: Thread PeripBusAddon 4204 terminating
21:31:36.786 T:2624 DEBUG: SECTION:UnloadDll(C:\Program Files (x86)\Kodi\addons\peripheral.joystick\peripheral.joystick.dll)
21:31:36.786 T:2624 INFO: ADDON: Dll Destroyed - Joystick Support
21:31:36.786 T:2624 NOTICE: clean cached files!
21:31:36.786 T:2624 DEBUG: ADDON: Stopping service addons.
21:31:36.817 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4680
21:31:36.917 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3868
21:31:36.985 T:4860 DEBUG: Thread EPGUpdater 4860 terminating
21:31:36.985 T:2212 DEBUG: Thread PVRGUIInfo 2212 terminating
21:31:37.018 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 2672
21:31:37.119 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3128
21:31:37.196 T:5008 INFO: CPythonInvoker(1, C:\Users\admin\AppData\Roaming\Kodi\addons\script.xbmcbackup\scheduler.py): script successfully run
21:31:37.196 T:2624 DEBUG: CPythonInvoker(1, C:\Users\admin\AppData\Roaming\Kodi\addons\script.xbmcbackup\scheduler.py): script termination took 402ms
21:31:37.207 T:5008 INFO: Python script interrupted by user
21:31:37.207 T:4260 DEBUG: YEEMEE >> EXIT
21:31:37.207 T:4260 INFO: CPythonInvoker(3, C:\Users\admin\AppData\Roaming\Kodi\addons\service.yeemee\service.py): script successfully run
21:31:37.207 T:2624 DEBUG: CPythonInvoker(3, C:\Users\admin\AppData\Roaming\Kodi\addons\service.yeemee\service.py): script termination took 1ms
21:31:37.207 T:5008 DEBUG: Thread LanguageInvoker 5008 terminating
21:31:37.208 T:4524 DEBUG: Thread ActiveAE 4524 terminating
21:31:37.213 T:4712 DEBUG: Thread AESink 4712 terminating
21:31:37.215 T:4260 INFO: Python script interrupted by user
21:31:37.215 T:4260 DEBUG: Thread LanguageInvoker 4260 terminating
21:31:37.219 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3892
21:31:37.265 T:2624 NOTICE: closing down remote control service
21:31:37.265 T:2624 NOTICE: stopped
21:31:37.265 T:3748 DEBUG: Thread RemoteControl 3748 terminating
21:31:37.320 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 2568
21:31:37.421 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4848
21:31:37.466 T:2624 NOTICE: destroy
21:31:37.466 T:2624 NOTICE: unload skin
21:31:37.466 T:2624 INFO: Unloading old skin ...
21:31:37.467 T:2624 DEBUG: ------ Window Deinit () ------
21:31:37.467 T:2624 DEBUG: ------ Window Deinit (Home.xml) ------
21:31:37.480 T:2624 DEBUG: ------ Window Deinit (Pointer.xml) ------
21:31:37.480 T:2624 DEBUG: ------ Window Deinit (DialogNotification.xml) ------
21:31:37.480 T:2624 DEBUG: ------ Window Deinit (DialogBusy.xml) ------
21:31:37.482 T:2624 DEBUG: CTextureBundleXBT::CloseBundle - Closed bundle
21:31:37.522 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4544
21:31:37.623 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4072
21:31:37.723 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 5104
21:31:37.824 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 2684
21:31:37.925 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4084
21:31:38.026 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4500
21:31:38.126 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4700
21:31:38.226 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 5092
21:31:38.327 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 5004
21:31:38.427 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3504
21:31:38.528 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4532
21:31:38.628 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4820
21:31:38.728 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4300
21:31:38.829 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4504
21:31:38.929 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3500
21:31:39.030 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4336
21:31:39.131 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3956
21:31:39.231 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 1400
21:31:39.331 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4964
21:31:39.432 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4836
21:31:39.532 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4252
21:31:39.632 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4684
21:31:39.733 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3628
21:31:39.833 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4140
21:31:39.933 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4480
21:31:40.034 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 2692
21:31:40.134 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4912
21:31:40.235 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4264
21:31:40.335 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3452
21:31:40.435 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4268
21:31:40.535 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4872
21:31:40.636 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4756
21:31:40.736 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 652
21:31:40.836 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4668
21:31:40.937 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4864
21:31:41.038 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4484
21:31:41.138 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4832
21:31:41.238 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3620
21:31:41.339 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4312
21:31:41.439 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3648
21:31:41.540 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 860
21:31:41.641 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4224
21:31:41.741 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4376
21:31:41.842 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3624
21:31:41.942 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3716
21:31:42.042 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4208
21:31:42.142 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 2396
21:31:42.244 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 4640
21:31:42.344 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 2340
21:31:42.444 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3368
21:31:42.517 T:2624 ERROR: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): script didn't stop in 5 seconds - let's kill it
21:31:42.544 T:4788 INFO: CPythonInvoker(6, special://home/addons/service.yeemee/standalone.py): waiting on thread 3228
21:31:42.654 T:4788 INFO: Python script interrupted by user
21:31:42.654 T:4788 DEBUG: Thread LanguageInvoker 4788 terminating
21:31:42.866 T:2624 NOTICE: unload sections
21:31:42.869 T:2624 NOTICE: special://profile/ is mapped to: special://masterprofile/
21:31:42.876 T:2624 NOTICE: PVRManager - stopping
Could you help me ? Really want to make this ambilight thing work. Because I can already see, turning them on manually, that I like it
RE: YeeMee - (Control Yeelight Smart Bulb + Ambi from Kodi) - User 325245 - 2018-01-08
Sorry but this is a complete mess
Can you delete addon, addondata and install it again and get it to the state that it works with bulbs (normal operation). Then turn on Ambi, turn on debugging, exit Kodi and start again. Try to play a movie for a minute, stop, exit Kodi and post the whole log to pastebin.
RE: YeeMee - (Control Yeelight Smart Bulb + Ambi from Kodi) - plenkske - 2018-01-08
(2018-01-08, 23:31)DaLanik Wrote: Sorry but this is a complete mess
Well, the log I posted is when I test a bulb and it cant find it. Then it tests, keeps the loading screen, gives an error message and it still loads. Have to kill Kodi manually. Maybe you can fix so the loading stops after testing fails.
I will try your other suggestions later this week
thanks already. Hope to get it back to work. Do I have to turn on ambi only, or also keep the normal yeemee service ?
RE: YeeMee - (Control Yeelight Smart Bulb + Ambi from Kodi) - plenkske - 2018-01-08
Oh yeah, another thing that bugged me.
After turning on ambi service, I couldnt normally exit Kodi. Not on any try. It simply crashes and had to kill Kodi. In the log it says something about force shut down the service script but nothing more.
Another thing I tried is looking for the port through netstat but I didnt find it so I guess its free.
RE: YeeMee - (Control Yeelight Smart Bulb + Ambi from Kodi) - User 325245 - 2018-01-09
It must work, just be sure you delete addon data for yeemee, just try one strip first, add IP etc. Keep Ambi off while testing normal operation, just to make things simpler
RE: YeeMee - (Control Yeelight Smart Bulb + Ambi from Kodi) - sksbir - 2018-01-09
I have an another suggestion for plenkske ;
if you have an android device at home, install kodi on it just to see how it works when it works.
try this trick : after each setting change in yeelight, exit kodi without testing anything(be patient, kodi needs 10s to exit when yeelight is in use) , start kodi and check settings if stored has you wished. if ok, exit settings without saving and test what you want.
try it with eg autodiscover : restart kodi just after autodiscover without saving config...
this helped me to perform initial configuration.
RE: YeeMee - (Control Yeelight Smart Bulb + Ambi from Kodi) - plenkske - 2018-01-09
Hey again @"DaLanik" and others reading.
Tonight I was able to add a stripe again for testing. Maybe it worked because I had the stripe powered off for a day, and now powered on again.
So, I started from scratch, added one stripe, rebooted Kodi some times and tested all non-ambi features. All work great !
Back to ambilight then. First tested it simply: setted the stripe to whole screen, turned service on, then restarted Kodi with debug log on.
Started a movie and nothing happens, no changeds in colors. I let it run for some time.
Here is the log: First Log
After that I changed some settings like ambi smoothness and turned of yeemee service.
But, no difference. Here is the log: Second Log
ps. I removed some pvr spam in the logs
Another thing I noticed, when ambi service is on, Kodi crashes on exit. When stopping a video also nothing happens (when both services are on).
Currently I have set the ambi service off and all non-ambi features work fine again. Exitting Kodi works fine aswell.
RE: YeeMee - (Control Yeelight Smart Bulb + Ambi from Kodi) - User 325245 - 2018-01-10
OK, the key to the problem is somewhere here:
Code:
21:49:36.024 T:2604 DEBUG: YEEMEE >> MESSAGE TO 192.168.1.77: {u'params': [u'power', u'music_on'], u'id': 1, u'method': u'get_prop'}
21:49:36.025 T:948 DEBUG: YEEMEE >> SERVER >> 192.168.1.76 WAITING FOR CONNECTION...
21:49:36.030 T:2604 DEBUG: YEEMEE >> RESPONSE FROM 192.168.1.77: on, 0
21:49:36.030 T:2604 DEBUG: YEEMEE >> MESSAGE TO 192.168.1.77: {u'params': [1, u'192.168.1.76', 55440], u'id': 1, u'method': u'set_music'}
21:49:54.070 T:2604 DEBUG: YEEMEE >> RESPONSE FROM 192.168.1.77: ,
As you can see, YeeMee asks the bulb for the state. Then starts the server. Bulb replies that it is ON and that it is NOT in music mode. YeeMee then sends command to TURN ON the music mode, and gets no reply....
Did you try to update the firmware of the strip?
RE: YeeMee - (Control Yeelight Smart Bulb + Ambi from Kodi) - plenkske - 2018-01-10
(2018-01-10, 00:25)DaLanik Wrote: OK, the key to the problem is somewhere here:
Code:
21:49:36.024 T:2604 DEBUG: YEEMEE >> MESSAGE TO 192.168.1.77: {u'params': [u'power', u'music_on'], u'id': 1, u'method': u'get_prop'}
21:49:36.025 T:948 DEBUG: YEEMEE >> SERVER >> 192.168.1.76 WAITING FOR CONNECTION...
21:49:36.030 T:2604 DEBUG: YEEMEE >> RESPONSE FROM 192.168.1.77: on, 0
21:49:36.030 T:2604 DEBUG: YEEMEE >> MESSAGE TO 192.168.1.77: {u'params': [1, u'192.168.1.76', 55440], u'id': 1, u'method': u'set_music'}
21:49:54.070 T:2604 DEBUG: YEEMEE >> RESPONSE FROM 192.168.1.77: ,
As you can see, YeeMee asks the bulb for the state. Then starts the server. Bulb replies that it is ON and that it is NOT in music mode. YeeMee then sends command to TURN ON the music mode, and gets no reply....
Did you try to update the firmware of the strip?
Both strips are updated to 1.4.1_40 . App says its latest version.
RE: YeeMee - (Control Yeelight Smart Bulb + Ambi from Kodi) - User 325245 - 2018-01-10
Strange. Can you turn on the music mode from your phone from Yeelight app?