Replies: 8 comments
-
Hi, there are a few errors that look like this. |
Beta Was this translation helpful? Give feedback.
-
Hello, I have two systems to test. One (the first one in the listing) on which I have made an update, and a second one on which I have installed a new image. I had already tried to research error -74 on the Internet, but found nothing. I suspected an authorization problem or moved folders, but didn't get any further. Is there a script that I can use to completely uninstall the driver? Then I could test whether it can then be reinstalled on the updated system? Thanks Ronald
|
Beta Was this translation helpful? Give feedback.
-
I don't think the npm errors you are seeing have anything to do with this driver. There is an uninstall.sh script in the bin directory. It removes the directories used by the driver. I would also recommend removing the dbus-mqtt-devices lines from your /data/rc.local file by hand then rebooting. |
Beta Was this translation helpful? Give feedback.
-
After I uninstalled the drivers and then tried to install the dashboard in node-red, I got the following error:
It is also not clear to me how the driver is connected to this? But I had a bare VenusOS installed. I was able to install and uninstall everything in node-red. After I installed the driver for dbus-mqtt-devices, it didn't work anymore?!?? |
Beta Was this translation helpful? Give feedback.
-
I think the fact that you get this error after installing this driver is a coincidence. The driver does not use npm, it 's a purely python code base. Googling this error I found this post on Stack Overflow with various tips of dealing with the npm cache. |
Beta Was this translation helpful? Give feedback.
-
I am moving this from Issues to Discussions as the is no obvious connections between this driver and the error. |
Beta Was this translation helpful? Give feedback.
-
Hello, I have had a look at stackoverflow. I had already read something similar on the npm website and tried it out. Unfortunately, it didn't work for me. I will now install a new image. Then the package I need in node-red, and then after that the driver from you. I hope everything works the way I think it will! Moving to discussion is OK for me! But is it still strange that the problems only occur after the driver has been installed? |
Beta Was this translation helpful? Give feedback.
-
Hello everyone, I have also updated my installation to Venus OS 3.53, it runs dbus-mqtt-devices in Verion 0.8.0 Everything works for me, thanks for the work at this point! Should only be understood as feedback. |
Beta Was this translation helpful? Give feedback.
-
Version
0.8.0 (current)
VenusOS version
V3.51
Does this issue occur during installation or at runtime ?
Runtime
Is there a Discussion thread for this issue? Please paste a link.
https://community.victronenergy.com/t/after-update-to-3-50-i-could-not-install-any-nodes-in-node-red/10014
What is the issue you are actually experiencing?
After creating the thread in the victron community forum, I have now carried out a few tests. As soon as I installed the dbus-mqtt-device driver, I can't install any plug-ins on the same machine via the palette in node-red. The behavior is also different whether you have updated from an older version of venusOS or flashed a fresh SD card (in the victron forum was the time of the update from an older version of venusOS!). With an update, not a single plug-in can be installed. With a completely new SD card, some plug-ins work, others don't?!? I don't have the know-how to go deeper into the error. Can you reproduce the problems?
Thanks Ronald
If this is not installation related, what does the status payload look like that you are publishing to the driver to register your device?
No response
Relevant log output
Beta Was this translation helpful? Give feedback.
All reactions