Good posts here folks!

Joel - If Chris Kelly used your codes and the vol + and - seemed to work well, (and quickly) than maybe there are other gremlins at work.

A learned code from a remote, will copy almost exaclty. Certain original codes are repeating codes and others are not. The typical repeating codes are for Vol + and -, FF, Rew, etc. The non-repeating codes are typically amp functions, simple input switching functions, mute, inputs and the like, etc. You may have received a poor learn or the code was modified by bright lighting when you learned into the SL. You already tried Chris' vol hex code and you said it didn't make a difference.

So, net-net, if your volume is acting badly, it may be a result of UEI's latest software upgrade. In 1.2, they noticed a problem with repeating codes going to a NevoLink. So, they changed the way the code is sent. Instead of just sending it, I believe they modified it to send in small batches, like a short macro, so run-away repeating was avoided. This was really the fix, to avoid run-away IR causing things like volume + to get stuck and repeat forever (or until your speakers melted...LOL)

The only way to really test this is to turn off the NevoLink in your config. Do this in Nevo Studio and then download the the Nevo SL. Before you download, change the settings so this device (Denon) will be controlled by IR, not wifi. Then see how your vol behaves. If it is significantly different, then UEI should probably know about this.

I just re-read your last post and you said it was working quite well in IR? Is that correct?

Dave

Dave,
I did change the setup to send IR to my Denon remote. The volume does seem to work fine by sending commands via IR. Chris Kelly also verified my setup with his system and the volume worked for him as well sending via IR. I noticed there is a settign in the tools section of Nevostudio which says something about sending repeatable commands as macros. I have that checked now. Should I change that?

Hi Joel,

Yes, give it a try. That is the main new update in v1.2. Turning that option off may very well fix the problem, even when you go back to the NevoLink. Let us know how you make out.

Dave

Dave,
I changed the setting last night (unchecked the send as macro box) and reloaded the Nevo. I now have the other extreme happening. I am getting a flashing yellow triangle with a ! inside it showing up over the circle next to the antenna at the top of the Nevo screen. When the yellow triangle appears, the volume will change 20 - 30 Db with one volume command. When the yellow triangle does not appear the volume changes by .5Db. I have noticed the yellow triangle appear using other commands before I made this change but it never seemed to cause any problems. Does the yellow triangle indicate a network issue?

I have the 5805 and it works fine with the Nevo SL. I can tap the volume buttons to go up and down in 1/2 db increments, or hold it down to go up quickly as is the case with the factory remote. I got the codes from the Nevo site, no learning.

Joel, I think the yellow triangle indicates it cannot talk to nor establish contact with the NevoLink. It is thinking it is supposed to talk to the NevoLink. You might want to experiment with the actual code conditions for the volume control. You can change the attributes of any button or soft button. You can tell it to use IR or to use the NevoLink.

Try this and see what happens.

Dave

Dave,
I'm not sure what you are saying by "experiment with the actual code conditions for volume control." Are you thinking the problem is in the setup of the specific command and not a network issue? I have tried using three ways to put in the volume control (command from Nevo site, HEX code, and learned). Are ther other ways to do it? In addition, I have noticed that if I check the send as macro box the volume is slow reacting but I do not get the yellow triangle.

Well the issue has been resolved. Hopefully this thread will help others that are having the same issue. Unfortunately, I cannot point to the exact change that was made but here is what I did that corrected the problem. I got a copy of the Nevo networking whitepaper and went thru that last night and made several changes as recommended in the whitepaper. Things I changed included using a different wireless channel, changing some settings that deal with network interference, etc. I would strongly recommend reading thru this if you are using the Nevolink. It has greatly improved the speed and reliability of the Nevo. The volume works just like the factory remote now thru the Nevolink. I do not have the send volume commands as macros checked now. They also talked about that setting in the whitepaper. Thanks to everyone for the help.

Joel,
I'm glad you've got this thing up & running.

Joel/Dave,
I have just one curiosity question. One of the reasons I've held off of a NevoLink and went with IR extension is due to the fact that after my remote "goes to sleep" between FF cthrough commercials on TiVo, I notice that for the first few seconds, the nevo is trying to re-establish a connection with the network. By the time it connects I'm almost through the commercials and am back to watching Lost. It's been hard for me to imagine waiting on this to connect before changing volume, channels or FF through commercials.

How long is the delay between picking up the remote and the ability to send a command? If you send a command BEFORE connection, does it hold that command and send it on in once connected?

Thx.

Chris

Chris,
I can't answer your questions directly yet. I will try to experiment with it as I use it more. I can tell you that once I made the network changes, it seemed to send commands and connect to Wifi much faster. The other thing I will mention, is that there are settings to control how long it stays connected to Wifi before it closes the connection. I have mine set to never disconnet from Wifi when its on the charging cradle and the longest option available when on battery ( it is either 15 or 30 minutes). I don't think it will send the command once it establishes the connection if you pressed it before you are connected. Dave will be a better resource on this.

you may be able to avoid the suspend option ... check-out the last section in the whitepaper.