Pioneer AVR Control plugin

---

New version (0.2.0) is out.
Changes:

• AVR Volume is shown
• AVR Display is shown 1:1
• Volume Slider support
• maxVolume implemented

Sample

Version 0.2.1 released

Changes:

• Fixed critical error that causes pimatic to crash if connection to AVR cannot be established

@mwittig

@mwittig said:

@Harry-van-der-Wolf said:

You might not like that but for me it is good news.

Well, I think it is on @sweetpi to decide which plugins will be added to the “official” list of plugins. i.e, the list of plugins on the website and integrated with the update mechanism of the mobile frontend.

Apart from this, users are free to add whatever they want to their private base, and, of course, they are free to share their contributions via github, npmjs, and the forum with other users. However, I believe, some rules must be followed for “official” plugins:

• Plugins must be written in Coffescript. If required, plugins may use supplemental Javascript libraries, which shall be published as separate npm packages.
• Plugins must have a Readme file written in Markdown with reasonable level of detail
• Plugin packages and sources must include a LICENSE
• Plugins must have a well written package.json descriptor
• Plugin authors shall be responsive to user requests. As this is difficult to achieve at all times, authors should seek for co-maintainers (github & npmjs) who can do fixture when the author has no time.

That’s right, however:

• Coffeescript is just strongly recommended but not mendetory.

The website is updated by a script that fetches all published packages starting with “pimatic-” from the npm-registry. However it need to be triggered manually for security reasons. So just ping me, if you want to have me update the website. Some more info: https://github.com/pimatic/pimatic/issues/323

@sweetpi Ok, I have not been aware of this github issue post. It is sometimes difficult to find such things if you don’t have the right key words in mind. May be you can consider my thoughts about co-maintainance of plugin. The number of plugins not properly maintained is growing, unfortunately.

The number of plugins with no LICENSE included too but that starts to become more and more offtopic

@SaxnPaule Agree. The discussion should be continued on the github issue thread.

@mwittig
I added the support for different brands to my plugin. Simply add the brand parameter to the pimatic config

    {
      "plugin": "pio-remote",
      "host": "192.168.0.15",
      "port": 23,
      "maxVolume": 100,
      "brand": "denon"
    }

I also outsourced the commands to a json file, that you are able to add you own commands. A Denon section is already started.

I released no new version, you have to use the plugin directly from git: https://github.com/saxn-paule/pimatic-pio-remote/tree/develop

nice!
i’m glad you and @mwittig are working together for the avr plugin!
also i like the idea to integrate yamaha and sony devices (if a dev is joining the project).
will try the plugin soon.

@leader21
Its not necessaryly needed, that a Sony/Yamaha dev joins. The config is open for any brand. Only someone needs to find a spec in the internet and map the plugin commands to the AVR commands that are internally used. The config is a simple json mapping file und should work out of the box.

version 0.3.0 released 2015-12-18

• Added support for other AVR brands
• Adjusted volume slider logic to work for denon aswell
• Added denon sample values and reference to documentation
• Outsourced command config
• Added some sound commands for pioneer

version 0.3.1 released 2015-12-18

• fixed bug in min volume detection

version 0.4.0 released 2016-04-18

• Fix missing commands.json in npm package
• Outsourced response handler to make dedicated parsing for different brands possible

hi @SaxnPaule
Thanks for updating your plugin.I’ve been using it for a while now.

However, I get an error after every update:
Could not initialize the plugin "pio-remote": Cannot find module './pioneerHandler.js'
I guess the file is not included in the npm repository. Is it possible to fix this?

I extended the package.json and pushed it to the develop branch. I’ll publish a new release today in the evening.

Thanks a lot!

Tested and released new version.

version 0.4.1 released 2016-04-21

• Added missing files to package.json

I did some minor changes to make the plugin pimatic 0.9 compatible.

Changes are pushed to develop branch: https://github.com/saxn-paule/pimatic-pio-remote.git

After I found some time to update my productive Pimatic to 0.9 I released the 0.9 compatible version of pio-remote too.

version 0.5.0 released 2016-10-03

• Added destroy method to AVRSensor to make the plugin pimatic 0.9 compatible

version 0.5.1 released 2016-10-03

• Added clearTimeout call in destroy method

version 0.5.2 released 2016-12-14

• Added status variabe to receive the current power state of the device
• refactored interval timer