Based on feedback from @mikeS7, I have added a new section to the readme. It explains how to use this node when Node-RED runs in a Docker container on a Raspberry.
To accomplish this request, I had to change the internal command I use from vcgencmd ... to the full path /opt/vc/bin/vcgencmd ....
Seems still to be working fine on my Raspberry (without Docker), which is rather normal since:
When I execute which vcgencmd I get /usr/bin/vcgencmd.
When I execute ls /usr/bin/vcgencmd -ltr I get lrwxrwxrwx 1 root root 20 Apr 7 2017 /usr/bin/vcgencmd -> /opt/vc/bin/vcgencmd.
But just to make sure: could I cause perhaps other problems using the full path?
If nobody sees a problem, I will publish the first version on NPM tomorrow...
Hi @Colin,
I don't use Docker myself, so I don't have an idea. But I suppose not, otherwise it would have been sufficient to mount the /opt/vc/ā¦ folders into the Docker container.
Just got a confirmation from the requester, that it works now on Docker.
I will publish version 1.0.0 on NPM, and we can always fix things afterwards if necessary.
Thanks to you all for the feedback and test work !!!
I have published it on NPM more than ten hours ago. It is there, but not on flows.nodered.org. Think my package.json file is ok:
"keywords": [
"node-red",
The weird thing is that I won't be found either when I search on it, using the searchbar in npmjs.com.
Anybody has any ideas. This is the first time that I have this issue ...
Version 1.0.1 published, and can find it on npm via I can find it via my username:
But again cannot find it again via the NPM search bar:
Saw that the title on the readme page still contained the original node name (node-red-contrib-pi-vcgencmd), so I removed the '-pi' part and published version 1.0.2 (about an hour ago). Command was successfull:
Hi Paul,
Meanwhile the 0.0.2 version is available on NPM, but nothing on flows.nodered.org. And I still can't find it via the npm search box, which is perhaps the reason why it doesn't become available on flows.nodered.org? I'm using the same procedure as I always use...
Exactly. We search npm to find modules with the node-red keyword. If they don't appear in the search results, we don't know about it.
If we manually add something to the flow library, it will get removed overnight when our job runs that looks for modules that have been removed from npm (or republished without the node-red keyword).
Doesn't normally take that long to get into the npm index. You must have caught them at a bad time. The flows index can take up to an hour but occasionally has a hiccup.
at the risk of repeating ourselves...
we (Node-RED) can take up to an hour to re-index as we loop around.
BUT if NPM have an issue and don't index it then WE won't see it to add it... Nothing our indexer can do about it.
How long they are failing to index is their problem which WE can't do anything about.
