I recently purchased an ADC-T40K-HD with two ADC-S40-T remote temp/humidity sensors. The thermostat works great, Ive set up schedules and confirming fire safety rules. The thermostat is in the hallway about 30 feet from the main Qolsys IQ Panel 4, and the RTS are in bedrooms off the hallway, about 20 feet from thermostat, and 40-50 ft from the main panel.
The RTS devices constantly lose connectivity. When learning I had them in their final location, and also ran a network rediscovery test. The RTS devices constantly report malfunction, or will have extremely high temps reported (168 deree F). The zwave test will fail unless I run over from panel to RTS to move the cover off to allow the LED to show up (trigger it on). Same with a rediscovery. It’s almost like the RTS will not use the thermostat as a zwave hop. I’ve tried to manually set in the neighbors section. The network map constantly shows different configs, sometimes RTA connected to thermostat, other times directly to panel. Is there a way to exclude hopping directly from RTS to the panel, forcing it to go from panel > thermostat > RTS and back?
It’s almost like the RTS prefers direct connection to panel but barely has connectivity causing weird things to happen. For example, if I have the set point at 68-72 degrees, the thermostat will constantly switch from 69 degrees (hallway temp only) to 66 degrees (hallway thermostat + bedroom RTS(s)) which causes a click (heating turns on) every 30 seconds, then turns off when it loses connection to the RTS and reports 69 degrees again. Please help!
I’ve cleared and factory reset all three devices. Relearned them via panel > zwave add device > include option, then triggering from the 3 devices in their permanent locations.
I instantly noticed 2 malfunctions on the 2 RTS and ran a network rediscovery on all 3 devices via zwave diagnostics. It was successful for the thermostat but failed to find neighbors on the 2 RTS devices.
I have a Aeotec zwave plus network extender I could throw in the hallway, just weird that the thermostat can’t act as a hub. You’re free to run whichever commands you’d like. I’m wondering if because it is technically a mechanical thermostat instead of digital (like the T2000 / T3000) if that is why it can’t be a hop? I have the G, Y, W, R, and C wires connected.
Your thermostat is now reporting it is functioning as a repeater, so you should be good there. That doesn’t mean it is sufficient for the RTS to communicate though, so if you still see communication issues it would be good to add another repeater. If you have an Aeotec Z-wave repeater I would include it in the network and run a rediscovery.
I am not seeing any malfunctions reported right now. Are the temp sensors showing issues locally?
I was still experiencing issues with averaging the temps on the RTS. Ran a network map and saw the same issue so I added the repeater. Having the same problem after adding the repeater and factory resetting the RTS devices.
Is there a way via grouping/associations or last working route that I can tell the RTS to only use the repeater node as its primary hop to the iqpanel4? Do you think it is firmware related? The box says FW 1.0. I was also playing around with running network rediscoveries after adding the RTS and found that they will state ’ Neighbor Info Update Failed ’ unless I run over and remove the RTS backplate to trigger the LED.
That’s interesting, and it sounds like you did but just to 100% confirm after you added the repeater you deleted and re-added the RTS?
It is interesting that it is not reporting the same data I expect in ADC either. On another user system with the S40T, I can get link quality and neighbors reported for the temp sensors, but on yours neither are provided by the system in response.
Are you adding these via smart start? Delete the two RTS and try smart start on one and manual Z-wave add-device steps for the other. Any difference?
So I can’t use Smart Start, I’ve tried for 10 minutes holding the barcode (on device and packaging) up to the panel, trying to get the QR code fully in the box, trying different lighting. I’m probably doing something wrong there but I’ve held it up close, far, halfway, upside down, whatever I do it won’t read the QR codes for any of the zwave devices (repeater, RTS, thermostat).
I did factory reset and readd the RTS in their final destination after adding the repeater but I’m happy to do it again. I also tried to manually set the last working node so that everything connects to the repeater.
If you bring one of the temp sensors a little closer to the panel, half the distance roughly, and relearn it, do you see a significant change in its behavior?
I’ll try that out and let you know. I’m sure that I will see a change in behavior, but it’s a valid test to see if the RTS is even functioning the way it should when in good range of the panel.
I did try to move the RTS further away when relearning, trying to force it to connect to the repeater… It almost feels like it will try to lock to the main panel and ignore any nodes (repeater, thermostat) with a stronger connection.
The RTS is probably only 40 feet + 2 walls in between the panel, but I’ll move them in sight of the panel to see if they function properly without needing to hop through a device.
I’m curious on that other user system if their RTS is directly connected to the panel or has any hops in between.
You mentioned Smart Start - should I be able to do that to add them? What am I doing wrong with scanning the QR code? Does the QR code need to fill the entire box when the camera pops up, or do you normally hold it 6 inches away from the panel?
The other user’s RTS reports neighbor nodes used for hops. It is a much larger Z-wave network, but I would still expect a result for yours.
You should be able to use smart start for any of the devices. Have you rebooted your panel during the troubleshooting? I would do that first if smart start just doesn’t work at all.
Baby Room Temp - located on a banister about 20 ft from IQ Panel 4.
Master Bedroom Temp - located in the hallway, about halfway from where it was before (basically right next to the thermostat + repeater).
Received malfunction error on baby RTS, immediately after adding it back in. Ran a rediscovery on whole z-wave network (after resetting + adding RTS) and had the same Neighbor Info failure. It will rediscover if I quickly open the back of the RTS to trigger it on while the test is running. Almost like it stops communicating to save battery. I ran a rediscovery successfully by doing this last night and let it run overnight.
I might have some spare CR2450 batteries, but what are the chances, right? With my luck probably higher than you think…
Ill try a reboot, I did recently update firmware on the panel but it cant hurt to try.
