Can you provide the string from the receiver when sending the “SYMO” command?
[quote=“zoot1612, post:101, topic:167791”]@santakrooz
Can you provide the string from the receiver when sending the “SYMO” command?[/quote]
Sure. How do I send it? Telnet?
Yes
Or you could try replacing “L_DenonReceiver1.lua” with the attached and it should pick it up.
[quote=“zoot1612, post:103, topic:167791”]Yes
Or you could try replacing “L_DenonReceiver1.lua” with the attached and it should pick it up.[/quote]
I’ve got Putty and my receiver’s IP address. Can you tell me how to send the symo cmd?
Change connection type to TELNET (port 23), put in IP address and open connection.
Type in
SYMO
and hit enter.
I have never really got the receivers to work properly with Telnet clients, you have to get it right first time or you have to drop the connection and try again. Also you need to ensure nothing else is connected to port 23 on the receiver.
[quote=“zoot1612, post:105, topic:167791”]Change connection type to TELNET (port 23), put in IP address and open connection.
I have never really got the receivers to work properly with Telnet clients, you have to get it right first time or you have to drop the connection and try again. Also you need to ensure nothing else is connected to port 23 on the receiver.[/quote]
Weird. It’s refusing the Telnet connection immediately before I can type anything. Wonder if there is a port or telnet enable in Denon the settings somewhere.
Tried Absolute Telnet as well and get
Connecting to 192.168.1.100:23
attempting 192.168.1.100:23… Failed: Connection Refused
Connect to 192.168.1.100 failed. Winsock Error: Connection Refused
I can connect to it in Putty via HTTP fine though. So if there is an http version of the cmd I can try that.
santakrooz,[quote=“santakrooz, post:106, topic:167791”]Weird. It’s refusing the Telnet connection immediately before I can type anything. Wonder if there is a port or telnet enable in Denon the settings somewhere.[/quote]
Is the Vera denon plugin currently connected to the receiver? Because Denons only support one telnet connection at a time. You might have to temporarily change the ip in the denon plugin config to something invalid to force it to disconnect.
Zoot is right about it not being really happy with telnet clients… I think the issue is the denon only wants a “\r” (carriage return) and not a “\r\n” or “\n” which is what I think the telnet clients add. At any rate with putty or absolute telnet you will get one command and then you have to disconnect and reconnect. But you should be able to get that one command in!
Is the Vera denon plugin currently connected to the receiver?
Could be. I’ll remove it and see. thx
Update: That was it. Thanks Radar. Worked immediately.
Zoot: The SYMO cmd returns AVR-2112USA
Thx Radar. Changing the terminal emulation (absolute telnet) so Enter sends CR instead of CR/LF fixed it so it keeps the connection and I can send as many commands as needed. I also turned local echo on, and host CR = CR/LF so that the display looks right. It works pretty well actually.
Hi all
I have attached a different version of the plugin below.
This is different in that it gets the input names from the receiver and populates as required. I have also changed to startup so it should now cater for serial/IP connection equally.
At the end I think I overcomplicated the whole thing so need to pull back for awhile
regards
zoot
By the way if you want a device to appear in the “AV Gear” tab in UI5
luup.attr_set("category_num","15",k)
cheers
Zoot
Awesome Zoot. I’ll try it out. How do you install the app? UI5 seems quite different than UI4 in this regard. Appears to only allow install apps from the appstore. -m
Go to tab “APPS”
sub tab “Develop Apps”
Choose menu item “Luup Files” and upload files as per UI4
regards
Zoot
Thx Zoot. Got it installed. It configured up and recognized the model name (AVR-2112USA) in adv settings. Vol up/dn, power, mute all work. But the inputs are remaining generic ie input1, input2, etc thru input25 - are these supposed to customize to the 2112?
@santakrooz
No, I have made the plugin generic as I don’t know what the input names are going to be. The plugin should map the inputs to input1 → input? (?depends on model).
The actual inputs are based on “urn:micasaverde-com:serviceId:InputSelection1” so don’t necessarily match the Denon inputs.
If you want to you can edit the json file to reflect your inputs as per example below: -
{
"ControlType": "button",
"Label": {
"lang_tag": "DiscreteinputPC",
"text": "Input3" <------------------------------------------------------------------- Change this to what text is to be displayed on button in interface.
},
"Display": {
"Service": "urn:micasaverde-com:serviceId:InputSelection1",
"Variable": "Input",
"Value": "HDP", <------------------------------------------------------------------- Change this to match input variable, in this case if "Input = HDP" then button is highlighted.
"Top": 70,
"Left": 210,
"Width": 50,
"Height": 20
},
I’m a little confused then, I thought it was getting the inputs from the receiver. Do you mean that it’s getting the input names dynamically from the receiver but the UI is not dynamic?
This is different in that it gets the input names from the receiver and populates as required.
If so, maybe we can put together a list of them from the various model API docs.
@santakrooz
Yes
Variables within plugin are dynamic and UI static as per: -
[url=http://forum.micasaverde.com/index.php/topic,9007.msg58855.html#msg58855]http://forum.micasaverde.com/index.php/topic,9007.msg58855.html#msg58855[/url]
I don’t know how to if there is a solution so decided on generic for now. The only solution I can think of at the moment is a json file for each receiver and that would up to each individual user.
Cheers
Zoot
Thanks Zoot. Attached is a screensnip of my mios setup. It’s working well. I only changed the Label:Text properties. I didn’t change the Display:Values to match. It’s not automatic, but it look/works fine. I will probably try to remove the extra buttons from the display.
I’m curious what would editing the Display:Values do? Since it works as is?
-sk
The ‘Input’ variable is tied to the table containing the actual input names e.g. CD, Tuner, Game1 etc. if the Display:Value matches the Input variable then the chosen input button should change colour to the darker blue (Same as the On button in your screen shot).
cheers
Zoot
I don't know how to if there is a solution so decided on generic for now. The only solution I can think of at the moment is a json file for each receiver and that would up to each individual user.
You could rewrite the [tt]json[/tt] file from within your plugin and then restart [tt]LuaUPnP[/tt].
Joking aside, dynamic labels for buttons should be implemented by MCV.