mwittig / pimatic-denon-avr Goto Github PK

View Code? Open in Web Editor NEW

6.0 2.0 2.0 111 KB

Pimatic plugin to monitor & control a Denon or Marantz AV Receiver

License: GNU Affero General Public License v3.0

CoffeeScript 95.07% HTML 4.93%

denon av-receiver home-automation pimatic pimatic-plugin master-volume marantz marantz-avr denon-avr

pimatic-denon-avr's People

Contributors

Stargazers

Watchers

Forkers

p4co86 sentzu01

pimatic-denon-avr's Issues

Input selector background-color

DenonAvrInputSelector can't be changed via rules?

Not sure if I'm doing anything wrong, but it seems like I can't select the DenonAvrInputSelector when creating a new rule. Master-volume, mute, and power are available in rules, but the input selector is not available. Is this a bug? Or is there a known workaround?

Use case: I use a dummy switch that's turned on/off via my amazon echo. Once it changes its state, I'd like to turn on the AV receiver (works) and 5 seconds later I'd like to switch the input to Bluetooth so I can connect my echo and play music.

Uncaught exception

Hi,

I received this error and it asked to report it. So here it is...

error [pimatic]: A uncaught exception occured: Error: read ETIMEDOUT
    at exports._errnoException (util.js:870:11)
    at TCP.onread (net.js:552:26)
From connect
    at Socket.connect (/home/pi/pimatic-app/node_modules/pimatic/startup.coffee:55:29)
    at Agent.exports.connect.exports.createConnection (net.js:69:26)
    at Agent.createSocket (_http_agent.js:175:16)
    at Agent.addRequest (_http_agent.js:144:23)
    at new ClientRequest (_http_client.js:142:16)
    at Object.exports.request (http.js:31:10)
    at new Request (/home/pi/pimatic-app/node_modules/pimatic-denon-avr/node_modules/restler-promise/node_modules/restler-base/lib/restler.js:75:24)
    at request (/home/pi/pimatic-app/node_modules/pimatic-denon-avr/node_modules/restler-promise/node_modules/restler-base/lib/restler.js:327:17)
    at Object.get (/home/pi/pimatic-app/node_modules/pimatic-denon-avr/node_modules/restler-promise/node_modules/restler-base/lib/restler.js:334:9)
    at /home/pi/pimatic-app/node_modules/pimatic-denon-avr/node_modules/restler-promise/lib/restler-promise.js:28:38
    at Promise._execute (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/debuggability.js:299:9)
    at Promise._resolveFromExecutor (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:481:18)
    at new Promise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:77:14)
    at Object.get (/home/pi/pimatic-app/node_modules/pimatic-denon-avr/node_modules/restler-promise/lib/restler-promise.js:27:20)
    at HttpAppProtocol._requestUpdate (/home/pi/pimatic-app/node_modules/pimatic-denon-avr/http-app-protocol.coffee:59:19)
    at HttpAppProtocol._requestUpdate (/home/pi/pimatic-app/node_modules/pimatic-denon-avr/http-app-protocol.coffee:2:1)
    at null._onTimeout (/home/pi/pimatic-app/node_modules/pimatic-denon-avr/node_modules/pimatic-plugin-commons/lib/index.js:218:27)
    at Timer.listOnTimeout (timers.js:92:15)
 This is most probably a bug in pimatic or in a module, please report it!

Add HTTP transport

Currently you can't use the plugin together with other apps as the "telnet/serial" communication only allows one client. Would be great if this can be changed. I know it is on the agenda but I wonder what the current status is.

Interval step change

Hello Marcus,
is it possible to change the minimum interval to maybe 1 second or 2 seconds? actually i need a smaller step size.

Thanks in Advance

Video signal is interrupted by changing volume

If i change the volume by the slider of the device DenonAvrMasterVolume i get a annoing behavior of the plugin, the video signal is swiched off so that the screen is getting black and on again while displaying MAIN ZONE on. Is that a bug or perhaps a behavior which could be enhanced/fixed?

I'm using the PlugIn with the Protocol TELNET on Port 23 and a Denon AVR-X3100W as hardware.

Source change for both zones

Would be great if this could be integrated that's the biggest thing I'm currently missing.

Most of the information should be here:
https://forum.pimatic.org/topic/979/denon-marantz-avr-remote-control

Unhandled exception if AVR is offline and network control is off

If the Denon AVR is offline and you haven’t activated the option network control the following error occurs:

Unhandled rejection Error: Expected variable Denon-Volume-Status.volume to have a numeric value.
    at /home/pi/pimatic-app/node_modules/pimatic/lib/variables-ast-builder.coffee:111:17
    at tryCatcher (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromise0 (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:614:10)
    at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:693:18)
    at Async._drainQueue (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:133:16)
    at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:143:10)
    at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:17:14)
    at processImmediate [as _immediateCallback] (timers.js:383:17)
Unhandled rejection Error: unknown state=""!

Can't set volume of Zone/Main via rules

I have not found a way to do this and thus volume can only be changed via GUI and not via rules

Volume not changed with slider as expected.

I have this for some time now but didn't find the time to report it yet.

Currently if I try to change the volume via the slider in the Pimatic web frontend the moment I let it go it jumps back to previous value or even decreases. Only after several tries I get it to increase a little bit.

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

Added the new Node.js version to your .travis.yml
The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

engines was only updated if it defined a single version, not a range.
.nvmrc was updated to Node.js 10
.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of grunt is breaking the build 🚨

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency grunt was updated from `1.0.4` to `1.1.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

grunt is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v1.1.0

Update to mkdirp ~1.0.3
Only support versions of Node >= 8

Commits

The new version differs by 8 commits.

d5cdac0 Merge pull request #1706 from gruntjs/tag-neew
4674c59 v1.1.0
6124409 Merge pull request #1705 from gruntjs/mkdirp-update
0a66968 Fix up Buffer usage
4bfa98e Support versions of node >= 8
f1898eb Update to mkdirp ~1.0.3
75da17b HTTPS link to gruntjs.com (#1683)
6795d31 Update js-yaml dependecy to ~3.13.1 (#1680)

See the full diff