iloveicedgreentea / jvc_homeassistant

JVC Integration for Home Assistant
20 stars 4 forks source link

Integration 'crashes' projector #46

Open Upke opened 1 week ago

Upke commented 1 week ago

Dear developer(s),

Apparently this integration has the ability to lock up the projector. I've had this in two instances. The projector wouldn't respond to any commands, not from the remote control, nor from the buttons on the back (nor from home assistant). The only way to shut the projector down and regain control, is by cutting the power. Perhaps it's a bug, perhaps the way I'm using the integration.

Details: Current home assistant version: 2024.4.4 (although I've had the same issue a couple of weeks ago on an older version, stil running on a RP4) Current integration version: pre-release 4.4.08 Projector: JVC NP5 (US: DLA-RS1100) System: NUC with intel N100

My home cinema (with Denon receiver, JVC projector and Apple TV) is behind a Zigbee plug to cut down standby power usage. I've got an automation which stops and starts the integrations pertaining to the aforementioned devices). If I don't do it, my log's are filled with 'can't connect' errors.

Attached is my entire log file for the JVC integration but I'll quote some lines from it. Might be different issues.

On start up (and than repeat): _2024-04-24 13:29:44.960 ERROR (MainThread) [custom_components.jvc_projectors.remote] Attribute not found - b'00FD' is not a valid ResolutionModes 2024-04-24 13:29:44.960 ERROR (MainThread) [custom_components.jvc_projectors.remote] ValueError in handle_queue: b'00FD' is not a valid ResolutionModes 2024-04-24 13:29:45.764 ERROR (MainThread) [custom_components.jvc_projectors.remote] Attribute not found - b'IF0300PJ' is not a valid ColorSpaceModes 2024-04-24 13:29:45.765 ERROR (MainThread) [custom_components.jvc_projectors.remote] ValueError in handle_queue: b'IF0300PJ' is not a valid ColorSpaceModes 2024-04-24 13:29:46.168 ERROR (MainThread) [custom_components.jvc_projectors.remote] Attribute not found - b'IS0' is not a valid PowerModes 2024-04-24 13:29:46.169 ERROR (MainThread) [custom_components.jvc_projectors.remote] ValueError in handle_queue: b'IS0' is not a valid PowerModes 2024-04-24 13:29:46.570 ERROR (MainThread) [custom_components.jvc_projectors.remote] Attribute not found - b'PW1' is not a valid SourceStatuses 2024-04-24 13:29:46.570 ERROR (MainThread) [custom_components.jvc_projectors.remote] ValueError in handle_queue: b'PW1' is not a valid SourceStatuses 2024-04-24 13:29:46.972 ERROR (MainThread) [custom_components.jvc_projectors.remote] Attribute not found - b'SC1' is not a valid AnamorphicModes 2024-04-24 13:29:46.973 ERROR (MainThread) [custom_components.jvc_projectors.remote] ValueError in handle_queue: b'SC1' is not a valid AnamorphicModes 2024-04-24 13:29:47.374 ERROR (MainThread) [custom_components.jvc_projectors.remote] Attribute not found - b'IN0' is not a valid InputLevel 2024-04-24 13:29:47.374 ERROR (MainThread) [custom_components.jvc_projectors.remote] ValueError in handle_queue: b'IN0' is not a valid InputLevel 2024-04-24 13:29:47.775 ERROR (MainThread) [custom_components.jvc_projectors.remote] Attribute not found - b'3' is not a valid MaskModes 2024-04-24 13:29:47.775 ERROR (MainThread) [custom_components.jvc_projectors.remote] ValueError in handle_queue: b'3' is not a valid MaskModes 2024-04-24 13:29:48.176 ERROR (MainThread) [custom_components.jvc_projectors.remote] Attribute not found - b'IS2' is not a valid ContentTypes 2024-04-24 13:29:48.177 ERROR (MainThread) [custom_components.jvc_projectors.remote] ValueError in handle_queue: b'IS2' is not a valid ContentTypes 2024-04-24 13:29:48.979 ERROR (MainThread) [custom_components.jvc_projectors.remote] Attribute not found - b'PM0' is not a valid InputModes 2024-04-24 13:29:48.979 ERROR (MainThread) [custom_components.jvc_projectors.remote] ValueError in handle_queue: b'PM0' is not a valid InputModes 2024-04-24 13:29:49.382 ERROR (MainThread) [custom_components.jvc_projectors.remote] Attribute not found - b'IP6' is not a valid PictureModes 2024-04-24 13:29:49.382 ERROR (MainThread) [custom_components.jvc_projectors.remote] ValueError in handle_queue: b'IP6' is not a valid PictureModes 2024-04-24 13:29:53.358 ERROR (MainThread) [custom_components.jvc_projectors.remote] Attribute not found - b'PM03' is not a valid AspectRatioModes 2024-04-24 13:29:53.359 ERROR (MainThread) [custom_components.jvc_projectors.remote] ValueError in handle_queue: b'PM03' is not a valid AspectRatioModes 2024-04-24 13:29:53.761 ERROR (MainThread) [custom_components.jvc_projectors.remote] Attribute not found - b'IS3' is not a valid ContentTypeTrans 2024-04-24 13:29:53.762 ERROR (MainThread) [custom_components.jvc_projectors.remote] ValueError in handle_queue: b'IS3' is not a valid ContentTypeTrans 2024-04-24 13:29:54.162 ERROR (MainThread) [custom_components.jvc_projectors.remote] Attribute not found - b'PM1' is not a valid InstallationModes 2024-04-24 13:29:54.163 ERROR (MainThread) [custom_components.jvc_projectors.remote] ValueError in handle_queue: b'PM1' is not a valid InstallationModes 2024-04-24 13:29:54.564 ERROR (MainThread) [custom_components.jvc_projectors.remote] ValueError in handlequeue: invalid literal for int() with base 16: b'IN0'

Then there is: 2024-04-24 17:56:18.567 WARNING (MainThread) [asyncio] socket.send() raised exception. (x200 or so) After which I noticed that the projector had locked up/crashed and was unresponsive. Cut the power en shut down the JVC add-on. Might be unrelated as I see errors in my scripts as well.

Is there a way to research and troubleshoot this issue?

Upke commented 1 week ago

Forgot the log.

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

iloveicedgreentea commented 1 week ago

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

iloveicedgreentea commented 1 week ago

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?

Upke commented 1 week ago

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.

iloveicedgreentea commented 1 week ago

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

va-lemon commented 1 week ago

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.

iloveicedgreentea commented 1 week ago

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