Resolve Node-RED/CODESYS Connectivity Issue

@Eliteinno

hello, The clue that tells me exactly where this problem lives is that UA Expert reads your variables as Good while Node-RED's browser comes back empty, since that rules out the server and the variables themselves entirely and points straight at how the Node-RED OPC UA node is browsing. It usually means one of two things, either a namespace and NodeId mismatch, since your example ns=0;i=85 is a standard OPC UA server node rather than your CODESYS application variables, which typically sit in a different namespace like ns=4 under the application object, or a security and session setting where UA Expert negotiates the connection differently than the Node-RED node is configured to. So the real fix is aligning the Node-RED node's browsing and security settings with how your CODESYS server actually exposes its variables, not rebuilding anything. So I would start by browsing the address space to find where your warehouse variables genuinely live in the namespace, since UA Expert can show you that tree, then point Node-RED at the correct namespace and node path, and match the security policy and session settings that UA Expert is successfully using, since a mismatch there is exactly what produces a "Done" with no items. Once the connection reads and writes cleanly, completing the dashboard, the status indicators, gauges, and the start, stop, and reset controls, is straightforward. Since your CODESYS project and HMI must stay untouched, I would work purely on the Node-RED side connecting to your existing OPC UA server, so nothing on the PLC or HMI changes. In UA Expert, what namespace and NodeId do your actual warehouse variables sit under, since if they are ns=4 rather than ns=0 that likely explains the empty browse immediately? And is your CODESYS OPC UA server set to allow anonymous connections, or does it require a security policy and certificate, since Node-RED needs to match whatever UA Expert is using to connect? have a nice day.

@jafarali14

Hi there, Your setup is clear: the **CODESYS PLC/HMI already works**, UA Expert confirms the OPC UA variables are healthy, and the remaining blocker is getting Node-RED to browse/read those same nodes reliably without touching the existing HMI. I have 8+ years of experience with Node.js, REST/API integrations, real-time dashboards, WebSockets, background processing, and automation systems. I can troubleshoot the OPC UA endpoint, namespace/NodeId configuration, browse permissions, security mode/policy, and Node-RED OPC UA node configuration before rebuilding anything unnecessarily. I can either fix your current flow or create a clean Node-RED dashboard that displays System Running, Processing Active, Emergency Stop, Fault status, order information, counters, timers, and processing-time charts. For controls such as Start/Stop/Reset and Order Request, I’ll use proper OPC UA writes and validate the PLC response rather than simply changing dashboard values. I’ll keep the existing CODESYS project and HMI untouched and test the Node-RED connection against the same variables confirmed through UA Expert. I can also document the final endpoint, NodeIds, flow configuration, and deployment steps so you can maintain it afterward. Send me your Node-RED flow, variable/NodeId list, and UA Expert configuration, and I can start by identifying why the browser is returning no items. Best, Jafarali

@Govind2892590

Hi, I would like to grab this opportunity and will work till you get 100% satisfied with my work. I just applied after read your job posting carefully and I believe that I am good fit to your project. I'm a serious bidder. I will satisfy you with my high skills! I am an expert which have 10+ years of experience on Mobile App Development, iPhone, User Interface / IA, PhoneGap, Mobile App Testing, Swift, Google Maps API, Web Development, iOS Development, Mobile Development I am looking forward to meet you to discuss the further detail about this project. Looking forward to hearing from you. Warm Regards

@dmytrot16

⭐⭐⭐Hello. The key issue here is not the dashboard itself—it’s getting Node-RED to correctly discover and communicate with the CODESYS OPC UA namespace while keeping your working HMI completely untouched. Since UA Expert already reports the variables as Good, I would first trace the Node-RED endpoint, namespace/NodeId handling, security settings, and browser configuration before rebuilding anything. I can fix the existing Node-RED OPC UA flow or build a clean dashboard from scratch with live PLC status, order information, timers, gauges/charts, and Start/Stop/Reset controls. I’ll work directly with your existing CODESYS OPC UA server and keep the PLC logic and CODESYS HMI unchanged. I can also validate read/write operations against the actual NodeIds rather than relying only on browser discovery. This fits my Full Stack and automation experience with Node.js, real-time systems, APIs, dashboards, and industrial data integration. I’ll keep the final Node-RED flow organized and documented so you can maintain it easily. Please send the current Node-RED flow, UA Expert configuration, and CODESYS variable/NodeId list. I can start by identifying why the browser returns “Done” without the expected nodes and then complete the dashboard. Best regards, Dmytro

@sandipm1307

With my extensive background in automation engineering, I am perfectly equipped to troubleshoot and resolve your Node-RED/CODESYS connectivity issue. My experience working across a range of industrial automation technologies including PLC programming, HMI design and system integration means I'm adept at finding robust solutions to complex problems such as the one you are currently experiencing. I have detailed knowledge of OPC UA, the communication protocol responsible for connecting your CODESYS PLC with the Node-RED dashboard, which will be extremely valuable in resolving this issue. My proficiency with Node.js, JavaScript and deep understanding of Node-RED will ensure I can debug your current setup effectively or create a new dashboard that flawlessly communicates with your existing CODESYS server.

@SupeRFreelancerz

Hi, I can fix your Node-RED ↔ CODESYS OPC UA connection and complete the dashboard without touching your existing CODESYS HMI or PLC logic. I’ll handle: Diagnose and fix the OPC UA browsing/NodeId issues Connect Node-RED reliably to your existing CODESYS OPC UA server Read/write PLC variables correctly Build the dashboard for status, orders, timers, faults, and gauges Add Start/Stop/Reset and other required controls Ensure real-time updates and reliable communication Test the complete flow against UA Expert and CODESYS simulation I can work with your existing Node-RED flow or build a clean one from scratch, depending on what is more reliable. Goal: a stable, real-time Node-RED dashboard communicating with your CODESYS PLC while leaving your existing HMI completely untouched. Ready to review your Node-RED flow and OPC UA configuration and get it working.

@SerhioDiamond

Hello there , Good morning! I’ve carefully checked your requirements and really interested in this job. I’m full stack node.js developer working at large-scale apps as a lead developer with U.S. and European teams. I’m offering best quality and highest performance at lowest price. I can complete your project on time and your will experience great satisfaction with me. I’m well versed in React/Redux, Angular JS, Node JS, Ruby on Rails, html/css as well as javascript and jquery. I have rich experienced in Industrial Engineering, PLC & SCADA, Software Development, Data Visualization, API Integration, Automation, Technical Support, Web Development, Node.js and JavaScript. For more information about me, please refer to my portfolios. I’m ready to discuss your project and start immediately. "Done" Looking forward to hearing you back and discussing all details.. Your Sincerely

@Jay6011

Hi, I can help troubleshoot the Node-RED OPC UA connection to your existing CODESYS PLC and complete the dashboard without modifying or disturbing your current CODESYS HMI. I understand that the OPC UA server is already working correctly in UA Expert, so I would first focus on the Node-RED side, particularly the endpoint configuration, namespace/NodeId handling, OPC UA client security settings, browsing configuration, and compatibility between the Node-RED OPC UA nodes and CODESYS. Once the connection is working, I can build the dashboard for the required PLC variables and controls, including System Running, Processing Active, Emergency Stop, Fault status, Order ID, order counters, timers, Start/Stop/Reset, order signals and processing-time visualization. I’m experienced with Node.js, JavaScript, backend integration, APIs and real-time data-driven web applications, and I can work from your existing CODESYS variable list and Node-RED flow rather than rebuilding what is already working. Please share the current Node-RED flow, OPC UA configuration, NodeIds and the exact browser/error output. I can first identify why the nodes are not being browsed and then complete the dashboard. Regards, Jay Patel

@Maxxionn

Hi , You need an expert in Web Development, Data Visualization, Node.js, Industrial Engineering, API Integration, Software Development, Automation, Technical Support, JavaScript and PLC & SCADA, and I have a tailor-made solution ready for you. Your project brief instantly reminded me of a recent client who faced similar challenges, and I know exactly how to execute this flawlessly for your specific needs. To ensure we hit the ground running, I have three quick questions: Are there any additional technical details or constraints not mentioned in the brief? What is the primary hurdle currently blocking your progress on this? What is your strict timeline for completion? Why trust me with your project? The Record: 250+ Projects. 6+ Years. 100+ consecutive 5-star reviews. The Standard: Zero misses. I don’t just finish the job; I guarantee flawless execution. The Availability: Full-time freelancer, online 9 AM - 9 PM EST. My biggest "heavy-hitter" projects are kept off my public portfolio to protect client confidentiality. Click 'CHAT', and I’ll immediately send over relevant, private samples so you can see the standard of my work firsthand. Best regards, Muhammad Arsalan

@bhargav922002

Hello, I’m bharghav, and I bring a decade of experience in matching job skills, particularly in JavaScript, Node.js, and web development. I understand that you need assistance in establishing a seamless connection between Node-RED and your existing CODESYS OPC UA server. My approach will ensure that your current CODESYS HMI remains unaffected while we resolve the issues you're facing with Node-RED's OPC UA browser. By troubleshooting your existing setup or creating a new dashboard, I will ensure the PLC variables are accurately displayed and interactive controls are integrated.

@CliveMSoftware

I have hands-on experience with Node-RED OPC UA connectivity and PLC integration. I'll start by diagnosing why your OPC UA browser isn't discovering nodes despite UA Expert working correctly, which often involves endpoint configuration, security settings, or node ID formatting issues. Once the connection is verified, I'll build out your complete Node-RED dashboard with all the display elements and controls you've listed, including the gauges, status indicators, and order monitoring widgets. I can deliver a fully functional dashboard that mirrors your CODESYS HMI without touching your existing setup, and I'll provide clear documentation on how to maintain and extend it. I'm ready to start immediately with the screenshots and variable list you have.

@harrisono6

Hello, I hope you're having a great day. I've worked on several similar builds where OPC UA servers check out fine in UA Expert but behave differently inside Node-RED, so this pattern is familiar. On one past project, the fix came down to how the endpoint was being resolved, since localhost can point to IPv6 while the server listens on IPv4. I'd usually start by comparing your Node-RED OPC UA node config against what UA Expert shows, then verify the security policy and endpoint URL match exactly. We can also test with a minimal flow before touching your dashboard. If you have ten minutes, I'd like to compare notes on your Node-RED flow and the exact errors you're seeing, since that'll tell us whether to fix the browsing or rebuild fresh. Thank you, Harrison

@Alexwebo23

Hi I see you're dealing with a tricky Node-RED and CODESYS OPC UA connectivity issue, where the Browser isn't browsing nodes even when your setup shows a "Done" status. This sounds like a common hurdle related to incorrect endpoint configurations or an issue with Node-RED's OPC UA nodes not properly handling the variable browsing feature. I'd start by inspecting the way Node-RED interacts with the OPC UA server and ensure there's no conflict or misconfiguration. js and JavaScript for automation and data visualization tasks. I’ve previously tackled similar issues while building automation systems that required precise control over factory operations via OPC UA. Your detailed setup with even the smallest aspects considered shows you've done thorough groundwork, which I appreciate. I can help you resolve this connection issue or build a new Node-RED dashboard as you need. Let’s dive into your existing configuration and get it working smoothly. Thanks, Oswaldo

@joshuajsaunders

The main issue here is the Node-RED OPC UA Browser not successfully browsing your CODESYS nodes. This can lead to delays and frustration, especially since your existing CODESYS HMI is functioning well. If the variables aren't visible in Node-RED, it could stall the entire dashboard project, costing time and resources. I'd start by troubleshooting the Node-RED OPC UA configuration first. Ensuring that the endpoint settings align perfectly with your CODESYS OPC UA server is crucial. Often, minor misconfigurations can prevent nodes from appearing. I can also check your NodeIds and verify they match with what’s published on the OPC UA server. I've tackled similar connectivity issues before, revising configurations and testing until every variable appears as it should. Revisions are part of my process, not an afterthought. Could you share the specific errors you're seeing in Node-RED? Also, do you have a deadline for this project?

@BaileyG07

Hi there! It sounds like you've made significant progress on your Smart Warehouse System, but I understand the frustration of facing connectivity issues between Node-RED and your CODESYS OPC UA server. Ensuring a seamless integration while maintaining your existing setup is crucial. With my experience in developing Node-RED dashboards and integrating OPC UA connections, I can diagnose and resolve the browsing issue. I’ll leverage tools like UA Expert to pinpoint the problem and ensure your CODESYS variables display correctly in Node-RED. Whether it’s fixing the existing setup or creating a new dashboard, I’m equipped to deliver a solution that meets your requirements and maintains the integrity of your current HMI. You can expect clear communication, timely execution, and thorough testing to ensure everything runs smoothly. Let’s get started on this—could you share any specific errors you’ve encountered in Node-RED? This will help me tackle the issue more effectively.

@patricko098

GIVE ME 30 SECONDS TO SHOW YOU WHY I'M THE RIGHT FIT FOR THIS PROJECT. I recently completed a project involving the integration of a Node-RED dashboard with a PLC system via OPC UA, resulting in seamless data visualization and control without disrupting existing HMI setups. With over five years of experience in industrial automation and IoT, I have a strong grasp of CODESYS, OPC UA, and Node-RED, making me well-suited to resolve your connectivity issues effectively. I understand your goal is to create a functional Node-RED dashboard that mirrors your current CODESYS HMI while ensuring your existing setup remains intact. I will troubleshoot the Node-RED connection and ensure proper variable mapping. My focus will be on clear communication and timely execution to achieve lasting success for your project. I am confident that my expertise will bring your vision to life. The difference between an average result and an exceptional one is usually decided before the work even begins. Regards Patrick

@christopherm0620

Hi, Most likely cause is an OPC UA client mismatch: UA Expert succeeds because it accepted the CODESYS server certificate and namespace, while Node-RED's opcua nodes are failing on certificate trust, endpoint security policy, or incorrect namespaceIndex/nodeId paths, preventing Browse from returning items. I have implemented Node-RED dashboards that read and write CODESYS PLC variables via OPC UA, and I have resolved similar issues where Node-RED could not browse a CODESYS OPC UA server. In those engagements I diagnosed certificate trust stores, aligned securityPolicy and securityMode settings, adjusted endpoint URLs to include the correct port and path, and fixed namespaceIndex/nodeId mapping so variables appear in the browser and can be subscribed. I also built dashboard controls to mirror existing HMI interactions without touching the CODESYS HMI. I will first reproduce the failure remotely or on a supplied capture: enable debug logs for node-red-contrib-opcua, attempt a browse with node-opcua CLI to compare responses, and inspect the CODESYS server certificate and endpoint configuration. If the problem is certificate trust I will import or accept the CODESYS certificate into Node-RED's OPC UA store and set matching securityPolicy/securityMode; if the issue is namespaceIndex or nodeId paths I will map variable nodes directly. Once browsing is fixed I will create dashboard UI widgets reflecting your HMI controls, with Read/Write nodes and subscriptions for live updates. - Can you provide the Node-RED logs from the OPC UA nodes and the exact endpoint URL you use to connect to CODESYS? - Do you prefer I attempt a remote session to debug directly, or would you like a written checklist and configuration changes I can apply? Looking forward to hearing from you, Christopher

@JohanEngelb

THE NODE-RED BROWSER NEEDS A TUNE-UP TO SEE YOUR PLC VARIABLES CLEARLY. I'd love to help you resolve this connectivity challenge. With my experience in integrating Node-RED with various OPC UA servers, I understand the nuances of maintaining existing systems while enhancing functionality. Have you considered checking the security settings on your OPC UA server? Sometimes those can block browsing access. Also, are you using the correct namespaces in Node-RED for your variables? The worst-case scenario is a free consultation to troubleshoot together and explore your options. Regards, Johan

@claudiomf1

Hi, I work with Node-RED, OPC UA and industrial dashboards. I can fix your CODESYS to Node-RED connection (endpoint, security policy, NodeId mapping) and complete the warehouse monitoring dashboard with live PLC variables — without touching your existing CODESYS HMI. Remote session + handover docs included. Claudio