I agree, I do have to wait for the Nevo to wake up and connect to the wifi before it will send to the nevolink, which can be a bit frustrating. Is the connect direct RF not WiFi IP? That might be nice, I can deal with the wait but I can see where it would upset some people.

I have the same problem with first version and believe me I tried everything. ;-)
so i think i will jump to new one Thks

I know what you guys mean. I have programmed a decent amount of NevoSLs in my time and when using them with the NevoLink, I'd set them to always stay on so that my customers didn't have to put up with that delay issue.

The cool thing that I've discovered with the NevoS70 is that it associates to a WiFi network MUCH faster than the NevoSL did. Plus if you assign a static IP to the S70, it seems to associate even a little bit faster. I see an association time of anywhere from 3-4 seconds (not bad considering the NevoSL was usually around +12!!).

LordPhilomont, if you are going to use an S70 with a NevoLink, I'd highly suggest to set a static IP through the settings screen on the S70 itself.

Well that would seem like a good idea, but it doesn't like my subnet. I'm using the 10.0.1 subnet and it tells me it's invalid if I try to use a static IP, for example 10.0.1.201. Oh well, I'm keeping it powered on in the cradle most of the time and it seems to be working pretty well. Just FYI, also tried to set the NevoConnect to static 10.0.1.202 and it complained as well, but they run just fine using DHCP.

Oh yeah, and I pretty consistently get the little red triangle ! in the menu bar next to the wifi signal meter. Everything seems to be working fine, z-wave, wifi, nevo connect, but the icon persists. Not too worried about it, but it would be nice to know why. Is there an error log anywhere?

I was under the assumption that the red triangle (of death! lol) meant that a command didn't go through. That's odd how you are seeing the red triangle yet commands are still going through.... I guess if it works, it works.

As for the Nevo system not liking your static IP. I just use the simple 192.168 range and things seem to work just fine for me (both on the NevoLink and the S70). I don't know what to tell you. Although you might as well call tech support and see if they can help you.

If your NevoS70 is already connected to your WiFi network, hold down the "Home" button on the front of the remote for about 3-5 seconds and you'll hear a beep. Back on your computer (which obviously has to be on the same network at the time), NevoStudio Pro will display a window saying that a Nevo remote is trying to communicate to it.

For some reason, after hearing the beep on the S70, it doesn't always seem to connect, so just try it again and usually it'll work the second time if needed.

Oh yeah, also make sure that in the Tools menu of NevoStudio Pro, the "Enable Wireless Programming" option is checked.

The cool thing is that configs seem to download even faster using WiFi than USB. >:-)

That totally rocks! In NevoStudio Pro it just connected, no message, just the little icon in the bottom right suddenly went ON. Sweet! :) I and my USB hatch cover thank you Ry-dog!

No problem!

I'll admit that when I first found out about that feature I thought I'd never use it since it's not very hard to just connect the controller with a cable, but after being in situations where my USB cable is lost or in another room, I've started turning to this feature much more often.

Yes, I can be a little lazy sometimes, lol.

Hi guys!

I'm now truying to make Nevo S70, Nevo Connect and various Merten z-wave devices working together. There is one problem: we can organize a z-wave net only via Nevo S70 or one of Merten sensors as a primary controller. So, if I have found some Merten sensor by Merten configurator, I can't find it by Nevo anymore. And, as well, I can't find any sensor by Merten controller, if it was previously found by Nevo. But I need to organize connections between different sensors by Merten configurator, and in the same time I need to control some of them by Nevo.

How can I find z-wave devices both by Nevo and Merten configurator?

Hi Guys,

I just wanted to say that when using any Nevo products on a network you should always use a 192.168.x.x IP range.

My understanding (my not be 100% correct) is that if you use a 10.0.x.x range to network device has to think about the possibility of a huge amount of IP addresses even if you are not using them.

By definition a 192.168.x.x range can only have a small range of IP addresses. Most domestic gear can only cope with a 192.168.x.x range.

Hopefully someone out there can confirm or correct me on this and do the math on the ammount of possible IP addresses per range.

D