[Support] Cmd4 Plugin not installed

Describe Your Problem:
Getting lots of different error messages such as
getValue. Last error found Getting: "CurrentTemperature". Perhaps you should run in debug mode to find out what the problem might be.
However, I have gone back to step 9 to the "Advantage Air Shell Check" and clicked on "Check Configuration" which tells me the Cmd4 Plugin is not installed, when it is showing as installed.
Link to Logs:

Paste of Logs:
[1/27/2022, 11:43:47 PM] [Homebridge UI] Homebridge restart request received
[1/27/2022, 11:43:47 PM] [Homebridge UI] Terminal session ended.
[1/27/2022, 11:43:47 PM] [Homebridge UI] UI / Bridge settings have not changed; only restarting Homebridge process
[1/27/2022, 11:43:47 PM] [Homebridge UI] Sending SIGTERM to Homebridge
[1/27/2022, 11:43:47 PM] Got SIGTERM, shutting down Homebridge...
[1/27/2022, 11:43:52 PM] [HB Supervisor] Homebridge Process Ended.  Last error found Getting: "StatusLowBattery". Perhaps you should run in debug mode to find out what the problem might be.

Cmd4 Config:

Screenshots:

Advantage Air System:

Control Unit: MyPlace
Temperature Sensors: Yes

Homebridge Environment:

Node.js Version: v16.13.2
NPM Version: v8.1.2
Homebridge Version: 1.4.0
homebridge-cmd4 Version: v6.0.4
homebridge-cmd4-AdvantageAir Version: v3.1.0
Operating System: Docker (Synology NAS)

Hi, may I know which operating system (OS) are you running your Homebridge in? In Raspberry Pi, intel Mac, M1 Mac or Windows?
I know of another user who runs his Homebridge in M1 Mac has the similar errors with his MyPlace system.  I am troubleshooting it as we speak. I suspect the OS might play a part here. Will certainly let you know if I found some solutions in the coming days.
I will leave it to Mitch on your Cmd4 Plugin not installed issue.

Hi, may I know which operating system (OS) are you running your Homebridge in? In Raspberry Pi, intel Mac, M1 Mac or Windows?
I know of another user who runs his Homebridge in M1 Mac has the similar errors with his MyPlace system. I am troubleshooting it as we speak. I suspect the OS might play a part here. Will certainly let you know if I found some solutions in the coming days.
I will leave it to Mitch on your Cmd4 Plugin not installed issue.

It's currently running from a Synology NAS DSM 7.0.1-42218 update 2 which I believe is the most recent version, and Docker 20.10.3-1239. Thanks for your help.

Thanks Ung Sing for starting to help out; this one might be a little different to your issue though.
@ozbastion sorry for the late reply. You may be my first user I know of using Docker and a Synology NAS; I have had a user with a QNAP, but not sure if they were using Docker. You have clearly shown that you have homebridge-cmd4 installed (thank you for that) and this may just be a 'false' issue with the Shell Check tool saying it is not there. How this check is performed is by looking for the file path of node_modules and if it cannot ascertain that it has hard coded file paths for systems we know to look for; Docker or the Synology may have an issue with the 'call' to figure out the file path and then not have the file path hardcoded for this system (I have faced this same issue with trying to set up Windows).
Can you please run whereis node_modules for me in your terminal and post the response? This will help me determine the issue I have just described. For you, it sounds like in the mean time we have to try and fault find your system without the Shell Check tool (doing it the old way).
Next (and as I found for the QNAP user), there may be different install commands for your system vs what I have in my README. Did you use apt-get install jq and apt-get install curl and if so did it install without issue? I tried to do a quick google for what commands Synology would use and did not come up with much useful information. You can check if they were installed proper with jq -V or curl -V (if those are the right commands for Synology).
After all that, I would need to see your config for cmd4 to make sure there are no silly mistakes (like repeated displayNames). That should give us a good starting point for figuring out your actual issue.

Hi @mitch7391 and @uswong  thank you both for your prompt response. This is the first time I have used Github and Synology/Docker with these various commands.
After running
/homebridge # whereis node_modules I get the response node_modules: /usr/local/lib/node_modules
In relation to the codes to install jq, I think I used 'apk add --no-cache jq' which I found here: https://github.com/cicciovo/homebridge-samsung-airconditioner/issues/4. JQ seemed to install with no problem, and Curl was already installed.
Here are the versions:
jq-master-v20200428-28-g864c859e9d

curl 7.79.1 (x86_64-alpine-linux-musl) libcurl/7.79.1 OpenSSL/1.1.1l zlib/1.2.11 nghttp2/1.41.0
Release-Date: 2021-09-22
Protocols: dict file ftp ftps gopher gophers http https imap imaps mqtt pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: alt-svc AsynchDNS HSTS HTTP2 HTTPS-proxy IPv6 Largefile libz NTLM NTLM_WB SSL TLS-SRP UnixSockets

Hey @ozbastion sorry for the late reply again, I have just transitioned into night shifts for the next few days. Thank you for providing all of that; your config for the one accessory so far looks perfect!
Now did you go with those installation commands due to the ones I had listed did not work or was it in preparation knowing you had a Synology and had found that issue linked? That being said if they gave you version numbers then they should be installed fine.

I think the IP address is <IP_ADDRESS> though it appears that is the address of the Android tablet? Does the Android tablet act as the master to the controller (i.e. the ethernet connection is simply PoE)?

Yep based on one of the screenshots you have sent, you have the IP address correct. Do you also have the remote access set up for the device? Which lets you use the MyAir app outside of the house? Could also be worth going into the settings and turning on the 'Google Home / Alexa' tick box (one user told me that fixed their issues, but I am unsure).

Not sure how these correlate to the z01-z06 notation etc. For example, do I just assume 'z01' = the first zone that is set up?

This is a good question as I do not think I have ever addressed it for users before. I am fairly certain it is the order they appear in the last screenshot. That being said, let's be extra sure and if you can punch this in your URL, you can check the data yourself:
htttp://<IP_ADDRESS>:2025/getSystemData

It will provide you with all the information our plug-in uses and presents. If you do not mind, could you send me a copy to look over? Just look over it carefully and take out any personal information, it may contain your postcode and location (as latitude and longitude); then send it through to<EMAIL_ADDRESS>If you do not wish to or do not feel comfortable than that is fine. It might help Ung Sing and I compare to a problem we are trying to sort out for his son.
Now one last test we can do to make sure the Synology is correctly using curl or jq is to run the following command from your terminal:
curl htttp://<IP_ADDRESS>:2025/getSystemData | jq '.aircon.ac1.zones.z01.measuredTemp'

That should return the value of your zone 1 temperature sensor; if it does not and returns some form of error, then please let me know what it is.

Side note and maybe a little cheeky for me to ask - but do you have a cat room or is that the name of a family member? :)

Hi Mitch, no need to apologise at all!

your config for the one accessory so far looks perfect!

Thanks, that's a good start!

Now did you go with those installation commands due to the ones I had listed did not work or was it in preparation knowing you had a Synology and had found that issue linked?

I used the other installation commands as those ones did not work for the Synology/Docker combination. JQ definitely didn't work, so had to Google how else I could install it.

Do you also have the remote access set up for the device? Which lets you use the MyAir app outside of the house?

Yes, confirmed that this works remotely.

This is a good question as I do not think I have ever addressed it for users before. I am fairly certain it is the order they appear in the last screenshot. That being said, let's be extra sure and if you can punch this in your URL, you can check the data yourself:

I followed the code and got quite a string of text. After formatting it for readability, it does seem that my assumption was right - the z numbering is in order of the appearance.

Now one last test we can do to make sure the Synology is correctly using curl or jq is to run the following command from your terminal:

I tried both of these commands. The curl one gave me the same output as the first one through the normal browser (I assume it is just a JSON GET)?
This one:
jq '.aircon.ac1.zones.z01.measuredTemp'
does not give me any error message- just seems to not respond (been waiting 10+ mins for it).

Side note and maybe a little cheeky for me to ask - but do you have a cat room or is that the name of a family member? :)

No Cat room I'm afraid, though we have a dog! I'm not sure he is too fond of cats though! Labrador x Retriever, his name is Ollie!

By way of further update, I am doing some network reconfiguration as a completely unrelated exercise. During the day, the IP address of the tablet changed (from <IP_ADDRESS> to <IP_ADDRESS>). During this changeover, my Homebridge was offline as well.
Here was the original error message (while the IP address was still correct).
[1/29/2022, 10:45:20 PM] [Cmd4] More than *50* errors were encountered in a row for "Front_Room" getValue. Last error found Getting: "CurrentTemperature". Perhaps you should run in debug mode to find out what the problem might be.

After booting up the NAS/Homebridge, I didn't update the IP address immediately. It still shows the exact same error message.
[1/29/2022, 11:10:49 PM] [Cmd4] More than *50* errors were encountered in a row for "Front_Room" getValue. Last error found Getting: "CurrentTemperature". Perhaps you should run in debug mode to find out what the problem might be.

Not sure if this helps with the troubleshooting, though it seems Homebridge can't even connect to the Android tablet? I don't think connectivity should be an issue as there's no firewall or any other network configuration (all on the same WiFi network). I've also managed to add the Homebridge to my iPhone Homekit, and as I have been testing a few of the accessories, it also showed up on my phone (just non-functional).

I used the other installation commands as those ones did not work for the Synology/Docker combination. JQ definitely didn't work, so had to Google how else I could install it.

Good to know, I will have to update my installation instructions; as I know the Synology is another popular choice for Homebridge.

I followed the code and got quite a string of text. After formatting it for readability, it does seem that my assumption was right - the z numbering is in order of the appearance.

We may have just realised that the MyPlace json body you saw could be a lot larger than the other systems; so I imagine it was a bit to look at haha...

I tried both of these commands. The curl one gave me the same output as the first one through the normal browser (I assume it is just a JSON GET)?

That command is actually one command; it takes the output of curl (the huge json body) and gives it as an input to jq to be parsed and take the info we want from it. If you only did the last half (the jq half) it would endlessly wait to receive nothing haha if you did not know, a ctrl+C command works to cut it short. If doing the whole command as one and it returned no value for you, then I may have given you an outdated command and will have to double check it when I get home to make sure I gave you the right one.

By way of further update, I am doing some network reconfiguration as a completely unrelated exercise. During the day, the IP address of the tablet changed (from <IP_ADDRESS> to <IP_ADDRESS>). During this changeover, my Homebridge was offline as well.

If you do not set a static IP address in your router for this device (and any others in your home automation system), you will face this all the time with power outages or reboots.

I've also managed to add the Homebridge to my iPhone Homekit, and as I have been testing a few of the accessories, it also showed up on my phone (just non-functional).

This means there is no issues with config or the cmd4 side of things; this and the alarms you sent means something is going wrong in terms of the actual communicating to the device itself in terms or get/set values. The issue is that it could be so many different things. We normally start by making sure jq and curl are working. I will confirm that command for you when I get home like 9hrs and we will take it from there. Also if you didn't send that command as one command, make sure you try it and you should get a value back in the form of something like 24.5 or whatever it is actually reading.

No Cat room I'm afraid, though we have a dog! I'm not sure he is too fond of cats though! Labrador x Retriever, his name is Ollie!

Ahh bugger, we are a cat household (well, we have birds and fish too), but will eventually get a dog :p

@ozbastion, I do not think this is needed anymore but there is no harm installing this:
apk add bash

A user with an issue on his QNAP NAS once had to also install bash for it to work; I do not think we use bash anymore, unless it is still used internally by cmd4. See if installing this helps you.

I actually have a stronger feeling now that bash might be missing and is your problem!

That command is actually one command; it takes the output of curl (the huge json body) and gives it as an input to jq to be parsed and take the info we want from it.

Not sure what it all means - looks like data/speed, not temperatures?
Also shows I have installed bash.
Unfortunately after a restart, I'm still getting the same errors:
[1/30/2022, 8:36:10 AM] Homebridge v1.4.0 (HAP v0.10.0) (Homebridge) is running on port 53037.
[1/30/2022, 8:36:50 AM] [Cmd4] *** Starting Polling
[1/30/2022, 8:36:53 AM] [Cmd4] *** All characteristics are now being polled
[1/30/2022, 8:38:01 AM] [Cmd4] More than *50* errors were encountered in a row for "Front_Room" getValue. Last error found Getting: "CurrentTemperature". Perhaps you should run in debug mode to find out what the problem might be.
[1/30/2022, 8:39:22 AM] [Cmd4] More than *100* errors were encountered in a row for "Front_Room" getValue. Last error found Getting: "StatusLowBattery". Perhaps you should run in debug mode to find out what the problem might be.

Also shows I have installed bash.

Damn… Well there goes that idea.
Also I gave you a typo in the curl command (I have gone back and edited my post); it had three ‘t’s in ‘http’ and only needs two. Also I should have given you a ‘-s’ in the command to silence the progress bar. Try this command:
curl -s http://<IP_ADDRESS>:2025/getSystemData | jq '.aircon.ac1.zones.z01.measuredTemp'

I can see it returned ‘null’ for you which is not good and I would expect it might do the same again. I am going to have to keep thinking about this one; sorry it has not been an easy solution so far!

This command also returns null unfortunately
curl -s http://<IP_ADDRESS>:2025/getSystemData | jq '.aircon.ac1.zones.z01.measuredTemp'

Hmm strange, that may not be an issue; as mine is returning null as well and I swear it never used to. But my system is also working…
You could try chmod +x jq as described here. You might need to go to the folder jq is in though before executing that. You can find that with which jq and use cd /file/path/to/jq to get to it. That’s my last idea before bed, I will try think up some more stuff tonight.

@uswong any ideas while I sleep today?

You could try chmod +x jq as described here. You might need to go to the folder jq is in though before executing that. You can find that with which jq and use cd /file/path/to/jq to get to it. That’s my last idea before bed, I will try think up some more stuff tonight.

I have done this one. It is saved in /usr/bin.
After another restart, still no success unfortunately:
[1/30/2022, 9:49:38 AM] [Cmd4] *** Starting Polling
[1/30/2022, 9:49:41 AM] [Cmd4] *** All characteristics are now being polled
[1/30/2022, 9:52:30 AM] [Cmd4] More than *50* errors were encountered in a row for "Front_Room" getValue. Last error found Getting: "StatusLowBattery". Perhaps you should run in debug mode to find out what the problem might be.

If it helps with the troubleshooting, I have successfully installed homebridge-keylights (https://www.npmjs.com/package/homebridge-keylights) and this works well for me.

Not sure if this helps but in the config, I noticed this code:
"state_cmd": "'/usr/local/lib/node_modules/homebridge-cmd4-advantageair/AdvAir.sh'"
The folder 'homebridge-cmd4-advantageair' doesn't seem to exist in that folder - should it?
bash-5.0# ls -l
total 0
drwxr-xr-x 1 root root  80 Jan 11 15:02 corepack
drwxr-xr-x 1 root root 152 Jan 23 01:47 homebridge
drwxr-xr-x 1 root root 236 Jan 23 01:47 homebridge-config-ui-x
drwxr-xr-x 1 root root 204 Jan 30 12:26 homebridge-keylights
drwxr-xr-x 1 root root 146 Jan 30 12:58 homebridge-tplink-smarthome
drwxr-xr-x 1 root root 160 Jan 11 15:02 npm

I have figured it out - the installation location is different, which is a little strange given the other plugins install in /usr/local/lib/node_modules
Original: "state_cmd": "'/usr/local/lib/node_modules/homebridge-cmd4-advantageair/AdvAir.sh'",
Modified:	"state_cmd": "'/homebridge/node_modules/homebridge-cmd4-advantageair/AdvAir.sh'",
I'm going through and configuring all the other sensors/accessories now.

Amazing @ozbastion, you have found the problem and what I would call a cheeky work-around. I assume everything is working now?
So it means the error for not finding cmd4 was true as it was not located where it should have been in the end. This is my bad for only checking your file path but not asking to see the directories inside of it.
Now this means that a different approach was taken for how you installed your other accessories vs how you installed homebridge-cmd4 and homebridge-cmd4-advantageair; am I safe in assuming this? If you bare with me I would like to try get to the root cause so I can make sure this does not happen to another user or I can help them out even quicker.

Ideally I would like us to get your homebridge-cmd4 and homebridge-cmd4-advantageair installed in the correct node_modules directory so that you can use the correct file path for the "state_cmd" and ensure a standard install like all others.

Yes, all working now thanks.
Happy to sort this out to what it should be. Is it something as simple as moving them to the right path?
What caused the initial installation path to the Homebridge folder - is it just the way that Docker works?
And a newbie question - are all plug-ins supposed to be in the /usr path?
Thank you

Yes, all working now thanks.

Awesome, so glad to hear it! :)
All these plug-ins are located in /usr/local/lib/node_modules/ correct?
corepack
homebridge
homebridge-config-ui-x
homebridge-keylights
homebridge-tplink-smarthome

And it seems that these plug-ins were located in /homebridge/node_modules correct?
homebridge-cmd4
homebridge-cmd4-advantageair

If I have that correct, then it means the first batch were installed one way and the other batch were installed another way. Did you user Homebridge UI to install these or did you use the terminal to install via command line?

And a newbie question - are all plug-ins supposed to be in the /usr path?

Yep they are all meant to be together and in the /usr/local/lib/node_modules/ file path. I can show you a quick way to copy them over, but would like to understand how they were installed and ended up there in the first place.

I can show you a quick way to copy them over, but would like to understand how they were installed and ended up there in the first place.

There's a search function in Homebridge and when you find the one you want you just click Install. That's all I did for all the packages so I'm puzzled why they are in different locations. It doesn't ask for any user inputs.

That is even more strange; as it is like some of them have not been installed globally. I have no idea why Homebridge UI would do that… You should be able to copy them over with this command for both plug-ins:
sudo cp -a /homebridge/node_modules/homebridge-cmd4-advantageair /usr/local/lib/node_modules

sudo cp -a /homebridge/node_modules/homebridge-cmd4 /usr/local/lib/node_modules

You may need to check /homebridge/node_modules and see if the plugins are still there after the copy. If they are you can remove them with
sudo rm -r homebridge-cmd4-advantageair

sudo rm -r homebridge-cmd4

Once copied over you would need to change your “state_cmd” back again. And hopefully updates in future will keep the two plugins in the correct directory!

Hi,all,
You should not be installing anything anymore with a copy command.
homebridge, homebridge-cmd4 and homebridge-cmd4-advantageair are all
installed via npm
Where npm installs it is based on the output of
sudo npm root -g
if you use copy, further upgrades will fail.
multiple homebridge installations with multiple node_modules can be
accidentally created by not following the installation instructions of the
various packages. I've screwed myself over many times, so don't feel bad
about it.
Pay attention to where the package gets installed. Use the verbose install
option to see where things are going. Check it afterwards to see that it
went where you expected it.
The important piece is your config.json. Startng over, paying attention is
never an issue.
Afterwards check where homebridge was installed. Start homebridge in debug
mode, all of these are key to getting it right and never having to worry
about it again.
Ttyl,
John
On Sun, Jan 30, 2022 at 5:44 PM Mitch Williams @.***>
wrote:

That is even more strange; as it is like some of them have not been
installed globally. I have no idea why Homebridge UI would do that… You
should be able to copy them over with this command for both plug-ins:
sudo cp -a /homebridge/node_modules/homebridge-cmd4-advantageair /usr/local/lib/node_modules
sudo cp -a /homebridge/node_modules/homebridge-cmd4 /usr/local/lib/node_modules
You may need to check /homebridge/node_modules and see if the plugins are
still there after the copy. If they are you can remove them with
sudo rm -r homebridge-cmd4-advantageair
sudo rm -r homebridge-cmd4
Once copied over you would need to change your “state_cmd” back again.
And hopefully updates in future will keep the two plugins in the correct
directory!
—
Reply to this email directly, view it on GitHub
https://github.com/mitch7391/homebridge-cmd4-AdvantageAir/issues/35#issuecomment-1025250055,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX7VN3PGBF2KBHC3TETUYW5OFANCNFSM5M56ERIQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>

You should not be installing anything anymore with a copy command.

Does this mean I should not copy the files/folders over to /usr/local/lib ?

Where npm installs it is based on the output of sudo npm root -g if you use copy, further upgrades will fail.

I ran this and below is the output:
bash-5.0# sudo npm root -g
/usr/local/lib/node_modules

Pay attention to where the package gets installed. Use the verbose install option to see where things are going. Check it afterwards to see that it went where you expected it.

Other than clicking "Install" in the UI, what are my other options to ensure it is installed to the correct path (/usr/local/lib/node_modules)?
Thanks also for your help and troubleshooting, I really appreciate it :)

Hi,
Thanks for sending the output of the npm root. As you can see, that is what
it should be. I would not copy anything. We are going to properly install
everything.
So now we have to figure out why it is not.
So where did you find homebridge and the plugins installed?
For example if it was installed in '/opt/local/lib/node_modules'
Please do a
ls -al /opt/local/lib
Thanks,
John
So
On Sun, Jan 30, 2022 at 8:18 PM ozbastion @.***> wrote:

You should not be installing anything anymore with a copy command.
Does this mean I should not copy the files/folders over to /usr/local/lib ?
Where npm installs it is based on the output of sudo npm root -g if you
use copy, further upgrades will fail.
I ran this and below is the output:
bash-5.0# sudo npm root -g
/usr/local/lib/node_modules
Pay attention to where the package gets installed. Use the verbose install
option to see where things are going. Check it afterwards to see that it
went where you expected it.
Other than clicking "Install" in the UI, what are my other options to
ensure it is installed to the correct path (/usr/local/lib/node_modules)?
Thanks also for your help and troubleshooting, I really appreciate it :)
—
Reply to this email directly, view it on GitHub
https://github.com/mitch7391/homebridge-cmd4-AdvantageAir/issues/35#issuecomment-1025291545,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX6GMRRLQEJT3AX6GVDUYXPMXANCNFSM5M56ERIQ
.
You are receiving this because you commented.Message ID:
@.***>

So where did you find homebridge and the plugins installed?

Homebridge is installed in the root directory
Within the /homebridge folder
bash-5.0# ls -al
total 628
drwxr-xr-x 1 abc  users    312 Jan 30 14:20 .
drwxr-xr-x 1 root root     210 Jan 27 23:07 ..
-rwxr-xr-x 1 abc  users     81 Jan 27 23:07 .docker.env
-rwxr-xr-x 1 abc  users    795 Jan 30 13:40 .uix-dashboard.json
-rwxr-xr-x 1 abc  users     81 Jan 27 23:07 .uix-secrets
drwxr-xr-x 1 abc  users    126 Jan 30 12:57 accessories
-rwxr-xr-x 1 abc  users    359 Jan 27 23:07 auth.json
drwxr-xr-x 1 abc  users     60 Jan 28 00:25 backups
-rwxr-xr-x 1 abc  users  15399 Jan 30 14:20 config.json
-rwxr-xr-x 1 abc  users 509298 Jan 31 15:42 homebridge.log
drwxr-xr-x 1 abc  users      0 Jan 27 23:07 logs
drwxr-xr-x 1 abc  users    154 Jan 30 13:36 node_modules
-rwxr-xr-x 1 abc  users  86235 Jan 30 13:36 package-lock.json
-rwxr-xr-x 1 abc  users    239 Jan 30 13:36 package.json
drwxr-xr-x 1 abc  users    128 Jan 27 23:07 persist
-rwxr-xr-x 1 abc  users    573 Jan 27 23:07 startup.sh

And within /homebridge/node_modules, we have:
drwxr-xr-x 1 abc users 402 Jan 27 23:09 homebridge-cmd4
drwxr-xr-x 1 abc users 242 Jan 30 13:36 homebridge-cmd4-advantageair
drwxr-xr-x 1 abc users 126 Jan 27 23:07 homebridge-dummy

Within /usr/local/bin, we have:
drwxr-xr-x 1 root root      132 Jan 23 01:47 .
drwxr-xr-x 1 root root       36 Sep  2  2020 ..
lrwxrwxrwx 1 root root       45 Jan 11 15:02 corepack -> ../lib/node_modules/corepack/dist/corepack.js
-rwxr-xr-x 1 root root 33308824 Sep  2  2020 ffmpeg
lrwxrwxrwx 1 root root       65 Jan 23 01:47 hb-service -> ../lib/node_modules/homebridge-config-ui-x/dist/bin/hb-service.js
lrwxrwxrwx 1 root root       45 Jan 23 01:47 homebridge -> ../lib/node_modules/homebridge/bin/homebridge
lrwxrwxrwx 1 root root       65 Jan 23 01:47 homebridge-config-ui-x -> ../lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
-rwxr-xr-x 1 root root 81029304 Jan 11 14:58 node
lrwxrwxrwx 1 root root       38 Jan 11 15:02 npm -> ../lib/node_modules/npm/bin/npm-cli.js
lrwxrwxrwx 1 root root       38 Jan 11 15:02 npx -> ../lib/node_modules/npm/bin/npx-cli.js

Within /usr/local/lib/node_modules, we have:
drwxr-xr-x 1 root root 180 Jan 30 12:58 .
drwxr-xr-x 1 root root  24 Jan 11 15:02 ..
drwxr-xr-x 1 root root  80 Jan 11 15:02 corepack
drwxr-xr-x 1 root root 152 Jan 23 01:47 homebridge
drwxr-xr-x 1 root root 236 Jan 23 01:47 homebridge-config-ui-x
drwxr-xr-x 1 root root 204 Jan 30 12:26 homebridge-keylights
drwxr-xr-x 1 root root 146 Jan 30 12:58 homebridge-tplink-smarthome
drwxr-xr-x 1 root root 160 Jan 11 15:02 npm

Hi,
Just to be clear, if you do
ls -al /homebridge
You get the listing above?
If so, this is definitely not correct. There are conventions in Unix and
tools do not  go directly in /
I'm surprised anything, even running as root this directory was created as
/ generally refers to a file system mount point that is extremely protected.
Ttyl,
John
On Mon, Jan 31, 2022 at 12:48 AM ozbastion @.***> wrote:

So where did you find homebridge and the plugins installed?
Homebridge is installed in the root directory
Within the /homebridge folder
bash-5.0# ls -al
total 628
drwxr-xr-x 1 abc  users    312 Jan 30 14:20 .
drwxr-xr-x 1 root root     210 Jan 27 23:07 ..
-rwxr-xr-x 1 abc  users     81 Jan 27 23:07 .docker.env
-rwxr-xr-x 1 abc  users    795 Jan 30 13:40 .uix-dashboard.json
-rwxr-xr-x 1 abc  users     81 Jan 27 23:07 .uix-secrets
drwxr-xr-x 1 abc  users    126 Jan 30 12:57 accessories
-rwxr-xr-x 1 abc  users    359 Jan 27 23:07 auth.json
drwxr-xr-x 1 abc  users     60 Jan 28 00:25 backups
-rwxr-xr-x 1 abc  users  15399 Jan 30 14:20 config.json
-rwxr-xr-x 1 abc  users 509298 Jan 31 15:42 homebridge.log
drwxr-xr-x 1 abc  users      0 Jan 27 23:07 logs
drwxr-xr-x 1 abc  users    154 Jan 30 13:36 node_modules
-rwxr-xr-x 1 abc  users  86235 Jan 30 13:36 package-lock.json
-rwxr-xr-x 1 abc  users    239 Jan 30 13:36 package.json
drwxr-xr-x 1 abc  users    128 Jan 27 23:07 persist
-rwxr-xr-x 1 abc  users    573 Jan 27 23:07 startup.sh
And within /homebridge/node_modules, we have:
drwxr-xr-x 1 abc users 402 Jan 27 23:09 homebridge-cmd4
drwxr-xr-x 1 abc users 242 Jan 30 13:36 homebridge-cmd4-advantageair
drwxr-xr-x 1 abc users 126 Jan 27 23:07 homebridge-dummy
Within /usr/local/bin, we have:
drwxr-xr-x 1 root root      132 Jan 23 01:47 .
drwxr-xr-x 1 root root       36 Sep  2  2020 ..
lrwxrwxrwx 1 root root       45 Jan 11 15:02 corepack -> ../lib/node_modules/corepack/dist/corepack.js
-rwxr-xr-x 1 root root 33308824 Sep  2  2020 ffmpeg
lrwxrwxrwx 1 root root       65 Jan 23 01:47 hb-service -> ../lib/node_modules/homebridge-config-ui-x/dist/bin/hb-service.js
lrwxrwxrwx 1 root root       45 Jan 23 01:47 homebridge -> ../lib/node_modules/homebridge/bin/homebridge
lrwxrwxrwx 1 root root       65 Jan 23 01:47 homebridge-config-ui-x -> ../lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
-rwxr-xr-x 1 root root 81029304 Jan 11 14:58 node
lrwxrwxrwx 1 root root       38 Jan 11 15:02 npm -> ../lib/node_modules/npm/bin/npm-cli.js
lrwxrwxrwx 1 root root       38 Jan 11 15:02 npx -> ../lib/node_modules/npm/bin/npx-cli.js
Within /usr/local/lib/node_modules, we have:
drwxr-xr-x 1 root root 180 Jan 30 12:58 .
drwxr-xr-x 1 root root  24 Jan 11 15:02 ..
drwxr-xr-x 1 root root  80 Jan 11 15:02 corepack
drwxr-xr-x 1 root root 152 Jan 23 01:47 homebridge
drwxr-xr-x 1 root root 236 Jan 23 01:47 homebridge-config-ui-x
drwxr-xr-x 1 root root 204 Jan 30 12:26 homebridge-keylights
drwxr-xr-x 1 root root 146 Jan 30 12:58 homebridge-tplink-smarthome
drwxr-xr-x 1 root root 160 Jan 11 15:02 npm
—
Reply to this email directly, view it on GitHub
https://github.com/mitch7391/homebridge-cmd4-AdvantageAir/issues/35#issuecomment-1025401868,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX5D5R6HLUIFXPYNM53UYYPEVANCNFSM5M56ERIQ
.
You are receiving this because you commented.Message ID:
@.***>

This is the root directory
bash-5.0# ls -l
total 4
drwxr-xr-x   1 abc  users    0 Jan 11 15:02 app
drwxr-xr-x   1 root root  5286 Jan 30 08:35 bin
drwxr-xr-x   1 abc  users    0 Jan 11 15:02 config
drwxr-xr-x   1 abc  users  100 Jan 23 01:46 defaults
drwxr-xr-x   5 root root   360 Jan 30 08:47 dev
drwxr-xr-x   1 root root  1082 Jan 30 08:47 etc
drwxr-xr-x   1 root root     0 Nov 12 22:14 home
drwxr-xr-x   1 abc  users  312 Jan 30 14:20 homebridge
-rwxr-xr-x   1 root root   389 Oct 20  2017 init
drwxr-xr-x   1 root root   962 Jan 11 19:52 lib
drwxr-xr-x   1 root root   104 Jan 11 15:02 libexec
drwxr-xr-x   1 root root    28 Nov 12 22:14 media
drwxr-xr-x   1 root root     0 Nov 12 22:14 mnt
drwxr-xr-x   1 root root     0 Nov 12 22:14 opt
dr-xr-xr-x 459 root root     0 Jan 30 08:47 proc
drwx------   1 abc  users   82 Jan 30 09:48 root
drwxr-xr-x   1 root root    86 Jan 27 23:07 run
drwxr-xr-x   1 root root  1238 Jan 11 19:52 sbin
drwxr-xr-x   1 root root     0 Nov 12 22:14 srv
dr-xr-xr-x  12 root root     0 Jan 30 08:45 sys
drwxrwxrwt   1 root root    30 Jan 31 06:44 tmp
drwxr-xr-x   1 root root   116 Jan 23 01:46 usr
drwxr-xr-x   1 root root    96 Jan 11 19:53 var

And then below is the /homebridge directory
bash-5.0# ls -al /homebridge
total 628
drwxr-xr-x 1 abc  users    312 Jan 30 14:20 .
drwxr-xr-x 1 root root     210 Jan 27 23:07 ..
-rwxr-xr-x 1 abc  users     81 Jan 27 23:07 .docker.env
-rwxr-xr-x 1 abc  users    795 Jan 30 13:40 .uix-dashboard.json
-rwxr-xr-x 1 abc  users     81 Jan 27 23:07 .uix-secrets
drwxr-xr-x 1 abc  users    126 Jan 30 12:57 accessories
-rwxr-xr-x 1 abc  users    359 Jan 27 23:07 auth.json
drwxr-xr-x 1 abc  users     60 Jan 28 00:25 backups
-rwxr-xr-x 1 abc  users  15399 Jan 30 14:20 config.json
-rwxr-xr-x 1 abc  users 509472 Jan 31 15:57 homebridge.log
drwxr-xr-x 1 abc  users      0 Jan 27 23:07 logs
drwxr-xr-x 1 abc  users    154 Jan 30 13:36 node_modules
-rwxr-xr-x 1 abc  users  86235 Jan 30 13:36 package-lock.json
-rwxr-xr-x 1 abc  users    239 Jan 30 13:36 package.json
drwxr-xr-x 1 abc  users    128 Jan 27 23:07 persist
-rwxr-xr-x 1 abc  users    573 Jan 27 23:07 startup.sh

I was following the instructions here:
https://github.com/oznu/docker-homebridge/wiki/Homebridge-on-Synology
Is it because of this particular instruction:
"Set the Mount path to be /homebridge." ?

Hi,
I know you must be thinking I'm nuts, but this is so weird.
Can you please do
uname -a
df /homebridge
which node
node -v
I want to know what platform we are on and what filesystem /homebridge is
on and also possibly if node is not properly installed.
Either way, whatever is in /homebridge is going to go bye-bye.
Ttyl,
John
On Mon, Jan 31, 2022 at 1:01 AM ozbastion @.***> wrote:

This is the root directory
bash-5.0# ls -l
total 4
drwxr-xr-x   1 abc  users    0 Jan 11 15:02 app
drwxr-xr-x   1 root root  5286 Jan 30 08:35 bin
drwxr-xr-x   1 abc  users    0 Jan 11 15:02 config
drwxr-xr-x   1 abc  users  100 Jan 23 01:46 defaults
drwxr-xr-x   5 root root   360 Jan 30 08:47 dev
drwxr-xr-x   1 root root  1082 Jan 30 08:47 etc
drwxr-xr-x   1 root root     0 Nov 12 22:14 home
drwxr-xr-x   1 abc  users  312 Jan 30 14:20 homebridge
-rwxr-xr-x   1 root root   389 Oct 20  2017 init
drwxr-xr-x   1 root root   962 Jan 11 19:52 lib
drwxr-xr-x   1 root root   104 Jan 11 15:02 libexec
drwxr-xr-x   1 root root    28 Nov 12 22:14 media
drwxr-xr-x   1 root root     0 Nov 12 22:14 mnt
drwxr-xr-x   1 root root     0 Nov 12 22:14 opt
dr-xr-xr-x 459 root root     0 Jan 30 08:47 proc
drwx------   1 abc  users   82 Jan 30 09:48 root
drwxr-xr-x   1 root root    86 Jan 27 23:07 run
drwxr-xr-x   1 root root  1238 Jan 11 19:52 sbin
drwxr-xr-x   1 root root     0 Nov 12 22:14 srv
dr-xr-xr-x  12 root root     0 Jan 30 08:45 sys
drwxrwxrwt   1 root root    30 Jan 31 06:44 tmp
drwxr-xr-x   1 root root   116 Jan 23 01:46 usr
drwxr-xr-x   1 root root    96 Jan 11 19:53 var
And then below is the /homebridge directory
bash-5.0# ls -al /homebridge
total 628
drwxr-xr-x 1 abc  users    312 Jan 30 14:20 .
drwxr-xr-x 1 root root     210 Jan 27 23:07 ..
-rwxr-xr-x 1 abc  users     81 Jan 27 23:07 .docker.env
-rwxr-xr-x 1 abc  users    795 Jan 30 13:40 .uix-dashboard.json
-rwxr-xr-x 1 abc  users     81 Jan 27 23:07 .uix-secrets
drwxr-xr-x 1 abc  users    126 Jan 30 12:57 accessories
-rwxr-xr-x 1 abc  users    359 Jan 27 23:07 auth.json
drwxr-xr-x 1 abc  users     60 Jan 28 00:25 backups
-rwxr-xr-x 1 abc  users  15399 Jan 30 14:20 config.json
-rwxr-xr-x 1 abc  users 509472 Jan 31 15:57 homebridge.log
drwxr-xr-x 1 abc  users      0 Jan 27 23:07 logs
drwxr-xr-x 1 abc  users    154 Jan 30 13:36 node_modules
-rwxr-xr-x 1 abc  users  86235 Jan 30 13:36 package-lock.json
-rwxr-xr-x 1 abc  users    239 Jan 30 13:36 package.json
drwxr-xr-x 1 abc  users    128 Jan 27 23:07 persist
-rwxr-xr-x 1 abc  users    573 Jan 27 23:07 startup.sh
—
Reply to this email directly, view it on GitHub
https://github.com/mitch7391/homebridge-cmd4-AdvantageAir/issues/35#issuecomment-1025405851,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX6POVH64PFWX5DO63LUYYQTLANCNFSM5M56ERIQ
.
You are receiving this because you commented.Message ID:
@.***>

bash-5.0# uname -a
Linux homebridge 3.10.108 #42218 SMP Mon Oct 18 19:15:17 CST 2021 x86_64 GNU/Linux
bash-5.0# df /homebridge
Filesystem              1K-blocks       Used  Available Use% Mounted on
/dev/mapper/cachedev_0<PHONE_NUMBER><PHONE_NUMBER><PHONE_NUMBER>  72% /homebridge
bash-5.0# which node
/usr/local/bin/node
bash-5.0# node -v
v16.13.2

Whatever it's done, it's all working well.. I switched on my air conditioning with HomeKit !

Hi,
Okay we are starting to make some sense now. Their instructions though
are a little disturbing.   I will look further into their instructions and
where they went wrong.
Any reason why you wanted it on the NAS specifically or is this just a
docker thing?
Putting the mount point in / was a bad idea on their part, probably the
easiest to describe as an example, but goes against Unix path structure.
Ttyl,
John
On Mon, Jan 31, 2022 at 1:03 AM ozbastion @.***> wrote:

I was following the instructions here:
https://github.com/oznu/docker-homebridge/wiki/Homebridge-on-Synology
Is it because of this particular instruction:
"Set the Mount path to be /homebridge." ?
—
Reply to this email directly, view it on GitHub
https://github.com/mitch7391/homebridge-cmd4-AdvantageAir/issues/35#issuecomment-1025407039,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX4XPV7PKARAGVEUJETUYYQ3FANCNFSM5M56ERIQ
.
You are receiving this because you commented.Message ID:
@.***>

Any reason why you wanted it on the NAS specifically or is this just a docker thing?

It's probably the only device that I have at home which is on most of the time - I don't have any server or server-like hardware. What are the other alternatives that people do - use a NUC or Raspberry Pi? I considered those two but would mean spending additional money when the NAS appears to be able to do the same job.

Okay,
I understood what they did and why. Still not the best thing to do.
By putting the mount point to / they have symbolic links everywhere from
the proper path of /usr/local/bin/homebridge to /homebridge/bin/homebridge
and so may others. I just saw this reading above in the long thread.
The sad part is that upgrading a package could possibly remove a symbolic
link and your screwed.
Ttyl,
John
On Mon, Jan 31, 2022 at 1:16 AM John Talbot @.***> wrote:

Hi,
Okay we are starting to make some sense now. Their instructions though
are a little disturbing.   I will look further into their instructions and
where they went wrong.
Any reason why you wanted it on the NAS specifically or is this just a
docker thing?
Putting the mount point in / was a bad idea on their part, probably the
easiest to describe as an example, but goes against Unix path structure.
Ttyl,
John
On Mon, Jan 31, 2022 at 1:03 AM ozbastion @.***>
wrote:

I was following the instructions here:
https://github.com/oznu/docker-homebridge/wiki/Homebridge-on-Synology
Is it because of this particular instruction:
"Set the Mount path to be /homebridge." ?
—
Reply to this email directly, view it on GitHub
https://github.com/mitch7391/homebridge-cmd4-AdvantageAir/issues/35#issuecomment-1025407039,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX4XPV7PKARAGVEUJETUYYQ3FANCNFSM5M56ERIQ
.
You are receiving this because you commented.Message ID:
@.***>

Hi,
What else could you use? Good question.  I guess the question may also be
what device do you have that is always on?
I have so many. Trying to get a Pi these days is difficult because of
shortages. If you lived in Ottawa Canada I could give you an older Pi2 or
Pi3.  I have several Pi4's.  One running a 8TB NAS configured as RAID10. My
Mac is also always on.
I have to look through more of your previous emails and that big Synology
instructions to see how I can optimize you out of your predicament.
Ttyl,
John
On Mon, Jan 31, 2022 at 1:19 AM ozbastion @.***> wrote:

Any reason why you wanted it on the NAS specifically or is this just a
docker thing?
It's probably the only device that I have at home which is on most of the
time - I don't have any server or server-like hardware. What are the other
alternatives that people do - use a NUC or Raspberry Pi? I considered those
two but would mean spending additional money when the NAS appears to be
able to do the same job.
—
Reply to this email directly, view it on GitHub
https://github.com/mitch7391/homebridge-cmd4-AdvantageAir/issues/35#issuecomment-1025416004,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX54VCNOR5L4SX2AEGDUYYSWTANCNFSM5M56ERIQ
.
You are receiving this because you commented.Message ID:
@.***>

Hi,
So this part of the thread had me concerned. There are a number of
homebridge plugins that are not in the same spot.
For example, /homebridge/node_modules contains Cmd4 and AdvAir, while
/usr/local/lib/node_modules we have homebridge-config-ui-x etc.
So /homebridge is NAS docker mount point and in it is the configuration
files for Homebridge. I do not believe their should be a node_modules
directory there. It was probably created when *** Cmd4 and AdvAir plugins
were installed as a local package and not a global one ***
Here is what I suggest we do
mv /homebridge/node_modules /homebridge/node_modules.del
sudo npm install -g --unsafe-perm homebridge-cmd4
sudo npm install -g --unsafe-perm homebridge-cmd4-advantageair
This should put the Cmd4 and AdvantageAir plugins in
/usr/local/lib/node_modules as dictated by 'sudo npm root -g'
Don't worry about the unsafe-perm. npm can sometimes get confused with who
owns what and fail to install properly. This fixes that.
backup your old config.json file
Édit the config.json file. The state_cmd for the AdvantageAir accessories
should be:
/usr/local/lib/node_modules/homebridge-cmd4-advantageair/AdvAir.sh
Restart homebridge
From the homebridge-cmd4-advantageair config-ui-x page press the check
Installation button. Hopefully all goes well at that point.
So I'm going back to bed.  Hopefully we now know what went wrong and why;
As well as how to fix it. The result should be a proper installation that
will upgrade in the future.
As you noticed, I backed up the old stuff as a precaution. It can be
deleted if after things are now working correctly.
Ttyl,
John
On Mon, Jan 31, 2022 at 12:48 AM ozbastion @.***> wrote:

So where did you find homebridge and the plugins installed?
Homebridge is installed in the root directory
Within the /homebridge folder
bash-5.0# ls -al
total 628
drwxr-xr-x 1 abc  users    312 Jan 30 14:20 .
drwxr-xr-x 1 root root     210 Jan 27 23:07 ..
-rwxr-xr-x 1 abc  users     81 Jan 27 23:07 .docker.env
-rwxr-xr-x 1 abc  users    795 Jan 30 13:40 .uix-dashboard.json
-rwxr-xr-x 1 abc  users     81 Jan 27 23:07 .uix-secrets
drwxr-xr-x 1 abc  users    126 Jan 30 12:57 accessories
-rwxr-xr-x 1 abc  users    359 Jan 27 23:07 auth.json
drwxr-xr-x 1 abc  users     60 Jan 28 00:25 backups
-rwxr-xr-x 1 abc  users  15399 Jan 30 14:20 config.json
-rwxr-xr-x 1 abc  users 509298 Jan 31 15:42 homebridge.log
drwxr-xr-x 1 abc  users      0 Jan 27 23:07 logs
drwxr-xr-x 1 abc  users    154 Jan 30 13:36 node_modules
-rwxr-xr-x 1 abc  users  86235 Jan 30 13:36 package-lock.json
-rwxr-xr-x 1 abc  users    239 Jan 30 13:36 package.json
drwxr-xr-x 1 abc  users    128 Jan 27 23:07 persist
-rwxr-xr-x 1 abc  users    573 Jan 27 23:07 startup.sh
And within /homebridge/node_modules, we have:
drwxr-xr-x 1 abc users 402 Jan 27 23:09 homebridge-cmd4
drwxr-xr-x 1 abc users 242 Jan 30 13:36 homebridge-cmd4-advantageair
drwxr-xr-x 1 abc users 126 Jan 27 23:07 homebridge-dummy
Within /usr/local/bin, we have:
drwxr-xr-x 1 root root      132 Jan 23 01:47 .
drwxr-xr-x 1 root root       36 Sep  2  2020 ..
lrwxrwxrwx 1 root root       45 Jan 11 15:02 corepack -> ../lib/node_modules/corepack/dist/corepack.js
-rwxr-xr-x 1 root root 33308824 Sep  2  2020 ffmpeg
lrwxrwxrwx 1 root root       65 Jan 23 01:47 hb-service -> ../lib/node_modules/homebridge-config-ui-x/dist/bin/hb-service.js
lrwxrwxrwx 1 root root       45 Jan 23 01:47 homebridge -> ../lib/node_modules/homebridge/bin/homebridge
lrwxrwxrwx 1 root root       65 Jan 23 01:47 homebridge-config-ui-x -> ../lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
-rwxr-xr-x 1 root root 81029304 Jan 11 14:58 node
lrwxrwxrwx 1 root root       38 Jan 11 15:02 npm -> ../lib/node_modules/npm/bin/npm-cli.js
lrwxrwxrwx 1 root root       38 Jan 11 15:02 npx -> ../lib/node_modules/npm/bin/npx-cli.js
Within /usr/local/lib/node_modules, we have:
drwxr-xr-x 1 root root 180 Jan 30 12:58 .
drwxr-xr-x 1 root root  24 Jan 11 15:02 ..
drwxr-xr-x 1 root root  80 Jan 11 15:02 corepack
drwxr-xr-x 1 root root 152 Jan 23 01:47 homebridge
drwxr-xr-x 1 root root 236 Jan 23 01:47 homebridge-config-ui-x
drwxr-xr-x 1 root root 204 Jan 30 12:26 homebridge-keylights
drwxr-xr-x 1 root root 146 Jan 30 12:58 homebridge-tplink-smarthome
drwxr-xr-x 1 root root 160 Jan 11 15:02 npm
—
Reply to this email directly, view it on GitHub
https://github.com/mitch7391/homebridge-cmd4-AdvantageAir/issues/35#issuecomment-1025401868,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX5D5R6HLUIFXPYNM53UYYPEVANCNFSM5M56ERIQ
.
You are receiving this because you commented.Message ID:
@.***>

Looks like I have a lot of emails from my repo today while asleep for night shift lol...
@ozbastion I would definitely listen to John's advice for all this stuff over mine; he has a lot more experience and I am still learning as I go. It sounds like John has confirmed that the copy over I was suggesting would have caused future issues with updates for those plugins.

Whatever it's done, it's all working well.. I switched on my air conditioning with HomeKit !

This is the part that makes me happy! I would suggest you following along with what John has to say to 'fix' the issue with your homebridge setup that might catch you out again in the future with this plug-in or others though. In the mean time I will close this issue as we do have your system working.
Also @ztalbot2000 a lot of people, especially testing the waters of Homebridge will try to use a device they already have dedicated to something else in there house. Not everyone has a heap of RPi's laying around the place like us or have the space or powerpoints to plug in another machine. Ozbastion, I do highly recommend a RPi if you ever decide to switch over to a dedicated machine.

If you lived in Ottawa Canada I could give you an older Pi2 or Pi3.

Remember John, the Advantage Air system is an Australian aircon system :p

Hi Mitch,
Well the last week our thermometer has been between -20 and -40°C. I'd
love to be in Australia right now.
I still wish AirCon would have sent me something to play with ;-)
I bet you I could take a Pi4 and use it to create an AdvAir replacement.
Hmmmm, No got to many things to do myself :-)
Ttyl,
John
On Mon, Jan 31, 2022 at 5:49 AM Mitch Williams @.***>
wrote:

Looks like I have a lot of emails from my repo today while asleep for
night shift lol...
@ozbastion https://github.com/ozbastion I would definitely listen to
John's advice for all this stuff over mine; he has a lot more experience
and I am still learning as I go. It sounds like John has confirmed that the
copy over I was suggesting would have caused future issues with updates for
those plugins.
Whatever it's done, it's all working well.. I switched on my air
conditioning with HomeKit !
This is the part that makes me happy! I would suggest you following along
with what John has to say to 'fix' the issue with your homebridge setup
that might catch you out again in the future with this plug-in or others
though. In the mean time I will close this issue as we do have your system
working.
Also @ztalbot2000 https://github.com/ztalbot2000 a lot of people,
especially testing the waters of Homebridge will try to use a device they
already have dedicated to something else in there house. Not everyone has a
heap of RPi's laying around the place like us or have the space or
powerpoints to plug in another machine. Ozbastion, I do highly recommend a
RPi if you ever decide to switch over to a dedicated machine.
If you lived in Ottawa Canada I could give you an older Pi2 or Pi3.
Remember John, the Advantage Air system is an Australian aircon system :p
—
Reply to this email directly, view it on GitHub
https://github.com/mitch7391/homebridge-cmd4-AdvantageAir/issues/35#issuecomment-1025606813,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3EYLSDZHPD2UZNEMDUYZSMDANCNFSM5M56ERIQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Well the last week our thermometer has been between -20 and -40°C. I'd love to be in Australia right now.

And I was just thinking I would love to be in Canada right now lol the heat waves we have been getting in Western Australia the last month or two has made it such that you look at the forecast and think oh thank god it is only going to be 36 today...

I still wish AirCon would have sent me something to play with ;-)

Very cheeky when you asked them to send you a control unit to play with and such a shame they never replied. They have never been interested in making this HomeKit compatible. The software for the control tablet can't even be put on an iPad sadly... As I would much rather an iPad on the wall...

I bet you I could take a Pi4 and use it to create an AdvAir replacement. Hmmmm, No got to many things to do myself :-)

Don't suggest that lol I am barely keeping on top of all of this project as it is! Hahaha...

I tried following the instructions (move, install and install), after that, the whole system broke, I couldn't see the status and couldn't even get to the config file, and I couldn't even restart it!

Restarting Homebridge
An error occured sending the restart command to the server.

Hi,
Please do the following
mv /homebridge/node_modules.del /homebridge/node_modules
ls -al /usr/local/lib/node_modules
The first will un break things. The second will see where the stuff got
installed to.
I still have to figure out why you have two node_modules directories.
John
On Mon, Jan 31, 2022 at 6:55 AM ozbastion @.***> wrote:

I tried following the instructions (move, install and install), after
that, the whole system broke, I couldn't see the status and couldn't even
get to the config file, and I couldn't even restart it!
[image: 2022 01 31 ENOENT Error on Status]
https://user-images.githubusercontent.com/31245090/151789426-b1054a98-4b80-4430-91bc-b3975db24a39.png
[image: 2022 01 31 Failed to Load Config]
https://user-images.githubusercontent.com/31245090/151789433-a828b79c-97f4-4d49-b9bb-8ea04fd9ff11.png
Restarting Homebridge
An error occured sending the restart command to the server.
[image: 2022 01 31 Restart Command]
https://user-images.githubusercontent.com/31245090/151789604-3ca896b4-3f50-49d6-9d22-466b56651a3a.png
—
Reply to this email directly, view it on GitHub
https://github.com/mitch7391/homebridge-cmd4-AdvantageAir/issues/35#issuecomment-1025661412,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCXYMI5NVHPGELRO6LPTUYZ2EVANCNFSM5M56ERIQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Might have raised the alarm a bit soon - looks like I had to restart the Docker container first. I will work my way through the update of the config file and revert.

Was just googling anything related just in case John was asleep... Keep us updated Nick!

You guys are amazing. John, good morning! Thanks for responding so quickly.
Mitch, thank you too.
After restarting the Docker container, and updating the config.json file, we're all systems go. It's even passed the shell check (green tick), so the system works as normal - looks like there are just some quirks/incompatibilities with the oznu/homebridge via Docker.
I'll do a bit more research on Pi2 / Pi3 / Pi4 - anything in particular you guys use it for?

I guess I would call this one of my passion projects; so always very keen to make it as seamless as possible for everyone. John had made that even more possible with the countless hours he has put into this project too.

looks like there are just some quirks/incompatibilities with the oznu/homebridge via Docker.

Do you have enough of a grasp of the situation to perhaps explain it in a issue raised on their repo so they are aware over there? Could save someone else getting into the same situation in the future.
My RPi4 (the first model) is used for Homebridge originally, I have then connected some HDDs to it to test the waters for if I want a NAS or not (and found it is doing a good enough job for what I need as is) and also continuously run downloads/uploads into/out of it, I ran Hyperion/HyperHDR on it (a TV ambilight server), it is now my dev machine for this project and I have recently installed Pi-Hole on it. It barely chews any power and the CPU usage all of that barely goes over 12% when it is under load. Eventually want to see how it handles homebridge CCTV/HKSV as well.
Man RPi's are good! John does so much more with them as well.

Hi all,
Sorry, I did not think about restarting docker, only Homebridge.
Glad it worked. Skip the last command about moving modules.del back to
modules.
I would still not mind the output of
ls -al /usr/local/lib/node_modules
I have probably at least a dozen Pi's ;-)   These ones are dedicated
NAS Server
Security system using Shinobi
Homebridge
Kodi
CNC controller
Kali box
Thermal camera
Those were Pi 4s. I have lots of Pi 3's and 2's kicking around unused. The
Pi4 being the best because they finally have separate busses for GigE and
USB.
I wasn't kidding about my ability to take a Pi4, with all it's GPIO's and
connectivity to make a replacement AirCon. Just not enough time in the day.
The Pi is not the only SBC on the market. It depends on what you need. For
Single Board Computers it is actually one of the more expensive ones.
Ttyl,
John
On Mon, Jan 31, 2022 at 7:06 AM ozbastion @.***> wrote:

You guys are amazing. John, good morning! Thanks for responding so quickly.
Mitch, thank you too.
After restarting the Docker container, and updating the config.json file,
we're all systems go. It's even passed the shell check (green tick), so the
system works as normal - looks like there are just some
quirks/incompatibilities with the oznu/homebridge via Docker.
I'll do a bit more research on Pi2 / Pi3 / Pi4 - anything in particular
you guys use it for?
—
Reply to this email directly, view it on GitHub
https://github.com/mitch7391/homebridge-cmd4-AdvantageAir/issues/35#issuecomment-1025670400,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX2J52S7PPO6AAYM3OTUYZ3NVANCNFSM5M56ERIQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Do you have enough of a grasp of the situation to perhaps explain it in a issue raised on their repo so they are aware over there? Could save someone else getting into the same situation in the future.

I'm happy to do so - sorry not sure what 'repo' means.
I've started drafting an issue, but have realised I'm not quite sure I have solved the problem myself. I have subsequently installed other plugins though those new ones are still going to /homebridge/node_modules (e.g. https://www.npmjs.com/package/homebridge-yeelight has also gone there).
bash-5.0# ls -al /homebridge/node_modules
total 88
drwxr-xr-x 1 abc users   328 Jan 31 23:02 .
drwxr-xr-x 1 abc users   312 Jan 31 23:01 ..
-rwxr-xr-x 1 abc users 88790 Jan 31 23:02 .package-lock.json
drwxr-xr-x 1 abc users   402 Jan 31 23:02 homebridge-cmd4
drwxr-xr-x 1 abc users   242 Jan 30 13:36 homebridge-cmd4-advantageair
drwxr-xr-x 1 abc users   126 Jan 27 23:07 homebridge-dummy
drwxr-xr-x 1 abc users   130 Jan 31 17:52 homebridge-fronius-inverter-energy
drwxr-xr-x 1 abc users   172 Jan 31 22:59 homebridge-fronius-inverter-lights
drwxr-xr-x 1 abc users    64 Jan 31 22:56 homebridge-yeelight

(the last two on the list were installed late this evening after moving the original homebridge over).
I suppose I would need to update the mount path below - I assume it would need to be updated to /usr ?

Not even sure where everything needs to go now!

ls -al /usr/local/lib/node_modules

bash-5.0# ls -al /usr/local/lib/node_modules
total 0
drwxr-xr-x 1 root root 320 Jan 31 21:47 .
drwxr-xr-x 1 root root  24 Jan 11 15:02 ..
drwxr-xr-x 1 root root  80 Jan 11 15:02 corepack
drwxr-xr-x 1 root root 152 Jan 31 17:50 homebridge
drwxr-xr-x 1 root root 402 Jan 31 21:47 homebridge-cmd4
drwxr-xr-x 1 root root 242 Jan 31 21:47 homebridge-cmd4-advantageair
drwxr-xr-x 1 root root 236 Jan 23 01:47 homebridge-config-ui-x
drwxr-xr-x 1 root root  82 Jan 31 17:50 homebridge-fronius-inverter
drwxr-xr-x 1 root root 204 Jan 30 12:26 homebridge-keylights
drwxr-xr-x 1 root root 146 Jan 30 12:58 homebridge-tplink-smarthome
drwxr-xr-x 1 root root 160 Jan 11 15:02 npm

Hi,
That looks correct!  You did not move the node_modules.del back and
everything is working.  Your good to go it seems.
Ttyl,
John
On Mon, Jan 31, 2022 at 8:22 AM ozbastion @.***> wrote:

ls -al /usr/local/lib/node_modules
bash-5.0# ls -al /usr/local/lib/node_modules
total 0
drwxr-xr-x 1 root root 320 Jan 31 21:47 .
drwxr-xr-x 1 root root  24 Jan 11 15:02 ..
drwxr-xr-x 1 root root  80 Jan 11 15:02 corepack
drwxr-xr-x 1 root root 152 Jan 31 17:50 homebridge
drwxr-xr-x 1 root root 402 Jan 31 21:47 homebridge-cmd4
drwxr-xr-x 1 root root 242 Jan 31 21:47 homebridge-cmd4-advantageair
drwxr-xr-x 1 root root 236 Jan 23 01:47 homebridge-config-ui-x
drwxr-xr-x 1 root root  82 Jan 31 17:50 homebridge-fronius-inverter
drwxr-xr-x 1 root root 204 Jan 30 12:26 homebridge-keylights
drwxr-xr-x 1 root root 146 Jan 30 12:58 homebridge-tplink-smarthome
drwxr-xr-x 1 root root 160 Jan 11 15:02 npm
—
Reply to this email directly, view it on GitHub
https://github.com/mitch7391/homebridge-cmd4-AdvantageAir/issues/35#issuecomment-1025733962,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCXZAG3HTOABR57B7WNTUY2EJTANCNFSM5M56ERIQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi, That looks correct! You did not move the node_modules.del back and everything is working. Your good to go it seems. Ttyl, John
…

Is it right that new plug-ins are being installed in /homebridge/node_modules ?

sorry not sure what 'repo' means.

Repo being short for repository; meaning this GitHub project itself :)

Is it right that new plug-ins are being installed in /homebridge/node_modules ?

They should hopefully be going to /usr/local/lib/node_modules not /homebridge/node_modules; our issue was that for some reason our two plug-ins went to the latter and not the former where they should have been.

Hi Mitch,
His installation was a docker image that gets mounted as a filesystem with
a mount point of /homebridge  This really has not anything to do with
homebridge/node_modules, but that was unfortunately where our plugins were
installed. This made everything confusing.
His /homebridge was essentially the /var/homebridge directory on your Pi.
If you can see that, then you can understand why node_modules should never
have been there.
Now that it's sorted out, our plugins are installed where we expect them to
be and work correctly. No additional coding required to handle his docker
image.
Ttyl,
John
On Mon, Jan 31, 2022 at 8:35 AM Mitch Williams @.***>
wrote:

sorry not sure what 'repo' means.
Repo being short for repository; meaning this GitHub project itself :)
Is it right that new plug-ins are being installed in
/homebridge/node_modules ?
They should hopefully be going to /usr/local/lib/node_modules not
/homebridge/node_modules; our issue was that for some reason our two
plug-ins went to the latter and not the former where they should have been.
—
Reply to this email directly, view it on GitHub
https://github.com/mitch7391/homebridge-cmd4-AdvantageAir/issues/35#issuecomment-1025745871,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3FRYBGNQTLIYD777TUY2FZNANCNFSM5M56ERIQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

I feel like I've duplicated the plug-in and it's still trying to use the one in /homebridge/node_modules
When I restart, I get the below:
[2/1/2022, 8:53:42 AM] Warning: skipping plugin found at '/usr/local/lib/node_modules/homebridge-cmd4' since we already loaded the same plugin from '/homebridge/node_modules/homebridge-cmd4'.
[2/1/2022, 8:53:42 AM] Warning: skipping plugin found at '/usr/local/lib/node_modules/homebridge-cmd4-advantageair' since we already loaded the same plugin from '/homebridge/node_modules/homebridge-cmd4-advantageair'.
[2/1/2022, 8:53:42 AM] Warning: skipping plugin found at '/usr/local/lib/node_modules/homebridge-yeelight' since we already loaded the same plugin from '/homebridge/node_modules/homebridge-yeelight'.

I'm quite sure yesterday I updated to the latest version but I am still seeing this:
[UPDATE AVAILABLE] Version 6.1.1 of homebridge-cmd4 is available. Any release notes can be found here: https://github.com/ztalbot2000/homebridge-cmd4/blob/master/ChangeLog.md

Is there a way I can temporarily (re)move the original installation of the instance in /homebridge/node_modules ? Just create a backup somewhere in another folder?

Hi,
I thought that we did not put back /homebridge/node_modules
Is that still true?
John
On Mon, Jan 31, 2022 at 5:57 PM ozbastion @.***> wrote:

I feel like I've duplicated the plug-in and it's still trying to use the
one in /homebridge/node_modules
When I restart, I get the below:
[2/1/2022, 8:53:42 AM] Warning: skipping plugin found at '/usr/local/lib/node_modules/homebridge-cmd4' since we already loaded the same plugin from '/homebridge/node_modules/homebridge-cmd4'.
[2/1/2022, 8:53:42 AM] Warning: skipping plugin found at '/usr/local/lib/node_modules/homebridge-cmd4-advantageair' since we already loaded the same plugin from '/homebridge/node_modules/homebridge-cmd4-advantageair'.
[2/1/2022, 8:53:42 AM] Warning: skipping plugin found at '/usr/local/lib/node_modules/homebridge-yeelight' since we already loaded the same plugin from '/homebridge/node_modules/homebridge-yeelight'.
I'm quite sure yesterday I updated to the latest version but I am still
seeing this:
[UPDATE AVAILABLE] Version 6.1.1 of homebridge-cmd4 is available. Any release notes can be found here: https://github.com/ztalbot2000/homebridge-cmd4/blob/master/ChangeLog.md
Is there a way I can temporarily (re)move the original installation of the
instance in /homebridge/node_modules ? Just create a backup somewhere in
another folder?
—
Reply to this email directly, view it on GitHub
https://github.com/mitch7391/homebridge-cmd4-AdvantageAir/issues/35#issuecomment-1026293683,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3M334ZOJEIRQDESQ3UY4HWFANCNFSM5M56ERIQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi,
Quickly though I did release a 6.1.1 an hour or so ago
On Mon, Jan 31, 2022 at 5:59 PM John Talbot @.***> wrote:

Hi,
I thought that we did not put back /homebridge/node_modules
Is that still true?
John
On Mon, Jan 31, 2022 at 5:57 PM ozbastion @.***>
wrote:

I feel like I've duplicated the plug-in and it's still trying to use the
one in /homebridge/node_modules
When I restart, I get the below:
[2/1/2022, 8:53:42 AM] Warning: skipping plugin found at '/usr/local/lib/node_modules/homebridge-cmd4' since we already loaded the same plugin from '/homebridge/node_modules/homebridge-cmd4'.
[2/1/2022, 8:53:42 AM] Warning: skipping plugin found at '/usr/local/lib/node_modules/homebridge-cmd4-advantageair' since we already loaded the same plugin from '/homebridge/node_modules/homebridge-cmd4-advantageair'.
[2/1/2022, 8:53:42 AM] Warning: skipping plugin found at '/usr/local/lib/node_modules/homebridge-yeelight' since we already loaded the same plugin from '/homebridge/node_modules/homebridge-yeelight'.
I'm quite sure yesterday I updated to the latest version but I am still
seeing this:
[UPDATE AVAILABLE] Version 6.1.1 of homebridge-cmd4 is available. Any release notes can be found here: https://github.com/ztalbot2000/homebridge-cmd4/blob/master/ChangeLog.md
Is there a way I can temporarily (re)move the original installation of
the instance in /homebridge/node_modules ? Just create a backup somewhere
in another folder?
—
Reply to this email directly, view it on GitHub
https://github.com/mitch7391/homebridge-cmd4-AdvantageAir/issues/35#issuecomment-1026293683,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3M334ZOJEIRQDESQ3UY4HWFANCNFSM5M56ERIQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi, I thought that we did not put back /homebridge/node_modules Is that still true? John
…

I might have reverted it just before I did the container restart. Should I just re-run the command? Is it similar to a delete? Does it ignore the '.del' folder?

Hi,
Homebridge would ignore the .del folder. If /homebridge/node_modules
exists, somehow something is downloading packages there, instead of to
/usr/local/lib/node_modules
Can you please do:
head /homebridge/node_modules/homebridge-cmd4/package.json
head /homebridge/node_modules.del/homebridge-cmd4/package.json
head /usr/local/lib/node_modules/homebridge-cmd4/package.json
I want to see if they are different versions.  One of the commands might
fail with no such file or directory. This is okay.
To fix things for the moment, we will redo what you did before. Except now
node_modules.del exists and we will deal with that first.
mv /homebridge/node_modules.del /tmp/
mv /homebridge/node_modules /homebridge/node_modules.del
restart your docker image as that is what you found was needed the last
time.
I will see if there is a configuration in homebridge-ui that installs
plugins locally, instead of globally.  That might explain what is going on.
Take care,
John
On Mon, Jan 31, 2022 at 6:02 PM ozbastion @.***> wrote:

Hi, I thought that we did not put back /homebridge/node_modules Is that
still true? John
… <#m_-6693830012017870886_m_5349022840925647957_>
I might have reverted it just before I did the container restart. Should I
just re-run the command? Is it similar to a delete? Does it ignore the
'.del' folder?
—
Reply to this email directly, view it on GitHub
https://github.com/mitch7391/homebridge-cmd4-AdvantageAir/issues/35#issuecomment-1026296230,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX5A6DOMW2WD7LZNFS3UY4IG3ANCNFSM5M56ERIQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Create SECURITY.md

A security reporting document is long overdue, but honestly I don't know where to start except for this.
Are there any recommendations reviewers can provide? I would hope to merge this before end of month (we can always adjust later as well if your feedback comes later).

I could create a form instead @nsunami - i cannot connect the email and Discord at this time. That does sound preferable, no?


[BUG] redis port not cast to integer when fetched from environ

https://github.com/openshift/lightspeed-service/blob/main/src/cache/redis_cache.py#L43-L47
This would potentially explode if the env was for some reason pulled as str and not int.

/close


init MultiQC at 1.23

Description of changes
Inits MultiQC and missing python packages
Would also close https://github.com/NixOS/nixpkgs/pull/249329, @apraga feel free to add yourself as a maintainer as well!
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-in-distress/3604/94

There are many mistakes here, but note that there are CI errors.

I am not understanding why so  much duplication.

What do you think ?

Sounds good to me! I'll get back around to this PR eventually, feel free to implement the changes if you'd like to see it done sooner!


Cannot specify slot for "list-publishing-profiles"

I'm trying to list publishing profile credentials etc for my slot and i'm following the instructions here but it isn't working
I have azure cli 2.0.1 installed
https://docs.microsoft.com/en-us/cli/azure/appservice/web/deployment#list-publishing-profiles
az appservice web deployment list-publishing-profiles [--ids IDS]
                                                      [--name NAME]
                                                      [--resource-group RESOURCE_GROUP]
                                                      [--slot SLOT]

but when I type the command I get an error saying unrecognized arguments
az appservice web deployment list-site-credentials -n is-main-app -g is-live-rg -s dev1
az: error: unrecognized arguments: -s dev1

Any ideas?
My version
$ az --version
azure-cli (2.0.1)

acs (2.0.1)
appservice (0.1.1b6)
batch (0.1.1b5)
cloud (2.0.0)
component (2.0.0)
configure (2.0.1)
container (0.1.1b4)
core (2.0.1)
documentdb (0.1.1b2)
feedback (2.0.0)
find (0.0.1b1)
iot (0.1.1b3)
keyvault (0.1.1b6)
network (2.0.1)
nspkg (2.0.0)
profile (2.0.1)
redis (0.1.1b3)
resource (2.0.1)
role (2.0.0)
sql (0.1.1b6)
storage (2.0.1)
vm (2.0.1)

@yugangw-msft

Please use newer version. This command has been replaced with list-publishing-profiles

when i tried to use list-publishing-profiles i get the following error
$ az appservice web deployment list-publishing-profiles
ERROR: az appservice web deployment: error: argument subcommand: invalid choice: 'list-publishing-profiles' (choose from 'slot', 'user', 'list-site-credentials')
usage: az appservice web deployment [-h] {slot,user,list-site-credentials} ...

I tried running az component update but it didn't make a difference

Nevermind, I didn't realise I had to use the nightly builds
Running
export AZURE_COMPONENT_PACKAGE_INDEX_URL=https://azureclinightly.blob.core.windows.net/packages
az component update --add appservice --private

did the trick for me


In master branch , can't use mosn as sidecar without modification

Bug description
Through the documents on the official website, I know that isto can use sidecar other than envoy, and I will follow the instructions as follows：
build istio like that
 ISTIO_ENVOY_VERSION=v0.13.0 ISTIO_ENVOY_RELEASE_URL=https://github.com/GLYASAI/mosn/releases/download/0.13.0/mosn.tgz ISTIO_ENVOY_MACOS_RELEASE_URL=https://github.com/GLYASAI/mosn/releases/download/0.13.0/mosn-macos.tar.gz ISTIO_ENVOY_MACOS_RELEASE_NAME=mosn-0.13.0 SIDECAR=mosn make docker.proxyv2
get error :

What are these. Wasm files for ？
I think this kind of operation will deepen the coupling between istio and sidecar.
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[X] Developer Infrastructure
Expected behavior
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
in the master code

In addition, I would like to ask if there is any way to bypass this

Please open MOSN issues on https://github.com/mosn/mosn, it is not officially supported by Istio.
But that looks like a curl request is failing ,maybe you have some firewall blocking it or something

I have the same problem. How did you solve it?


Project manager window initial position not centered on hiDPI displays

Godot version
v4.0.alpha1.official [31a7ddbf8]
v3.4.2.stable.official [45eaa2daf]
System information
Windows 10
Issue description
See #13017 It's an issue we've had several times before.
I thought it was finally fixed in Godot 4. But I think is slightly another reason. The initial window is centered. But it sizes increases after loading. And btw. the first loading window is just white which is a bad UX. But it seems that this is the same window until the project manager is loaded. In this case the initial centered position does not matter anymore, since the window size changes after loading completed. See recorded screen (gif).

It just feels cheap and annoying when the window behaves like that.
Steps to reproduce
Start Godot. See the initial small window is centered. But the final window state (bigger size) is not centeres.
My screen resolution is: 3840 x 2160 with 200% scale.
This is what I want (window position center):

Update: Same with Godot 3 I see now. I think it's because the window expanse on loaded.

This is due to the same cause as https://github.com/godotengine/godot/issues/13017. I remember it working correctly at some point, but maybe it never did.

The white color of the initial window is not problem. Just the first start(s) was very slow. Looked like window without response. May be solved by first load the window (less as possible) and set a splash and then load the other stuff. But anyway...
The initial position seems to work correctly. The only problem is that the window width and height are changed after loading. Without knowing the code I would guess that either the window position should be centered again or the initial window size should have the same size as the final size. Just some thoughts. But I think you know more about it. :)

The white color of the initial window is not problem. Just the first start(s) was very slow. Looked like window without response. May be solved by first load the window (less as possible) and set a splash and then load the other stuff.

This is being tracked in https://github.com/godotengine/godot-proposals/issues/3657.

Ok, I think my guess wasn't quite right. Don't let that confuse you. The final window (red) size is 2x greater that the initial state (green). So I think it's just because the initial state is just not yet scaled to the OS UI scale, right? So back again, it seems to be the initial cause of that problem. I hope we'll find a solution of this. How does other programs handle that? A workaround could be to start the window maximized.

Ok, I think my guess wasn't quite right. Don't let that confuse you. The final window (red) size is 2x greater then the initial state (green). So I think it's just because the initial state is just not yet scaled to the OS UI scale, right? So back again, it seems to be the initial cause of that problem. I hope we'll find a solution of this. How does other programs handle that?

Other programs handle this by creating the window at the scaled size automatically, rather than scaling the window via window management functions after it is created.
For the record, this scaling behavior was implemented in https://github.com/godotengine/godot/pull/20831.

A workaround could be to start the window maximized.

That would work too, but I feel it would be too large when you have 1080p of screen real estate available (if not more).

Having taken a brief look at the code i think the window is rezised based on the editor scale setting (with a minimum value of 1). However after the resize the window is not repositioned to the center of the screen. The code to do that is fairly straight forward, and I've got it working in some sandbox testing I'm doing.
I'm happy to put together a PR that will solve the window not being centered, but looking toward a long term solution if we attempt to read the display scaling from the operating system/platform we may hit a hurdle on Windows, as the current compilation parameters look target a minimum build OS of Windows 7 and this may be too low to use some of the more advanced DPI scaling APIs.

@TechnicalSoup Feel free to open a pull request for this :slightly_smiling_face:

I'm happy to put together a PR that will solve the window not being centered, but looking toward a long term solution if we attempt to read the display scaling from the operating system/platform we may hit a hurdle on Windows, as the current compilation parameters look target a minimum build OS of Windows 7 and this may be too low to use some of the more advanced DPI scaling APIs.

Can't we use those APIs conditionally at run-time, similar to enabling ANSI escape codes on Windows 10 (for instance)?


feat: 3D Printing and Additive Manufacturing: Unlocking Agile Product Development and Digital Transformation for Corporate Innovation

:tada: This PR is included in version 1.31.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[Bug] Storage information not accurate on BTRFS RAID (Type 5)

Description of the bug
I have a BTRFS raid 5 array.
On split view: Most of the HDDs hit bug #935 but the one that does not lists that it is 47.6TiB / 16 TiB full.
On non-split view: The pie chart shows 47.6 TiB / 67.3 TiB.
The first one is showing the used of the entire raid array / capacity of the individual HDD. The second is showing used of the entire raid array / sum(capacity of each HDD in the raid array).
Neither shows used / capacity of the raid array.
I'm not sure how to handle this exactly, as df -Thl itself reports 47.6 TiB / 67.3 TiB; I know btrfs fi usage /mnt/foo shows the correct amount of 49 TiB. But even if this is a won't fix, I think at least the split view display value is incorrect.
How to reproduce

Create a BTRFS raid 5 array using 4 HDDs
Run dash

Relevant log output
dashdot  |   storage: [
dashdot  |     {
dashdot  |       size:<PHONE_NUMBER>016,
dashdot  |       disks: [ { device: 'nvme0n1', brand: 'Samsung', type: 'NVMe' } ]
dashdot  |     },
dashdot  |     {
dashdot  |       size:<PHONE_NUMBER>7536,
dashdot  |       disks: [ { device: 'sda', brand: 'Western Digital', type: 'HD' } ]
dashdot  |     },
dashdot  |     {
dashdot  |       size:<PHONE_NUMBER>7536,
dashdot  |       disks: [ { device: 'sdb', brand: 'Western Digital', type: 'HD' } ]
dashdot  |     },
dashdot  |     {
dashdot  |       size:<PHONE_NUMBER>7536,
dashdot  |       disks: [ { device: 'sdc', brand: 'Western Digital', type: 'HD' } ]
dashdot  |     },
dashdot  |     {
dashdot  |       size:<PHONE_NUMBER>7536,
dashdot  |       disks: [ { device: 'sdd', brand: 'Western Digital', type: 'HD' } ]
dashdot  |     },
dashdot  |     {
dashdot  |       size:<PHONE_NUMBER>,
dashdot  |       disks: [ { device: 'zram0', brand: 'zram0', type: 'SSD' } ]
dashdot  |     }
dashdot  |   ],

Info output of dashdot cli
yarn run v1.22.19
$ node dist/apps/cli/main.js info
node:internal/modules/cjs/loader:1080
  throw err;
  ^

Error: Cannot find module 'systeminformation'
Require stack:
- /app/dist/apps/cli/apps/cli/src/main.js
- /app/dist/apps/cli/main.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1077:15)
    at Module._resolveFilename (/app/dist/apps/cli/main.js:32:36)
    at Module._load (node:internal/modules/cjs/loader:922:27)
    at Module.require (node:internal/modules/cjs/loader:1143:19)
    at require (node:internal/modules/cjs/helpers:121:18)
    at Object.<anonymous> (/app/dist/apps/cli/apps/cli/src/main.js:26:18)
    at Module._compile (node:internal/modules/cjs/loader:1256:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
    at Module.load (node:internal/modules/cjs/loader:1119:32)
    at Module._load (node:internal/modules/cjs/loader:960:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/app/dist/apps/cli/apps/cli/src/main.js',
    '/app/dist/apps/cli/main.js'
  ]
}

Node.js v18.17.1
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

What browsers are you seeing the problem on?
Chrome
Where is your instance running?
Linux Server
Additional context
In docker

Hi there! The minor difference in the values is probably due to different units used (GiB vs GB). About the split-view: That is definitely wrong.
 But even if this is a won't fix, I think at least the split view display value is incorrect.

I don't know how to fix this exactly as it also shows up incorrectly in df. I think it's because this is a raid array as mentioned above. The problem is there are 4 HDD's Raid 5'd into one array:
$ btrfs fi df /mnt/cryo | grep RAID5
Data, RAID5: total=48.96TiB, used=46.79TiB

Okay I see. Unfortunately, there is not much I can fix right now, because the mounted path is directly assigned to the /dev/sdc drive. The best fix for this would be to correctly detect the raid array, but that is somewhat impossible from the given data, because there is normally a raid block in there, to match the data.
Something like this:
{
  name: 'md0',
  type: 'raid1',
  fsType: 'vfat',
  mount: '/mnt/host/boot/efi',
  size: 268369920,
  physical: '',
  uuid: 'F539-5EE9',
  label: 'archlinux-latest-64-minimal:0',
  model: '',
  serial: '',
  removable: false,
  protocol: '',
  group: '',
},

This is missing on your system and I don't know why. I would suggest opening an issue on the systeminformation repository, managed by @sebhildebrandt. Maybe he can add the functionality to support your raid type.
In the meantime, I would suggest using the following variables to get a somewhat desired result:
DASHDOT_FS_DEVICE_FILTER: 'sda,sdb,sdd'
DASHDOT_OVERRIDE_STORAGE_SIZES: 'sdc=72000831750144'

It will look like there are only 2 drives in your system (which is kind of correct, but it will omit the raid info), but they should show the correct sizes.

@MauriceNino I normally would open an issue but I don't know anything about systeminformation or what it is so I don't feel too comfortable making a bug report. If you do so though, feel free to tag me and I can provide help in the form of df -hl or the like.

@zwimer I have created an issue for you. If you can please comment all the information that might help on there, that would be nice.
What would help:

A command to get the exact size and usage of your RAID (in bytes/bit, not human-readable)
A command to get the name/label of your RAID
Anything you deem important information

For btrfs:
Size:
$ btrfs fi df -b /mnt/my_mount
Data, RAID5: total=53856703610880, used=51651465285632
System, RAID1: total=33554432, used=4571136
Metadata, RAID1: total=95563022336, used=77258293248
GlobalReserve, single: total=536870912, used=0

I'm not sure what you want for label, so here are a few options (there are options to show raw bytes here too if you want):
$ btrfs fi label /mnt/my_mount

I don't have any labels on this FS. Assuming you were looking for stuff like /dev/sda though:
$ sudo btrfs filesystem show /mnt/my_mount  # sudo is required
Label: none  uuid: <REDACTED>
        Total devices 4 FS bytes used 47.05TiB
        devid    1 size 16.37TiB used 16.37TiB path /dev/sdc1
        devid    2 size 16.37TiB used 16.37TiB path /dev/sdd1
        devid    3 size 16.37TiB used 16.37TiB path /dev/sda
        devid    4 size 16.37TiB used 16.37TiB path /dev/sdb

$ sudo btrfs filesystem usage -b /mnt/my_mount  # sudo gives more info
Overall:
    Device size:<PHONE_NUMBER>5840
    Device allocated:<PHONE_NUMBER>1536
    Device unallocated:                    4194304
    Device missing:                              0
    Device slack:                                0
    Used:<PHONE_NUMBER>9944
    Free (estimated):<PHONE_NUMBER>522      (min:<PHONE_NUMBER>522)
    Free (statfs, df):<PHONE_NUMBER>520
    Data ratio:                               1.33
    Metadata ratio:                           2.00
    Global reserve:                      536870912      (used: 0)
    Multiple profiles:                          no

Data,RAID5: Size:53856703610880, Used:51651477647360 (95.91%)
   /dev/sdc1<PHONE_NUMBER>7120
   /dev/sdd1<PHONE_NUMBER>7120
   /dev/sda<PHONE_NUMBER>6880
   /dev/sdb<PHONE_NUMBER>6880

Metadata,RAID1: Size:95563022336, Used:77258145792 (80.85%)
   /dev/sdc1<PHONE_NUMBER>6
   /dev/sdd1<PHONE_NUMBER>6
   /dev/sda<PHONE_NUMBER>0
   /dev/sdb<PHONE_NUMBER>0

System,RAID1: Size:33554432, Used:4571136 (13.62%)
   /dev/sdc1      33554432
   /dev/sdd1      33554432

Unallocated:
   /dev/sdc1       1048576
   /dev/sdd1       1048576
   /dev/sda        1048576
   /dev/sdb        1048576

$ btrfs filesystem usage -b /mnt/my_mount  # non-sudo version
WARNING: cannot read detailed chunk info, per-device usage will not be shown, run as root
Overall:
    Device size:<PHONE_NUMBER>5840
    Device allocated:<PHONE_NUMBER>36
    Device unallocated:<PHONE_NUMBER>2304
    Device missing:                              0
    Device slack:<PHONE_NUMBER>3508612096
    Used:<PHONE_NUMBER>96
    Free (estimated):                            0      (min:<PHONE_NUMBER>671976960)
    Free (statfs, df):<PHONE_NUMBER>232
    Data ratio:                               0.00
    Metadata ratio:                           2.00
    Global reserve:                      536870912      (used: 0)
    Multiple profiles:                          no

Data,RAID5: Size:53856703610880, Used:51651479707648 (95.91%)

Metadata,RAID1: Size:95563022336, Used:77258227712 (80.85%)

System,RAID1: Size:33554432, Used:4571136 (13.62%)

There are also options to show this in a more compact table (might be more parsable)
This is what df -Thl gives by the way:
/dev/sdc1      btrfs      66T   48T  2.1T  96% /mnt/my_mount

As you can see ,the percentage is correct (matches with previous info) but the capacity is only the sum of the disks, it doesn't take into account the loss of data due to parity overhead like the commands above do.
If you want to poke around more and have a btrfs mount yourself, btrfs fi help will give you info about the main tool I used above to get all that info.


Authorization status

Adds bridge method authorizationStatusForType in order for JS code to detect if the app has a certain permission.
Also changes all NSError situations to preserve the native error information over to the JS side, using RCTJSErrorFromNSError instead of making a new error object. Remove NSLog because I didn't see any reason to log all of these expected situations, and with the full error information that can be done from JS side, if desired.

Fixes #68

@terrillo ping

Or @EJohnF @JulianKingman please have a look.
Only now, I see there is a different authorization status implementation available in #41 as well. I'm happy to have either one merged. If the other one is preferred, then I'd still like to include the exception handling changed from this one.

I see that you want to remove NSLogs and make promisified check for authorisations status.
As we know, there is not way to check read permisstions.
And for write(=share) permissions there is checkSharePermission function.

@EJohnF I’m confused about your comment.

I’ve changed error handling so that the real exception information is sent over to JS.
Hence, there is no need for NSLog.
Implemented bridge method to get query share permission, I don’t see any checkSharePermission method in this library.

Please accept this PR.

how to use this?
what are the params for authorizationStatusForType(...)?

Sorry, I forget that checkPermission is in another PR, not in the lib at the moment

@EJohnF thanks, I've added some documentation now!

hm, in code you are using promises, but in docs callback?
May be change code also to callback - in order to keep uniformity with the other functions?

@adbl ping

Right, sorry for the delay! I’ll try to fix this within a few days

@EJohnF I see that the docs I wrote are wrong (copy/paste 😅), I can gladly fix the docs, but changing the code is not likely to happen any time soon I'm afraid. Can the PR be accepted as it is if I change the docs?

Is this released?


Upgrade css-select from ^3.1.2 to ^4.1.2

Resolves #1488
This updates the css-select dependency from ^3.1.2 to ^4.1.2 in order to get the transitive dependency css-what updated to 5.0.1, which was vulnerable to ReDoS up-to-and-including 5.0.0. Given my understanding of SVGO, this means SVGO may be vulnerable as well when provided with a carefully crafted SVG containing CSS.
Alternatively, css-select can be set to as low as ^4.0.0 in order to get css-what updated to an appropriate version. I just set it to ^4.1.2 as that is the latest version as of opening this Pull Request.
As this concerns a vulnerable dependency that is also used in the latest SVGO v1, ideally SVGO v1 should also be patched. I'm not sure what the procedure is for updating SVGO v1 though...

👋 @TrySound, are you able to review this change?

Noting that this "Resolves #1488" in the hopes that that magic phrase will close the issue when/if this get merged (I know that works if it's in the description of a PR, guess we'll find out if it works if its in a comment...)

FYI the breaking changes from css-select 3.1.2 -> 4.1.2 changelog (for someone with better knowledge of this codebase to be able to more easily review):

Several built-in pseudos are now stricter. This aligns them with the CSS spec, but might lead to changes in results.
In HTML, attributes are now automatically considered case-insensitive, based on the HTML spec. Some selectors might now match more elements.
Removed strict option.

@underoot This is a breaking change, as it affects CSS selectors in <style> elements, which requires svgo to bump to v3 major. Therefore, patching v1 is not viable.

For Yarn users (in your package.json):
"resolutions": {
  "**/css-what": "^5.0.0"
}

This should be safe to do, as it avoids any of the breaking changes introduced in css-select@4.

This is a breaking change, as it affects CSS selectors in

Christ. Enough with the approvals. Just merge it already! 😢

Looks like @TrySound is AWOL

Looks like @TrySound is AWOL

No I don't think so, I think we just need to be more patient/uncomplaining.
On Discord in SVGO: https://discord.gg/z8jX8NYxrE

@TrySound answered 21.06.21 07:31UTC (i.e. 09:31 CEST)
https://discord.com/channels/815166721315831868/815166722041839668/856436221604528128
Hi, I will publish new versions today

And if you check https://github.com/TrySound , TrySound did 9 contriutions yesterday and 3 contributions today. I think it is just different priorities.
However @GreLI and @deepsweet  are imho also members of https://github.com/svg and might be able also be able to merge?

Approving much?

In case it's not clear for everyone: you don't have to be an active participant to receive updates. Use the subscribe option instead. And please avoid doing reviews or posting comments just to "bump" the thread - as it can fire off unnecessary emails to a lot of people.
And for those who just want to catch the merge, you can update your preference like so:
(Found by clicking "Customize" next to the Subscribe button)

Above all; please be patient and keep in mind that maintainers have lives/souls too :-)
To keep things clean I'd humbly suggest that we keep activity in this thread directly relevant to the nature of the PR (e.g. discussing potential issues with merging it), and that anything else goes in the linked issue (#1488) instead.

Thanks!

Released https://github.com/svg/svgo/releases/tag/v2.3.1

As this concerns a vulnerable dependency that is also used in the latest SVGO v1, ideally SVGO v1 should also be patched. I'm not sure what the procedure is for updating SVGO v1 though...

@TrySound, do you have any comment in this regard?


readthedocs manual

As the https://fairicube.readthedocs.io/ is directly accessible to all partners (via https://github.com/FAIRiCUBE/collaboration-platform PullRequests (PRs)) and uses markdown language it is the right place to conclude problems&solutions from GitHub issues and/or is the platform for collecting e.g. requirements for a FAIRiCUBE user management.  What is missing :

General guidelines of how to use it (a session in a common topic seminar, a page in the FAIRiBOOK, page in hte readthedocs?)
Review existing issues and see if the https://fairicube.readthedocs.io/ has the appropriate structure
Communication to all project partners to explain the topology
o	what can directly go into fairicube.readthedocs.io
o	what happens if the discussion started in a GitHub issue
o	how and what to migrate to fairicube.readthedocs.io

reinforcing this:

* General guidelines of how to use it (a session in a common topic seminar, a page in the FAIRiBOOK, page in hte readthedocs?)

...I would like to tell some team member to contribute, but to this end some step-by-step explanation is needed.

I confirm that I will provide a chapter "Howto contribute to ..."  during the 6th calender week (this week)

A first version of "Howto contribute to ..." has been provided:
ReadtheDocs:  https://fairicube.readthedocs.io/en/latest/guide/howto_readthedocs/
github:  https://github.com/FAIRiCUBE/collaboration-platform

I consider this issue now complete, how to has been provided, communication to the FiC members has happened

@jetschny @eox-cs1 while the "Howto contribute to ..." has been provided, at least for me it's useless as I'm not working on Linux, don't have git, python etc installed. Maybe provide at least external links for us poor fools working on Windows?

Have you ever heard of Google or Bing?   ;-)
There you get the latest links to download stuff for your OS, including instruction for the installation.

True - no need for any documentation, we're done! ;)

to bridge the gap: I believe Christian meant that one can easily find instructions how to install the necessary tools for windows while Kathi was expressing the wish to get some instructions how to add content to the RtD on Windows? the first one does indeed not need a page in FIC RtD, wheras the latter would be useful to lower the technical bar for contribution...

The tools might be different, but in general the procedure is the same on any OS, as already described.  And to be fair both OS should be described then.
Since I'm neither a Windows-OS nor a MacOS user I can't be of help here. I have zero knowledge about the available SW on any of those OSs.
But since this is a RtD document, please anyone with the respective know-how, feel free to add respective information.

I'm just miffed because I've successfully avoided this step over MANY years!!! I'll do my best to take notes when I set up here and document!