I have a RNL36 and and a 823A. I use the RNL alarm output,. I see two or three variations in functionality (latest firmware installed) and do not understand what is happening. Is there a certain sequence in the firmware that causes this? To me it looks like the 823 sends an alarm, and it decides to yes or no switch on the spotlight. The RNL receives the alarm, switches on the alarm output, but might not start recording. So i have condition 1, all works fine. Conditions 2 and 3 are false alarms and for some reason almost only in the early morning before sunrise hours, and in the evening after sunset And it is then sometimes almost continuously. What is causing this and how can i reduce it? Alarm delay setting has no effect, sensitivity als not. Rain doesn't seem to affect it, and any moving trees/bushes are blocked. Pet's are disabled and I use a minimum object size

1) I walk outside in the dark and it works great; 823 LED lights go on, 823 tracks me, RNL36 records, and alarm output (a light) goes on
2) Alarm output light goes on, nothing happening outside, no recording, and no 823 spotlight (happens much less with current firmware)
3) As 2) but it starts recording too

Not sure how it works, but my 823A detects something, and the RLN36 alarm out I've connected to a light via a wireless Thrust switch is activated immediately. The light goes on, the camera's white LED's (at night) do not go on, and it does not start recording. It looks to me the alarm is activated immediately, while the software decides it's not a real alarm. Would a 0.5 second delay in alarm out activation avoid this?

And then i can not imagine people rewiring their house to utilize the 4 outputs, so a*sume they use like me wireless (Thrust like) switches. In that case it looks to me one could simulate one getting out of bed and switch on lights if (just thinking aloud)

• the RLN relay would only be activated for less than a second, just enough to activate the switch
• the Thrust like switches have an option to select auto off at a selectable time
• if the RLN 36 would then have delay times (real delays from the alarm on) at 0 (ot the 0.5) seconds at output 1 (for those wanting to have lights on immediately, and 15, 30, 45 delays on output 2, 3, and 4

And the Thrust switch only works ok if the alarm out is set to Normally Closed

Never mind, left everything without power for an hour, switched it back on and now it works fine. I did try that before, but just for a minute or two.

Camera (823A) and NVR (RNL36) connected to Router. Both show up as connected in client. Camera simply named Channnel01. The camera works in Client and provides llve view in all 3 quality settings. But I can not get it to load on the NVR. Channel01 states connection failed. Before it worked with the camera connected to the NVR, but then I can not easily do an eventual camera security update. Am I doing something wrong?

I have the RLN36 with a RCL823A. Now playing with the alarm outputs to switch on lights thu wireless Thrust switches. That seems to work fine. However I notice I get short alarms, alarm out is activated, light goes on for up to 10-12 seconds, but no video recording. Also LED spot lights on the 823 are not activated. On longer alarm durations the lights go on, recording starts, and LED spot lights go on. I can't figure out what is causing this?

I have modified the RLN36, removed the cooling fans and fitted a SSD. I used a 320mm long 20x20x20 aluminium U section I had as heatsink. Measured with a fluke infrared, the processor stays at 45-47C surface temp, the U section is at 30C on top of it, and 28C at the ends. This at 20C ambient. Also used two pieces of light foam as a spring between the U section and cover, it ensures a minimal contact force with the processor. The fan connectors are impossible to remove due to the red glue. I've cut the wires at the connector and used tape as insulation as the alu profile sits right above it. The RLN36 now makes no noise at all, except for the alarm relay when activated. It only records on alarm.