ELK PG3 not connected and won't run

[mrwkbrdr]

I just noticed my ELK PG3 node server had disconnected and will not start. Attached is the error log file. Any help would be greatly appreciated.

I have deleted the elk node and re-installed it, restarted PG3, no luck still won't run.

PG3 version 3.1.21, IOX version 5.6.0, ELK node version 3.7.0

ELK_5-29-2023_94804_AM.zip

[jimboca]

Please download log package and attach that. It looks like PG3 did not install it properly.

[mrwkbrdr]

Here is the PG3 log package.

Thank you,

Mike Bell
530-945-6445

On May 30, 2023, at 11:38 AM, Jimbo.Automates @.***> wrote:

Please download log package and attach that. It looks like PG3 did not install it properly.

— Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/97#issuecomment-1568657910, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXASWEO7DRW3WPHSTH6P7VLXIYIA5ANCNFSM6AAAAAAYTEUA5A. You are receiving this because you authored the thread.

[mrwkbrdr]

Log package pg3_5-30-2023_100651_AM.zip

[jimboca]

I've added @bpaauwe to this issue, there are PG3 errors in the above log:

5/30/2023, 09:22:29 [pg3] error: [ELK(1)] :: STDERR: python3: can't open file '/var/polyglot/pg3/ns/000db95337ec_1/./elk-poly.py': [Errno 2] No such file or directory

5/30/2023, 09:22:29 [pg3] info: [ELK(1)] :: Exit cause code: 2 - signal: null
5/30/2023, 09:22:29 [pg3] error: startNs: ELK process died

Also, FYI there are different errors in that log for the rachio NS which is causing it to die.

[mrwkbrdr]

Yes, I have several NS that won’t run, but some that are ok?

The 3 NS that are connected but won’t run:

1. ELK
2. Weatherflow
3. Rachio

Thank you,

Mike Bell
530-945-6445

On May 30, 2023, at 12:17 PM, Jimbo.Automates @.***> wrote:

I've added @bpaauwe https://github.com/bpaauwe to this issue, there are PG3 errors in the above log:

5/30/2023, 09:22:29 [pg3] error: [ELK(1)] :: STDERR: python3: can't open file '/var/polyglot/pg3/ns/000db95337ec_1/./elk-poly.py': [Errno 2] No such file or directory

5/30/2023, 09:22:29 [pg3] info: [ELK(1)] :: Exit cause code: 2 - signal: null 5/30/2023, 09:22:29 [pg3] error: startNs: ELK process died Also, FYI there are different errors in that log for the rachio NS which is causing it to die.

— Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/97#issuecomment-1568715892, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXASWEMEH6J7WPKQ3QBDDADXIYMQVANCNFSM6AAAAAAYTEUA5A. You are receiving this because you authored the thread.

[jimboca]

The rachio error needs to be fixed by the author of that NS:

5/30/2023, 04:30:36 [pg3] error: [Rachio(6)] :: STDERR:   File "/var/polyglot/pg3/ns/000db95337ec_6/./rachio-poly.py", line 2
    LOGGER.debug('Obtained Person ID (%s), %s/%s API requests remaining until %s', str(self.person_id), str(_person_id[0]['x-ratelimit-remaining']), str(_person_id[0]['x-ratelimit-limit']),str(_person_id[0]['x-ratelimit-reset']))
IndentationError: unexpected indent

[mrwkbrdr]

Thanks,

I just deleted the Rachio NS restarted PG3, re-booted Polisy, and still cannot run ELK or Weatherflow NS’s

Attached a new log pkg after completing the above steps.

Thanks,



Mike Bell
530-945-6445

On May 30, 2023, at 2:09 PM, Jimbo.Automates @.***> wrote:

The rachio error needs to be fixed by the author of that NS:

5/30/2023, 04:30:36 [pg3] error: [Rachio(6)] :: STDERR: File "/var/polyglot/pg3/ns/000db95337ec_6/./rachio-poly.py", line 2 LOGGER.debug('Obtained Person ID (%s), %s/%s API requests remaining until %s', str(self.person_id), str(_person_id[0]['x-ratelimit-remaining']), str(_person_id[0]['x-ratelimit-limit']),str(_person_id[0]['x-ratelimit-reset'])) IndentationError: unexpected indent — Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/97#issuecomment-1568860410, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXASWELX2VJYC3UUF5VURBDXIYZWBANCNFSM6AAAAAAYTEUA5A. You are receiving this because you authored the thread.

[jimboca]

Sorry, didn't mean to imply that rachio NS issue would cause any issues with other NS. Just need to notify the author of that NS to fix it since that's their problem, not PG3.

[mrwkbrdr]

That is ok.

I am just really appreciative that you are trying to help me resolve my NS issues.

Thank you sir!

Mike Bell
530-945-6445

On May 30, 2023, at 2:28 PM, Jimbo.Automates @.***> wrote:

Sorry, didn't mean to imply that rachio NS issue would cause any issues with other NS. Just need to notify the other of that NS to fix it since that's their problem, not PG3.

— Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/97#issuecomment-1568883114, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXASWEJPW3PG72Z7DJZZOQTXIY33LANCNFSM6AAAAAAYTEUA5A. You are receiving this because you authored the thread.

[bpaauwe]

Can you ssh into your Polisy?

If so, please run the following commands and post the results here

df -h

ps auxww | grep bzip

[mrwkbrdr]

Here are the results after ssh polisy.



Mike Bell
530-945-6445

On May 30, 2023, at 2:28 PM, Jimbo.Automates @.***> wrote:

Sorry, didn't mean to imply that rachio NS issue would cause any issues with other NS. Just need to notify the other of that NS to fix it since that's their problem, not PG3.

— Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/97#issuecomment-1568883114, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXASWEJPW3PG72Z7DJZZOQTXIY33LANCNFSM6AAAAAAYTEUA5A. You are receiving this because you authored the thread.

[mrwkbrdr]

Sorry got the last ssh entry wrong. Here are the results.

     ________  ________  ___       ___  ________       ___    ___
    |\   __  \|\   __  \|\  \     |\  \|\   ____\     |\  \  /  /|
    \ \  \_\  \ \  \|\  \ \  \    \ \  \ \  \___|_    \ \  \/  / /
     \ \   ____\ \  \ \  \ \  \    \ \  \ \_____  \    \ \    / /
      \ \  \___|\ \  \_\  \ \  \____\ \  \|____|\  \    \/  /  /
       \ \__\    \ \_______\ \_______\ \__\____\_\  \  _/  / /
        \|__|     \|_______|\|_______|\|__|\_________\|___/ /
                                          \|_________\|___|/

Welcome to Polisy! If you're not a geek, you should not be here!!! Please contact us at @.*** Otherwise, enjoy your session!

@. ~]$ df -h Filesystem Size Used Avail Capacity Mounted on zudi/ROOT/default 25G 4.3G 20G 17% / devfs 1.0K 1.0K 0B 100% /dev procfs 4.0K 4.0K 0B 100% /proc zudi 20G 23K 20G 0% /zudi zudi/tmp 20G 33K 20G 0% /tmp zudi/var/log 20G 974K 20G 0% /var/log zudi/var/db 20G 205M 20G 1% /var/db zudi/usr/home 20G 42K 20G 0% /usr/home zudi/var/crash 20G 23K 20G 0% /var/crash zudi/var/empty 20G 23K 20G 0% /var/empty zudi/var/tmp 20G 23K 20G 0% /var/tmp zudi/var/run 20G 68K 20G 0% /var/run zudi/var/polyglot 10G 148M 9.9G 1% /var/polyglot zudi/var/db/pkg 20G 46M 20G 0% /var/db/pkg @. ~]$ ps auxww / grep bzip ps: illegal argument: /

usage: ps [-aCcdefHhjlmrSTuvwXxZ] [-O fmt | -o fmt] [-G gid[,gid...]] [-J jid[,jid...]] [-M core] [-N system] [-p pid[,pid...]] [-t tty[,tty...]] [-U user[,user...]] ps [-L] @. ~]$ ps auxww | grep bzip admin 5259 0.0 0.1 12840 2324 0 S+ 19:31 0:00.01 grep bzip @. ~]$

Mike Bell
530-945-6445

On May 30, 2023, at 7:17 PM, Bob Paauwe @.***> wrote:

Can you ssh into your Polisy?

If so, please run the following commands and post the results here

df -h

ps auxww | grep bzip

— Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/97#issuecomment-1569261503, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXASWEOTMKSWY4BY5CRTBJTXIZ5XHANCNFSM6AAAAAAYTEUA5A. You are receiving this because you authored the thread.

[bpaauwe]

Thanks, those results look normal/correct

Can you try the following from ssh?

cd /var/polyglot/pg3/ns/000db95337ec_7

sudo git status (this will say something about dubios ownership and give you a command to run that starts with git config --global. Use sudo to run that command) sudo git config --global --add safe.directory /var/polyglot/pg3/ns/000db95337ec_7

sudo git status

sudo zpool status -v zudi

[mrwkbrdr]

Here are the results.

---

@. ~]$ cd /var/polyglot/pg3/ns/000db95337ec_7 @. /var/polyglot/pg3/ns/000db95337ec_7]$ sudo git status Password: fatal: detected dubious ownership in repository at '/var/polyglot/pg3/ns/000db95337ec_7' To add an exception for this directory, call:

git config --global --add safe.directory /var/polyglot/pg3/ns/000db95337ec_7

@. /var/polyglot/pg3/ns/000db95337ec_7]$ sudo git config --global --add safe.directory /var/polyglot/pg3/ns/000db95337ec_7 @. /var/polyglot/pg3/ns/000db95337ec_7]$ sudo git status error: non-monotonic index .git/objects/pack/pack-6177972b64913d5cd47b99643c123b72cb497b26.idx error: non-monotonic index .git/objects/pack/pack-cf1436df88d1b95d767e19e595f02fca64c6ece0.idx error: non-monotonic index .git/objects/pack/pack-6177972b64913d5cd47b99643c123b72cb497b26.idx error: non-monotonic index .git/objects/pack/pack-cf1436df88d1b95d767e19e595f02fca64c6ece0.idx error: non-monotonic index .git/objects/pack/pack-6177972b64913d5cd47b99643c123b72cb497b26.idx error: non-monotonic index .git/objects/pack/pack-cf1436df88d1b95d767e19e595f02fca64c6ece0.idx On branch master Your branch is up to date with 'origin/master'.

Changes not staged for commit: (use "git add ..." to update what will be committed) (use "git restore ..." to discard changes in working directory) modified: install.sh modified: nodes/derived.py modified: nodes/forecast.py modified: nodes/hub.py modified: nodes/weatherflow.py modified: profile/nls/en_us.txt modified: profile/nodedef/nodedefs.xml modified: weatherflow.py

Untracked files: (use "git add ..." to include in what will be committed) nodes/pycache/

no changes added to commit (use "git add" and/or "git commit -a") @.*** /var/polyglot/pg3/ns/000db95337ec_7]$ sudo zpool status -v zudi pool: zudi state: ONLINE status: Some supported and requested features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details. scan: scrub repaired 0B in 00:01:22 with 0 errors on Sat May 27 03:10:55 2023 config:

NAME         STATE     READ WRITE CKSUM
zudi         ONLINE       0     0     0
  gpt/disk0  ONLINE       0     0     0

errors: No known data errors @.*** /var/polyglot/pg3/ns/000db95337ec_7]$

Mike Bell
530-945-6445

On May 30, 2023, at 8:03 PM, Bob Paauwe @.***> wrote:

sudo zpool status -v zudi

[jimboca]

@bpaauwe what about the issue with ELK NS?

[mrwkbrdr]

There are 3 NS including elk that will not start.Elk still will not start. I restarted PG3 after performing the ssh as requested, still won’t start.Thanks,Mike Bell530-945-6445On May 30, 2023, at 9:03 PM, Jimbo.Automates @.***> wrote: @bpaauwe what about the issue with ELK NS?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[jimboca]

Yes, all 3 are failing for different reasons.

ELK is failing due to what looks like a PG3 failure to unzip the package completely.

[mrwkbrdr]

Since there has been so much back and forth through email could I suggest a remote session?Thank you,Mike Bell530-945-6445On May 31, 2023, at 9:35 AM, Jimbo.Automates @.***> wrote: Yes, all 3 are failing for different reasons. ELK is failing due to what looks like a PG3 failure to unzip the package completely.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[mrwkbrdr]

FYI,I also have [Ticket #21603] open with UDI for the 3 nodes that won’t start.Thank you,Mike Bell530-945-6445On May 31, 2023, at 9:42 AM, Michael Bell @.> wrote:Since there has been so much back and forth through email could I suggest a remote session?Thank you,Mike Bell530-945-6445On May 31, 2023, at 9:35 AM, Jimbo.Automates @.> wrote: Yes, all 3 are failing for different reasons. ELK is failing due to what looks like a PG3 failure to unzip the package completely.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[bpaauwe]

I don't really think they are failing for different reasons. Review of both Rachio and WeatherFlow appear to be caused by corrupted files and Elk because it is missing a file when the package is unzipped.

@jimboca you saw the same problem with Notification node server a week ago, did you ever resolve that?

A few weeks back there was another case of corrupted files on install, @michel was going to look into that more but I've not heard anything about it from him.

The git status of the WeatherFlow node server is showing that when it made a copy of git repository from github, a bunch of stuff was corrupted. I expect the same type of issue if you do the same steps in the Rachio node server directory. There may be more problems in the ELK directory as well, but since the main file is missing, nothing runs.

I don't think it's a problem with PG3 or the node servers, but rather a OS/file system problem. That's not something either @jimboca or I can debug/resolve. I'll follow up with @michel on your ticket and see if he has any ideas on how to proceed.

[mrwkbrdr]

I tend believe you are correct, because I have 3 other nodes that are connected and running just fine.Thank you so much for all of your time and assistance.I’m hoping Michel can help me resolve the issue.Mike Bell530-945-6445On May 31, 2023, at 12:12 PM, Bob Paauwe @.***> wrote: I don't really think they are failing for different reasons. Review of both Rachio and WeatherFlow appear to be caused by corrupted files and Elk because it is missing a file when the package is unzipped. @jimboca you saw the same problem with Notification node server a week ago, did you ever resolve that? A few weeks back there was another case of corrupted files on install, @michel was going to look into that more but I've not heard anything about it from him. The git status of the WeatherFlow node server is showing that when it made a copy of git repository from github, a bunch of stuff was corrupted. I expect the same type of issue if you do the same steps in the Rachio node server directory. There may be more problems in the ELK directory as well, but since the main file is missing, nothing runs. I don't think it's a problem with PG3 or the node servers, but rather a OS/file system problem. That's not something either @jimboca or I can debug/resolve. I'll follow up with @michel on your ticket and see if he has any ideas on how to proceed.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[jimboca]

@jimboca you saw the same problem with Notification node server a week ago, did you ever resolve that?

I did not, it was on my development Polisy at home, and I've not been home. My issue was also with PG3 Version 3.1.21 after upgrading all modules.

[bpaauwe]

Can you try the following from ssh:

sudo zpool scrub -w zudi (this may take 4-5 minutes)

sudo zpool status -v zudi

The results should show something like:

  pool: zudi
 state: ONLINE
status: Some supported and requested features are not enabled on the pool.
    The pool can still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
    the pool may no longer be accessible by software that does not support
    the features. See zpool-features(7) for details.
  scan: scrub repaired 0B in 00:04:50 with 0 errors on Wed May 31 14:55:30 2023
config:

    NAME         STATE     READ WRITE CKSUM
    zudi         ONLINE       0     0     0
      gpt/disk0  ONLINE       0     0     0

errors: No known data errors

[mrwkbrdr]

Hi Bob,

Michel suggested I update to PG3X. After updating to 3.1.27 all nodes are now connected and running, However:

After updating to PG3X my weatherflow NS message "invalid station ID"

This node worked with the same configuration on PG3?

IOX 5.6.0, PG3X 3.1.27, WF NS 3.0.29



Mike Bell
530-945-6445

On May 31, 2023, at 5:56 PM, Bob Paauwe @.***> wrote:

Can you try the following from ssh:

sudo zpool scrub -w zudi (this may take 4-5 minutes)

sudo zpool status -v zudi

The results should show something like:

pool: zudi state: ONLINE status: Some supported and requested features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details. scan: scrub repaired 0B in 00:04:50 with 0 errors on Wed May 31 14:55:30 2023 config:

NAME STATE READ WRITE CKSUM zudi ONLINE 0 0 0 gpt/disk0 ONLINE 0 0 0

errors: No known data errors — Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/97#issuecomment-1571016240, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXASWEIGUR45I5ZL37HK34TXI65CRANCNFSM6AAAAAAYTEUA5A. You are receiving this because you authored the thread.

[bpaauwe]

Mike,

There isn't any difference in WeatherFlow, it's the same node server that runs on either. Make sure there aren't any spaces around the id in the configuration parameters.

Also, if you can, please the zpool commands anyway. Just changing to PG3x wouldn't remove any file system corruptions but since PG3x uses a different installation process it could just be using a part of the file system that isn't corrupt.

[mrwkbrdr]

Hi Bob,

The station ID is exactly the same as what was config in PG3?



Here are the results of the SSH

---

@. ~]$ sudo zpool scrub -w zudi Password: @. ~]$ sudo zpool status -v zudi pool: zudi state: ONLINE status: Some supported and requested features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details. scan: scrub repaired 0B in 00:01:19 with 0 errors on Wed May 31 18:58:11 2023 config:

NAME         STATE     READ WRITE CKSUM
zudi         ONLINE       0     0     0
  gpt/disk0  ONLINE       0     0     0

errors: No known data errors @.*** ~]$

Mike Bell
530-945-6445

On May 31, 2023, at 6:30 PM, Michael Bell @.***> wrote:

Hi Bob,

Michel suggested I update to PG3X. After updating to 3.1.27 all nodes are now connected and running, However:

After updating to PG3X my weatherflow NS message "invalid station ID"

This node worked with the same configuration on PG3?

IOX 5.6.0, PG3X 3.1.27, WF NS 3.0.29

Mike Bell 530-945-6445 > On May 31, 2023, at 5:56 PM, Bob Paauwe ***@***.***> wrote: > > > Can you try the following from ssh: > > sudo zpool scrub -w zudi (this may take 4-5 minutes) > > sudo zpool status -v zudi > > The results should show something like: > > pool: zudi > state: ONLINE > status: Some supported and requested features are not enabled on the pool. > The pool can still be used, but some features are unavailable. > action: Enable all features using 'zpool upgrade'. Once this is done, > the pool may no longer be accessible by software that does not support > the features. See zpool-features(7) for details. > scan: scrub repaired 0B in 00:04:50 with 0 errors on Wed May 31 14:55:30 2023 > config: > > NAME STATE READ WRITE CKSUM > zudi ONLINE 0 0 0 > gpt/disk0 ONLINE 0 0 0 > > errors: No known data errors > — > Reply to this email directly, view it on GitHub , or unsubscribe . > You are receiving this because you authored the thread. >

[bpaauwe]

Thanks! Looks like you have clean file system so that's good.

The invalid station id happens when the node server queries for the station info and doesn't get anything back. The url that it uses is:

https://swd.weatherflow.com/swd//rest/stations/**station id/?api_key=api key**

Where the station id and api key would be what you have in the node server configuration. If you do that from a browser it should return JSON formatted data on your station.

[mrwkbrdr]

Hi Bob,

Im not doubting you but the api is good and shows in IOX admin, but its missing the station ID that reports all of the weather station data. I save all my node configs copied to a word doc, and have also confirmed my station ID is 31461?

There must be something wrong, but it appears it is not my config as you can see by the data below.

Thank you,

  

Mike Bell
530-945-6445

On May 31, 2023, at 6:48 PM, Bob Paauwe @.***> wrote:

Mike,

There isn't any difference in WeatherFlow, it's the same node server that runs on either. Make sure there aren't any spaces around the id in the configuration parameters.

Also, if you can, please the zpool commands anyway. Just changing to PG3x wouldn't remove any file system corruptions but since PG3x uses a different installation process it could just be using a part of the file system that isn't corrupt.

— Reply to this email directly, view it on GitHub https://github.com/UniversalDevicesInc-PG3/udi-poly-ELK/issues/97#issuecomment-1571063754, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXASWEKRHI6YEN5ZI4SZWUDXI7DEPANCNFSM6AAAAAAYTEUA5A. You are receiving this because you authored the thread.

[bpaauwe]

Whatever you pasted into the comment it seems like the form didn't understand.

I don't doubt that you have the correct station id, but the node server takes whatever is entered as that config parameter value and uses it in the URL. If it has extra spaces at the front or back, it will use those and that will cause the query to fail. Since you copied from a word document, it's not plain text and there could also be invisible characters in configuration field.

I recommend you clear what's in the config now and type the station id in there, don't copy it from a word document.

[mrwkbrdr]

Hi Bob,I did not copy from a word doc, I just use it as a reference.I have completed deleted the NS and typed in the data without copying it. Plus when I updated from PG3 it automatically transferred the NS data and it stated invalid station ID.I have a test Polisy and it is running PG3 with the exact config and the station ID works and the data shows up in IOX?I guess I will just throw this pile of crap Polisy in the trash and move on to my test Polisy. Really frustrated with all of the recent issues. Hopefully nobody else has this issue because I guess it’s going to go unresolved?Thanks for all of your time,Mike Bell530-945-6445On May 31, 2023, at 8:27 PM, Bob Paauwe @.***> wrote: Whatever you pasted into the comment it seems like the form didn't understand. I don't doubt that you have the correct station id, but the node server takes whatever is entered as that config parameter value and uses it in the URL. If it has extra spaces at the front or back, it will use those and that will cause the query to fail. Since you copied from a word document, it's not plain text and there could also be invisible characters in configuration field. I recommend you clear what's in the config now and type the station id in there, don't copy it from a word document.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[bpaauwe]

Hi Mike, I'm trying to help and haven't given up yet.

What's in the WeatherFlow log file? Can you restart the node server and paste in the relevant log entries here? I want to see the log message as it exists in the log so maybe paste it here inside a code <> block

What the node server is doing isn't all that complicated, It make the HTTPS request I posted above and looks for the station info the returned data. Invalid station id is the error it reports when there is no station data in the returned data. So there are really only a couple of cases where this can happen. 1) the station id is wrong and at this point, we've ruled that out. 2) the station id has extra characters 3) the weatherflow server is unable to return the station data.

I guess it could also be that the API key is wrong, but I've been assuming that correct. You can test for #3 by entering the URL in the browser address bar and making the same query from the browser. What ever that returns is what the node server should be seeing.