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

No ackTimer for #540

Open
zoizo030 opened this issue May 6, 2024 · 1 comment
Open

No ackTimer for #540

zoizo030 opened this issue May 6, 2024 · 1 comment

Comments

@zoizo030
Copy link

zoizo030 commented May 6, 2024

Describe the bug

Hello which means No ackTimer for loxone?

Expected behavior

I have the time in main.js
to const ackTimeoutMs = 2000;

Screenshots & Logfiles

loxfehler

and many more of the entries

Versions:

  • Adapter version: 3.0.1
  • JS-Controller version: 5.0.19
  • Node version: 18.20.2
  • Operating system: iobroker v6.13.16 on Synology Disk Station Docker (Buanet version)
  • Free Diskspace: 84%, Gesamte RAM-Auslastung: 2168 Mb / Frei: 17% = 6020 Mb [Server: buanet-iobroker-1 - 20 Prozesse]

Loxone Miniserver Gen.1 Version 14.7.3.6

Additional context
Contrib.: Alexa2 (Amazon Echo) 3.26.5 no longer transmits to Loxone.

@raintonr
Copy link
Collaborator

raintonr commented May 7, 2024

It means that events sent to your Miniserver by the adapter have not been acknowledged by the Miniserver within the timeout period.

You are probably flooding your Miniserver with too many updates in close succession.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants