Ethernet RJ45 TCP/IP Relay Remote Control Board 8-Channel Relay Module Board 10A Relay Controller Network Relay Switch Controller Module for Smart Home Control 250V/AC with Case(Black)

Like others, this unit is junk. Access the web page, try to control any relay and the unit locks up. It stops responding, can't even ping the device, it just goes off in a corner and requires a power cycle to restart communication again.Also tried controlling via the very awkward 'port' GET API. Same nonsense. After sending a single command, the unit locks up and requires a reboot.Total waste of time and money. There are others for the same price, ordered two of them, both work fine. It's the particular unit this seller is selling that is junk.Hopefully I can still return and get my $50 back. This one's a doorstop.

Believe all the reviews that say this is junk. I could not get the device to successfully change the ip address. Sending back.

This device works fine for about 1-2 hours, then the web interface stops responding, and the device stops responding to pings at its IP address. If you then remove power from the board for 2 seconds and then supply power again, it works again for about 1-2 hours. It would be OK for a student science project, experimentation or learning to write programs for control boards, but since it cannot stay working for longer than 1-2 hours, it is unsuitable for serious use.On the plus side, running for 1-2 hours it is better than the cheaper web control relay boards on Amazon. Those usually only last for about 3-5 relay cycles (assuming you have any load attached to the relays) and then they stop running until they are power cycled. So this would be my board of choice for a short-run experiment or project, but again let me emphasize, it will not run more than 1-2 hours without locking up.

when i saw these last year for $40 i thought what a good deal but i soon learned you get what you pay for. how could someone screw up going to an IP address and turning on a relay be so difficult. well these guys answered the question. the unit locks up and you can not reach the IP address and it has to be manually power cycled, maybe multiple times before it starts to respond again. what good is remote IP relay technology if you have to be on site to power cycle it. Hopefully the next person will take this warning and spend the extra hundred bucks and buy a real unit.

Items ordered work intermittently, vendor does not provide answers to questions.

When propperly supplied power would not boot

The NC800 seems to be very stable when being controlled via the REST API. I have yet to have it lock up when using only REST API commands such as the following.Turn off all relays: GET 192.168.1.10:80/30000/44(or from a command line, type "curl 192.168.1.10:80/30000/44")Turn on all relays: GET 192.168.1.10:80/30000/45However, accessing the NC800 via a web browser is VERY unreliable and seems to quicky cause the device to lock up and stop responding. I still give it four stars because it is a great low-cost option for controlling relays via REST API commands over routable TCP/IP.If you are looking for a low-cost interface with 8 relays that can be controlled via REST API (http commands), this unit works great when controlled via a home automation controller (such as those from Universal Devices) or when controlling it via scripting or code. But again, controlling it from a Web browser seems to quickly lock it up, so I would avoid using the browser interface. (See "Notes on calling APIs" toward the bottom for more details.)Contrary to NC800 reviews elsewhere on Amazon, the NC800 does in fact use TCP/IP, and it can be routed via port forwarding. See "Notes on Port/Routing" toward the bottom for more details.Examples of the REST API commands are below, using the default 192.168.1.10 address for these examples. (Substitute the word "curl" for "GET" when issuing these commands from a command line using curl).Turn off all relays: GET 192.168.1.10:80/30000/44(or from a command line, type "curl 192.168.1.10:80/30000/44")Turn on all relays: GET 192.168.1.10:80/30000/45Turn off relay #1: GET 192.168.1.10:80/30000/00Turn on relay #1: GET 192.168.1.10:80/30000/01Turn off relay #2: GET 192.168.1.10:80/30000/02Turn on relay #2: GET 192.168.1.10:80/30000/03Turn off relay #3: GET 192.168.1.10:80/30000/04Turn on relay #3: GET 192.168.1.10:80/30000/05Turn off relay #4: GET 192.168.1.10:80/30000/06Turn on relay #4: GET 192.168.1.10:80/30000/07Turn off relay #5: GET 192.168.1.10:80/30000/08Turn on relay #5: GET 192.168.1.10:80/30000/09Turn off relay #6: GET 192.168.1.10:80/30000/10Turn on relay #6: GET 192.168.1.10:80/30000/11Turn off relay #7: GET 192.168.1.10:80/30000/12Turn on relay #7: GET 192.168.1.10:80/30000/13Turn off relay #8: GET 192.168.1.10:80/30000/14Turn on relay #8: GET 192.168.1.10:80/30000/15Changing network settings:You can change the TCP/IP network address via a web browser at the following URL (assuming the device has default IP address 192.168.1.10)http://192.168.0.92/30000/41Notes on Port/Routing:Please note that the NC800 ALWAYS uses port 80 (e.g. 192.168.1.10:80) and changing the "port" via the NC800 network settings does NOT actually change the TCP/IP port. The default "port" 30000 is not actually the TCP/IP port at all, but rather the prefix of the URL for the REST API commands. For example, the default for turning on all relays is 192.168.1.10:80/30000/45, but if you change the "port" from 30000 to 40000, all you actually do is change the URL to 192.168.1.10:80/40000/45, while port 80 remains the same (note, since port 80 is always the default for HTTP, both "192.168.1.10:80/30000/45" and "192.168.1.10/30000/45" are effectively the same URL, with or without specifying port 80.) This means you can indeed set up port forwarding from a router, using port 80 from the NC800, and forwarding that to any port you choose. But note that the NC800 has no security, so it will be wide open to the Internet.)Notes on calling APIs: In my experience, the best way to control the NC800 devices is using the REST API, which can be called from a home automation controller, a script, a software application, or via a command line using curl. You can use the "curl" command from a CLI (Command Line Interface) such as the command prompt or PowerShell in Windows, a Windows Subsystem for Linux shell, or a terminal shell in Mac OS or Linux, etc.