How to Bring Any Security NVR Into Ring Using ONVIF and a J‑TECH ENCH4 Encoder

Using a JTECH‑ENCH4 to encode the HDMI output of a security NVR into an ONVIF‑compatible H.264 stream is a powerful way to bring a non‑IP or closed‑ecosystem surveillance system into the Ring platform. This allows you to view your entire NVR’s live display, including all of its cameras, directly inside the Ring app. The encoder converts any HDMI feed, such as a multi‑camera grid, into a standard ONVIF camera stream that Ring Alarm Pro can recognize. This approach lets you preserve your existing cameras and NVR while gaining unified monitoring through Ring, making it ideal for users who want to integrate legacy security hardware with modern smart‑home systems without replacing their entire infrastructure.

Ring Alarm Pro requires ONVIF‑compatible cameras to provide:

• A valid ONVIF username
• A valid password
• A stream encoded with H.264 at 1080p or lower
  
• NVR must be on the same network as Ring Alarm Pro

However, the J‑Tech Digital JTECH‑ENCH4 does not expose ONVIF user management in its web interface. Common login attempts (admin, root, blank username) did not work for me because the ENCH4 internally uses an undocumented ONVIF account.

Through troubleshooting and elimination, I discovered the correct ONVIF username is:

username: viewer
password: <your password>

Ring authorization succeeded.

Ensure in the ENCH4 web interface, ONVIF Password is Disabled. 

Network settings:

• Enable DHCP
1. Find the IP in your router
2. Reserve the IP so the router assigns a static IP for the device
3. Access the web interface via the new static IP

My Main Stream settings

• FPS 30
• GOP 60
• Bitrate 4096
• Encoding size 1920x1080
• Bitrate CBR

Ring will sometimes say the device is not connected during Live View, just tap on the device again to reconnect and the device will display.

Enjoy

---

For reference Factory Reset:

• Hold RESET button 10 seconds until all three LEDs turn off, then release.
• Device reboots to default IP 192.168.1.168 and clears internal ONVIF state

PARTIAL FIXED: USB 3.0 External SSD not showing up in Disk Management XHCI

Symptom: Connecting an external USB 3.0 drive, in Windows, does not display in Disk Management. The only thing you see is the device is displayed in connected USB devices.

This happened to me with an Asus Zenbook UX series laptop. Attempts to connect a Samsung T3 drive failed. The drive would not show up in Disk Management, nor in the BIOS. Disabling XHCI in the BIOS allowed the drive to show in Windows 8.1, but this would revert the drive to USB 2.0 which is not what we want.

Re-enabling XHCI in the BIOS allowed for USB 3.0, but again, the Samsung T3 drive was still not displaying.

Solution: The Windows XHCI driver needs to be updated. Go to Device Manager, USB Controllers, then right click the Intel USB 3 XHCI device and select Update Driver Software.

NOTE: Not all External USB 3.0 drives will be compatible with the Windows driver and same goes with the Intel driver. The Samsung T3 works fine with the Windows driver, but another external drive randomly disconnects after copying files.

The driver will update with a Microsoft XHCI driver, and you should be able to see your drive in My Computer as well as Disk Management.

Intel WiDi Sucks

*********Update 9/4/13*********
WiDi hit a new level of suckiness. With the new driver update, my WiFi still randomly disconnects and is unable to reconnect. WiDi disconnects and is unable to reconnect. Now, the Netgear PTV2000 goes into some kind of screensaver mode and doesn't wake up out of it, so I have to disconnect the power to the device and reconnect power to the device.

I have updated the drivers listed on the Intel site. Download them here: http://www.intel.com/support/wireless/wtech/iwd/sb/CS-031109.htm
*****************************

I try not to complain about technologies because technology is always improving. There's always a positive. Intel's WiDi on the other hand was such a bad user experience, I felt the need to share this with those looking to invest in the technology.

Intel WiDi sucks as a wireless display technology, and here's why. The connection constantly disconnects, fails to connect, freezes, laggy refresh rate, and has poor driver updates. As a consumer, it's already frustrating finding the right driver, and to add to this frustration, Intel instructs the user to install multiple drivers and install the drivers in a specific order as well.

Once completing the driver installation, it's like rolling the dice to see if the WiDi connects to the display. Most of the time, the dice come up snake eyes. If you're lucky enough to get the device to connect, a few minutes later, the screen freezes, so disconnect, reconnect, rinse repeat.

If using WiDi as a monitor extension, the mouse cursor and screen have laggy refresh rates. There is an option to scale down the resolution to 720P, which helps with refresh rates, but if you're trying to do some gaming, you can forget about using WiDi.

My setup:

Asus Zenbook UX51VZ with latest Intel Wireless drivers
Netgear PTV2000 with updated firmware

[OUTDATED] iDEN Bluetooth DUN tether for Android [Dial Up Networking]

[OUTDATED] FYI, IDEN WILL BE SHUTTING DOWN IN THE NEXT YEAR OR SO.

In this post, we will connect to Boost Mobile's iDEN network to provide internet access to our Bluetooth Android device. The speed is capped at 19.2 Kilobits per second, so we'll run an optimized internet browser, Opera Mini, to maximize the bandwidth. Cost of keeping the pay as you go plan active is $10 for 3 months of use with unadvertised unlimited internet. You also get friendly and helpful Boost Mobile customer support and $0.20 a minute pay as you go minutes. Time and time again, I've had positive experiences with their customer support. I digress...

This setup is particularly useful for those looking for a WiFi only Android device (no carrier) with basic internet capabilities to check email, text, navigation, etc. Personally, when I'm going out, I only use Google Navigation, Fourquare, and Yelp so these apps run smoothly on the 19.2K connection. I want to balance between being human vs. being a machine plugged into the net, so this way, my internet access will be limited.

(leave me a message if you're interested in linux or palm device instructions)

Tutorial

My setup:

Boost Mobile Motorola i576
HTC EVO 3D rooted
Cyanogenmod 7 ROM

Phone Requirements:

• Boost Mobile Motorola iDEN phone (i335, i576, i776, etc.)
• Rooted phone with a stable version of Cyanogenmod 7 or 9 with packages hcitool, rfcomm, and pppd OR stable kernel with packages hcitool, rfcomm, and pppd
• Stable Bluetooth connection

Check to see if you have these packages by going into Terminal Emulator and typing hcitool --help, rfcomm --help, pppd --help. You should see a Version number and list of Options. If not, your kernel will not support Bluetooth DUN.

App Requirements:

• Terminal Emulator 
• ES File Explorer
• Q5Bluetooth Dialup Network
• chat binary (I compiled this using lophyte's guide. My chat binary is for Ice Cream Sandwich pppd 2.4.3, and it worked on my CM7 running Gingerbread pppd 2.4.3. Lophyte compiled a ppp 2.4.4 for Gingerbread to download here.)

Instructions:

Download and install above Apps and download the chat binary to your Android device 

Open ES File Explorer and go to Settings. Scroll all the way down and check/enable Root Explorer and Mount File System. While in Settings, go to Directory Settings and change the Home Directory to just /. Now go back to /sdcard/download/ and copy the chat file to /system/bin/ by long pressing the chat file and Copy to. 

Then browse to /system/bin/ and look for the chat file. Long press the chat file and a pop up will say Operations. Scroll down to Properties. Change permissions to rwx r-x r-x.

Pair your Android device to your Bluetooth Boost Mobile phone. Paired but not connected is what we want to see.

Go to Settings and turn off Wi-Fi

Open up Bluetooth Dial Up Network App

To get your Bluetooth Address and Channel, touch the Settings button to bring up "Search Device" and "Search Channel." Select "Search Channel" and you'll see your Bluetooth MAC address show up as XX:XX:XX:XX:XX:XX. Copy that down and copy the address down. Now go back to Bluetooth DUN App and paste the address and channel in.

Copy and paste the following Boost Mobile DUN Chat

ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO DIAL TONE' ABORT 'NO ANSWER' ABORT DELAYED
'' ATZ
OK-AT-OK "ATDTS=2"
CONNECT \d\c


Open up Terminal Emulator

su

setprop net.dns1 8.8.8.8 

Now you're connected. Bluetooth Tethering FTW.

For Developers Only:

Boost DUN Peer & Chat scripts for download

Boost Mobile DUN Peer Script

# This optionfile was generated by pppconfig 2.3.18.
# 
# 
hide-password
noauth
connect "/system/bin/chat -v -f /etc/chatscripts/boostchatscript"
debug
/dev/rfcomm0
38400
defaultroute
noipdefault
user replace_with_your_login_name
remotename boost
ipparam boost
usepeerdns
logfile /etc/ppp/peers/ppp.log