Just updated from 1.1 on UI5, everything seems to work but what I was really really waiting for was a way to switch between A/B speakers from vera on my TX-8050. I know its possible because my roomie app can do it.
Or if anyone has any info on a command to send via luup I could deal with that. I tried to wireshark it but i don’t really know exactly what I am looking for and I can’t physically isolate my network stuff like that with ease.
You can not switch between A/B speakers other than physically hitting the button selector on the front of the receiver. True story. Trust me, I’d love to be able to do so and previously looked into it. I even spoke to a tech at Onkyo asking them to add it to a future firmware release, and he said it’s not going to happen.
I think i have all the tools to create a tcp command to switch speakers I just need some kid free time. Cant sit at the computer without one sitting on each knee. Good for the heart bad for automation.
Hi! Trying to setup the plugin (2.11) with Vera Light and an NR-TX609 Receiver… I have the IP address setup, but still getting “cannot detect device” error… can?t control anything.
Any ideas?
Same here. Have a static IP on the receiver and definitely entered into the device advanced tab. Even copied IP from browser window to make sure it was right and I have connectivity.
Onkyo sucks… I pretty much have to cycle the power everytime I switch control methods. Maybe yamaha too, but at least I only need vera to do anything i want. Also make sure you have your firmware up to date.
Hi guys, I am trying to get a light to turn on when a particular input is set, I have tried to piece together a luup code of;
local lul_tmp = luup.variable_get(“urn:micasaverde-com:serviceId:InputSelection1”,“DiscreteinputVCR”, 95)
if (lul_tmp = “DiscreteinputVCR”)
then
luup.call_action(“urn:upnp-org:serviceId:Dimming1”, “SetLoadLevelTarget”, {newLoadlevelTarget = “30”}, 83)
end
but it fails, I know it will be something simple that I am doing wrong, if anyone has any suggestions that would be great.
Thanks in advance.
Rob
I’ve been the developer for the last year and have failed to improve the app primarily due to lack of time to actually work on it. I want to openly apologize to the community as I should have released the reigns many months ago. That being said, if anyone has the time and skills and wants to take over the app for further development, please PM me.
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.”[/quote]
For anyone who cares, A and B speaker levels can be toggled by EventGhost (windows) along with everything this plug in does as well (i think).
So using the webserver and onkyo plug ins for eventghost, all you need to do is create a scene to send an http request to the eventghost socket and its good.
To turn on A speakers type SPA in command box in the EG plugin, SPB for B. MVL20 for master volume 20. PWR00 and PWR01 for on and off. Theres more but you can google.
Id just like to say how awesome it is to flip on the light switch for the bathroom and music start playing…
ON A SIDE NOTE… I FOUND THAT ONKYO KNOWS THEIR NIC CARDS ARE GARBAGE AND ARE REPLACING SOME FREE OF CHARGE, SHIPPING INCLUDED. WHILE THIS SUCKS ITS BETTER THAN BUYING A NEW ONE. ONKYO HAS A WEBSITE SET UP SO YOU CAN MATCH YOUR SN AND EITHER SEND THE UNIT IN FOR REPAIRS OR GIVE YOU A CREDIT IF YOU QUALIFY ON A NEW PURCHASE. I DIDNT QUALIFY BUT HAVE A LOWER END STEREO RECIEVER. OTHER ISSUES ARE ALSO INCLUDED IN THIS SYSTEM, SEEMS LIKE MULTIPLE RECALL TERRITORY BUT OF COARSE THEY WONT NOTIFY YOU, YOU NEED TO DIG FOR IT.
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.”[/quote]
MCV, still working on a fix?[/quote]
Any update on this. Im running the new VeraPlus on UI7 and get the “port not defined, cannot detect device” error message
You might be right. But on the 3rd page of that thread a fellow came up with some code that resolves the issue for some people. It worked for me.
local hasFailure = false
for devNum, devAttr in pairs(luup.devices) do
local commfailure = luup.variable_get("urn:micasaverde-com:serviceId:HaDevice1", "CommFailure", devNum)
if (commfailure == "1") then
luup.log("Device "..devNum.." has CommFailure="..commfailure..". set it to 0")
luup.variable_set("urn:micasaverde-com:serviceId:HaDevice1", "CommFailure", "0", devNum)
hasFailure = true
end
end
if (hasFailure == true) then
luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1", "Reload", {}, 0)
end