Rotronic HF532 not connecting

[kentrols]

I have a number of HF532-WB1XXLXX Temp/RH units with HC2-S HygroClip2 sensors installed in an agricultural application. We are connecting the ethernet for remote monitoring/diagnostics and the two analog channels for signalling into the control system. We've just installed the 3rd unit (the first 2 installed and worked without issue) but for this unit we're not getting any analog signals. I can see the HF532 on the network at its static IP address using the Digi Device Discovery app and can open its webpage using the default login credentials. All of the settings appear identical to the 2 working units but when I try to connect to the HF532 using HW4, nothing appears. I have HW4 opened with the 2 working HF532 units but the 3rd will just not connect. I've tried "Search for Ethernet Master" and "Search for a specific IP" with no success. What does it indicate when HW4 cannot connect to an HF532 that can be seen with the discovery device? Is it an issue with the HC2-S?

[kentrols]

Dario

Thanks for your quick response. The network doesn't have a DHCP server but I tried a few different IP addresses with the same result. To clarify, I can see the HF532 on the network and can open the webpage and view/change settings without issue. The issue is connecting to the unit with HW4 and viewing the sensor settings and readings.

Regards,
Ken

[Purmse]

I was lucky to find this article when I was having the same problem. basket random

[vardanantone]

It sounds like the issue may not be directly related to the HC2-S sensor, as the device is visible on the network and accessible via its IP address. Since you're able to connect to the other HF532 units, there are a few potential areas to check: Network Configuration, HW4 Software Version, Firewall/Security Settings, Analog Channel Configuration, Sensor Calibration or Failure

1.tubidy, 2.tubidy, 3.tubidy

[miabrown11]

That's frustrating! I've had similar issues with network devices before. love tester

[nocturnalhelm]

Turn off any firewall or antivirus software that might be preventing the HF532 from communicating with your computer. If the HF532 is linked to a network, make sure it has authorization to speak with your PC.

[sofiacarsol]

The problem is still that the HF532 connection is unstable.
tap tap shots

[andrewbevis]

Hey, I ran into a similar headache with my HF532 units a while back—two worked fine, but the third just wouldn’t play nice with HW4, even though I could ping it and access the webpage. Since you’re seeing it on the network but HW4 isn’t connecting, it’s probably not the HC2-S sensor itself—those are pretty reliable. I’d double-check the firmware version on the third unit; a mismatch with HW4 can cause that disconnect. Also, maybe try a different Ethernet cable or port - just to rule out a flaky connection. While troubleshooting mine, I took a quick break to mess around with block breaker to clear my head, and it actually helped me come back with a fresh perspective. Let us know how it goes!

[truthridaa]

Hey, I ran into a similar headache with my HF532 units a while back—two worked fine, but the third just wouldn’t play nice with HW4, even though I could ping it and access the webpage. Since you’re seeing it on the network but HW4 isn’t connecting, it’s probably not the HC2-S sensor itself—those are pretty reliable. I’d double-check the firmware version on the third unit; a mismatch with HW4 can cause that disconnect. Go on over to Geometry Dash Lite homepage for a plethora of fascinating games if you're in the mood for more diversity. Also, maybe try a different Ethernet cable or port - just to rule out a flaky connection. While troubleshooting mine, I took a quick break to mess around with to clear my head, and it actually helped me come back with a fresh perspective. Let us know how it goes!

Totally agree with this approach—if you can ping the unit and access the web interface, the hardware’s likely fine. Firmware mismatch is a sneaky culprit and worth checking right away. Swapping cables or ports is also a good low-effort test to rule out simple issues. And honestly, stepping away for a bit like you did with block breaker is underrated—it really helps reset your brain during troubleshooting. Curious to hear if any of those steps fix it!

[Mitchelly]

It could be a configuration issue or incorrect analog settings. Please check your device settings and connections to determine the cause.
snow road

[dianereese]

I’ve run into a similar issue before with the HF532 units. Make sure HW4 is fully up to date and check that the HF532 isn’t set to Modbus or another protocol mode that HW4 can’t read. Also, double-check that the unit has HW4 support enabled in the config — this is sometimes disabled by default.

It’s less likely to be the HC2-S sensor if you’re not getting any analog output either — that might point to a wiring or configuration issue on the analog side (wrong scaling, range, or mapping). I know this isn't geometry dash lite, but troubleshooting can feel like jumping through levels — one small misstep in setup and nothing works right.

Hope that helps!