Integration 'crashes' projector about jvc_homeassistant HOT 10 CLOSED

alright well at this point I will just add the new features to the latest stable version and call it a day. I don't have the time to debug this issue

from jvc_homeassistant.

Forgot the log.

home-assistant_jvc_projectors_2024-04-24T15-56-19.386Z.log

from jvc_homeassistant.

Damn I thought I fixed it. I will take a look

from jvc_homeassistant.

Just want to confirm you are definitely running the latest beta? Can you try to redownload and restart? I was able to reproduce this freeze in .07 and then can't reproduce it in .08.

The projector freezing is a JVC bug when it gets too many commands and their internal server crashes.

What were you doing when this happened?

from jvc_homeassistant.

Thanks for your response!
It says v4.4.08 on the hacs page but to be safe, I've redownloaded it and restarted home assistant.
I'm a bit wary to use the integration for fear of another lockup. Not sure how much uncooled shutdowns my lamp can take.

Edit: What I was doing when this happend...nothing I believe. I was just taking a break from watching a movie via my Apple TV. I run my pause automation. It turn ons the lights and does nothing with the projector. When I came back after 5 minutes the projector screen was blue (as if no signal) and it would not respond to any commands.

Edit; I thought about it some more, the crash might have happend much sooner. I started watching a movie on Netflix and wanted to activate a certain lens memory. I remember the projector not responding, but thought nothing of it. Later, when I took a break, the Apple tv screensaver comes on which have a different refresh rate and hdr setting for which the projector auto adjusts. Since it has crashed it can’t activate the proper settings and displays only a blue screen. Time stamp: 16.21 the first of the main exception errors.

from jvc_homeassistant.

Yeah thats understandable. If it happens again feel free to revert to the latest stable version

The previous lock up was caused by sending a command sometimes which I fixed in the latest beta and have not been able to replicate since. I will try to replicate in the meantime just in case

from jvc_homeassistant.

I have experienced the projector lockup with my NZ7 as well. I can’t remember if most recently was with the 4.4.0.8 version or 4.4.0.7. I use MadVR on my HTPC to send requests for picture mode changes through HA and also have my remote control change inputs after power on state is true.
I’ve added a queue manager in HA to see if I could limit the picture mode commands as MadVR could sometimes switch rapidly.
I will report back if I experience another lockup.

from jvc_homeassistant.

Verifying the version is crucial because I know for a fact it was a problem on 4.4.07 but I wasn't able to replicate it on 4.4.08 after adding some fixes

from jvc_homeassistant.

Hello,

I've just had the projector lock up again. Not sure when it happend but noticed it when the image started showing artifacts and the projector wasn't able to switch between different modes (resolution and hz). I started the projector at about 14.10 and from 15.00 a whole line of errors:

2024-05-05 15:00:26.696 WARNING (MainThread) [asyncio] socket.send() raised exception.
At 16.02 I noticed the projector had locked up but could've happened a lot sooner.
2024-05-05 16:02:41.893 WARNING (MainThread) [asyncio] socket.send() raised exception.

Running version v4.4.09.

You've set expectations about maintaining this integration quite clear in the other open issue. So this might get resolved, might not. No problem, I thank you for your effort!

from jvc_homeassistant.

please follow discussion in #42

from jvc_homeassistant.