Using node-red-contrib-tfjs-coco-ssd locally

General
1

Hi, I'm trying to use node-red-contrib-tfjs-coco-ssd locally (offline) withouth success.
windows 10
node-red V1.2.6
node.js V14.15.4
I tryed installing the node in both way, via "npm" and "manage palette": It works great if I leave blank the URL setting (so using the on-line model), but I cannot find the correct path to make it working offline.

2

Immagine 2021-01-10 101558
Immagine 2021-01-10 101558972Ă—485 166 KB

3

I may be wrong but that looks as if it may be an issue that the contrib node should have caught to prevent node-red from crashing. Tagging @dceejay as he is the maintainer of the node I believe.

For the future please try to copy/paste output here rather than screenshot it. When pasting use the </> button at the top of the forum text window.

4

Thanks Colin. Here the output message

10 Jan 15:19:12 - [info] Server now running at http://127.0.0.1:1880/
(node:10136) UnhandledPromiseRejectionWarning: FetchError: request to http://localhost:1880/coco/model.json failed, reason: connect ECONNREFUSED 127.0.0.1:1880
    at ClientRequest.<anonymous> (C:\Users\Io\.node-red\node_modules\node-fetch\lib\index.js:1393:11)
    at ClientRequest.emit (events.js:315:20)
    at Socket.socketErrorListener (_http_client.js:469:9)
    at Socket.emit (events.js:315:20)
    at emitErrorNT (internal/streams/destroy.js:106:8)
    at emitErrorCloseNT (internal/streams/destroy.js:74:3)
    at processTicksAndRejections (internal/process/task_queues.js:80:21)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:10136) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:10136) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
5

The error is caused by the fact that there is you get a connection refused from http://localhost:1880/coco/model.json. However that should not cause a crash.

6

Thanks. Can you help me to understand why this happens and how to solve it?

7

No, sorry, I don't know anything about that node. That is why I tagged Dave earlier, as he is the maintainer of the node.

8

Once you tag someone, is this already informed? Once I tried the message option of the forum, but this actually starts a new topic inviting to the recipient.

9

Yes, he should get notified.

10

Does the example flow from the node's readme work for you?

11

Today is Sunday so I was taking some time away from the keyboard.
Yes it shouldn't crash - but it seems like it's coming from inside the tfjs library - I'll have a look.
Meanwhile you can see the url it is trying to load... - it's getting a 401 from you so presumably you have some form of authentication turned on which it can't just handle - Is there an endpoint where you could move that file to where which you can access locally ?

12

Hi dceejay, thanks a lot. Yes, it's Sunday and I understand :slightly_smiling_face:.

Sorry, I don't understand what you mean and what attempt I should make. I set both password protection in settings.js: flows and dashboard

13

Hi, I'm making several trying but without success. I always get back error messages.
Any help is welcome.

1 Like
14

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.