Welcome to the new FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
If you are having a problem, please refer to the product documentation or check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.

NodeRed and Monitoring your Bandwidth

Options
Mike-VA3MW
Mike-VA3MW Administrator, FlexRadio Employee, Community Manager, Super Elmer, Moderator admin

Thanks Kyle AA0Z for great NodeRed flow to monitoring your bandwidth.

This can be important if you need to have performance discussions with your ISP.


Comments

  • AA1SS
    AA1SS Member ✭✭
    Options

    Trying to load speedtest into the pallet and I get this error . . . Any Ideas???


    023-06-22T12:01:05.630Z Install : node-red-contrib-speedtest 1.1.0


    2023-06-22T12:01:05.948Z npm.cmd install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-contrib-speedtest@1.1.0

    2023-06-22T12:01:07.125Z [err] npm WARN config production Use `--omit=dev` instead.

    2023-06-22T12:01:12.022Z [err] npm

    2023-06-22T12:01:12.022Z [err]  WARN deprecated node-pre-gyp@0.11.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future

    2023-06-22T12:01:16.761Z [err] npm ERR! code 1

    2023-06-22T12:01:16.761Z [err] npm ERR! path C:\Users\ww1ss\.node-red\node_modules\lzma-native

    2023-06-22T12:01:16.763Z [err] npm ERR!

    2023-06-22T12:01:16.763Z [err]  command failed

    2023-06-22T12:01:16.763Z [err] npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node-pre-gyp install --fallback-to-build && rimraf build

    2023-06-22T12:01:16.763Z [err] npm

    2023-06-22T12:01:16.763Z [err] ERR! Building the projects in this solution one at a time. To enable parallel build, please add the "-m" switch.

    2023-06-22T12:01:16.763Z [err] npm ERR!

    2023-06-22T12:01:16.763Z [err] npm ERR!   build

    2023-06-22T12:01:16.763Z [err] npm

    2023-06-22T12:01:16.764Z [err] ERR!   Microsoft (R) Library Manager Version 14.36.32535.0

    2023-06-22T12:01:16.764Z [err] npm ERR!   Copyright (C) Microsoft Corporation.  All rights reserved.

    2023-06-22T12:01:16.764Z [err] npm ERR!  

    2023-06-22T12:01:16.764Z [err] npm ERR!      Creating library C:\Users\ww1ss\.node-red\node_modules\lzma-native\deps\bin_x86-64\lzma.lib and object C:\Users\ww1ss\.node-red\node_modules\lzma-native\deps\bin_x86-64\lzma.exp

    2023-06-22T12:01:16.764Z [err] npm ERR!   deploy

    2023-06-22T12:01:16.764Z [err] npm ERR!           1 file(s) copied.

    2023-06-22T12:01:16.764Z [err] npm ERR! C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(248,5): warning MSB8065: Custom build for item "..\deps\doc\liblzma.def" succeeded, but specified output "c:\users\ww1ss\.node-red\node_modules\lzma-native\build" has not been created. This may cause incremental build to work incorrectly. [C:\Users\ww1ss\.node-red\node_modules\lzma-native\build\liblzma.vcxproj]

    2023-06-22T12:01:16.764Z [err] npm

    2023-06-22T12:01:16.764Z [err] ERR!   util.cpp

    2023-06-22T12:01:16.764Z [err] npm ERR! C:\Users\ww1ss\AppData\Local\node-gyp\Cache\18.16.0\include\node\v8.h(39,10): fatal  error C1083: Cannot open include file: 'v8-locker.h': No such file or directory [C:\Users\ww1ss\.node-red\node_modules\lzma-native\build\lzma_native.vcxproj]

  • AA1SS
    AA1SS Member ✭✭
    Options

    2023-06-22T12:01:16.764Z [err] npm ERR! Failed to execute 'C:\Program Files\nodejs\node.exe C:\Users\ww1ss\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js build --fallback-to-build --module=C:\Users\ww1ss\.node-red\node_modules\lzma-native\binding-v4.0.6-node-v108-win32-x64\lzma_native.node --module_name=lzma_native --module_path=C:\Users\ww1ss\.node-red\node_modules\lzma-native\binding-v4.0.6-node-v108-win32-x64 --napi_version=8 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v108' (1)

    2023-06-22T12:01:16.764Z [err] npm

    2023-06-22T12:01:16.764Z [err]  ERR! node-pre-gyp info it worked if it ends with ok

    2023-06-22T12:01:16.764Z [err] npm

    2023-06-22T12:01:16.764Z [err]  ERR! node-pre-gyp info using node-pre-gyp@0.11.0

    2023-06-22T12:01:16.764Z [err] npm ERR!

    2023-06-22T12:01:16.764Z [err]  node-pre-gyp info using node@18.16.0 | win32 | x64

    2023-06-22T12:01:16.764Z [err] npm ERR!

    2023-06-22T12:01:16.764Z [err]  node-pre-gyp WARN Using needle for node-pre-gyp https download

    2023-06-22T12:01:16.764Z [err] npm ERR!

    2023-06-22T12:01:16.764Z [err]  node-pre-gyp info check checked for "C:\Users\ww1ss\.node-red\node_modules\lzma-native\binding-v4.0.6-node-v108-win32-x64\lzma_native.node" (not found)

    2023-06-22T12:01:16.764Z [err] npm ERR! node-pre-gyp http GET https://node-pre-gyp.addaleax.net/lzma-native/lzma_native-v4.0.6-node-v108-win32-x64.tar.gz

    2023-06-22T12:01:16.764Z [err] npm ERR! node-pre-gyp http 404 https://node-pre-gyp.addaleax.net/lzma-native/lzma_native-v4.0.6-node-v108-win32-x64.tar.gz

    2023-06-22T12:01:16.764Z [err] npm

    2023-06-22T12:01:16.764Z [err]  ERR! node-pre-gyp WARN Tried to download(404): https://node-pre-gyp.addaleax.net/lzma-native/lzma_native-v4.0.6-node-v108-win32-x64.tar.gz

    2023-06-22T12:01:16.764Z [err] npm ERR!

    2023-06-22T12:01:16.764Z [err]  node-pre-gyp WARN Pre-built binaries not found for lzma-native@4.0.6 and node@18.16.0 (node-v108 ABI, unknown) (falling back to source compile with node-gyp)

    2023-06-22T12:01:16.764Z [err] npm ERR!

    2023-06-22T12:01:16.764Z [err]  node-pre-gyp http 404 status code downloading tarball https://node-pre-gyp.addaleax.net/lzma-native/lzma_native-v4.0.6-node-v108-win32-x64.tar.gz

    2023-06-22T12:01:16.764Z [err] npm

    2023-06-22T12:01:16.764Z [err] ERR! gyp info it worked if it ends with ok

    2023-06-22T12:01:16.764Z [err] npm

    2023-06-22T12:01:16.764Z [err] ERR! gyp info using node-gyp@9.3.1

    2023-06-22T12:01:16.764Z [err] npm

    2023-06-22T12:01:16.764Z [err]  ERR! gyp info using node@18.16.0 | win32 | x64

    2023-06-22T12:01:16.764Z [err] npm

    2023-06-22T12:01:16.764Z [err]  ERR! gyp info ok

    2023-06-22T12:01:16.764Z [err] npm

    2023-06-22T12:01:16.764Z [err]  ERR! gyp info it worked if it ends with ok

    2023-06-22T12:01:16.764Z [err] npm ERR! gyp info using node-gyp@9.3.1

    2023-06-22T12:01:16.764Z [err] npm ERR! gyp info using node@18.16.0 | win32 | x64

    2023-06-22T12:01:16.764Z [err] npm

    2023-06-22T12:01:16.764Z [err] ERR! gyp info find Python using Python version 3.10.11 found at "C:\Users\ww1ss\AppData\Local\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\python.exe"

    2023-06-22T12:01:16.764Z [err] npm ERR!

    2023-06-22T12:01:16.764Z [err]  gyp info find VS using VS2022 (17.6.33815.320) found at:

    2023-06-22T12:01:16.764Z [err] npm ERR! gyp info find VS "C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools"

  • AA1SS
    AA1SS Member ✭✭
    Options

    2023-06-22T12:01:16.764Z [err] npm

    2023-06-22T12:01:16.764Z [err]  ERR! gyp info find VS run with --verbose for detailed information

    2023-06-22T12:01:16.764Z [err] npm ERR!

    2023-06-22T12:01:16.764Z [err]  gyp info spawn C:\Users\ww1ss\AppData\Local\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\python.exe

    2023-06-22T12:01:16.764Z [err] npm ERR! gyp info spawn args [

    2023-06-22T12:01:16.764Z [err] npm ERR! gyp info spawn args   'C:\\Users\\ww1ss\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp\\gyp\\gyp_main.py',

    2023-06-22T12:01:16.764Z [err] npm ERR!

    2023-06-22T12:01:16.765Z [err]  gyp info spawn args   'binding.gyp',

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp info spawn args   '-f',

    2023-06-22T12:01:16.765Z [err] npm ERR!

    2023-06-22T12:01:16.765Z [err]  gyp info spawn args   'msvs',

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp info spawn args   '-I',

    2023-06-22T12:01:16.765Z [err] npm

    2023-06-22T12:01:16.765Z [err] ERR! gyp info spawn args   'C:\\Users\\ww1ss\\.node-red\\node_modules\\lzma-native\\build\\config.gypi',

    2023-06-22T12:01:16.765Z [err] npm ERR!

    2023-06-22T12:01:16.765Z [err]  gyp info spawn args   '-I',

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp info spawn args   'C:\\Users\\ww1ss\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp\\addon.gypi',

    2023-06-22T12:01:16.765Z [err] npm ERR!

    2023-06-22T12:01:16.765Z [err]  gyp info spawn args   '-I',

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp info spawn args   'C:\\Users\\ww1ss\\AppData\\Local\\node-gyp\\Cache\\18.16.0\\include\\node\\common.gypi',

    2023-06-22T12:01:16.765Z [err] npm

    2023-06-22T12:01:16.765Z [err] ERR! gyp info spawn args   '-Dlibrary=shared_library',

    2023-06-22T12:01:16.765Z [err] npm

    2023-06-22T12:01:16.765Z [err] ERR! gyp info spawn args   '-Dvisibility=default',

    2023-06-22T12:01:16.765Z [err] npm

    2023-06-22T12:01:16.765Z [err] ERR! gyp info spawn args   '-Dnode_root_dir=C:\\Users\\ww1ss\\AppData\\Local\\node-gyp\\Cache\\18.16.0',

    2023-06-22T12:01:16.765Z [err] npm

    2023-06-22T12:01:16.765Z [err] ERR! gyp info spawn args   '-Dnode_gyp_dir=C:\\Users\\ww1ss\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp',

    2023-06-22T12:01:16.765Z [err] npm ERR!

    2023-06-22T12:01:16.765Z [err]  gyp info spawn args   '-Dnode_lib_file=C:\\\\Users\\\\ww1ss\\\\AppData\\\\Local\\\\node-gyp\\\\Cache\\\\18.16.0\\\\<(target_arch)\\\\node.lib',

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp info spawn args   '-Dmodule_root_dir=C:\\Users\\ww1ss\\.node-red\\node_modules\\lzma-native',

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp info spawn args   '-Dnode_engine=v8',

    2023-06-22T12:01:16.765Z [err] npm

    2023-06-22T12:01:16.765Z [err] ERR! gyp info spawn args   '--depth=.',

    2023-06-22T12:01:16.765Z [err] npm ERR!

    2023-06-22T12:01:16.765Z [err]  gyp info spawn args   '--no-parallel',

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp info spawn args   '--generator-output',

    2023-06-22T12:01:16.765Z [err] npm

    2023-06-22T12:01:16.765Z [err] ERR! gyp info spawn args   'C:\\Users\\ww1ss\\.node-red\\node_modules\\lzma-native\\build',

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp info spawn args   '-Goutput_dir=.'

    2023-06-22T12:01:16.765Z [err] npm

    2023-06-22T12:01:16.765Z [err]  ERR! gyp info spawn args ]

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp info ok

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp info it worked if it ends with ok

    2023-06-22T12:01:16.765Z [err] npm

    2023-06-22T12:01:16.765Z [err] ERR! gyp info using node-gyp@9.3.1

    2023-06-22T12:01:16.765Z [err] npm ERR!

    2023-06-22T12:01:16.765Z [err]  gyp info using node@18.16.0 | win32 | x64

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp info spawn C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Current\Bin\MSBuild.exe

    2023-06-22T12:01:16.765Z [err] npm

    2023-06-22T12:01:16.765Z [err]  ERR! gyp info spawn args [

    2023-06-22T12:01:16.765Z [err] npm ERR!

    2023-06-22T12:01:16.765Z [err]  gyp info spawn args   'build/binding.sln',

    2023-06-22T12:01:16.765Z [err] npm ERR!

    2023-06-22T12:01:16.765Z [err]  gyp info spawn args   '/clp:Verbosity=minimal',

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp info spawn args   '/nologo',

    2023-06-22T12:01:16.765Z [err] npm

    2023-06-22T12:01:16.765Z [err] ERR!

    2023-06-22T12:01:16.765Z [err]  gyp info spawn args   '/p:Configuration=Release;Platform=x64'

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp info spawn args ]

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp ERR! build error

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp ERR! stack Error: `C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\MSBuild\Current\Bin\MSBuild.exe` failed with exit code: 1

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp ERR! stack     at ChildProcess.onExit (C:\Users\ww1ss\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\build.js:203:23)

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp ERR! stack     at ChildProcess.emit (node:events:513:28)

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:291:12)

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp ERR! System Windows_NT 10.0.22621

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\ww1ss\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "build" "--fallback-to-build" "--module=C:\\Users\\ww1ss\\.node-red\\node_modules\\lzma-native\\binding-v4.0.6-node-v108-win32-x64\\lzma_native.node" "--module_name=lzma_native" "--module_path=C:\\Users\\ww1ss\\.node-red\\node_modules\\lzma-native\\binding-v4.0.6-node-v108-win32-x64" "--napi_version=8" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v108"

    2023-06-22T12:01:16.765Z [err] npm ERR! gyp ERR! cwd C:\Users\ww1ss\.node-red\node_modules\lzma-native

    2023-06-22T12:01:16.765Z [err] npm ERR!

    2023-06-22T12:01:16.766Z [err]  gyp ERR! node -v v18.16.0

    2023-06-22T12:01:16.766Z [err] npm ERR! gyp ERR! node-gyp -v v9.3.1

    2023-06-22T12:01:16.766Z [err] npm ERR! gyp ERR! not ok

    2023-06-22T12:01:16.766Z [err] npm ERR! node-pre-gyp ERR! build error

    2023-06-22T12:01:16.766Z [err] npm ERR! node-pre-gyp ERR! stack Error: Failed to execute 'C:\Program Files\nodejs\node.exe C:\Users\ww1ss\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js build --fallback-to-build --module=C:\Users\ww1ss\.node-red\node_modules\lzma-native\binding-v4.0.6-node-v108-win32-x64\lzma_native.node --module_name=lzma_native --module_path=C:\Users\ww1ss\.node-red\node_modules\lzma-native\binding-v4.0.6-node-v108-win32-x64 --napi_version=8 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v108' (1)

    2023-06-22T12:01:16.766Z [err] npm ERR! node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (C:\Users\ww1ss\.node-red\node_modules\node-pre-gyp\lib\util\compile.js:83:29)

    2023-06-22T12:01:16.766Z [err] npm ERR! node-pre-gyp ERR! stack     at ChildProcess.emit (node:events:513:28)

  • AA1SS
    AA1SS Member ✭✭
    Options

    2023-06-22T12:01:16.766Z [err] npm ERR! node-pre-gyp ERR! stack     at maybeClose (node:internal/child_process:1091:16)

    2023-06-22T12:01:16.766Z [err] npm ERR! node-pre-gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:302:5)

    2023-06-22T12:01:16.766Z [err] npm ERR! node-pre-gyp ERR! System Windows_NT 10.0.22621

    2023-06-22T12:01:16.766Z [err] npm ERR! node-pre-gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\ww1ss\\.node-red\\node_modules\\node-pre-gyp\\bin\\node-pre-gyp" "install" "--fallback-to-build"

    2023-06-22T12:01:16.766Z [err] npm ERR! node-pre-gyp ERR! cwd C:\Users\ww1ss\.node-red\node_modules\lzma-native

    2023-06-22T12:01:16.766Z [err] npm ERR! node-pre-gyp ERR! node -v v18.16.0

    2023-06-22T12:01:16.766Z [err] npm ERR! node-pre-gyp ERR! node-pre-gyp -v v0.11.0

    2023-06-22T12:01:16.766Z [err] npm ERR! node-pre-gyp ERR! not ok

    2023-06-22T12:01:16.767Z [err]

    2023-06-22T12:01:16.767Z [err] npm ERR! A complete log of this run can be found in: C:\Users\ww1ss\AppData\Local\npm-cache\_logs\2023-06-22T12_01_07_068Z-debug-0.log

    2023-06-22T12:01:16.788Z rc=1

  • Mike-VA3MW
    Mike-VA3MW Administrator, FlexRadio Employee, Community Manager, Super Elmer, Moderator admin
    Options

    @AA0Z any ideas?

  • AA0Z
    AA0Z Member ✭✭
    Options

    Looks like the speedtest API changed and the owner of the speedtest node is not updating so I would say this flow is broken until we can find a new speedtest node to substitute.

  • AA0Z
    AA0Z Member ✭✭
    Options

    OK, for those of you playing at home, I'll have a fix out soon. Looks like the speedtest team has a CLI command you can install, so I'll need to update the flow. Thanks to some peeps in the Node Red for Ham Radio Groups i/o for showing me some info to get this updated!

    ....more to come....watch this space or my YouTube channel for an update to this flow.

    https://www.youtube.com/@aa0z

  • Bob W4PG
    Bob W4PG Member ✭✭
    Options

    Wondering if this is still an issue? I cannot add speedtest either, getting a lengthy error message similar to AA1SS above. I downloaded Kyle's flow from groups.io but missing the speedtest node. Anyone have it working?


    .............Bob W4PG

Leave a Comment

Rich Text Editor. To edit a paragraph's style, hit tab to get to the paragraph menu. From there you will be able to pick one style. Nothing defaults to paragraph. An inline formatting menu will show up when you select text. Hit tab to get into that menu. Some elements, such as rich link embeds, images, loading indicators, and error messages may get inserted into the editor. You may navigate to these using the arrow keys inside of the editor and delete them with the delete or backspace key.