Polyglot LIFX NodeSever

skunkiechris · February 8, 2017

Oh... that makes me remember something I saw in the code. I think in the new stuff they let me do staging then activate. I'll have to test that, but I only have the 1 bulb at the moment. I never got around to buying the strip, so I'll have to order that. I'll try to do that this weekend.

I know what you're referring to...I saw it and thought (hoped?) the same thing. From what I read, I think it only applies to devices with multiple zones (at this point just the LIFX Z), where you can stage and apply the zone colors. But hopefully I'm wrong!

einstein.42 · February 8, 2017

Ahh, that would make sense. I'll check either way.

einstein.42 · February 16, 2017

Ok guys. I got a multizone Z light. Release 1.0.3.

You need to update your profile.zip as well. So re-upload it to ISY and reboot.

git checkout multizone

In the program view, you can 'set hsbkdz' which lets you set any zone you like (but does not apply). Make sure you send an apply for the changes to take effect.

Zones are 1 - 80 (LiFX Z are 8 zones per meter, maximum 10 meters. If you send a command to zone '0' it will change the whole unit and does not need an apply.

Any changes on the 'node' non program view, changes zone 0 therefore the whole bulb. I wrote some fixes into lifxlan and merged them in last summer, unfortunately one of my exception changes has been reverted, which was causing the instabilities.

This release includes the lifxlan module in it so you do not need to have the lifxlan module installed as it will use the in-built version.

-E

kzboray · February 19, 2017

Einstein,

Absolutely brilliant! I tested this on my "strip" and it worked like a champ. I want to thank you for doing all the work, as well as spending personal $$$ to make this happen. Truly a remarkable effort. Thank you again.

einstein.42 · February 19, 2017

Great news. Glad for the feedback.

kzboray · February 19, 2017

One thing I have noticed in playing with this is that I can no longer change bulb attributes from the bulb itself. i.e. <Set Hue>, <Set Saturation>, etc. These values now seem to be display only. Clicking the commit button to the left of the fields doesn't change the actual value. If this is because of the changes, would it be possible to add a field to the <Set Color To> drop down something like <User Defined>? I've had the LifX NS crash on me once in the last few hours unfortunately I didn't catch the error. I'll keep an eye out and post the log if it happens again.

Einstein, Thank you once more.

einstein.42 · February 19, 2017

In the bulb view itself the up and down arrows don't seem to work? Or inputting a value? Yes please let me know if it crashes. I tested it for hours and didn't have any crashes.

kzboray · February 20, 2017

Inputting a value or changing the value via the up/down arrows and then clicking the commit button to the left of the field does not change the value, It reverts to the value of <Set Color To>.

If it should crash again I'll try to catch the error and post the log file.

einstein.42 · February 20, 2017

It should take effect as soon as you change the value and switch off the field. You shouldn't have to hit the buttons to the left. The buttons at the bottom work though?

kzboray · February 20, 2017

lol ask and thee shall receive.

INFO     [02-19-2017 23:53:22] polyglot.element_manager.isy: ISY: [1] ( 0.04) 200 OK: http://10.0.0.50:8880/rest/nodes/n001_nestcontrol
INFO     [02-19-2017 23:53:22] polyglot.nodeserver_manager: Nest: **INFO: probe: fa=n001_nestcontrol pfa=n001_nestcontrol id=nestcontrol fl=128 en=True nm="Nest Control"
INFO     [02-19-2017 23:53:29] polyglot.element_manager.isy: ISY: [1] ( 0.04) 200 OK: http://10.0.0.50:8880/rest/nodes/n002_lifxcontrol
INFO     [02-19-2017 23:53:29] polyglot.nodeserver_manager: LifX: **INFO: probe: fa=n002_lifxcontrol pfa=n002_lifxcontrol id=lifxcontrol fl=128 en=True nm="LIFX Control"
INFO     [02-19-2017 23:53:29] polyglot.element_manager.isy: ISY: [1] ( 0.03) 200 OK: http://10.0.0.50:8880/rest/nodes/n001_aa01ac14160bat
INFO     [02-19-2017 23:53:29] polyglot.nodeserver_manager: Nest: **INFO: probe: fa=n001_aa01ac14160bat pfa=n001_nestcontrol id=nestthermostat fl=0 en=True nm="Street Address. downsta"
INFO     [02-19-2017 23:53:36] polyglot.element_manager.isy: ISY: [1] ( 0.03) 200 OK: http://10.0.0.50:8880/rest/nodes/n001_aa01ac14160agp
INFO     [02-19-2017 23:53:36] polyglot.nodeserver_manager: Nest: **INFO: probe: fa=n001_aa01ac14160agp pfa=n001_nestcontrol id=nestthermostat fl=0 en=True nm="Street Address. upstair"
INFO     [02-19-2017 23:53:38] polyglot.element_manager.isy: ISY: [1] ( 0.03) 200 OK: http://10.0.0.50:8880/rest/nodes/n002_d073d5149bcb
ERROR    [02-19-2017 23:53:38] polyglot.element_manager.isy: ISY: [1] ( 0.01) 404 ERR: http://10.0.0.50:8880/rest/nodes/n002_
INFO     [02-19-2017 23:53:38] polyglot.nodeserver_manager: LifX: **INFO: probe: fa=n002_d073d5149bcb pfa=n002_lifxcontrol id=lifxmultizone fl=0 en=True nm="LIFX LIFX Bulb 149bcb"
WARNING  [02-19-2017 23:53:38] polyglot.nodeserver_manager: LifX: **WARNING: probe: status code: 404
INFO     [02-19-2017 23:54:39] polyglot.element_manager.isy: ISY: [1] ( 0.03) 200 OK: http://10.0.0.50:8880/rest/ns/2/nodes/n002_d073d5149bcb/report/status/GV6/80.7/20
INFO     [02-19-2017 23:55:52] tornado.access: 304 GET /api/servers/active (10.0.0.6) 2004.87ms
INFO     [02-19-2017 23:55:53] tornado.access: 304 GET /api/server/BAdYn (10.0.0.6) 1004.82ms
INFO     [02-19-2017 23:56:30] polyglot.element_manager.isy: ISY: [1] ( 0.04) 200 OK: http://10.0.0.50:8880/rest/ns/1/nodes/n001_aa01ac14160bat/report/status/CLIHCS/0/66
INFO     [02-19-2017 23:57:17] tornado.access: 200 GET /ns/ZEdpb/nodes/n001_aa01ac14160agp/cmd/QUERY (10.0.0.50) 2.66ms
INFO     [02-19-2017 23:57:18] polyglot.element_manager.isy: ISY: [1] ( 0.02) 200 OK: http://10.0.0.50:8880/rest/ns/1/nodes/n001_aa01ac14160agp/report/status/CLISPC/70/14
INFO     [02-19-2017 23:57:18] polyglot.element_manager.isy: ISY: [1] ( 0.01) 200 OK: http://10.0.0.50:8880/rest/ns/1/nodes/n001_aa01ac14160agp/report/status/CLIFS/0/99
INFO     [02-19-2017 23:57:18] polyglot.element_manager.isy: ISY: [1] ( 0.02) 200 OK: http://10.0.0.50:8880/rest/ns/1/nodes/n001_aa01ac14160agp/report/status/ST/71/14
INFO     [02-19-2017 23:57:18] polyglot.element_manager.isy: ISY: [1] ( 0.05) 200 OK: http://10.0.0.50:8880/rest/ns/1/nodes/n001_aa01ac14160agp/report/status/CLIHCS/0/66
INFO     [02-19-2017 23:57:18] polyglot.element_manager.isy: ISY: [1] ( 0.02) 200 OK: http://10.0.0.50:8880/rest/ns/1/nodes/n001_aa01ac14160agp/report/status/CLISPH/70/14
INFO     [02-19-2017 23:57:18] polyglot.element_manager.isy: ISY: [1] ( 0.01) 200 OK: http://10.0.0.50:8880/rest/ns/1/nodes/n001_aa01ac14160agp/report/status/GV2/56/14
INFO     [02-19-2017 23:57:18] polyglot.element_manager.isy: ISY: [1] ( 0.01) 200 OK: http://10.0.0.50:8880/rest/ns/1/nodes/n001_aa01ac14160agp/report/status/GV3/0/14
INFO     [02-19-2017 23:57:18] polyglot.element_manager.isy: ISY: [1] ( 0.01) 200 OK: http://10.0.0.50:8880/rest/ns/1/nodes/n001_aa01ac14160agp/report/status/CLIHUM/47/51
INFO     [02-19-2017 23:57:18] polyglot.element_manager.isy: ISY: [1] ( 0.02) 200 OK: http://10.0.0.50:8880/rest/ns/1/nodes/n001_aa01ac14160agp/report/status/GV1/0/14
INFO     [02-19-2017 23:57:18] polyglot.element_manager.isy: ISY: [1] ( 0.03) 200 OK: http://10.0.0.50:8880/rest/ns/1/nodes/n001_aa01ac14160agp/report/status/CLIMD/1/67
INFO     [02-19-2017 23:57:18] polyglot.element_manager.isy: ISY: [1] ( 0.01) 200 OK: http://10.0.0.50:8880/rest/ns/1/nodes/n001_aa01ac14160agp/report/status/GV4/1/2
INFO     [02-19-2017 23:57:29] tornado.access: 304 GET /api/server/BAdYn (10.0.0.6) 1003.30ms
INFO     [02-19-2017 23:57:31] tornado.access: 304 GET /api/servers/active (10.0.0.6) 2004.32ms
INFO     [02-19-2017 23:57:32] tornado.access: 304 GET /api/server/BAdYn (10.0.0.6) 1004.79ms
INFO     [02-19-2017 23:57:34] tornado.access: 304 GET /api/servers/active (10.0.0.6) 2003.81ms
INFO     [02-19-2017 23:59:38] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SETK/3962/26 (10.0.0.50) 1.46ms
INFO     [02-19-2017 23:59:39] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SETK/3500/26 (10.0.0.50) 1.46ms
INFO     [02-19-2017 23:59:46] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SETK/3512/26 (10.0.0.50) 1.46ms
INFO     [02-19-2017 23:59:49] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/APPLY (10.0.0.50) 1.45ms
INFO     [02-19-2017 23:59:59] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SETK/5500/26 (10.0.0.50) 1.49ms
INFO     [02-20-2017 00:00:05] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/APPLY (10.0.0.50) 1.77ms
INFO     [02-20-2017 00:00:09] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/APPLY (10.0.0.50) 1.63ms
INFO     [02-20-2017 00:00:15] tornado.access: 304 GET /api/servers/active (10.0.0.6) 1002.85ms
INFO     [02-20-2017 00:00:16] tornado.access: 304 GET /api/server/BAdYn (10.0.0.6) 1003.79ms
INFO     [02-20-2017 00:00:18] tornado.access: 304 GET /api/servers/active (10.0.0.6) 2003.71ms
INFO     [02-20-2017 00:00:18] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SETK/5500/26 (10.0.0.50) 1.85ms
INFO     [02-20-2017 00:00:20] tornado.access: 304 GET /api/servers/active (10.0.0.6) 2004.03ms
INFO     [02-20-2017 00:00:21] tornado.access: 304 GET /api/server/BAdYn (10.0.0.6) 1002.97ms
INFO     [02-20-2017 00:00:22] tornado.access: 304 GET /api/servers/active (10.0.0.6) 1002.72ms
INFO     [02-20-2017 00:00:23] tornado.access: 304 GET /api/server/BAdYn (10.0.0.6) 1003.22ms
INFO     [02-20-2017 00:00:25] tornado.access: 304 GET /api/servers/active (10.0.0.6) 2003.64ms
INFO     [02-20-2017 00:00:26] tornado.access: 304 GET /api/server/BAdYn (10.0.0.6) 1003.11ms
INFO     [02-20-2017 00:00:27] tornado.access: 304 GET /api/server/BAdYn (10.0.0.6) 1003.30ms
WARNING  [02-20-2017 00:00:47] polyglot.nodeserver_manager: Node Server LifX: time since last pong: 71.05
ERROR    [02-20-2017 00:00:47] polyglot.nodeserver_manager: Node Server LifX has stopped responding.
INFO     [02-20-2017 00:01:04] polyglot.element_manager.isy: ISY: [1] ( 0.02) 200 OK: http://10.0.0.50:8880/rest/ns/1/nodes/n001_aa01ac14160agp/report/status/ST/72/14

Second line from the bottom is the crash report. I posted a few lines back hoping something jumps out at you.

ISY:

5.0.8

Raspberry Pi3

PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian

kzboray · February 20, 2017

Yes the buttons at the bottom work great. If I setup a program and use the HSBKDZ selection I can change any field without a problem. It's just off the main bulb screen that I can't seem to figure out how to change the values.

einstein.42 · February 20, 2017

Interesting. I don't see any errors, there, just the nodeserver stopping responding. Interesting was there anything in the LiFX.log...

kzboray · February 20, 2017

LifX.Log

2017-02-20 00:09:21,033 INFO     LifX LIFX Node Server Interface version 0.1.6 created. Initiating setup.
2017-02-20 00:09:21,033 INFO     LifX Config File param: config.yaml
2017-02-20 00:09:22,483 INFO     LifX 1 bulbs found. Checking status and adding to ISY
2017-02-20 00:09:23,505 INFO     LifX Adding new MultiZone Bulb: LIFX LIFX Bulb 149bcb(d073d5149bcb)
2017-02-20 00:09:27,619 INFO     LifX Adding new LIFX Group:
2017-02-20 00:09:27,621 INFO     LifX Setup completed. Running Server.

Here is LifX.log.2017-02-19 But unfortunately the time stamps don't line up. This is the last few lines of this log file and it dosen't show 00:00:47.

$
2017-02-19 23:39:07,021 INFO     LifX LIFX Node Server Interface version 0.1.6 created. Initiating setup.
2017-02-19 23:39:07,021 INFO     LifX Config File param: config.yaml
2017-02-19 23:39:08,350 INFO     LifX 1 bulbs found. Checking status and adding to ISY
2017-02-19 23:39:09,167 INFO     LifX Adding new MultiZone Bulb: LIFX LIFX Bulb 149bcb(d073d5149bcb)
2017-02-19 23:39:13,283 INFO     LifX Adding new LIFX Group:
2017-02-19 23:39:13,285 INFO     LifX Setup completed. Running Server.
2017-02-19 23:39:28,862 INFO     LifX Received manual change, updating the mz bulb to: [65535, (58275, 0, 0, 5500), (58275, 0, 0, 5500), (58275, 0, 0, 5500), (29814, 0, 0, 5500), (5525, 0, 0, 5500), (50486, 0, 0, 5500), (43634, 0, 0, 55$
2017-02-19 23:39:57,052 INFO     LifX Received manual change, updating the mz bulb to: [65535, (58275, 0, 65535, 5500), (58275, 0, 65535, 5500), (58275, 0, 65535, 5500), (29814, 0, 65535, 5500), (5525, 0, 65535, 5500), (50486, 0, 65535,$
2017-02-19 23:40:20,056 INFO     LifX Received manual change, updating the mz bulb to: [65535, (58275, 0, 65535, 5500), (58275, 0, 65535, 5500), (58275, 0, 65535, 5500), (29814, 0, 65535, 5500), (5525, 0, 65535, 5500), (50486, 0, 65535,$
2017-02-19 23:40:30,301 INFO     LifX Received SetColor command from ISY. Changing color to: CYAN
2017-02-19 23:40:38,513 INFO     LifX Received manual change, updating the mz bulb to: [65535, (29814, 65535, 65535, 3500), (29814, 65535, 65535, 3500), (29814, 65535, 65535, 3500), (29814, 65535, 65535, 3500), (29814, 65535, 65535, 350$
2017-02-19 23:41:45,760 INFO     LifX Received manual change, updating the mz bulb to: [0, (29814, 65535, 65535, 3500), (29814, 65535, 65535, 3500), (29814, 65535, 65535, 3500), (29814, 65535, 65535, 3500), (29814, 65535, 65535, 3500), $
2017-02-19 23:42:10,953 INFO     LifX Received SetColor command from ISY. Changing color to: YELLOW
2017-02-19 23:42:12,880 INFO     LifX Received manual change, updating the mz bulb to: [(7615, 65535, 65535, 3500), (7615, 65535, 65535, 3500), (7615, 65535, 65535, 3500), (7615, 65535, 65535, 3500), (7615, 65535, 65535, 3500), (7615, 6$
2017-02-19 23:42:20,425 INFO     LifX Received manual change, updating the mz bulb to: [(7615, 65535, 65535, 3500), (7615, 65535, 65535, 3500), (7615, 65535, 65535, 3500), (7615, 65535, 65535, 3500), (7615, 65535, 65535, 3500), (7615, 6$
2017-02-19 23:42:47,168 INFO     LifX LIFX Node Server Interface version 0.1.6 created. Initiating setup.
2017-02-19 23:42:47,168 INFO     LifX Config File param: config.yaml
2017-02-19 23:42:48,510 INFO     LifX 1 bulbs found. Checking status and adding to ISY

einstein.42 · February 20, 2017

How frustrating... Ok, let me see what I can find.

einstein.42 · February 20, 2017

Ok I fixed the manual set, the bulb display might take a few seconds more to update as I tried to simplify some of the constant polling, but I let it run for an hour and it seemed stable. Let me know if you get any more crashes...

On the multizone branch:

git pull

kzboray · February 20, 2017

Einstein,

First let me say that just because I post something I do not have any expectation of urgency. I understand you have a life outside of this forum and while you have been extremely responsive there is zero expectation of immediacy. I appreciate your development and continued work on the many node servers you have created and if you ever become frustrated with my bangging away on them, don't feel that I expect anything at all.

OK onto version 0.1.3 multizone

I have created a program in ISY that is supposed to display a rainbow effect across the strip.

Here is the log of what this looks like running. Its just a series of <Set...Change HSBKDZ> followed by an <Apply> at the end.

INFO     [02-20-2017 21:09:21] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SET_HSBKDZ?H.uom56=58000&S.uom56=65535&B.uom56=65535&K.uom26=3500&D.uom42=0&Z.uom56=16 (10.0.0.50) 3.31ms
INFO     [02-20-2017 21:09:21] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SET_HSBKDZ?H.uom56=53000&S.uom56=65535&B.uom56=65535&K.uom26=3500&D.uom42=0&Z.uom56=15 (10.0.0.50) 3.14ms
INFO     [02-20-2017 21:09:21] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SET_HSBKDZ?H.uom56=48000&S.uom56=65535&B.uom56=65535&K.uom26=3500&D.uom42=0&Z.uom56=14 (10.0.0.50) 3.30ms
INFO     [02-20-2017 21:09:21] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SET_HSBKDZ?H.uom56=43000&S.uom56=65535&B.uom56=65535&K.uom26=3500&D.uom42=0&Z.uom56=13 (10.0.0.50) 3.26ms
INFO     [02-20-2017 21:09:21] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SET_HSBKDZ?H.uom56=38000&S.uom56=65535&B.uom56=65535&K.uom26=3500&D.uom42=0&Z.uom56=12 (10.0.0.50) 3.41ms
INFO     [02-20-2017 21:09:21] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SET_HSBKDZ?H.uom56=33000&S.uom56=65535&B.uom56=65535&K.uom26=3500&D.uom42=0&Z.uom56=11 (10.0.0.50) 3.42ms
INFO     [02-20-2017 21:09:21] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SET_HSBKDZ?H.uom56=28000&S.uom56=65535&B.uom56=65535&K.uom26=3500&D.uom42=0&Z.uom56=10 (10.0.0.50) 3.17ms
INFO     [02-20-2017 21:09:21] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SET_HSBKDZ?H.uom56=23000&S.uom56=65535&B.uom56=65535&K.uom26=3500&D.uom42=0&Z.uom56=9 (10.0.0.50) 3.42ms
INFO     [02-20-2017 21:09:21] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SET_HSBKDZ?H.uom56=18000&S.uom56=65535&B.uom56=65535&K.uom26=3500&D.uom42=0&Z.uom56=8 (10.0.0.50) 1.83ms
INFO     [02-20-2017 21:09:21] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SET_HSBKDZ?H.uom56=13000&S.uom56=65535&B.uom56=65535&K.uom26=3500&D.uom42=0&Z.uom56=7 (10.0.0.50) 1.77ms
INFO     [02-20-2017 21:09:21] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SET_HSBKDZ?H.uom56=8000&S.uom56=65535&B.uom56=65535&K.uom26=3500&D.uom42=0&Z.uom56=6 (10.0.0.50) 1.96ms
INFO     [02-20-2017 21:09:21] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SET_HSBKDZ?H.uom56=5500&S.uom56=65535&B.uom56=65535&K.uom26=3500&D.uom42=0&Z.uom56=5 (10.0.0.50) 1.84ms
INFO     [02-20-2017 21:09:21] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SET_HSBKDZ?H.uom56=3000&S.uom56=65535&B.uom56=65535&K.uom26=3500&D.uom42=0&Z.uom56=4 (10.0.0.50) 1.84ms
INFO     [02-20-2017 21:09:21] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SET_HSBKDZ?H.uom56=0&S.uom56=0&B.uom56=0&K.uom26=0&D.uom42=0&Z.uom56=3 (10.0.0.50) 1.87ms
INFO     [02-20-2017 21:09:21] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SET_HSBKDZ?H.uom56=0&S.uom56=0&B.uom56=0&K.uom26=0&D.uom42=0&Z.uom56=2 (10.0.0.50) 1.83ms
INFO     [02-20-2017 21:09:21] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/SET_HSBKDZ?H.uom56=0&S.uom56=0&B.uom56=0&K.uom26=0&D.uom42=0&Z.uom56=1 (10.0.0.50) 1.82ms
INFO     [02-20-2017 21:09:21] tornado.access: 200 GET /ns/BAdYn/nodes/n002_d073d5149bcb/cmd/APPLY (10.0.0.50) 1.61ms

It takes just under 40ms to complete, but the catch is that the results don't get displayed on the actual strip for between ten to twentyfive seconds. Is there some way to speed this up?

I also created a simple zone zero <Set...Change HSBKDZ> for the color white. It's two lines.

<Set...Change HSBKDZ>

<Apply>

When I run this right after the first program to reset the strip back to all white only zone 16 changes to white. all the other zones remain set as they were.

This may or may not be related to another interesting effect. If you go back to the original program setting sixteen zones sequentially, but this time stick an <Apply> in between each <Set...Change HSBKDZ> starting with an all white strip, you will notice that each zone is set correctly, but the previous zone reverts to the original color. So if you set zone sixteen to pink and then set zone fifteen to purple, zone sixteen reverts back to white. This effect continues all the way to the end of the program. Each zone lighting to the correct color until the next zone change is executed at which time it reverts back to white.

Anyway I'm off to try 0.1.3 with the manual update fixes. Good bug hunting and thank you!

kzboray · February 20, 2017

Einstein I just found something really interesting!!!!

If I execute a program from ISY Admin it works as my previous post lists. It takes forever to execute, But if I run the same program from https://my.isy.io/udajax/udajax.htm?mode=corp via ISY portal the change to the strip is immediate. I still get the weirdness with only zone sixteen changing back to white with a zone zero command, but there is no delay in execution.

I also loaded up 0.1.3 with the manual update changes and they seem to work all be it slowly. On average it takes three to four seconds for the actual change to occur.

But it works! Thank you.

kzboray · February 21, 2017

Einstein,

I'm not sure if this is important or not, but I thought I would show it to you just in case. About every ten minutes I see the following LifX /rest error.

ERROR    [02-21-2017 04:08:15] polyglot.element_manager.isy: ISY: [1] ( 0.02) 404 ERR: http://10.0.0.50:8880/rest/nodes/n002_
WARNING  [02-21-2017 04:08:15] polyglot.nodeserver_manager: LifX: **WARNING: probe: status code: 404
INFO     [02-21-2017 04:08:28] polyglot.element_manager.isy: ISY: [1] ( 0.04) 200 OK: http://10.0.0.50:8880/rest/nodes/n001_nestcontrol
INFO     [02-21-2017 04:08:28] polyglot.nodeserver_manager: Nest: **INFO: probe: fa=n001_nestcontrol pfa=n001_nestcontrol id=nestcontrol fl=128 en=True nm="Nest Control"
INFO     [02-21-2017 04:09:02] polyglot.element_manager.isy: ISY: [1] ( 0.02) 200 OK: http://10.0.0.50:8880/rest/ns/2/nodes/n002_d073d5149bcb/report/status/GV6/3.1/20
INFO     [02-21-2017 04:11:46] polyglot.element_manager.isy: ISY: [1] ( 0.12) 200 OK: http://10.0.0.50:8880/rest/nodes/n001_aa01ac14160bat
INFO     [02-21-2017 04:11:47] polyglot.nodeserver_manager: Nest: **INFO: probe: fa=n001_aa01ac14160bat pfa=n001_nestcontrol id=nestthermostat fl=0 en=True nm="Street address. downsta"
INFO     [02-21-2017 04:12:49] polyglot.element_manager.isy: ISY: [1] ( 0.04) 200 OK: http://10.0.0.50:8880/rest/nodes/n002_lifxcontrol
INFO     [02-21-2017 04:12:49] polyglot.nodeserver_manager: LifX: **INFO: probe: fa=n002_lifxcontrol pfa=n002_lifxcontrol id=lifxcontrol fl=128 en=True nm="LIFX Control"
INFO     [02-21-2017 04:14:58] polyglot.element_manager.isy: ISY: [1] ( 0.04) 200 OK: http://10.0.0.50:8880/rest/nodes/n001_aa01ac14160agp
INFO     [02-21-2017 04:14:58] polyglot.nodeserver_manager: Nest: **INFO: probe: fa=n001_aa01ac14160agp pfa=n001_nestcontrol id=nestthermostat fl=0 en=True nm="Street address. upstair"
INFO     [02-21-2017 04:15:00] polyglot.element_manager.isy: ISY: [1] ( 0.03) 200 OK: http://10.0.0.50:8880/rest/ns/2/nodes/n002_d073d5149bcb/report/status/GV6/3.2/20
INFO     [02-21-2017 04:15:58] polyglot.element_manager.isy: ISY: [1] ( 0.16) 200 OK: http://10.0.0.50:8880/rest/nodes/n002_d073d5149bcb
INFO     [02-21-2017 04:15:58] polyglot.nodeserver_manager: LifX: **INFO: probe: fa=n002_d073d5149bcb pfa=n002_lifxcontrol id=lifxmultizone fl=0 en=True nm="LIFX LIFX Bulb 149bcb"
INFO     [02-21-2017 04:18:45] polyglot.element_manager.isy: ISY: [1] ( 0.05) 200 OK: http://10.0.0.50:8880/rest/nodes/n001_nestcontrol
INFO     [02-21-2017 04:18:45] polyglot.nodeserver_manager: Nest: **INFO: probe: fa=n001_nestcontrol pfa=n001_nestcontrol id=nestcontrol fl=128 en=True nm="Nest Control"
ERROR    [02-21-2017 04:18:59] polyglot.element_manager.isy: ISY: [1] ( 0.02) 404 ERR: http://10.0.0.50:8880/rest/nodes/n002_
WARNING  [02-21-2017 04:18:59] polyglot.nodeserver_manager: LifX: **WARNING: probe: status code: 404

mwester · February 21, 2017

Your configuration.json file apparently contains a node with an empty name, or perhaps the name has illegal or non-printable characters in it.

The "probe:" messages are from the Polyglot framework -- in order to keep the names and status (enabled/disabled, etc) in sync between the ISY and Polyglot, the framework periodically performs a REST API call to the ISY for each node that is listed in memory (and that in-memory structure is created by each specific node server and persistently stored in a single unified json file by the Polyglot framework).

In the logs above, the probe mechanism has constructed what should be the node name on the ISY (which involves concatenating the node number with the in-memory name of the node). However the constructed name has only the prefix (the node number) and no name. Hence the 404 error.

It is possible that this is just a remnant from a bad day for the node server in question -- in which case you can manually delete that small portion of the configuration.json file (while Polyglot is shut down, of course!). However, that's just a guess, and I wouldn't do that. Instead, you might just sanitize that file (IIRC it may have credentials in it that you'll wish to redact) and post it. Perhaps that will give a clue as to the origin of that node, but it will also help to assess the impact of removing it manually. And help to file a bug report on the framework -- if it is in fact a null name, the framework shouldn't allow that to happen in the first place, it should have thrown an error when that node was being registered instead (JMO).

kzboray · February 21, 2017

mwester,

What a wonderfully complete and comprehensive description of what could be happening to cause this error mwester! Thank you.

I took a look at the configuration.json file and it indeed had a remnant from a previous server in it. I manually deleted this and no more errors.

I am continuing to learn, thank you again.

skunkiechris · February 22, 2017

Hi Einstein,

I've noticed that at some point in the recent changes (I'm not using the multizone branch), Polyglot has stopped "noticing" when bulbs go offline. I have programs set up that power cycle the insteon control for a given lightbulb if its online status goes to "false" for more than 2 minutes, and they never run anymore. Bulbs will drop offline and stay that way, but they still show online in the ISY interface.

I tried doing a query while a bulb was physically powered off, and the logs looked identical to when it was on...not sure if that's how it should function or not, but seemed odd. Any ideas?

Also - does the multizone branch have newer general code, or is it all specific to multizone? AKA, should even those of us without multizone devices go on that branch?

As always, thanks for all your work on this!

Chris

einstein.42 · February 22, 2017

Chris, do a git pull and it should fix your offline stuff. You don't need to go to the multizone branch, but it should work for you. Once it all settles down and everything seems stable, I'll merge the two anyway. My normal color bulbs work with both.

skunkiechris · February 23, 2017

Chris, do a git pull and it should fix your offline stuff. You don't need to go to the multizone branch, but it should work for you. Once it all settles down and everything seems stable, I'll merge the two anyway. My normal color bulbs work with both.

Great - thanks!!

skunkiechris · February 23, 2017

Hmmm...so I did a pull, but now am getting this:

ERROR    [02-23-2017 11:45:55] polyglot.nodeserver_manager: LIFX: Traceback (most recent call last):
ERROR    [02-23-2017 11:45:55] polyglot.nodeserver_manager: LIFX:   File "/home/pi/Polyglot/config/node_servers/lifx-nodeserver/polylifx.py", line 7, in <module>
ERROR    [02-23-2017 11:45:55] polyglot.nodeserver_manager: LIFX:     from polylifx_types import LIFXControl
ERROR    [02-23-2017 11:45:55] polyglot.nodeserver_manager: LIFX:   File "/home/pi/Polyglot/config/node_servers/lifx-nodeserver/polylifx_types.py", line 2, in <module>
ERROR    [02-23-2017 11:45:55] polyglot.nodeserver_manager: LIFX:     import lifxlan
ERROR    [02-23-2017 11:45:55] polyglot.nodeserver_manager: LIFX:   File "/home/pi/Polyglot/config/node_servers/lifx-nodeserver/lifxlan/__init__.py", line 1, in <module>
ERROR    [02-23-2017 11:45:55] polyglot.nodeserver_manager: LIFX:     from .lifxlan import LifxLAN
ERROR    [02-23-2017 11:45:55] polyglot.nodeserver_manager: LIFX:   File "/home/pi/Polyglot/config/node_servers/lifx-nodeserver/lifxlan/lifxlan.py", line 6, in <module>
ERROR    [02-23-2017 11:45:55] polyglot.nodeserver_manager: LIFX:     from device import Device, UDP_BROADCAST_IP, UDP_BROADCAST_PORT, DEFAULT_TIMEOUT, DEFAULT_ATTEMPTS
ERROR    [02-23-2017 11:45:55] polyglot.nodeserver_manager: LIFX:   File "/home/pi/Polyglot/config/node_servers/lifx-nodeserver/lifxlan/device.py", line 1, in <module>
ERROR    [02-23-2017 11:45:55] polyglot.nodeserver_manager: LIFX:     device.py
ERROR    [02-23-2017 11:45:55] polyglot.nodeserver_manager: LIFX: NameError: name 'device' is not defined
INFO     [02-23-2017 11:45:55] polyglot.nodeserver_manager: Started Node Server: lifx-nodeserver:LIFX (18979)
ERROR    [02-23-2017 11:45:55] polyglot.nodeserver_manager: Node Server LIFX has exited unexpectedly.

Ack!

Edit: Ah, I think maybe the device.py file is just missing the '#' on the first line, but not at home to try it at the moment.

einstein.42 · February 23, 2017

Oh holy cow... that wasn't embarrassing at all.

git pull

No idea how that happened. Sorry.

Sign In

Polyglot LIFX NodeSever

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Archived

Recently Browsing

Who's Online (See full list)

Forum Statistics