-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[yamahareceiver] connect timed out since 2.5M4 #6328
Comments
I can confirm it. Problem with Pi4 and OH 2.5M4. But i have always 2019-11-15 14:01:42.343 [hingStatusInfoChangedEvent] - 'yamahareceiver:zone:9ab0c000_f668_11de_9976_00a0de711e58:Zone_2' changed from ONLINE to OFFLINE (CONFIGURATION_ERROR): connect timed out
2019-11-15 14:01:42.347 [hingStatusInfoChangedEvent] - 'yamahareceiver:zone:9ab0c000_f668_11de_9976_00a0de711e58:Main_Zone' changed from ONLINE to OFFLINE (CONFIGURATION_ERROR): connect timed out
2019-11-15 14:01:42.365 [hingStatusInfoChangedEvent] - 'yamahareceiver:zone:9ab0c000_f668_11de_9976_00a0de711e58:Zone_2' changed from OFFLINE (CONFIGURATION_ERROR): connect timed out to ONLINE
2019-11-15 14:01:42.396 [hingStatusInfoChangedEvent] - 'yamahareceiver:zone:9ab0c000_f668_11de_9976_00a0de711e58:Main_Zone' changed from OFFLINE (CONFIGURATION_ERROR): connect timed out to ONLINE On OH 2.4 was ok. |
I also get the timeouts for feature detection of RX-V3900 (now with really long exceptions). |
I am on the OH 2.5-SNAPSHOT and do not see any issues. |
The message : "Could not perform feature detection for RX-V3900" - I get it too for Yamaha RX-601D. But the receiver itself works. OH2.5 M6. One more idea, can you open the receiver url with a browser on the platform where openhab runs ? |
Hi @ozirissp are you able to open any of the following URLs from your browser while on local network? The browser should display (or donwnload) an XML file. http://192.168.86.219:80/YamahaRemoteControl/desc.xml I would like to rule out the network connectivity issues as suggested by @KenkiCK . If the yamaha receiver is getting different IPs in your home network the binding would not be able to reach it on 192.168.86.219. Static IPs assignments should be configured on the router, so that the device always gets the same IP. @michel53 and @RestOp could you guys also try the above URLs (with your counter part IPs)? |
Hi @zarusz , I am only able to get the first xml (desc.xml) desc.xml.txt The second enpoint (UnitDesc.xml) seems to not exist on my yahama device. Sometimes the bindings works (but it keeps going OFFLINE) ... I still get this kind of LOG :
Thanks for your help. |
I have tested the Yamaha binding with latest OH 2.5.0 and was able to reproduce the issue. A custom build containing the fix is available here:
I recommend testing with OH 2.5.0. Could you guys please test and report if it solved the problem? |
@zarusz Pozdro |
With the fix, the problem is gone for me, too. |
@zarusz Perfect ! This solve the problem for me too ! Thanks did you open a pull request ? |
@ozirissp I plan to open the PR once I get enough testing proof from the community. Should be pretty soon. |
On my receiver I am still observing one more glitch (see below). I will look into this and provide a new build JAR.
|
The fixed jar solved the Problem for me on a HTR4069 and Openhab 2.5 RC |
after installing the fix i have reproducible delay of approx. 5 -6 seconds for all rules. |
@cauer71 can you please provide some more details (and logs) on the said delay? Regarding the binding build for 2.4, I am not sure if there is any automated way to build these. I think I would have to rebase my fixes against 2.4 binding and built it locally. |
Signed-off-by: Tomasz Maruszak <maruszaktomasz@gmail.com>
Signed-off-by: Tomasz Maruszak <maruszaktomasz@gmail.com>
Signed-off-by: Tomasz Maruszak <maruszaktomasz@gmail.com>
…b#6835) Signed-off-by: Tomasz Maruszak <maruszaktomasz@gmail.com>
The last fix does not work for me:
desc.txt with the this version i had no delay in executing the rules. |
@cauer71 the below WARN is generated only when the binding is initializing:
When no connectivity to device is detected during init phase, the bridge thing will be put to OFFLINE state. Few ideas:
|
…b#6835) Signed-off-by: Tomasz Maruszak <maruszaktomasz@gmail.com> Signed-off-by: Tim Roberts <timmarkroberts@gmail.com>
you're right, I mistakenly had the original plugin and the patched version online at the same time :-( |
is it the intention that items are first set to NULL on an update and then get their actual value?
|
…b#6835) Signed-off-by: Tomasz Maruszak <maruszaktomasz@gmail.com> Signed-off-by: leluna <hengrui.jiang@googlemail.com>
…b#6835) Signed-off-by: Tomasz Maruszak <maruszaktomasz@gmail.com> Signed-off-by: Hans-Reiner Hoffmann <hans-reiner.hoffmann@gmx.de>
…b#6835) Signed-off-by: Tomasz Maruszak <maruszaktomasz@gmail.com>
…b#6835) Signed-off-by: Tomasz Maruszak <maruszaktomasz@gmail.com>
…b#6835) Signed-off-by: Tomasz Maruszak <maruszaktomasz@gmail.com>
…b#6835) Signed-off-by: Tomasz Maruszak <maruszaktomasz@gmail.com>
Since update 2.5M4 the Yamaha Binding with my Yamaha RX-V485 is not working anymore.
I tried to uninstall the binding then clear the cache and reinstall ...
I also tried the latest version from snapshot : 2.5.0.201911020354
And also a bad warning for device detection ...
See the forum here : communty thread
I use Openhabian on my Raspberry Pi 3 updated to the latest Milestone 2.5M4
My Yahama Receiver RX-V485 has the latest firmware (and was working fine before the update to the 2.5M4).
The text was updated successfully, but these errors were encountered: