Skip to content
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

Tons of errors in logs, controller unresponsive #722

Open
mhendu opened this issue Nov 1, 2024 · 3 comments
Open

Tons of errors in logs, controller unresponsive #722

mhendu opened this issue Nov 1, 2024 · 3 comments
Labels
stale There has not been activity on this issue or PR for quite some time.

Comments

@mhendu
Copy link

mhendu commented Nov 1, 2024

Problem/Motivation

Recently, within the past couple of weeks, I've been seeing the controller become unresponsive and tons of errors in my log file

Expected behavior

The controller should not become unresponsive, and there shouldn't be errors

Some of the errors (probably represent different issues):

Z-Wave error 103 - The controller is not yet ready!
Z-Wave error 1405 - The node failed to decode the message
Entity None (<class 'homeassistant.components.zwave_js.fan.ZwaveThermostatFan'>) does not set FanEntityFeature.TURN_OFF but implements the turn_off method
Entity None (<class 'homeassistant.components.zwave_js.fan.ZwaveThermostatFan'>) does not set FanEntityFeature.TURN_ON but implements the turn_on method
RuntimeError: RenderInfo already set while rendering Template<template=({{ 'homeassistant.components.zwave_js' in trigger.event.data.name }}) renders=5215>, this usually indicates the template is being rendered in the wrong thread

Copy link

github-actions bot commented Dec 2, 2024

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Dec 2, 2024
@mhendu
Copy link
Author

mhendu commented Dec 2, 2024

No, still having this issue and using the latest version.

@github-actions github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Dec 3, 2024
Copy link

github-actions bot commented Jan 3, 2025

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale There has not been activity on this issue or PR for quite some time.
Projects
None yet
Development

No branches or pull requests

1 participant