-
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not get Device by id #19
Comments
Just tried to read a new device and deleting the old one and that works. |
Also found out that the cards are quite different and now can deal with multi zone. That's great. |
Hi,
Thanks for your feedback. It is correct that you have to re-add the device. That’s a unfortunate side effect of the altered software to support multi zone.
I will look into adding the set volume then card. Unfortunately I do not have sufficient time at the moment. So I expect a small update not sooner than August.
Kind regards,
Rinze Winters
Op 13 mrt. 2023 om 08:38 heeft KvDaalen ***@***.***> het volgende geschreven:
Also found out that the cards are quite different and now can deal with multi zone. That's great.
Missing however is the set volume then card. Could you add that?
—
Reply to this email directly, view it on GitHub<#19 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACCQYBXZTVXY73VA3JFIATDW33FI3ANCNFSM6AAAAAAVYVR3OY>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Hi, I do not use the multi zone, but do use the old set volume card. Is it possible to keep the same functionality as the 0.4.1 version on the hp23? |
I have a VSX-S510. |
Hi,
Thanks for reaching out. I did add the set volume and mute card to test version 1.0.4.
Besides, in theory, all available actions could be done using the custom command card, it is not tested though.
I am not sure what you mean by “the tab”. Do you mean a flow card to in-/decrease the volume by 1 step?
Kind regards,
Rinze Winters
|
The set volume card should be visible in 1.04. I did not add the set volume relative. The communication manual including most commands accepted by receivers can be found here: https://github.com/rinwinte/com.pioneer.avr/tree/rinwinte/com.pioneer.avr/manual Although I am not able to test whether the apps works on Homey 2023 pro, I think it should. |
Thank You for answer, Alex |
Hi, I am not sure what is different. My language setting is Dutch. Not sure whether that’s a problem. I have four When cards. Of which one is … volume changed. I have two And cards. And 11 Then cards. Of which volume related are
How many cards do you have of each? |
Thanks! I see.. I made a copy paste error in the English language. You have to use the switch the .. to volume card. I will fix the error soon. |
Hello, I tested the switch the ... to volume card and found that the volume starts to fluctuate irregularly between different values. Cannot switch inputs or use mute. Various values flash on the receiver display. The solution is to restart the application, but as soon as I use sound editing, the situation repeats itself. Here is the code to generate the log function if it helps: 04164c53-ae75-4ab6-bc0d-390000171da6 |
Hi, I looked at the logs. But I have no clue why it is fluctuating. Some devices (like mine) support the SL command, which directly sets the volume to a certain level. Some devices, do not support that. So, for those devices, I implemented a looping function that increments/decrements one level until it reaches the required setting. In the logs I see your device uses the loop instead of the SL, so probably SL is not supported by your device. Could you tell me what happens when you manually set the volume using the slider in the app? If you make a big increment, does it display the new value directly on the pioneer screen? Or do you see it is incrementing until the setting is reached? (or does it fluctuate as well) |
Hi, |
It is hard to help with this issue as I cannot replicate it on my device. Could you try te create another diagnostic report directly after you see the first fluctuation. The log snippets are limited in length so I hope to get some more relevant info. |
Halo, 8c831f38-38bf-4773-be73-6e0c04d5deae Thank you for your help in solving the problem Alex |
Thanks! can you tell me your volume range? How many dB is displayed when (almost) off en loudest. My range is -80.0dB until +25.0dB. also tell me what your step size is. My device has 0.5dB per time. I think yours might be 1.0dB |
On the receiver's display, the range is 0-80, the step is 1. I don't know if it's in dB |
Probably I know the problem for your device. In order to solve it I need some details. Can you try the following:
|
Hi it could be that port 23 is not accepted for your device. Try 8102. Username and password are not required |
This port is ok. With the original remote control (I normally use harmony) there in telnet is a step of 2, the first step is 3. Example: 0-3-5-7-9-11.... max 151. The receiver display shows a range of 0-75. |
To be sure: Are u using zone1 (mainzone) or also zone2? |
I use mainzone |
i think it is just not supported. Sadly I could not find any documentation about supported commands for your device |
Try the new 1.05 version. In the settings you can change the volume range to 0 and 151. Check whether that works for you |
Hi,
Moved to the 1.03 version to be able to migrate to hp23. I get the following error in a toast: Could not get Device by ID. And "dit type apparaat word in de toekomst wellicht niet meer ondersteund."
It is a Pioneer sc-lx57
Report created:
e116cc67-ea03-4c6c-bf68-6e2b559143e3
Could you take a look at it? This is my last app that prevents me from starting the migration. A big thank you in advance
The text was updated successfully, but these errors were encountered: