The App Tab only shows one decimal place on the version. So even when I do an update and make it 2.15 it shows as version 2.1 and I don’t want to make it version 2.2 for a small bug fix.
Sent from my iPhone using Tapatalk
Considering we are now at FireFox version 39, and Chrome version 44 it is nice to see a developer still caring for the proper major.minor.point versioning when dealing with small fixes. But if the version number can not be shown to the user to verify they have it installed I must agree with the OP that it should not matter if a small fix leads to a higher version number, as the whole point of them is to show changes have been made.
fair enough, but don’t expect big changes when you see 3.0
-BC
Well, went to the Apps tab. Selected Onkyo Receiver (AVR) Details. Then, clicked update app. Now i get the following when I Reload Engine.
Onkyo Receiver (AVR)[38] : Lua Engine Failed to Load
Onkyo Receiver (AVR) : Lua error
Tried to uninstall and then reinstall to see if the issue cleared but, no luck. Thought I would mention here to see if anyone else had experienced the same.
I got the same thing…
Onkyo Receiver (AVR)[187] : Lua Engine Failed to Load
Onkyo Receiver (AVR) : Lua error
I’m sure these will be fixed any moment, for the impatient:
to fix
Onkyo Receiver (AVR)[NNNN] : Lua Engine Failed to Load
The file L_OnkyoReceiver1.lua needs to have html markup changed. search and replace the following
" should be "
< should be <
> should be >
I think those were the only ones that needed updating.
then strip the ^M’s from I_OnkyoReceiver1.xml and upload.
To get mine working I deleted everything from the UI, then any onkyo related file I could find on the file system (/etc/cmh-ludl/, no idea if that’s necessary). Did a fresh install from market in the UI7 panel (20150727), then download and alter the two files listed above. up load them then in a few moments it hopefully it works. “it worked for me”
I tried the fix to the L_OnkyoReceiver1.lua file. Could not find ^M’s in the I_OnkyoReceiver1.xml. And no success.
I have an Onkyo TX-NR747.
Version 1.7.1320 of the VeraEdge firmware.
Downloaded the Onkyo App version 2.1 dated 7/19/2015.
Any help would be greatly appreciated. Thanks.
I can confirm the above fix works!
In searching a Vera Lite box for files with Onkyo in the name, they all have a lzo extension. I assume this is some manner of Lempel-Ziv compression.
Is there a resource that explains how to deal with modifying the files mentioned above?
[quote=“lkas, post:227, topic:178032”]I tried the fix to the L_OnkyoReceiver1.lua file. Could not find ^M’s in the I_OnkyoReceiver1.xml. And no success.
I have an Onkyo TX-NR747.
Version 1.7.1320 of the VeraEdge firmware.
Downloaded the Onkyo App version 2.1 dated 7/19/2015.[/quote]
I fixed L_OnkyoReceiver1.lua with the instructions above and that fixed the Lua Engine errors but I also couldn’t find any ^M’s in I_OnkyoReceiver1.xml.
The plugin adds the devices like it’s supposed to but I am not able to control the receiver nor get any status from it.
I have an Onkyo TX-NR636.
Like lkas, I am running 1.7.1320 and the Onkyo App version 2.1. Has anyone with 1.7.1320 got this to work?
I’m new to Vera so I assume it depends on the UI version you have but in UI7 you go to: Apps → Develop apps → Luup Files. That section allows you to download and upload luup files on the device easily. It has a file handler that appears to decompress them on the fly.
If you are interested in working on the device itself, check out this form post about lzo files http://forum.micasaverde.com/index.php?topic=4541.0
Could someone please tell me how to install the “Onkyo plugin”?
As you can see from my post counts, i am novice into this. Please tell me how to install the plugins and do they simulate the real TV functionality?
I mean its told here that as we install the plugi, it generates the service and we can access the device using M-SEARCH protocol.
Please give me initial tips to proceed.
It appears after the upgrade to version 2.1 I can’t get setvolumetarget to work when trying to set a specific volume.
Am I using the wrong parameter now?
I created a single scene with only this in it to test and nothing happens.
Any help is appreciated.
Edit: oops v 2.1 - made the above edits and still isn’t working. No response from the receiver at all. My have not bee working correctly for a while.
Edit2: followed same process 2 days later with success. Getting “can’t detect device” but everything functions.
2.4?
@ALL hardware note:
For those having difficulty, first make sure your receiver is online. I’ve had the HDMI board replaced on my unit before but it seems even the factory repair was faulty and has been recalled. After setting up this plugin my receiver died AGAIN >:( [b]Onkyo recall info: http://www.onkyousa.com/Support/service_info.php#[/b]
The HDMI board issue takes networking offline and annoying audio issues. If your unit is covered in the link above, you may want consider the service. It also extends the warranty until 12/31/2018.
@wesley69, the “can’t connect” message is ‘fixed’ from altering L_OnkyoReceiver1.lua. Apparently that message is a ui7 sanity check.
The ^M’s are a dos/micros~1 issue. google around replacing line feeds for your situation will be more helpful than me. I’ve seen notepad++ mentioned.
@Ikas - if yours is still not working see if you can find the pesky invisible ^M stuff. I think that’s all that’s holding it up if the recent onkyo mobile app works.
@luvrajind - my first post, Reply #225, is from an initial install on UI7 from the web interface. Once the plugin is downloaded/installed from the web interface I then had to download the files mentioned above from the vera web interface. Edit them as noted, then upload them through the web interface and reload a few times. There is no upnp/m-search for it, just enter the ip address of your receiver in the device’s Advanced tab and reload a few more times. That should get base functionality going but not all features may work without you modifying the plugin.
@all - from what I’ve read on onkyo’s interface this plugin should at least be able to do the basics on all models, power on/off, volume, mute, switch inputs, etc. Those base things seem to be the same but features and input naming vary among implementations.
MCV really needs to hire a dev/advocate/plugin person to do this well. i’ve wasted hours on wemo devices that are not implemented and there’s no maintainer there either.
hope that helps
Instaling the app from the ap store (v2.11), putting IP address in advanced tab and and reloading LUUP (luup.reload() in apps develop did the trick to start working.
But i doesnt take away the message “Can’t Detect Device”
[quote=“derrick, post:235, topic:178032”]@ALL hardware note:
For those having difficulty, first make sure your receiver is online. I’ve had the HDMI board replaced on my unit before but it seems even the factory repair was faulty and has been recalled. After setting up this plugin my receiver died AGAIN >:( [b]Onkyo recall info: http://www.onkyousa.com/Support/service_info.php#[/b][/quote]
@derrick - Are you saying that the repairs to the original HDMI board problem are faulty and needs to be sent back? Is this a generally known problem or in rare cases that you experienced ? I do not see anything from Onkyo regarding the repair being recalled as well.
I stopped using internet and this plugin and my unit (sound and HDMI) wise has been ok now after thinking it was a goner. I posted awhile back where i had problems took it in for repair and they didn’t find the issue. I brought it back and started using it with the plugin again until it acted it up. After that I disconnected everything and it started working fine and since I just left it without internet. No issues so far.
All,
After several minor plug-in revisions in an attempt to fix the “Can’t Detect Device,” I finally contact MCV and received the following response:
“Hello and thank you for contacting Vera Support. Please know that we are aware of the issue with ?Can?t detect device? error that is displayed on the devices (or plugins), eventhough the devices are working just fine. This issue is related to the ?CommFailure? variable and the algorithm on which this value is being set from 0 to 1. Our development team is already working on fixing this. Once the fix will be available it will be included in a future firmware update for your Vera unit. Thank you for your patience and understanding.”
I revisited this plugin because I’ve reconfigured my AV upstairs. Today, I was able to get the plugin to install and, apparently, at least ping the receiver. This is the first time I’ve ever actually gotten the plugin installed without some Lua error. However… the buttons do nothing. No control over the receiver. It’s online, I can ping it, but the plugin doesn’t do anything. Also, I can’t get to the Config tab… it just loads, and loads, and gets nowhere. I have two zones, and the plugin automatically creates three devices (for three zones) each time I restart Vera.
Any ideas?