Cams / NVR Arrived - Have I Made a Mistake :-/

Nothing - then everything all at once!! A few notes: Turns out it's not possible to change my modem / router's default range from 192.168.0.x, it's fixed by the ISP who provide the (crappy) unit. So - following advice here, and elsewhere, I manually changed my MacBook's IP to 192.168.1.200. Hooked up the NVR to the router, open browser, tap in 192.168.1.108 - still nothing. Then I had a bit of a lightbulb moment, add https:// and I was in! (after dispatching Safari's security warning) :D

Worked through the initial setup, then the first I thing I did after that was navigate to the Display settings. Turns out the NVR display resolution was defaulted to 1280x1024. Changed it to 1920x1080, and it worked! Then to 3480x2160@30fps, and this works too!

Then to look at the IP situation. Setting > Network > TCP/IP > Modify > Mode - change from Static to DHCP > OK > Apply. Power down NVR, boot up again, check device connection status on the router, NVR now showing as 192.168.0.4, browse to et voila!

Think I need a lie down after that :D
 
Nothing - then everything all at once!! A few notes: Turns out it's not possible to change my modem / router's default range from 192.168.0.x, it's fixed by the ISP who provide the (crappy) unit. So - following advice here, and elsewhere, I manually changed my MacBook's IP to 192.168.1.200. Hooked up the NVR to the router, open browser, tap in 192.168.1.108 - still nothing. Then I had a bit of a lightbulb moment, add https:// and I was in! (after dispatching Safari's security warning) :D

Worked through the initial setup, then the first I thing I did after that was navigate to the Display settings. Turns out the NVR display resolution was defaulted to 1280x1024. Changed it to 1920x1080, and it worked! Then to 3480x2160@30fps, and this works too!

Then to look at the IP situation. Setting > Network > TCP/IP > Modify > Mode - change from Static to DHCP > OK > Apply. Power down NVR, boot up again, check device connection status on the router, NVR now showing as 192.168.0.4, browse to et voila!

Think I need a lie down after that :D
You can change the default range on the VM Hubs but it's best to leave it. What you might want to do now is to change the IP address of the NVR. You don't want it changing, which it can if set to DHCP. You can either set a reservation on the VM Hub so that the NVR always gets its current address or disable DHCP and set it statically. Virgin have a habit of remotely resetting their hubs when it suits them (the equivalent of you sticking a pin on the reset button) so setting a static address is preferable. With DHCP disabled set it to an unused address that's high in the range (that'll ensure the address doesn't get assigned to another device). I'd use 192.168.0.250 with the gateway set to 192.168.0.1. Primary DNS to a public DNS (8.8.8.8 or 1.1.1.1) and secondary DNS to your router/hub (192.168.0.1)
 
  • Like
Reactions: machineage
OK - changed it to a static IP, clicked on 'Test', which was green-lighted, applied & browsed to the new IP with success. The gateway is set to 192.168.0.1. Do I need to change anything else?
 
OK - plugged in each camera, one at a time, waited until each cam was registered & showing on Live. All three registered within a few minutes. Labelled each cam to its respective NVR port. I haven't changed any other settings yet. So I guess the next step is to get the cables made up, and carry out the physical installation. No going back now!
 
  • Haha
Reactions: mat200
Not nearly as fun as the bra size calculator!
 
There was some good info in this thread that I actually understood and can use. Not long ago, I was in the same boat as the OP and like...huh?? lol

Thanks @machineageage for this thread and the others for the easy to understand replies
 
Well, this is pretty hopeless then, I'm certainly out of ideas :rolleyes:

Hang in there .. once you've got it setup it will be nice and stable

( looks like he got it )

New folks, do expect it to take a bit of time to figure out the setup. Once you put into the time the first ID quality image you get will be a big payoff.
 
Last edited:
  • Like
Reactions: machineage
Well, it's been some months! I had a pressing 'situation' that required me to install cams. The presence of the cams alone appears to have solved that particular situation, at least for now!

@Madflamethrower glad the thread was of some use. It's a steep learning curve when you're stuck on the start-line!

I've done little with the system since installing it - I've not even set each cam up properly, something I must do. That said, the cams / NVR are working fine, and I can't imagine being without them now.

However, I've had plenty of issues - all to do with my accessing the NVR / cams on my MacBook, and the obvious issue of the non-native SmartPSS Lite, which is just painful to use on my MacBook. There have been so many glitches, I'd be here all day listing them. Similarly so when accessing the NVR via a browser. I've gotten to the point now of deciding to switch out the NVR, and move to SecuritySpy on a dedicated Mac mini.

My immediate issue is that of being unable to access the NVR with SmartPSS Lite. It started to not see the NVR ⛔️, and when I would try after leaving it a while, the NVR would magically become accessible again. Alas this got worse, to the point SmartPSS Lite no longer sees the NVR at all. I've tried uninstalling / reinstalling the app to no avail. When I first installed it, after sorting the IP issues, the NVR appeared first time when clicking on 'Devices'. Now, it just doesn't see it at all, searching for devices returns a blank. The IP range for searching is the same, the NVR IP is the same (192.168.0.250). Nothing has changed to my knowledge, and I can still access the NVR via a browser.

So, does anyone have any pointers I could try to get SmartPSS Lite communicating with my NVR again?

Many thanks :)
 
If it was a PC I would try to help but it sounds to me like you have Mac conflict issues and possibly networking issues. The thought that its an actual problem with SmartPSS is IMHO remote
 
Last edited:
  • Like
Reactions: machineage
Yes, I feel sure it's a compatibility issue. It's been glitchy from the get-go, and painful to use some features, like searching & clipping footage etc.
I think it stopped working completely around the time our clocks went forward one hour for British Summer Time. I just tried syncing the NVR clock to my computer, but that hasn't resolved the issue.