(2017-10-26, 19:18)Nicholask Wrote: [ -> ]Hi,
I have a yeelight Ceiling light. Everything is working except return to original state (tried with "stop playing") which doesn't restore to previous state, but change the lighting to a little higher, maybe 30 or 40 while my original state was 100. Is there anything you can do?
Kodi 17.4
Thank you.
return to original state on STOP, I suppose?
First, thanks for the addon, it's amazing to see someone willing to create an addon for something that i paid 5€ lol.
I use the addons with Librelec on a raspberry pi 3. I want to use the addon only to have some kind of ambilight in the house. It works. Every time i start a movie or a tv show, the light change based on what is the screen. Perfect. The only problem i got it's the fact that it's working for less than 5 min. After 5 min, sometimes even less, the yeelight doesn't change the colour and stays white for ex. If i restart the movie, it work again. But, again, only for 5 min.
Any solution ?
(2017-10-28, 00:15)Saraz1 Wrote: [ -> ]First, thanks for the addon, it's amazing to see someone willing to create an addon for something that i paid 5€ lol.
I use the addons with Librelec on a raspberry pi 3. I want to use the addon only to have some kind of ambilight in the house. It works. Every time i start a movie or a tv show, the light change based on what is the screen. Perfect. The only problem i got it's the fact that it's working for less than 5 min. After 5 min, sometimes even less, the yeelight doesn't change the colour and stays white for ex. If i restart the movie, it work again. But, again, only for 5 min.
Any solution ?
Now this is really strange... please turn on debugging an post the log.
v3.65 in TEST repo
- Fixed a bug with autodiscover of bulbs wasn't able to write settings
- Fixed bug with various options not working correctly with Ambi turned on
hopefully this finally fixes bugs with normal light operation when Ambi is active. Please test and let me know.
I can't make schedule to work for ambi. It starts the light irrespective of what settings I have either automatic or manual.
I have set it to start from 19:30 to 05:00. I have android amlogic s912 with light strip. I have disabled hardware acceleration as well.
Any thing I am missing
(2017-10-28, 23:50)ace310 Wrote: [ -> ]I can't make schedule to work for ambi. It starts the light irrespective of what settings I have either automatic or manual.
I have set it to start from 19:30 to 05:00. I have android amlogic s912 with light strip. I have disabled hardware acceleration as well.
Any thing I am missing
Hardware acceleration has nothing to do with this. Please post debug log.
(2017-10-29, 01:13)ace310 Wrote: [ -> ]Here is the log https://pastebin.com/ZkRb5Vch.
Thanx for the log, but are you sure it is the whole log? I don't see any configuration data which should be there on YeeMee start?
I.e. this is my log:
Code:
09:51:53.784 T:7708 DEBUG: YEEMEE >> STARTED VERSION 3.65 on Kodi 17.5
09:51:54.124 T:7708 DEBUG: YEEMEE >> GOT CURRENT LAT-LON: 50.1333, 14.4167
09:51:54.406 T:7708 DEBUG: YEEMEE >> GOT TIMEZONE OFFSET: 2:00:00
09:51:54.742 T:7708 DEBUG: YEEMEE >> GOT CURRENT SUNRISE: 07:48
09:51:54.742 T:7708 DEBUG: YEEMEE >> GOT CURRENT SUNSET: 17:43
09:51:54.742 T:7708 DEBUG: YEEMEE >> GOT CIVIL TW: 18:17
09:51:54.742 T:7708 DEBUG: YEEMEE >> GOT NAUTIC TW: 18:55
09:51:54.965 T:7708 DEBUG: YEEMEE >> YEMME - AMBI PRIORITY >> 0
09:51:54.965 T:7708 DEBUG: YEEMEE >> LOWER BRIGHTNESS ON AMBI PAUSE >> 0
09:51:54.965 T:7708 DEBUG: YEEMEE >> AMBI SMOOTHEN (MS) >> 0
09:51:54.965 T:7708 DEBUG: YEEMEE >> REPORT ERRORS >> False
09:51:54.965 T:7708 DEBUG: YEEMEE >> NUMBER OF BULBS >> 5
09:51:54.965 T:7708 DEBUG: YEEMEE >> ON AT START >> 0
09:51:54.965 T:7708 DEBUG: YEEMEE >> DISABLE FOR SHORT FILMS >>FALSE<<
09:51:54.965 T:7708 DEBUG: YEEMEE >> ACTIVATION TIME >> 17:43:00 - 07:48:00
09:51:54.965 T:7708 DEBUG: YEEMEE >> MAX BRIGHT DAY >> 100
09:51:54.965 T:7708 DEBUG: YEEMEE >> MAX BRIGHT CIVIL TW >> 100
09:51:54.965 T:7708 DEBUG: YEEMEE >> MAX BRIGHT NAUTIC TW >> 100
09:51:54.965 T:7708 DEBUG: YEEMEE >> MAX BRIGTH NIGHT >> 100
09:51:54.966 T:7708 DEBUG: YEEMEE >> INIT BULB NUM: 1, IP ADDR: 192.168.1.210, MODEL: stripe
09:51:54.966 T:7708 DEBUG: YEEMEE >> INIT BULB NUM: 2, IP ADDR: 192.168.1.231, MODEL: mono
09:51:54.966 T:7708 DEBUG: YEEMEE >> INIT BULB NUM: 3, IP ADDR: 192.168.1.221, MODEL: color
09:51:54.966 T:7708 DEBUG: YEEMEE >> INIT BULB NUM: 4, IP ADDR: 192.168.1.220, MODEL: color
09:51:54.967 T:7708 DEBUG: YEEMEE >> INIT BULB NUM: 5, IP ADDR: 192.168.1.230, MODEL: mono
09:51:54.967 T:7708 DEBUG: YEEMEE >> NUMBER OF ACTIVE BULBS >> 5
09:51:54.967 T:7708 DEBUG: YEEMEE >> Number Act Int Color Eff Duration
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 0 PLAY : >> 1 20 #BA2B2B 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 0 STOP : >> 2 100 #FFFFFF 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 0 PAUSE: >> 2 50 #FF0000 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 0 AMBI: >> 0 BIAS: 0
09:51:54.967 T:7708 DEBUG: YEEMEE >> Number Act Int Color Eff Duration
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 1 PLAY : >> 1 20 #BA2B2B 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 1 STOP : >> 2 100 #BA2B2B 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 1 PAUSE: >> 2 50 #BA2B2B 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 1 AMBI: >> 0 BIAS: 0
09:51:54.967 T:7708 DEBUG: YEEMEE >> Number Act Int Color Eff Duration
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 2 PLAY : >> 1 20 #BA2B2B 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 2 STOP : >> 2 100 #FFFFFF 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 2 PAUSE: >> 2 50 #FF0000 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 2 AMBI: >> 7 BIAS: 0
09:51:54.967 T:7708 DEBUG: YEEMEE >> Number Act Int Color Eff Duration
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 3 PLAY : >> 1 20 #BA2B2B 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 3 STOP : >> 2 100 #FFFFFF 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 3 PAUSE: >> 2 50 #FF0000 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 3 AMBI: >> 4 BIAS: 0
09:51:54.967 T:7708 DEBUG: YEEMEE >> Number Act Int Color Eff Duration
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 4 PLAY : >> 0 20 #BA2B2B 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 4 STOP : >> 0 20 #BA2B2B 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 4 PAUSE: >> 0 20 #BA2B2B 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 4 AMBI: >> 0 BIAS: 0
09:51:54.967 T:7708 DEBUG: YEEMEE >> NUMBER OF AMBI BULBS >> 2
09:51:54.967 T:7708 DEBUG: YEEMEE >> NUMBER OF CONTROLLERS >> 0
and in your log it is immediately playing:
Code:
12:07:13.281 T:500953592912 DEBUG: YEEMEE >> PLAYBACK >>PLAYING<<
12:07:13.290 T:500860204112 DEBUG: YEEMEE >> LUMIFACTOR IS 100
12:07:13.646 T:500953592912 DEBUG: YEEMEE >> MESSAGE TO 192.168.1.67: {u'params': [u'power', u'music_on'], u'id': 1, u'method': u'get_prop'}
12:07:13.647 T:501111444560 DEBUG: YEEMEE >> SERVER >> 192.168.1.65 WAITING FOR CONNECTION...
12:07:13.688 T:500953592912 DEBUG: YEEMEE >> RESPONSE FROM 192.168.1.67: off, 0
12:07:13.689 T:500953592912 DEBUG: YEEMEE >> MESSAGE TO 192.168.1.67: {u'params': [u'on', u'smooth', 200], u'id': 1, u'method': u'set_power'}
12:07:13.721 T:500953592912 DEBUG: YEEMEE >> RESPONSE FROM 192.168.1.67: ok,
12:07:13.823 T:500953592912 DEBUG: YEEMEE >> MESSAGE TO 192.168.1.67: {u'params': [1, u'192.168.1.65', 55440], u'id': 1, u'method': u'set_music'}
12:07:13.854 T:500953592912 DEBUG: YEEMEE >> RESPONSE FROM 192.168.1.67: ok,
12:07:13.875 T:501111444560 DEBUG: YEEMEE >> SERVER >> CONNECTION FROM: ('192.168.1.67', 49182) ACCEPTED
12:07:13.877 T:501066257488 DEBUG: YEEMEE >> SERVER >> CONNECTION OPEN FOR ('192.168.1.67', 49182)
12:07:13.877 T:501066257488 DEBUG: YEEMEE >> SERVER >> LUMIFACTOR IS 100
12:07:26.789 T:500953592912 DEBUG: YEEMEE >> PLAYBACK >>STOPPED<<
12:07:26.791 T:501066257488 DEBUG: YEEMEE >> SERVER >> CONNECTION CLOSED FOR 192.168.1.67
12:07:26.800 T:501111444560 DEBUG: YEEMEE >> SERVER >> CONNECTION FROM: ('192.168.1.65', 53983) ACCEPTED
12:07:26.803 T:501107770448 DEBUG: YEEMEE >> SERVER >> NO BULB, CONNECTION FROM ('192.168.1.65', 53983), TERMINATING HANDLER
12:07:26.804 T:501111444560 DEBUG: YEEMEE >> SERVER >> END
12:07:26.805 T:500953592912 DEBUG: YEEMEE >> SERVER >> STOP SERVER EXCEPTION (THIS IS EXPECTED AND OK): [Errno 9] Bad file descriptor
12:07:26.994 T:501066257488 DEBUG: YEEMEE >> MESSAGE TO 192.168.1.67: {u'params': [u'power', u'music_on'], u'id': 1, u'method': u'get_prop'}
12:07:27.007 T:501066257488 DEBUG: YEEMEE >> RESPONSE FROM 192.168.1.67: on, 0
12:07:27.108 T:501066257488 DEBUG: YEEMEE >> MESSAGE TO 192.168.1.67: {u'params': [u'off', u'smooth', 500], u'id': 1, u'method': u'set_power'}
12:07:27.116 T:501066257488 DEBUG: YEEMEE >> RESPONSE FROM 192.168.1.67: ok,
hey DaLanik, do you think that the new bedside lamp II will work with your addon?
(2017-10-29, 11:56)TeDeV Wrote: [ -> ]hey DaLanik, do you think that the new bedside lamp II will work with your addon?
No reason it shouldn't. Maybe it won't recognize it's name etc but when someone gets it and reports here if it works and what is the problem, it should be easy to fix. The only thing is getting it's name.
Addon works fine the last weeks, but now it doesnt work anymore.
Maybe the reason is an automatic update?
Testing works fine (on/off). But on playing video it just starts the lamps with the last colour and nothing more happend. When i stop the video they are not going off and ambilight doesnt work too.
And advice? I didnt change anything in the options or something like that.
Just stay put, I'll figure it out. I added a lot of functionality and there's a glitch in logic somewhere, it's too complex and I have to make it simpler
(2017-10-29, 10:51)DaLanik Wrote: [ -> ] (2017-10-29, 01:13)ace310 Wrote: [ -> ]Here is the log https://pastebin.com/ZkRb5Vch.
Thanx for the log, but are you sure it is the whole log? I don't see any configuration data which should be there on YeeMee start?
I.e. this is my log:
Code:
09:51:53.784 T:7708 DEBUG: YEEMEE >> STARTED VERSION 3.65 on Kodi 17.5
09:51:54.124 T:7708 DEBUG: YEEMEE >> GOT CURRENT LAT-LON: 50.1333, 14.4167
09:51:54.406 T:7708 DEBUG: YEEMEE >> GOT TIMEZONE OFFSET: 2:00:00
09:51:54.742 T:7708 DEBUG: YEEMEE >> GOT CURRENT SUNRISE: 07:48
09:51:54.742 T:7708 DEBUG: YEEMEE >> GOT CURRENT SUNSET: 17:43
09:51:54.742 T:7708 DEBUG: YEEMEE >> GOT CIVIL TW: 18:17
09:51:54.742 T:7708 DEBUG: YEEMEE >> GOT NAUTIC TW: 18:55
09:51:54.965 T:7708 DEBUG: YEEMEE >> YEMME - AMBI PRIORITY >> 0
09:51:54.965 T:7708 DEBUG: YEEMEE >> LOWER BRIGHTNESS ON AMBI PAUSE >> 0
09:51:54.965 T:7708 DEBUG: YEEMEE >> AMBI SMOOTHEN (MS) >> 0
09:51:54.965 T:7708 DEBUG: YEEMEE >> REPORT ERRORS >> False
09:51:54.965 T:7708 DEBUG: YEEMEE >> NUMBER OF BULBS >> 5
09:51:54.965 T:7708 DEBUG: YEEMEE >> ON AT START >> 0
09:51:54.965 T:7708 DEBUG: YEEMEE >> DISABLE FOR SHORT FILMS >>FALSE<<
09:51:54.965 T:7708 DEBUG: YEEMEE >> ACTIVATION TIME >> 17:43:00 - 07:48:00
09:51:54.965 T:7708 DEBUG: YEEMEE >> MAX BRIGHT DAY >> 100
09:51:54.965 T:7708 DEBUG: YEEMEE >> MAX BRIGHT CIVIL TW >> 100
09:51:54.965 T:7708 DEBUG: YEEMEE >> MAX BRIGHT NAUTIC TW >> 100
09:51:54.965 T:7708 DEBUG: YEEMEE >> MAX BRIGTH NIGHT >> 100
09:51:54.966 T:7708 DEBUG: YEEMEE >> INIT BULB NUM: 1, IP ADDR: 192.168.1.210, MODEL: stripe
09:51:54.966 T:7708 DEBUG: YEEMEE >> INIT BULB NUM: 2, IP ADDR: 192.168.1.231, MODEL: mono
09:51:54.966 T:7708 DEBUG: YEEMEE >> INIT BULB NUM: 3, IP ADDR: 192.168.1.221, MODEL: color
09:51:54.966 T:7708 DEBUG: YEEMEE >> INIT BULB NUM: 4, IP ADDR: 192.168.1.220, MODEL: color
09:51:54.967 T:7708 DEBUG: YEEMEE >> INIT BULB NUM: 5, IP ADDR: 192.168.1.230, MODEL: mono
09:51:54.967 T:7708 DEBUG: YEEMEE >> NUMBER OF ACTIVE BULBS >> 5
09:51:54.967 T:7708 DEBUG: YEEMEE >> Number Act Int Color Eff Duration
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 0 PLAY : >> 1 20 #BA2B2B 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 0 STOP : >> 2 100 #FFFFFF 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 0 PAUSE: >> 2 50 #FF0000 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 0 AMBI: >> 0 BIAS: 0
09:51:54.967 T:7708 DEBUG: YEEMEE >> Number Act Int Color Eff Duration
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 1 PLAY : >> 1 20 #BA2B2B 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 1 STOP : >> 2 100 #BA2B2B 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 1 PAUSE: >> 2 50 #BA2B2B 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 1 AMBI: >> 0 BIAS: 0
09:51:54.967 T:7708 DEBUG: YEEMEE >> Number Act Int Color Eff Duration
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 2 PLAY : >> 1 20 #BA2B2B 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 2 STOP : >> 2 100 #FFFFFF 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 2 PAUSE: >> 2 50 #FF0000 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 2 AMBI: >> 7 BIAS: 0
09:51:54.967 T:7708 DEBUG: YEEMEE >> Number Act Int Color Eff Duration
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 3 PLAY : >> 1 20 #BA2B2B 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 3 STOP : >> 2 100 #FFFFFF 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 3 PAUSE: >> 2 50 #FF0000 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 3 AMBI: >> 4 BIAS: 0
09:51:54.967 T:7708 DEBUG: YEEMEE >> Number Act Int Color Eff Duration
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 4 PLAY : >> 0 20 #BA2B2B 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 4 STOP : >> 0 20 #BA2B2B 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 4 PAUSE: >> 0 20 #BA2B2B 0 500
09:51:54.967 T:7708 DEBUG: YEEMEE >> BULB 4 AMBI: >> 0 BIAS: 0
09:51:54.967 T:7708 DEBUG: YEEMEE >> NUMBER OF AMBI BULBS >> 2
09:51:54.967 T:7708 DEBUG: YEEMEE >> NUMBER OF CONTROLLERS >> 0
and in your log it is immediately playing:
Code:
12:07:13.281 T:500953592912 DEBUG: YEEMEE >> PLAYBACK >>PLAYING<<
12:07:13.290 T:500860204112 DEBUG: YEEMEE >> LUMIFACTOR IS 100
12:07:13.646 T:500953592912 DEBUG: YEEMEE >> MESSAGE TO 192.168.1.67: {u'params': [u'power', u'music_on'], u'id': 1, u'method': u'get_prop'}
12:07:13.647 T:501111444560 DEBUG: YEEMEE >> SERVER >> 192.168.1.65 WAITING FOR CONNECTION...
12:07:13.688 T:500953592912 DEBUG: YEEMEE >> RESPONSE FROM 192.168.1.67: off, 0
12:07:13.689 T:500953592912 DEBUG: YEEMEE >> MESSAGE TO 192.168.1.67: {u'params': [u'on', u'smooth', 200], u'id': 1, u'method': u'set_power'}
12:07:13.721 T:500953592912 DEBUG: YEEMEE >> RESPONSE FROM 192.168.1.67: ok,
12:07:13.823 T:500953592912 DEBUG: YEEMEE >> MESSAGE TO 192.168.1.67: {u'params': [1, u'192.168.1.65', 55440], u'id': 1, u'method': u'set_music'}
12:07:13.854 T:500953592912 DEBUG: YEEMEE >> RESPONSE FROM 192.168.1.67: ok,
12:07:13.875 T:501111444560 DEBUG: YEEMEE >> SERVER >> CONNECTION FROM: ('192.168.1.67', 49182) ACCEPTED
12:07:13.877 T:501066257488 DEBUG: YEEMEE >> SERVER >> CONNECTION OPEN FOR ('192.168.1.67', 49182)
12:07:13.877 T:501066257488 DEBUG: YEEMEE >> SERVER >> LUMIFACTOR IS 100
12:07:26.789 T:500953592912 DEBUG: YEEMEE >> PLAYBACK >>STOPPED<<
12:07:26.791 T:501066257488 DEBUG: YEEMEE >> SERVER >> CONNECTION CLOSED FOR 192.168.1.67
12:07:26.800 T:501111444560 DEBUG: YEEMEE >> SERVER >> CONNECTION FROM: ('192.168.1.65', 53983) ACCEPTED
12:07:26.803 T:501107770448 DEBUG: YEEMEE >> SERVER >> NO BULB, CONNECTION FROM ('192.168.1.65', 53983), TERMINATING HANDLER
12:07:26.804 T:501111444560 DEBUG: YEEMEE >> SERVER >> END
12:07:26.805 T:500953592912 DEBUG: YEEMEE >> SERVER >> STOP SERVER EXCEPTION (THIS IS EXPECTED AND OK): [Errno 9] Bad file descriptor
12:07:26.994 T:501066257488 DEBUG: YEEMEE >> MESSAGE TO 192.168.1.67: {u'params': [u'power', u'music_on'], u'id': 1, u'method': u'get_prop'}
12:07:27.007 T:501066257488 DEBUG: YEEMEE >> RESPONSE FROM 192.168.1.67: on, 0
12:07:27.108 T:501066257488 DEBUG: YEEMEE >> MESSAGE TO 192.168.1.67: {u'params': [u'off', u'smooth', 500], u'id': 1, u'method': u'set_power'}
12:07:27.116 T:501066257488 DEBUG: YEEMEE >> RESPONSE FROM 192.168.1.67: ok,
Here is another log.
https://pastebin.com/F9UNEA3W. Hopefully this is what you are looking for.
Edit: Here is the filtered log related to YeeMee.
https://pastebin.com/JVduSDMW
I am completely rewriting the logic for yeemee service and ambi service, hold on, I'll have something soon...
(2017-10-30, 09:47)DaLanik Wrote: [ -> ]I am completely rewriting the logic for yeemee service and ambi service, hold on, I'll have something soon...
Looking forward to it.