Onkyo

instalator

С power разобрался, пулреквест отправил.

А вот с громкостью что то чудеса творятся.

Почему в логе сообщения от mqtt??? :?:

! onkyo.0 2016-02-25 21:58:08 debug inMem message onkyo.0.* onkyo.0.master-volume
! onkyo.0 2016-02-25 21:57:45 info onkyo.0 stateChange onkyo.0.command {"val":"MVL28","ack":true,"ts":1456415865,"q":0,"from":"system.adapter.onkyo.0","lc":1456415865}
! onkyo.0 2016-02-25 21:57:45 debug inMem message onkyo.0.* onkyo.0.command
! onkyo.0 2016-02-25 21:57:45 info onkyo.0 stateChange onkyo.0.volume {"val":40,"ack":true,"ts":1456415865,"q":0,"from":"system.adapter.onkyo.0","lc":1456415865}
! onkyo.0 2016-02-25 21:57:45 debug inMem message onkyo.0.* onkyo.0.volume
! onkyo.0 2016-02-25 21:57:45 info onkyo.0 stateChange onkyo.0.master-volume {"val":40,"ack":true,"ts":1456415865,"q":0,"from":"system.adapter.onkyo.0","lc":1456415865}
! onkyo.0 2016-02-25 21:57:45 debug inMem message onkyo.0.* onkyo.0.master-volume
! onkyo.0 2016-02-25 21:57:45 debug onkyo.0 Received: command[MVL28]
! onkyo.0 2016-02-25 21:57:45 debug onkyo.0 Received: volume[40]
! onkyo.0 2016-02-25 21:57:45 debug onkyo.0 Received: master-volume[40]
! onkyo.0 2016-02-25 21:57:45 info onkyo.0 Got message: {"command":["master-volume","volume"],"argument":40,"iscp_command":"MVL28","host":"192.168.1.210","port":"60128","model":"TX-NR818"}
! onkyo.0 2016-02-25 21:57:45 debug onkyo.0 DEBUG (received_data) Received data from 192.168.1.210:60128 - {"command":["master-volume","volume"],"argument":40,"iscp_command":"MVL28","host":"192.168.1.210","port":"60128","model":"TX-NR81
! mqtt.0 2016-02-25 21:57:44 warn mqtt.0 Cannot resolve topic name for ID: onkyo.0.volume (object not found)
! mqtt.0 2016-02-25 21:57:44 warn mqtt.0 Cannot resolve topic name for ID: onkyo.0.volume (object not found)
! mqtt.0 2016-02-25 21:57:44 warn mqtt.0 Cannot resolve topic name for ID: onkyo.0.volume (object not found)
! mqtt.0 2016-02-25 21:57:44 warn mqtt.0 Cannot resolve topic name for ID: onkyo.0.volume (object not found)
! mqtt.0 2016-02-25 21:57:44 warn mqtt.0 Cannot resolve topic name for ID: onkyo.0.volume (object not found)
! mqtt.0 2016-02-25 21:57:44 warn mqtt.0 Cannot resolve topic name for ID: onkyo.0.volume (object not found)
! mqtt.0 2016-02-25 21:57:44 warn mqtt.0 Cannot resolve topic name for ID: onkyo.0.volume (object not found)
! mqtt.0 2016-02-25 21:57:44 warn mqtt.0 Cannot resolve topic name for ID: onkyo.0.volume (object not found)
! mqtt.0 2016-02-25 21:57:44 warn mqtt.0 Cannot resolve topic name for ID: onkyo.0.volume (object not found)
! onkyo.0 2016-02-25 21:57:44 debug onkyo.0 DEBUG (sent_command) Sent command to 192.168.1.210:60128 - MVL2D
! onkyo.0 2016-02-25 21:57:44 debug onkyo.0 DEBUG (command_to_iscp) raw command "MVL2D"
! onkyo.0 2016-02-25 21:57:44 debug onkyo.0 DEBUG (command_to_iscp) Zone: main | Command: volume | Argument: 45
! onkyo.0 2016-02-25 21:57:44 info onkyo.0 stateChange onkyo.0.volume {"val":45,"ack":false,"ts":1456415864,"q":0,"from":"system.adapter.admin.0","lc":1456415864}
! onkyo.0 2016-02-25 21:57:44 debug inMem message onkyo.0.* onkyo.0.volume

instalator

~~@instalator:~~

Перестала работать команда power, работает только system-power. Раньше работало, вроде ничего не делал. В принципе не принципиально, подвязал на другую переменную (Правда пришлось в onkyo.js заменить power на system-power), но сам факт не понятен. Может фильтр по моделям какой сработал из-за добавленных новых переменных. Надо поковырять список команд "высокого уровня".
var newVal = state.val;
                if (newVal === true || newVal === 'true' || newVal === '1' || newVal === 1) {
                    newVal = "on";
                } else if (newVal === false || newVal === 'false' || newVal === '0' || newVal === 0) {
                	if (ids == 'system-power') {
				newVal = "standby";
			} else {
		    	newVal = "off";
			}

```` `  

Я не понимаю что ломает логику.

Сейчас system-power не создается, а в нативных объектах

! {
! "_id": "power",
! "type": "state",
! "common": {
! "name": "Power state",
! "type": "boolean",
! "role": "button",
! "read": true,
! "write": true,
! "def": null
! },
! "native": {
! "command": "system-power",
! "values": ["standby","on","query"]
! }
! },
Заменил снова строчку на````
if (ids == 'power') {
newVal = "standby";

instalator

BlueFox а может из-за этих пакетов глюки ловить драйвер?

https://github.com/caolan/async

https://github.com/nodeca/js-yaml

instalator

После всех обновления ошибка с громкостью остается.

instalator

Вчера появился system-power)

Видимо с версиями глюк, а вот громкость так и работает криво, регулировать невозможно. Похоже что после изменения уровня не правильно отрабатывает запрос на текущее значение.

instalator

system-power появился и теперь на power ругается

onkyo-0 2016-03-11 18:19:13 error Error: ERROR (cmd_not_exist) Command power does not exist in zone main

instalator

BlueFox давай разберемся с драйвером, уже поднадоел он, громкостью управлять невозможно.

Может попробуем его подключить к тебе? я порты проброшу у себя.

ДОБАВЛЕНО!

Вспомнил, что я когда то вроде правил файл eiscp-commands.json и добавлял туда свой ресивер. Но так как у меня полетел бекап и пришлось IoB ставить с нуля я соответственно файлик не подложил.

В итоге сейчас добавил корректно свою модель в данный файл и вроде как все заработало. Все файлы с командами добавил в первый пост данного топика

Eisbaeeer

Hi Guys

I can not speak russian. So I don´t know about your discuss here. I have added some code to the onkyo adapter to control with VIS. Eventually you have the same thematic!?

After installing the "new test version" through npm you can use buttons to power on|off zone1 and zone2, muting and other things.

If you will thest this and report to me (I will do a pull request and need feedback from you) you can do the following:

1. Delete onkyo instance

2. Delete onkyo adapter

3. Delete all onkyo objects

4. Connect wiht SSH in the folder /opt/iobroker

5. npm install https://github.com/Eisbaeeer/ioBroker.o … ll/master/

The adapter appears in admin.

6. Install instance

7. configure (check box!)

8. Start adapter

Your feedback is welcome!

instalator

~~@Eisbaeeer:~~

Hi Guys

I can not speak russian. So I don´t know about your discuss here. I have added some code to the onkyo adapter to control with VIS. Eventually you have the same thematic!?

After installing the "new test version" through npm you can use buttons to power on|off zone1 and zone2, muting and other things.

If you will thest this and report to me (I will do a pull request and need feedback from you) you can do the following:

1. Delete onkyo instance

2. Delete onkyo adapter

3. Delete all onkyo objects

4. Connect wiht SSH in the folder /opt/iobroker

5. npm install https://github.com/Eisbaeeer/ioBroker.o … ll/master/

The adapter appears in admin.

6. Install instance

7. configure (check box!)

8. Start adapter

Your feedback is welcome! `
A strange development, why do we need a new driver for the VIS widget?

! ````
[{"tpl":"tplMetroTileToggle","data":{"visibility-cond":"==","visibility-val":1,"hover":"true","transform":"true",
"bg_class_false":"bg-gray","bg_class_true":"bg-teal","icon_class_false":"icon-arrow-up-2","icon_class_true":"icon-arrow-up-2",
"icon_badge_false":"","icon_badge_true":"","badge_bg_class_false":"","badge_bg_class_true":"","brand_bg_class_false":"",
"brand_bg_class_true":"","visibility-oid":"","oid":"","label_false":"Закрыто","label_true":"Закрыто","icon_false":"","icon_true":"",
"oidTrue":"onkyo.0.command","oidFalse":"onkyo.0.command","select_on_true":false,"oidTrueValue":"ZMT00",
"oidFalseValue":"ZMT01","badge_top":"0","badge_left":"0","gestures-offsetX":0,"gestures-offsetY":0,
"gestures-swiping-value":"","gestures-rotating-value":"","gestures-pinching-value":"","gestures-swipeRight-value":"",
"gestures-swipeLeft-value":"","gestures-swipeUp-value":"","gestures-swipeDown-value":"","gestures-rotateLeft-value":"",
"gestures-rotateRight-value":"","gestures-pinchIn-value":"","gestures-pinchOut-value":""},
"style":{"left":"246px","top":"30px","width":"88px","height":"91px","z-index":"9999","opacity":"1"},"widgetSet":"metro"}]

Eisbaeeer

~~@instalator:~~

A strange development, why do we need a new driver for the VIS widget? `

Hi Instalator

We asked some times in forum, how to use the onkyo with VIS. Nobody tell us, how to use the onkyo adapter.

Can you explain us how to use the adapter in VIS. Perhaps you realized a much better surface.

There are some more users who want to use the adapter with VIS. It would be great if you tell us how we can put on/off the zones and the other tools.

Perhaps you can provide some screenshots?

I used this strange way for 2nd driver because I don´t know how we should use it and I don´t want to change anything of your code. If the adapter works with VIS, let me say, hey, I learned verry much by programming in this adapter. There is no reaoson to use the code, if the adapter works with VIS.

Greetings Eisbaeeer

instalator

~~@Eisbaeeer:~~

~~@instalator:~~

A strange development, why do we need a new driver for the VIS widget? `

Hi Instalator

We asked some times in forum, how to use the onkyo with VIS. Nobody tell us, how to use the onkyo adapter.

Can you explain us how to use the adapter in VIS. Perhaps you realized a much better surface.

There are some more users who want to use the adapter with VIS. It would be great if you tell us how we can put on/off the zones and the other tools.

Perhaps you can provide some screenshots?

I used this strange way for 2nd driver because I don´t know how we should use it and I don´t want to change anything of your code. If the adapter works with VIS, let me say, hey, I learned verry much by programming in this adapter. There is no reaoson to use the code, if the adapter works with VIS.

Greetings Eisbaeeer `

All objects in IoB work with VIS.

I looked at your driver and understand your idea. Make better pullreqest the https://github.com/ioBroker/ioBroker.onkyo drivers and will test together. I think that BlueFox would not mind.

instalator

BlueFox! объкты для второй, третьей зоны не создаются по причине отсутствия имени команды в файле команд?

Получается для основной зоны имена прописаны:

"PWR":{
"name":"system-power","description":"System Power Command","values":{
"00":{
"name":"standby","description":"sets System Standby","models":"set1"},
"01":{
"name":"on","description":"sets System On","models":"set1"},
"QSTN":{
"name":"query","description":"gets the System Power Status","models":"set1"}}},

А для остальных зон нет:

"zone2":{
"ZPW":{
"standby":{
"value":"00","models":"set139"},
"on":{
"value":"01","models":"set139"},
"query":{
"value":"QSTN","models":"set139"}},

Если переименовать так? они создадутся? или почему тогда создаются не все объекты для команд?

"ZPW":{
"name":"zone2-power","description":"System Power Command","values":{
"00":{
"name":"standby","description":"sets System Standby","models":"set139"},
"01":{
"name":"on","description":"sets System On","models":"set139"},
"QSTN":{
"name":"query","description":"gets the System Power Status","models":"set139"}}},

instalator

Нашел косячек в файле команд.

Там для PWZ имя стоит power как и для основной зоны.

исправил на

"zone2":{
"Zone2.power":"ZPW",

И Zone2.power появился в списке объектов.

Так что не русско говорящий товарищь зря пилил свой код)

Добавлено! Создал пулреквест, получается мы создаем объекты только для зоны main и имена в разных зонах пересекаются.

Eisbaeeer

` > All objects in IoB work with VIS.

I looked at your driver and understand your idea. . `

OK, can you shortly explain, wich button do you use to power on/off and the corrosponding objekt?

I don't get running it with only one button.

Eisbaeeer

Gesendet von meinem SM-G920F mit Tapatalk

Eisbaeeer

` > All objects in IoB work with VIS.

I looked at your driver and understand your idea. . `

OK, can you shortly explain, wich button do you use to power on/off and the corrosponding objekt?

I don't get running it with only one button.

Eisbaeeer

Bluefox

Hello Installator,

i am on vacation till next week, so only then I can help you.

greetings,

bluefox

instalator

~~@Eisbaeeer:~~

` > All objects in IoB work with VIS.

I looked at your driver and understand your idea. . `

OK, can you shortly explain, wich button do you use to power on/off and the corrosponding objekt?

I don't get running it with only one button.

Eisbaeeer `
You wrote a little wrong code.

I have made changes that allow you to automatically create objects, but check when BlueFox will return from vacation.

https://github.com/GermanBluefox/node-e … 9fac6dca4d

https://github.com/ioBroker/ioBroker.on ... 1532dd5799

https://github.com/ioBroker/ioBroker.on ... ca6105cb19

Change at these files, delete all the objects in Onkio driver and restart the IOB.

instalator

~~@Eisbaeeer:~~

` > All objects in IoB work with VIS.

I looked at your driver and understand your idea. . `

OK, can you shortly explain, wich button do you use to power on/off and the corrosponding objekt?

I don't get running it with only one button.

Eisbaeeer `
I changed the driver. Objects are created automatically. Replace folder with the drivers, and delete all the objects in Onkio driver and restart the IOB.

instalator

~~@instalator:~~

I changed the driver. Objects are created automatically. Replace folder with the drivers, and delete all the objects in Onkio driver and restart the IOB.
filename="iobroker.onkyo.rar" index="0">~~ `
What result?

Eisbaeeer

~~@instalator:~~

~~@instalator:~~

I changed the driver. Objects are created automatically. Replace folder with the drivers, and delete all the objects in Onkio driver and restart the IOB.
filename="iobroker.onkyo.rar" index="0">~~ What result?

Hi,

I tested with the main power button. Result is, that the button doesn´t change the colour, because the status in iobroker is NOT "true" or "false" or "1" or "0". And this can not be working. Only this 4 states are allowed in iobroker. The object get´s the state (value) "standby".

I have attached a screenshot of my test. The buttons left of the marked are my working buttons who changes the logo by selecting a picture for the value "false" and an other for the value "true".

I tested the "Mute" button, too. This is working how it should !!!

So it seems, that only the feedback of power button is wrong. Can you change that from "standby" to "false" and if the receiver is on to "true"?

At the moment we get:

Receiver off = "standby"

Receiver on = "1"

Correct feedbacks will be:

Receiver off = "false"

Receiver on = "true"

Eisbaeeer

NEWS

Onkyo

Support us

791
Online

31.8k
Users

80.0k
Topics

1.3m
Posts

NEWS

Onkyo

Support us

791Online

31.8kUsers

80.0kTopics

1.3mPosts

791
Online

31.8k
Users

80.0k
Topics

1.3m
Posts