Since a few days, I’m also having these messages in my log:
2017-12-08 18:34:56.818 [WARN ] [inding.denon.internal.DenonConnector] - Unable to get secondary zone information.
2017-12-08 18:35:16.836 [WARN ] [inding.denon.internal.DenonConnector] - Unable to get secondary zone information.
2017-12-08 18:35:44.122 [WARN ] [inding.denon.internal.DenonConnector] - Unable to get secondary zone information.
2017-12-08 18:36:09.140 [WARN ] [inding.denon.internal.DenonConnector] - Unable to get secondary zone information.
2017-12-08 18:36:34.287 [WARN ] [inding.denon.internal.DenonConnector] - Unable to get secondary zone information.
I guess it started somewhere when upgrading OH (I’m on a recent OH 2.2 snapshot), but I’m not sure.
with this binding I get the following messages in the log when the receiver is turned off:
denonmarantz:avr:0005cd614026’ changed from OFFLINE (COMMUNICATION_ERROR): IO error while sending command to AVR: Keine Route zum Zielrechner to OFFLINE (COMMUNICATION_ERROR): IO error while connecting to AVR: Keine Route zum Zielrechner
Hi Rene,
it looks like the receiver shuts down the network interface when powered off.
Can you check the receiver settings, maybe you can specify the behavior to go to ‘standby’ instead of full power off.
but for Hue things for example I dont get every 10 seconds an failure like in that binding also if it is offline and not reachable. That is the big difference.
Are you using HTTP or Telnet config?
I think the issue is there is multiple texts in the error, causing a ‘change’ of the status and hence an update to the events log.
I could check whether I can use only 1 text, then you get one log each time you switch off the AVR.
But best for now would be to just enable the IP Control to be ‘always on’.