Will Install Dev-Packages install Bitstring 3.1.9 for LifX?

[kzboray]

@bpwwer

==================UPDATE============
I fixed it. but the question remains, will dev-packages install the correct Bitstring version for the LifX NS?

 

Thank you again Bob, you rock and I so appreciate you and all your hard work!

 

=====================Original Issue==================================


I had to reboot my Polisy this morning and now my LifX is dead again. I applied the same fix I used last time.

sudo -u polyglot bash
pip3 uninstall bitstring
pip3 install --prefix /var/polyglot/.local bitstring==3.1.9

But it's not working. I'm wondering if the Bitstring 3.1.9 is part of the dev-pacakages. It seems when I add it, it gets erased upon reboot which isn't a long term solution. And now I can't get it to work at all. Any suggestion would be appreciated!

Thank you!

Edited January 29, 2023 by kzboray

[asbril]

10 hours ago, kzboray said:

I fixed it

How ?

I am a wanna be Geek but not a real one  .

Do I use PuTty  and just enter

 

sudo -u polyglot bash
pip3 uninstall bitstring
pip3 install --prefix /var/polyglot/.local bitstring==3.1.9

Edited January 29, 2023 by asbril

[kzboray]

@asbril I've thought about your inability to get LifX working for the last few days and I'm not sure how to help you. I'm on a Polisy and you're using the eisy. The file structure is different between them so the original fix posted by xKing didn't work on the Polisy and I had to figure it out for the Polisy. The path for install on a Polisy is

/var/polyglot/.local

For the eisy you need to use:
You will need to use putty or something similar to access the Polisy / eisy via SSH. You can log in with the user name <admin> and the password <admin>, then just copy and past the lines below one at a time and hit <enter> after each one. On the first command you will be promoted for password; use <admin> again.

sudo -u polyglot bash
pip3 uninstall bitstring
pip3 uninstall --prefix /var/polyglot/pg3/ns/0021b9026038_7/.local bitstring
pip3 install --prefix /var/polyglot/pg3/ns/0021b9026038_7/.local bitstring==3.1.9

Note that the /0021b9026038_7/ will need to be changed for your installation of the LifX NS. Look at your Polyglot dashboard and find the LifX NS slot number, then open putty and <cd> to /var/polyglot/pg3/ns. Then type <ls> you will see a list of NS by slot number, cut and past the correct NS name into the above command lines replacing /0021b9026038_7/ in both lines with your specific NS name. You should see something similar to this when you list <ls> the installed NS's. The number at the end of each name is the slot number. Be sure to use the correct one.
 

[admin@polisy /var/polyglot/pg3/ns]$ ls
000db9560fac_1  000db9560fac_11 000db9560fac_3  000db9560fac_5  000db9560fac_7  000db9560fac_9
000db9560fac_10 000db9560fac_2  000db9560fac_4  000db9560fac_6  000db9560fac_8

You will need to restart Polyglot after you install Bitstrng 3.1.9. You should then see device discovery working. If not open a ticket with UD as the problem is not Bitstring.

 

[Bumbershoot]

22 minutes ago, kzboray said:

You will need to restart Polyglot after you install Bitstrng 3.1.9. You should then see device discovery working. If not open a ticket with UD as the problem is not Bitstring.

Just curious, but can't you bypass discovery by using a .yaml file?  They're kind of a PITA to create, but this post indicates that this technique still works on an eisy.

I'm still on Polisy, so I'm not having this issue.

[kzboray]

@Bumbershoot Great idea, but it won't work for this problem. The issue is one of the NS's dependencies is missing. More specifically the correct version is missing. The LifX NS hasn't been maintained and is becoming out of date in regards to the API and dependencies. The NS won't even start correctly unless you replace Bitstring 4.x with the expected 3.1.9 version.

It shows up immediately upon starting the NS when you will see errors in the log file indicating it couldn't find the Bitstring dependency, and then when discovery tries to start, it won't be able to find any devices.

Edited January 29, 2023 by kzboray

[asbril]

36 minutes ago, kzboray said:

@asbril I've thought about your inability to get LifX working for the last few days and I'm not sure how to help you. I'm on a Polisy and you're using the eisy. The file structure is different between them so the original fix posted by xKing didn't work on the Polisy and I had to figure it out for the Polisy. The path for install on a Polisy is

/var/polyglot/.local

For the eisy you need to use:
You will need to use putty or something similar to access the Polisy / eisy via SSH. You can log in with the user name <admin> and the password <admin>, then just copy and past the lines below one at a time and hit <enter> after each one. On the first command you will be promoted for password; use <admin> again.

sudo -u polyglot bash
pip3 uninstall bitstring
pip3 uninstall --prefix /var/polyglot/pg3/ns/0021b9026038_7/.local bitstring
pip3 install --prefix /var/polyglot/pg3/ns/0021b9026038_7/.local bitstring==3.1.9

Note that the /0021b9026038_7/ will need to be changed for your installation of the LifX NS. Look at your Polyglot dashboard and find the LifX NS slot number, then open putty and <cd> to /var/polyglot/pg3/ns. Then type <ls> you will see a list of NS by slot number, cut and past the correct NS name into the above command lines replacing /0021b9026038_7/ in both lines with your specific NS name. You should see something similar to this when you list <ls> the installed NS's. The number at the end of each name is the slot number. Be sure to use the correct one.
 

[admin@polisy /var/polyglot/pg3/ns]$ ls
000db9560fac_1  000db9560fac_11 000db9560fac_3  000db9560fac_5  000db9560fac_7  000db9560fac_9
000db9560fac_10 000db9560fac_2  000db9560fac_4  000db9560fac_6  000db9560fac_8

You will need to restart Polyglot after you install Bitstrng 3.1.9. You should then see device discovery working. If not open a ticket with UD as the problem is not Bitstring.

 

Thanks for your step-by-step guidance, but no luck and I will open a ticket.

[kzboray]

@asbril Sorry mate. Keep us updated on the solution.

[asbril]

Thanks to all. I ordered some more Kasa bulbs and will just give up on Lifx