For those interested, I just released v0.1 alpha. The plugin works just fine for my needs and your mileage may vary.
I’d like to acknowledge the work originally done by @Richard, which got me kick started on creating an enchanted p enhanced version of it.
The plugin is bidirectional, allowing scenes and triggers to be executed when actions are performed on the receiver. For example, I have my home theater lights turn on whenever the amp is muted and off on mute off.
Some features
[ul][li]Status display (the info which shows up on the front of the amp) is decoded[/li]
[li]volume is decoded to dB as well as percent [/li]
[li]mute on and off actions which avoids blind “mute toggle”.[/li]
[li]Direct volume set action by percent[/li]
[li]Decoding of audio parameters (bit rate, depth, channels, etc. for input as well output[/li]
[li]Decoding of video parameters (in format, resolution, color space, etc, and their output[/li]
[li]Modular command set which should make it easy to expand supported variables/models[/li]
[li]Custom icon set for “default”, “on”/“on & muted”/“off”[/li]
[li]Command queuing[/li]
[li]AltUi devices view status lines[/li]
[li]*** tested on AltUi/OpenLuup only at this point since the plugin was developed on them using Eclipse Lua Development Tools[/li]
[li]Open source, available on GitHub[/li][/ul]
I encourage everyone to fork and and to it; I will implement the missing actions/status variables from the Pioneer RS232 specs (which are the same as the TELNET protocol), but I don’t plan on maintaining it to much afterwards.
If anyone can figure out the code page used by Pioneer for their status display, let me know. I managed to have text displayed, but special characters just aren’t mapped correctly.
Enjoy!
[ul][li]2016/11/30 created new branch for Vera, where I am doing some refactoring to get it to work on vera’s different lua loader implementation. I got the basic operations to work and will try on openLuup to ensure noting got broken. Link : https://github.com/sle118/mios-pioneer-receiver/tree/veralite[/li]
[li]2016/12/3 Busy day! Lots of changes in the Veralite branch of the plugin. Several improvement include performance increase for status query processing, more status variables implemented (I’m working with a Pioneer ref document from 2012), improved timeout processing when querying the amplifier, general bug fixes. The branch should be friendly with the Vera now. Link : https://github.com/sle118/mios-pioneer-receiver/tree/veralite[/li][/ul]
I tried installing this plug-in today. I am not experienced with installing a plug-in manually so I probably did something wrong. End result is I am getting a lua message saying: PioneerReceiver plugin: Plugin not correctly installed
The device appears in the vera interface but displays the message Lua Startup Failure.
First time through I tried following the instructions in the wiki translating as needed to the UI7 interface. I uploaded the two files, D_PioneerReceiver1.xml and I_PioneerReceiver1.xml without reloading the Lua after the file upload. I then created the devices specifying the device file name “D_PioneerReceiver1.xml”.
Second time through, I uninstalled the device and deleted the files, rebooted the Vera. Then I uploaded all of the files from GitHub source and tried creating the device again - same results.
I have a VSX-1123. It does work with the plug-in from the vera store but that plug-in has some limitations. I’m hoping to get this one working and, if necessary, try to help extend its capabilities.
Which version did you try to install? The plugin was mostly developed under altui and I have started porting the code to vera UI7. The work, however, is in a different git branch in my repository.
Ideally, it would be best if you could post logs somewhere (pastebin, etc) or extract the “PioneerReceiver” lines from the log and post them here.
After un-installing, re-downloading and re-installing I managed to move the ball. Now the Lua is running and not reporting an error with the plug-in installation but it is reporting the message “Can’t detect device”. And when I try to change the settings, I get a Control panel with no options - no advanced tab etc.
I had entered the IP address when I created the new device.
Doesn’t seem to matter if I just specify the device file or if I specify the device file and the implementation file.
I am not seeing anything in the log LuaUPnP log file that identifies the problem (to me). I will try to get you some log information tomorrow.
@SLE118. Is the plugin now working on the Vera? I am tempted to test and it looks like we have to manually create the device.
Edit: I am seeing the same problem as Bb98. The plugin does not appear to communicate with the receiver. Once created, the device json also does not appear to have the advanced tab to modify anything. Would be nice to have.
[quote=“rafale77, post:7, topic:194545”]@SLE118. Is the plugin now working on the Vera? I am tempted to test and it looks like we have to manually create the device.
Edit: I am seeing the same problem as Bb98. The plugin does not appear to communicate with the receiver. Once created, the device json also does not appear to have the advanced tab to modify anything. Would be nice to have.[/quote]
1- Did you download the objects from the vera branch in github? The main branch was developed under openluup/Alt UI and does not work for vera. Once I get the vera branch running, I’ll merge with master.
2- What files did you upload? It’s important that all the files are uploaded to vera (the I_* file, the L_* files, etc)
3- Can you provide logs of what’s happening? This would help tremendously as the symptom you are referring to could be caused by a number of things.
I might be able to spend more time on this next week, but I’ve been otherwise busy with real life over the past weeks.
[quote=“sle118, post:8, topic:194545”]1- Did you download the objects from the vera branch in github? The main branch was developed under openluup/Alt UI and does not work for vera. Once I get the vera branch running, I’ll merge with master.
2- What files did you upload? It’s important that all the files are uploaded to vera (the I_* file, the L_* files, etc)
3- Can you provide logs of what’s happening? This would help tremendously as the symptom you are referring to could be caused by a number of things.
I might be able to spend more time on this next week, but I’ve been otherwise busy with real life over the past weeks.[/quote]
I downloaded from the Veralite branch
I uploaded all the files (D_, i_, L_, S_) and manually created a device using the corresponding device (D_) and implementation file along with the correct IP address. One thing I did not try is to use the IP address with the open port. Does the app know to use port 23 by default?
Sorry can’t help on that, I have not yet figured out how to generate logs from installing an app manually.
Under the device advanced parameters, again, I highly recommend to make that tab available in the JSON so that the parameters can be changed after the device is created.
that will switch the input to what maps to 19FN (DVI in most cases).
the full list of supported commands is a quick google search away, I uploaded the PDF here for posterity.
If people are having much difficulty getting this plugin to work, they could just create virtual buttons and assign the relevant code to send over TCP (volume up would look like tcp:send(“VU” … “\r\n”).
this is so useful to me since every time I turn on my television it automatically switches the receiver’s input - the receiver is 2 flights of stairs away and it takes too long to wait for the android app to open and switch the input. having this work automagically ups the WAF of the setup.