@mcm1957 I mean the modbus adapter, the main point that I want to be able to do this for is so that I can update all of the instances at once if I need to make changes instead of having to manually go through each of the instances.
NEWS
Latest posts made by Jack 3
-
RE: Automatic Instance Generation
-
Automatic Instance Generation
I would like to be able to automatically generate an instance (or at most with 1 or 2 clicks) when I connect a new TCP device with a predetermined and known IP adress. Does anybody have any tips for this? I tried using the JavaScript adapter but I couldn't find any node modules which had this functionality. Thanks in advance.
-
RE: JavaScript adapter wont detect modbus-serial
2024-07-09 09:07:46.559 - error: modbus.0 (604) Socket Error 2024-07-09 09:07:46.564 - error: modbus.0 (604) Client in error state. 2024-07-09 09:07:46.564 - warn: modbus.0 (604) On error: {"errno":-4039,"code":"ETIMEDOUT","syscall":"connect","address":"131.246.75.233","port":5020} 2024-07-09 09:07:46.592 - error: modbus.1 (12848) Socket Error 2024-07-09 09:07:46.601 - error: modbus.1 (12848) Client in error state. 2024-07-09 09:07:46.601 - warn: modbus.1 (12848) On error: {"errno":-4078,"code":"ECONNREFUSED","syscall":"connect","address":"127.0.0.1","port":502} 2024-07-09 09:08:47.615 - error: modbus.1 (12848) Socket Error 2024-07-09 09:08:47.615 - error: modbus.1 (12848) Client in error state. 2024-07-09 09:08:47.615 - warn: modbus.1 (12848) On error: {"errno":-4078,"code":"ECONNREFUSED","syscall":"connect","address":"127.0.0.1","port":502} 2024-07-09 09:09:08.775 - error: modbus.0 (604) Socket Error 2024-07-09 09:09:08.775 - error: modbus.0 (604) Client in error state. 2024-07-09 09:09:08.775 - warn: modbus.0 (604) On error: {"errno":-4039,"code":"ETIMEDOUT","syscall":"connect","address":"131.246.75.233","port":5020} 2024-07-09 09:09:12.133 - info: admin.0 (5516) ==> Connected system.user.admin from ::1 2024-07-09 09:09:12.221 - error: host.PCRT49 cannot call visUtils: Not exists 2024-07-09 09:09:18.930 - info: admin.0 (5516) ==> Connected system.user.admin from ::1 2024-07-09 09:09:21.197 - info: javascript.0 (12652) Start JavaScript script.js.Test (Javascript/js) 2024-07-09 09:09:21.206 - error: javascript.0 (12652) script.js.Test compile failed: at script.js.Test:4
is that what you mean?
-
RE: JavaScript adapter wont detect modbus-serial
@fastfoot I ran the command again using the directory you said and Im still getting the same errors, I can even see in the node_modules directory that I do have Modbus-serial installed
-
RE: JavaScript adapter wont detect modbus-serial
@fastfoot Thats the thing, I do not have an /opt/iobroker directory, it does not exist is what the terminal tells me
-
RE: JavaScript adapter wont detect modbus-serial
@fastfoot I tried this code which I copied and edited from the modbus serial documentation and I am getting these errors
-
RE: JavaScript adapter wont detect modbus-serial
@homoran Im still getting this error even after adding modbus-serial to the instance, are there perhaps other steps I can take to troubleshoot this?
-
RE: JavaScript adapter wont detect modbus-serial
@homoran I did add it to the npm modules in the javascript instance but there is still the error, I think maybe its because I didnt download it to the correct directory , where do I need to download it to?
-
RE: JavaScript adapter wont detect modbus-serial
@homoran i did so by typing 'npm install modbus-serial' into the terminal in iobroker, im not sure what you mean by add the npm package via its instance.