Set Reaction > Script Action

[tunnus]

@toggledbits ok, sorry about that snippet, it was indeed a console log for a container.

I looked through reactor logs, but couldn't see any errors there. A bit challenging as there's a lot going on (a couple of variables update very often, every 1-3 seconds and those cause a lot of log events as rules referencing them get evaluated). Btw, there's a related request/question in this thread.

[toggledbits]

@tunnus If your specific concern is the Timer messages, don't be concerned. Long story shortened: these Timer objects were originally used for long intervals and the warning was put in place to help identify bugs in computing the length of those intervals, but they ended up being used for short intervals, too, and there are some conditions where those intervals can randomly be so short that they trigger the warning. I think it's time for this warning to be relegated to debug level or removed.

You clearly have something that's logging a lot, and that's causing frequent log rotations. This not only wastes time/cycles and bytes on the disk, but it also makes debugging anything on your system harder for the reason you stated: you can't find the errors, likely because (a) it's logging too much (you're sipping from a firehose), and (b) it's rotating so frequently that you're losing useful data quickly.

What I'd suggest is that you identify the affected rules (i.e. those that are responding to the frequent entity attribute changes), and increase their specific log levels to reduce the log output. You can do that for an individual rule. You need to get the rule ID, which you can derive from the UI by opening the rule's state in the list. You can also see it logged. Let's pick on rule-ktmrcd6d... we modify config/logging.yaml by adding the following:

  # The line below is indented two spaces; the line after is indented four spaces.
  "Rule#rule-ktmrcd6d":
    level: 3

This puts the logging minimum level at "NOTICE", so all of the INFO messages associated with rule evaluation will be suppressed for that rule only (other rules will not be affected). That should considerably reduce your log traffic.

I saw your question about the frequent updates as it relates to InfluxDB, and that's a sticky business. I'll respond to that over there.

[tunnus]

This post is deleted!

[tunnus]

@toggledbits thanks for the tip, now logging traffic is considerably slower (log rotation ca. 10 minutes)

[toggledbits]

userauth build 24137

• Updated the documentation theme and its supporting plugins; improved the appearance of code snippets with syntax highlighting in most cases; add line highlighting in many code snippets to draw attention to certain elements or changes.
• Dashboard: added new Thermostat type (supported by Level.updown layout) for capabilities hvac_heating_unit/hvac_cooling_unit. Evolving; further improvements coming.
• VirtualEntityController: Support for time-series data collection and aggregation. See the docs). As of this build, not all aggregators have been tested.
• Remove spurious debug warning about short timers.
• Fix detection of local docs and handling of static HTML files in the local installation.
• HassController: Bless Hass to 2024.5.3

[tunnus]

@toggledbits thanks, can confirm that (local) manual is fixed now, no more "initializing search"

[gwp1]

@toggledbits I think the restart reactor button is down again. When I click it I'm pushed back to the user login screen and immediately login to see the Status screen loading normally... not showing Disconnected as it usually does as it restarts. Logs provided in Dropbox.

[toggledbits]

Does it do that every time you use it?

[gwp1]

@toggledbits Yessir.

[toggledbits]

OK. That's normal behavior if the login/session cookie expires or is no longer valid. And it's all browser-side, so the logs aren't of any value there. And it's working for me, so we may have to dig a little. Next time you are tempted to use the Restart button, just do a plain refresh on your browser and see (report) what happens.

Also, what browser are you using? And, please upload your users.yaml file (redact any plaintext passwords)

[gwp1]

@toggledbits Using Brave browser. Redacted users.yaml on it's way.

[tunnus]

Happens to me as well (Chrome + userauth-24137-57b41335 on Docker)

[toggledbits]

If you just refresh the page instead of hitting the button, does it refresh, or go to the login page?

[tunnus]

If I refresh that Tools-page, it'll go to Status-page

[toggledbits]

userauth build 24143

• Fixes something that might, perhaps, address the Restart button issue some people are having (and I cannot reproduce at all on any broser). Also adds some debug (browser side) that we might be able to access to figure it out if it persists.
• Revamps the port determination. Some of you, particularly docker users, may find that your Reactor UI shifts to port 8554, and is actually the desired location for HTTPS service.
• Updated a lot of docs, including developer docs for building controllers.

[tunnus]

@toggledbits Restart-button still does not work. Chrome:

[toggledbits]

That's ACL restriction. You probably need to give logged-in users permission to use the API, or at least, that particular API.

[tunnus]

@toggledbits here's my users.yaml: (how should I change that?)

users:
  # This section defines your valid users. The format is:
  # username: password (one per line).

  admin: xxxxxxxx
  
groups:
  admin:
    users:
      - admin
    applications: true  # special form allows access to ALL applications
    api:
      default: allow

session:
  timeout: 43200  
  rolling: true  # activity extends timeout when true

# If log_acls is true, the selected ACL for every API access is logged.
log_acls: true
# If debug_acls is true, even more information about ACL selection is logged.
debug_acls: false

[toggledbits]

That's not up to date with current usage/structure. Refer to the users.yaml file that came in the dist-config directory, and the documentation for Access Control.

[tunnus]

@toggledbits ok, using that new file as a reference, now Restart-button is working