Reintegrate external BSB LAN

@lmilcent

Hello

Thank you for this external BSB LAN integration that allows interfacing with all equipment managed by a SIEMENS controller. I am sharing a link to the list of all systems supported by BSB LAN: Modèles pris en charge de différents fabricants - BSB-LAN.

Given the large number of heat pumps or boilers that BSB LAN can manage, it would be great to be able to select the categories and indexes we want to manage in Gladys (http://xxx.xxx.xxx.xxx/JK=ALL). However, I don’t know if this is possible and, not being a developer, I can’t judge the feasibility. I think there must be possibilities in this direction. The idea would be to read the configuration file of the heat pump or boiler and then select the indexes we want.
This approach seems important to me because the indexes and categories, being standardized, are not used in all configurations and differ from one brand to another. Or between a heat pump and a boiler (Ex: The consumption feedback is available on a heat pump, but not on a boiler.

On HA, the integration offered is outdated because it can only manage the very first versions of BSB LAN. On the latest versions, there is no integration; it has to be done in Yaml and MQTT, which is cumbersome and tedious.

For my part, I have just tested the integration on my Atlantic Axeo Condens 5000 boiler, which manages 2 heating circuits and no hot water production

For my configuration, I would like to request these additional features:

  • Ability to manage a second heating circuit.
  • Ability to manage hot water production as an option (Useful for heat pumps and boilers) not all installations necessarily have hot water production.
  • Ability to manage the Reduced and Comfort settings independently.
  • Keep the operating mode selection: Protection Mode, Comfort Mode, Reduced Mode, and Automatic Mode, for both circuits.

Feedback on the first tests of the integration

Equipment: Axeo Condens 5000 boiler, RVS13.143/227 controller, BSB-LAN on ESP32, firmware 5.0.111.

1. Settings (write access, same behavior as the existing comfort setting)

  • Circuit 1: comfort 710 (already managed) and reduced 712.
  • Circuit 2: comfort 1010 and reduced 1012.
  • Keep the reduced setting less than or equal to the comfort setting.
  • Respect the controller limits: antifreeze 714 / 1014 (minimum) and maximum comfort 716 / 1016.

2. Circuit 2

  • Heating mode 1000 (same values as 700: 0 protection, 1 automatic, 2 reduced, 3 comfort).

3. State and temperatures of each circuit (read-only)

  • Circuit 1: state 8000, departure setting 8744, departure temperature 8743.
  • Circuit 2: state 8001, departure setting 8774, departure temperature 8773.

4. Domestic hot water

  • Mode 1600 (0 stop, 1 on, 2 eco).
  • Nominal setting 1610, reduced setting 1612, maximum 1614 (limit).
  • State 8003.

5. Boiler state (read-only)

  • State 8005, boiler temperature 8310, outside temperature 8700.
  • First burner speed signal 7881, burner fault signal S3 7870.
  • Last fault in history: 6800 (date) and 6801 (code).

Currently, I can’t write even though it works via the BSB LAN web interface. Here are the screenshots

Thank you again for this integration

Hi @XDECO,

Thanks for your very detailed feedback, it helped me find the issue right away.

The fake « read-only » is fixed in version 0.2.0, released today; it will arrive in the store at the next indexer run. It wasn’t your setting: your DEFAULT_FLAG 0 is correct, and your info page is right. Until its version 5.1.18, BSB-LAN sent Gladys an « write allowed » information that meant nothing (a small display bug in the firmware, fixed by them since). The module no longer relies on it: it now checks, parameter by parameter, what BSB-LAN says it can write. It works with your version 5.0.111, no need to update BSB-LAN.

What’s added:

  • Circuit 2: mode (protection, automatic, reduced, comfort), comfort and reduced setpoints, state, setpoint and departure temperature. It only appears if your controller actually has a circuit 2.
  • Circuit 1: the reduced setpoint becomes adjustable, as well as the state, setpoint, and departure temperature.
  • Setpoints: always between the frost protection and the maximum given by your controller, and the reduced one never above the comfort one.
  • Hot water (only if your installation has one): the mode (on, eco, off), the normal and reduced setpoints, and the state. It never exceeds 65 °C, nor the maximum of your controller.
  • Boiler, read-only: state, boiler temperature, outside temperature, first burner speed signal, burner fault S3, and the last fault (date and code).
  • Your own parameters: a new configuration field accepts up to 10 parameter numbers (for example 8326, 8338). Each one is displayed with the name and unit given by BSB-LAN.

For safety:

  • Commands remain disabled until you check « Allow commands ».
  • « Protection (frost) » and « Off » of the hot water always pass, even without this box: that’s what serves as a shutdown.
  • Gladys only says « successful » after having read the value back from the boiler.

What I didn’t do:

  • Choose entire categories (JK=ALL): that would make hundreds of parameters, several minutes of bus reading each time, and as many lines in Gladys. The list of numbers above does the same job for those you’re interested in.
  • Write parameters at will: no, on purpose. Only the settings listed above are modifiable, with their limits.

Small detail if you already created the device: your old « Reduced setpoint » lines remain read-only and continue to update. The new, adjustable ones appear in the Discovery tab: click on « Update » to add them.

I don’t have a BSB boiler to test in real life, so your help is very valuable. After the update, can you send me back:

  1. the message displayed by « Test the connection »;
  2. the logs of the integration (Logs tab of the container) right after a command, for example changing the reduced setpoint of circuit 1;
  3. what the new lines « First burner speed signal », « Burner fault S3 input » and « Last fault » show;
  4. if you have a circuit 2: does it appear correctly?

Remember to remove your password key and password if they appear anywhere before pasting (they normally never do).

Thanks again!

@lmilcent

Test feedback on a real adapter (2 heating circuits) and request to add the ambient temperature of circuit 2 (8770)

Hello,

Thank you for this integration. I tested it on BSB-LAN, with a Siemens controller and two heating circuits. I’m leaving you this feedback, as the repository indicates that it hadn’t yet been tried with 2 Circuits.

1. Commands failed when BSB-LAN’s MQTT was active

  • My BSB-LAN published to MQTT to a broker, in parallel, for Home Assistant.
  • In this configuration, most writes from Gladys (modes, setpoints) failed, with timeout or readback errors.
  • I disabled MQTT on BSB-LAN, without changing anything else in Gladys, then I set a read interval of 30 s.
  • The result is that all commands go through. I counted about fifteen in 5 minutes, on both circuits (modes, setpoints, protection).
  • The only remaining rejections are “Another command is still in progress” when I click less than 3 s apart. That’s the expected rule, not a defect.
  • Protection commands are properly confirmed (“protective command applied”).

My hypothesis is that the adapter processes only one request at a time, and the MQTT load keeps it busy too long for Gladys commands to fit within their deadlines (3.5 s for sending). I think it’s the load (interval, number of parameters) more than MQTT itself, but I haven’t tested a lighter setting.

Suggestion for the documentation. It would be useful to add a note in the README and in docs/fr.md / docs/en.md: “If BSB-LAN publishes to MQTT to a broker (for example for Home Assistant), the load on the adapter can cause Gladys commands to fail (timeouts). Disable MQTT on BSB-LAN, or lighten it (longer interval, fewer parameters), and keep a reasonable read interval in Gladys.” This would save other users from searching long for the cause.

2. Warning on /data

On every startup, I get an EACCES warning when writing to /data: [

[2026-11-01T18:41:21.445Z] [WARN] [bsblan] The state could not be saved in /data: EACCES

].
This isn’t blocking, but I assume that the pause state and protection commands aren’t then preserved after a container restart. It might be a permissions issue on the volume.

3. Request to add: ambient temperature of circuit 2 (8770)

Today, the ambient temperature is read only for circuit 1 (8740). My adapter does return a value for 8770; I checked with /JQ?Parameter=8770. Could you add it as standard, with a feature and the ambient temperature of circuit 2?

I can test your versions on my installation.

Thanks again, and bravo for the work.

Thanks a lot @XDECO for this test on a real two-circuit installation, that’s exactly what was missing! The documentation no longer says « never tested ».

Version 0.3.0 (Release v0.3.0 · LM1LC3N7/gladys-bsblan · GitHub) includes your three points; it will be in the store at the next indexer run.

1. MQTT from BSB-LAN

Your hypothesis is correct: the adapter processes one request at a time. The note has been added to the README, docs/fr.md and docs/en.md, almost in your own words, and in the read interval help. Additionally, when a command times out while the adapter was actually reachable, the message now adds: « BSB-LAN responds slowly: is it also publishing in MQTT, or is the read interval too short? ». The timeouts and the rule of 3 seconds between two commands do not change.

2. The EACCES warning on /data

This is not the integration: Gladys mounts a folder from your host into the container, /var/lib/gladysassistant/external-integrations/ext-lm1lc3n7-gladys-bsblan, and must give it to user 1000 when creating the container. In your case, it remained root. To fix, on the Gladys host:

sudo chown 1000:1000 /var/lib/gladysassistant/external-integrations/ext-lm1lc3n7-gladys-bsblan

(adjust the beginning of the path if your Gladys data is elsewhere), then restart the integration.

You are right about what is lost: without /data, a restart forgets a pause after an adapter error, the wait after rejected credentials, and an unapplied Protection. But commands, Protection and hot water (including when stopped) are never rejected or delayed due to /data. Version 0.3.0 displays this at startup in the integration status, with this correction.

3. Room temperature of circuit 2 (8770)

Added by default: « Room temperature (circuit 2) ». It is read only if your controller has a circuit 2, and only when the value is valid (not « — »). To have it on your existing device: Discovery tab, then « Update » on your BSB-LAN.

It is declared as a probe, so that Gladys does not average the two circuits in the room: only 8740 (circuit 1) counts as the room temperature of the device.

If you had entered 8770 in the additional parameters, it will continue to work. Once the new feature is added, you can remove 8770 from the list, then delete « BSB 8770 » from the device.

If you have a moment:

  1. After the chown and an integration restart, does the EACCES warning disappear? And if it’s not too indiscreet: Gladys version, and installation (docker run or compose, NAS, Docker rootless)? This would help me understand why Gladys couldn’t prepare this folder. The Gladys log might contain « Unable to prepare the data folder of integration ext-lm1lc3n7-gladys-bsblan ».
  2. Does the temperature of circuit 2 remain consistent with what your controller shows?
  3. If you try a lighter MQTT (longer interval, fewer parameters): do Gladys commands pass?

Thanks again, and thanks for offering to test!

@lmilcent Thanks for 0.3.0 and for your questions. Here is my summary, with the answers.

1. EACCES on /data: fixed with a chmod

The integration folder already belonged to 1000:1000, so chown didn’t change anything for me. The warning disappeared after a chmod 755 of the folder followed by a restart, and it hasn’t come back.

What I observed on my Synology NAS (DSM, Container Manager):

  • in the container, /data appeared as dr-xr-xr-x (owner node, uid 1000), and touch /data/test.tmp gave « Permission denied »;
  • the folder has a Synology ACL (the + in ls -l) that only grants read access to « everyone », with administrators and ContainerManager in read-write;
  • after chmod 755, touch works and /data appears as drwxr-xr-x.

Installation: Gladys gladysassistant/gladys:v5 (exact version: V5.3), container launched by docker run or from the Container Manager interface (no compose project), as root and in privileged mode, so not rootless. Automatic update by Watchtower.

Gladys log: I don’t find « Unable to prepare the data folder » or « data folder ». The folder was created on November 1st at 18:41 UTC, when the integration reconnected, and the first EACCES arrived 17 seconds later.

2. BSB-LAN MQTT: confirmed

With BSB-LAN MQTT active, commands are refused (« The current value could not be reread just before (timeout) »). With MQTT turned off, they all go through, except for the 3-second rule between two commands. I didn’t try a lighter setting, only active or off. The new message from 0.3.0 (« does it also publish in MQTT… ») appeared exactly in this case for me.

3. Temperature of circuit 2 (8770)

The Temperature value is correct

4. Refused commands: the card keeps the entered value

A point observed while manually adjusting the setpoints of circuit 2:

  • I set the reduced setpoint to 15.5 in Gladys. The card displays 15.5.
  • The integration refuses the command (« Another command to BSB-LAN is still in progress: not sent »), because the previous one, the comfort setpoint, was not finished.
  • BSB-LAN remains at 16, but Gladys continues to display 15.5 until the page is reloaded.
[2026-11-02T19:55:59.374Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-reduced-target refused: Another command to BSB-LAN is still in progress: not sent.
[2026-11-02T19:55:59.380Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 20

According to what I read in the 0.2.0 code, the value read back from BSB-LAN (16) is identical to the last value published, so it is not sent back to Gladys: unchanged values are only republished every 30 minutes (stateHeartbeat), while BSB-LAN is read every 30 seconds for me. If 0.3.0 behaves differently, ignore this point.

Two suggestions, at your discretion:

  1. After refusing a command, immediately republish the real value of the concerned feature, so that the card returns to 16.
  2. Queue the second command instead of refusing it when it arrives during the first (which takes 2 to 3 seconds to be confirmed). Adjusting two setpoints in a row is a common use of a thermostat.

I understand that the rule of one command at a time protects the adapter. The first suggestion would be enough to avoid misleading display without touching it.

Thanks again for your reactivity.

Thanks @XDECO for these precise answers, and for the Synology investigation!

Version 0.3.1 (Release v0.3.1 · LM1LC3N7/gladys-bsblan · GitHub) incorporates your two suggestions; it will arrive in the store at the next indexer run.

Rejected Commands: The Card Returns to the Real Value

Your reading of the code was correct: the re-read value, identical to the last published one, was not returned for 30 minutes. Now, when a command is rejected or abandoned without being sent, the card immediately returns to the value read on BSB-LAN (16 in your example). If the command could be sent without confirmation (the « timeout » case with MQTT active), the integration does not randomly reset the old value: the re-reads at 5 s and 20 s decide and publish the real value.

Two Consecutive Commands: Both Go Through

You are right, this is normal usage of a thermostat. A command that arrives during another one, or less than 3 s after, is no longer rejected: it waits and goes right after, always one request at a time and with a 3 s gap for the adapter. The message becomes « Another command to BSB-LAN is in progress: this one waits and goes after it… ».

  • If you change the same setting twice while waiting, only the last value is sent.
  • A command that is waiting goes through all checks again when it is time to go.
  • A Protection or the hot water turned off always go first and cancel pending commands, like a restart of the integration.
  • A command that cannot be sent within 30 s is abandoned, not sent, and its card returns to the real value.

/data on Synology

Thanks for the diagnosis: the documentation and the integration message now ask for owner 1000 and write permission. They describe your case (folder already at 1000:1000 but in dr-xr-xr-x with a Synology ACL, fixed by chmod 755), with ls -ld to verify.

MQTT and 8770: Thanks for the confirmations, nothing to change on this side.

If you have a moment with 0.3.1:

  1. Do two consecutive commands both go through? Is the waiting message clear?
  2. Does a rejected command (for example while a Protection is going) make the card return without reloading the page?
  3. Does the ACL of your folder remain correct after an update by Watchtower?

Thanks again for your tests, they have made the integration much better!

@lmilcent

Hello,

Thank you for handling the /data folder. I tested directly with version 0.3.2. Here are my feedback (logs in UTC, I am in UTC+1).

1. Two consecutive commands
Yes, everything starts correctly. Example on 07/11 around 06:20 UTC: several quick changes of hc2-setpoint, then hc2-reduced-target. Intermediate values are discarded (« A newer value of this setting arrived while it was waiting: not sent »), the last one is sent and confirmed by the reread (hc2-setpoint 21, hc2-reduced-target 11.5). When the two commands follow each other, the second one waits for the first one (« Another command to BSB-LAN is in progress »).
The message is understandable, but it is displayed as WARN while it is normal behavior. It would be more readable as INFO/DEBUG, with two distinct messages: « waiting » and « replaced by a newer value ».

2. Rejected command
The range control works: on 07/11 at 06:45 UTC, hc2-setpoint was rejected with « The controller accepts this command between 16 and 21 °C currently: not sent ». The message is very clear. The lower bound follows the reduced command (hc2-reduced-target was at 16 at that moment; it was at 11.5 earlier in the morning), the upper bound was at 21.
After the rejection, the card returned alone to the real value (21 °C), without reloading the page.
Suggestion: bound the card slider to the range read on the controller to avoid these rejections.

3. Folder permissions after update
Gladys update forced manually on 06/11 (container recreated, integration restarted and reconnected alone at ≈17:14 UTC). Then: ls -ld gives drwxr-xr-x 1000 1000, synoacltool -get responds « It’s Linux mode » (no more Synology ACL, probably due to my previous chmod 755), and writing to /data from the container works (touch/rm OK). I haven’t seen Watchtower pass yet; I’ll let you know if something changes.

Other remarks on the logs

  • During the outage related to the Gladys update, « Sending to Gladys failed: fetch failed » is repeated about once per second (about sixty lines in 2 minutes). It would be more readable to display it only once, then add a message of return to normal.
  • The timestamps are in UTC (suffix Z). An option to display the local time, or the mention « UTC », would avoid confusion.

Suggestion: make the BSB-LAN integration known
Now that the Gladys integration works correctly (commands, command ranges, recovery after restart), it would be useful to inform Frederik Holst, the maintainer of BSB-LAN, at the address bsb@code-it.de. He could add it to the « Home Automation Integrations » page of the documentation (Connecter à la Smart Home - BSB-LAN), where Gladys does not yet appear, which would help Gladys users to find it. In the message, it would be good to specify that MQTT must remain deactivated on BSB-LAN for the commands to work, and to give the link to the integration repository.

Thank you again for your work!

Thanks @XDECO for this very complete feedback on 0.3.2, and for the checks on the /data folder. It’s in the v0.3.3: Release v0.3.3 · LM1LC3N7/gladys-bsblan · GitHub (it will arrive in the store at the next indexer run).

1. Waiting messages in INFO
A command waiting behind another is written once, in INFO, when it starts waiting. A pending command replaced by a more recent value has its own INFO line. Real rejections remain in WARN, as do a Protection or a hot water shutdown.

2. The slider bounded to the regulator range
Not possible for now: Gladys never updates the minimum and maximum of an already created device. And as you saw, the range moves while running (the low bound follows the reduced setpoint, 11.5 then 16): fixed bounds at creation would then reject valid values. So we keep the rejection with the indicated range, then the card returns alone to the true value. It’s explained in the documentation.

3. « Sending to Gladys failed » repeated
It is written only once per failure, then « Sending to Gladys works again » on return. If the cause changes during the failure, the new cause is written once more, up to three times (numbers, like an hour or a port, do not count as a new cause).

4. Times in UTC
They come from the common log of the SDK for integrations, not from the BSB-LAN integration: I can’t convert them to local time on my side. The documentation now specifies that it’s UTC (the final Z).

Thanks also for the point on the folder after the update: it’s good if the Synology ACL doesn’t come back. Let me know if Watchtower changes anything.

To notify the BSB-LAN maintainer, good idea, I’ll get back to you on that.

@lmilcent

Hello, and thank you for the integration and for the quick release of v0.3.0.

Rejected commands: 3.5s budget too short when BSB-LAN slows down after a write, and commands blocked during the entire backoff

I still have rejected commands on hc2-setpoint, even though MQTT is disabled on BSB-LAN and nothing else is querying it. I measured BSB-LAN directly and read the code to understand; everything is below.

Configuration

  • Integration version: [v0.3.0 - correct if different]
  • Gladys on a Home Assistant Yellow (CM4, equivalent to Raspberry Pi 4); no other client is querying BSB-LAN (no Home Assistant, no MQTT)
  • BSB-LAN 5.1.42 on ESP32, Wi-Fi, BSB bus, MQTT logging disabled, debugging disabled
  • 2 heating circuits, no domestic hot water
  • Tested read intervals: 30 s, 60 s, and 10 min

Logs (UTC)

19:44:27.384 WARN refused: The current value could not be reread just before (timeout): command not sent.
19:44:29.599 WARN refused: BSB-LAN responded too slowly to send the command on time: not sent.

20:08:20.779 INFO hc2-setpoint: 18          (sent)
20:08:25.047 INFO hc2-setpoint: 19.5        (sent 4.3 s later, after commandSpacing)
20:08:46.694 WARN 192.168.8.39: unreachable; next try in 600 s
20:09:04.364 WARN refused: This device is not the adapter currently being read (BSB-LAN unresponsive...)
20:09:18.712 WARN refused: (same message)

20:14:48.046 INFO hc2-setpoint: 20          (sent)
20:14:57.903 WARN refused: ... could not be reread just before (timeout)   (9.9 s after the previous write, single click)
```BSB-LAN had not restarted (21 hours of operation at that point) and responded in 200 just after.

**BSB-LAN Measurements** (curl from a PC on the same network, `GET /1010`)
- At rest, integration stopped: 0.23 to 0.27 s per read, with a few peaks (0.45, 0.61, 1.13, 1.16 s) over 40 reads
- Grouped read of 12 parameters (`/JQ=...`): 2.6 to 3.5 s, i.e. approximately 0.22 to 0.29 s per parameter
- Integration running, reads launched just after a command: 0.68, 1.12, 1.92, 0.92, 1.21 s for approximately 10 s, then back to 0.25 s

After a write, BSB-LAN takes 1 to 2 s per read for about ten seconds.

**What I understand from the code** (`src/constants.js`, `src/app.js`)
1. The budget for a command is `commandSendBy` = 3500 ms from reception, and the reread is limited by `commandReadMax` = 2500 ms. In `commandSession`, the reread does `raw.info()` then `raw.query()`, so two requests in these 2.5 s. You also have to wait for the end of any ongoing /JQ request (4 parameters, approximately 1 s). With reads at 1-2 s after a write, this budget doesn't hold. For comparison, `requestTimeout` is 15000 ms for periodic reads.
2. The reread is not retried: a failure calls `this.block(err)` and the command is refused.
3. After a failed read, `online = false`, so `live` is false and `checkBeforeSend` refuses any user command (`ERRORS.unknownDevice`) during the entire backoff. A user command does not trigger its own attempt (only `protect()` and the test button do). As the backoff is never shorter than the read interval, with 10 min, a single timeout blocks commands for 10 min.

@lmilcent 

For priority: I saw that commands already go ahead of reads in the queue in the Gate, thanks, that's great.

**Proposals**
1. Make `commandSendBy` and `commandReadMax` configurable, or extend them (8 to 10 s approximately) for slow adapters. Or start the budget from the beginning of the reread rather than from reception.
2. Retry the reread once before refusing.
3. Avoid `raw.info()` for each command if the adapter has been identified recently (for example during the last successful read).
4. During the backoff, allow a user command to make its own attempt (like `protect()`), instead of refusing it outright; or decouple the backoff from the read interval.

I can test a corrected build on my heating if it helps, and provide other logs.

For transparency: I did this diagnosis and wrote this ticket with the help of Claude (Anthropic's AI). The logs and measurements come from my installation. The code reading was done on the main branch and may contain interpretation errors: feel free to correct me.

Thanks!

Thanks @XDECO for this very precise diagnosis, including measurements: your code analysis was correct. It’s in v0.3.4: Release v0.3.4 · LM1LC3N7/gladys-bsblan · GitHub (it will arrive in the store on the next indexer run).

1. Command Budget
It no longer starts from reception but from when the command gets the adapter: 15 s to obtain it, then 12 s for adapter verification and re-read. Gladys has its response in 4.2 s; if BSB-LAN is slow, it says “the command continues”, and the result then arrives in the logs. With your measurements (1 to 2 s per read after a write), the command passes.

2. During the Retry Delay
A command is no longer automatically rejected: it makes its own attempt and only leaves if the MAC address of the adapter is verified. If this attempt fails, the next ones wait 30 s, to avoid hammering a non-responsive BSB-LAN. A Protection or hot water shutdown is never retained.

3. What I Didn’t Take from Your Proposals

  • Retry the re-read: no, no request is retried; the longer budget covers your case.
  • Skip adapter verification: no, the MAC is verified before each command. It is served by the ESP32 itself, not read on the bus, so it costs little.
  • Make delays adjustable: no, the code knows how to size them itself.

4. Two New Features That Follow

  • A command not yet sent is replaced by a more recent value of the same setting: if you click 22 then 23, only 23 is written.
  • After a rejection, the card takes the value that the command just re-read. If BSB-LAN does not respond at all, it waits for the next read.

Worst case: a direct command can leave up to approximately 27 s after the click, a queued command approximately 42 s. It’s in the documentation.

I still don’t have a BSB-LAN: everything has been tested on a fake adapter that reproduces your response times. Your offer to test a build comes at a good time: let me know if the rejections disappear for you, with a few lines of logs if they don’t.

Hi @lmilcent

With the latest version of BSB-LAN, the setpoint changes are working fine.

This is not a bug: everything works and the rejections are justified. These are optimization suggestions to make the messages clearer. I did indeed run some “Bourain” tests :slightly_smiling_face: to see the behavior.

Tests were only done on circuit 2. Circuit 1 should follow the same rules with its own parameters (710, 712, 714, 716), but I haven’t checked.


1. Specify where the regulator’s limits come from

The message “The regulator accepts this setpoint between 17 and 21 °C currently” is correct, but it doesn’t say which parameter to modify. It took me a moment to understand that the 21 °C maximum comes from parameter 1016.

From my logs:

  • comfort setpoint (1010): between the reduced setpoint (1012) and the maximum comfort setpoint (1016);
  • reduced setpoint (1012): between the frost protection setpoint (1014) and the comfort setpoint (1010).

BSB-LAN page for circuit 2 (/K9): with the reduced setpoint (1012) at 17 °C and the maximum comfort (1016) at 25 °C, the comfort setpoint (1010) is accepted between 17 and 25 °C. The reduced setpoint is limited between frost protection (1014, 8 °C) and the comfort setpoint.

Suggested message:

The regulator accepts this setpoint between 17 °C (reduced setpoint, 1012) and 25 °C (maximum comfort, 1016): not sent.

2. “Between 5 and 35 °C” messages

Some rejections display “The setpoint must be between 5 and 35 °C”. These limits seem to come from the Gladys configuration, not the regulator, and the log doesn’t indicate the requested value: impossible to know why the command was rejected.

Extract (UTC):

16:48:31.396 INFO  [bsblan] BSB-LAN hc2-setpoint: 22.5
16:48:41.769 WARN  hc2-setpoint refused: The setpoint must be between 5 and 35 °C: not sent.
16:48:44.523 WARN  hc2-setpoint refused: The setpoint must be between 5 and 35 °C: not sent.
16:48:49.032 INFO  [bsblan] BSB-LAN hc2-setpoint: 24
16:48:53.395 WARN  hc2-setpoint refused: The regulator accepts this setpoint between 10 and 25 °C currently: not sent.

Another series: 9 rejections “between 5 and 35 °C” between 16:18:47 and 16:19:11, then “hc2-setpoint: 21” sent at 16:19:17.

Suggestions:

  • indicate the requested value in each rejection message;
  • display the limits read from BSB-LAN instead of Gladys’s 5-35 range;
  • ideally, adapt the slider limits in Gladys to the BSB-LAN limits, for both circuits.

3. For information

Between 16:24 and 16:27 (UTC), right after modifying parameter 1016, all hc2-setpoint commands were rejected with “BSB-LAN did not give the current value or the allowed range of this setting”. Everything returned to normal around 16:33. Is this expected (re-reading limits after a change)?


The full log is attached.

Full log (UTC) ``` [2026-11-14T16:02:14.788Z] [INFO] Starting the BSB-LAN integration... [2026-11-14T16:02:15.877Z] [INFO] [gladys-sdk] connected to Gladys (http://172.30.0.1:80) [2026-11-14T16:03:56.682Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 22.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:03:57.523Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The regulator accepts this setting between 16 and 21 °C currently: not sent. [2026-11-14T16:03:58.581Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The regulator accepts this setting between 16 and 21 °C currently: not sent. [2026-11-14T16:04:52.065Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 21.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:04:52.501Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 22 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:04:52.501Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T16:04:53.218Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T16:04:53.865Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 19.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:04:53.871Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T16:04:54.484Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 18 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:04:55.048Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T16:04:58.004Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 18 [2026-11-14T16:05:15.541Z] [INFO] [bsblan] BSB-LAN hc2-reduced-targ ```et 14 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:05:17.348Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-reduced-target not sent: replaced by a newer value of the same setting [2026-11-14T16:05:18.371Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target: 14 [2026-11-14T16:05:18.577Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 14.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:05:19.766Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 11.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:05:19.767Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T16:05:22.954Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The regulator accepts this setting between 14 and 21 °C currently: not sent. [2026-11-14T16:05:47.774Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 20 [2026-11-14T16:05:56.197Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 19 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:05:56.749Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T16:05:58.386Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 19 [2026-11-14T16:06:15.409Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 18 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:06:17.445Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T16:06:18.485Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 18 [2026-11-14T16:06:27.883Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target: 15.5 [2026-11-14T16:08:42.265Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 20 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:08:42.528Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T16:08:43.592Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 20 [2026-11-14T16:09:15.771Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target 17 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:09:16.370Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target 17.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:09:16.371Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-reduced-target not sent: replaced by a newer value of the same setting [2026-11-14T16:09:16.639Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target 18 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:09:16.640Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-reduced-target not sent: replaced by a newer value of the same setting [2026-11-14T16:09:17.377Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-reduced-target not sent: replaced by a newer value of the same setting [2026-11-14T16:09:18.611Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target: 18 [2026-11-14T16:09:31.055Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target: 17 [2026-11-14T16:10:30.125Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The setpoint must be between 5 and 35 °C: not sent. [2026-11-14T16:10:31.419Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 21 [2026-11-14T16:11:14.315Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The setpoint must be between 5 and 35 °C: not sent. [2026-11-14T16:11:14.892Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The setpoint must be between 5 and 35 °C: not sent. [2026-11-14T16:11:19.183Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The setpoint must be between 5 and 35 °C: not sent.oyée. [2026-11-14T16:11:24.822Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The regulator currently accepts this setpoint between 17 and 21 °C: not sent. [2026-11-14T16:11:43.242Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The regulator currently accepts this setpoint between 17 and 21 °C: not sent. [2026-11-14T16:17:34.333Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The setpoint must be between 5 and 35 °C: not sent. [2026-11-14T16:17:36.713Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 23 [2026-11-14T16:18:47.967Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The setpoint must be between 5 and 35 °C: not sent. [2026-11-14T16:18:48.440Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The setpoint must be between 5 and 35 °C: not sent. [2026-11-14T16:18:55.583Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The setpoint must be between 5 and 35 °C: not sent. [2026-11-14T16:18:56.047Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The setpoint must be between 5 and 35 °C: not sent. [2026-11-14T16:19:06.967Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The setpoint must be between 5 and 35 °C: not sent. [2026-11-14T16:19:07.326Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The setpoint must be between 5 and 35 °C: not sent. [2026-11-14T16:19:08.722Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The setpoint must be between 5 and 35 °C: not sent. [2026-11-14T16:19:09.721Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The setpoint must be between 5 and 35 °C: not sent. [2026-11-14T16:19:11.542Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The setpoint must be between 5 and 35 °C: not sent. [2026-11-14T16:19:17.372Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 21 [2026-11-14T16:24:31.516Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 20 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:24:31.897Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: BSB-LAN did not give the current value or the allowed range of this setting: not sent. [2026-11-14T16:24:32.931Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: BSB-LAN did not give the current value or the allowed range of this setting: not sent. [2026-11-14T16:24:38.550Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 20 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:24:39.308Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: BSB-LAN did not give the current value or the allowed range of this setting: not sent. [2026-11-14T16:24:40.372Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: BSB-LAN did not give the current value or the allowed range of this setting: not sent. [2026-11-14T16:24:42.266Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: BSB-LAN did not give the current value or the allowed range of this setting: not sent. [2026-11-14T16:25:19.220Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-reduced-target refused: The controller accepts this setpoint between 8 and 21 °C currently: not sent. [2026-11-14T16:25:23.639Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target 24 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:25:23.639Z][2026-11-14T16:25:24.419Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-reduced-target not sent: replaced by a newer value of the same setting [2026-11-14T16:25:27.375Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-reduced-target refused: The regulator currently accepts this setting between 8 and 21 °C: not sent. [2026-11-14T16:25:29.728Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target 26 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:25:30.513Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-reduced-target refused: The regulator currently accepts this setting between 8 and 21 °C: not sent. [2026-11-14T16:25:31.548Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-reduced-target refused: The regulator currently accepts this setting between 8 and 21 °C: not sent. [2026-11-14T16:25:36.422Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 20 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:25:37.410Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: BSB-LAN has not given the current value or the allowed range of this setting: not sent. [2026-11-14T16:25:38.460Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: BSB-LAN has not given the current value or the allowed range of this setting: not sent. [2026-11-14T16:25:42.184Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: BSB-LAN has not given the current value or the allowed range of this setting: not sent. [2026-11-14T16:25:50.771Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: BSB-LAN has not given the current value or the allowed range of this setting: not sent. [2026-11-14T16:25:54.683Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: BSB-LAN n'a did not provide the current value or the allowed range of this setting: not sent. [2026-11-14T16:27:17.779Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: BSB-LAN did not provide the current value or the allowed range of this setting: not sent. [2026-11-14T16:27:21.158Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: BSB-LAN did not provide the current value or the allowed range of this setting: not sent. [2026-11-14T16:27:31.328Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: BSB-LAN did not provide the current value or the allowed range of this setting: not sent. [2026-11-14T16:27:47.430Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: BSB-LAN did not provide the current value or the allowed range of this setting: not sent. [2026-11-14T16:27:49.056Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: BSB-LAN did not provide the current value or the allowed range of this setting: not sent. [2026-11-14T16:32:58.960Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 20.5 [2026-11-14T16:33:08.015Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target: 16.5 [2026-11-14T16:41:59.997Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 21 [2026-11-14T16:42:07.008Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 18.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:42:07.165Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T16:42:09.008Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 18.5 [2026-11-14T16:42:22.909Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 20.5 [2026-11-14T16:42:25.821Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 21.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:42:28.164Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The regulator currently accepts this instruction between 16.5 and 21 °C: not sent. [2026-11-14T16:46:24.669Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 22.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:46:25.211Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T16:46:27.341Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 22.5 [2026-11-14T16:46:29.252Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target 18 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:46:31.588Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target: 18 [2026-11-14T16:46:31.979Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 23.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:46:37.092Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 23.5 [2026-11-14T16:46:38.701Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 23.5 (queued): done [2026-11-14T16:46:57.199Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 19.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:46:57.417Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 19 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:46:57.418Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T16:46:57.600Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T16:46:57.633Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 18.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:46:58.622Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T16:46:59.668Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 18.5 [2026-11-14T16:46:59.729Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 18 waiting: another commandto BSB-LAN is running, sent after it [2026-11-14T16:47:01.863Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 17.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:47:01.863Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T16:47:02.180Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 17 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:47:02.181Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T16:47:04.327Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The regulator currently accepts this setting between 18 and 25 °C: not sent. [2026-11-14T16:47:07.997Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The regulator currently accepts this setting between 18 and 25 °C: not sent. [2026-11-14T16:48:21.403Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 14 [2026-11-14T16:48:21.612Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 11 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:48:23.071Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 13 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:48:23.071Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T16:48:26.776Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 13 [2026-11-14T16:48:27.051Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 20.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:48:27.231Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 13 (queued): done [2026-11-14T16:48:27.383Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 21 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:48:27.383Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T16:48:29.743Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 22.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:48:29.744Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T16:48:31.396Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 22.5 [2026-11-14T16:48:41.769Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The setpoint must be between 5 and 35 °C: not sent. [2026-11-14T16:48:44.110Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 22 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:48:44.523Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The setpoint must be between 5 and 35 °C: not sent. [2026-11-14T16:48:44.544Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T16:48:47.060Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 24 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:48:47.387Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T16:48:49.032Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 24 [2026-11-14T16:48:51.054Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 28.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:48:53.395Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The controller currently accepts this setpoint between 10 and 25 °C: not sent. [2026-11-14T16:48:59.770Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-reduced-target refused: The setpoint must be between 5 and 35 °C: not sent. [2026-11-14T16:49:04.92[2Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-reduced-target refused: The regulator currently accepts this setpoint between 8 and 24 °C: not sent. [2026-11-14T16:53:14.807Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-reduced-target refused: The setpoint must be between 5 and 35 °C: not sent. [2026-11-14T16:53:17.710Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target: 9.5 [2026-11-14T16:53:19.669Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target 9 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:53:21.977Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target: 9 [2026-11-14T16:53:23.465Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target 8.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:53:27.010Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target 8 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:53:27.745Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target 8.5 (queued) not sent: replaced by a newer value of the same setting [2026-11-14T16:53:29.603Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target: 8 [2026-11-14T16:53:31.002Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target 7.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:53:34.358Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-reduced-target refused: The regulator currently accepts this setpoint between 8 and 24 °C: not sent. [2026-11-14T16:53:37.788Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-reduced-target refused: The regulator currently accepts this setpoint between 8 and 24 °C: not sent. [2026-11-14T16:53:39.470Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target 6 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T16:53:39.603Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-reduced-target not sent: replaced by a newer value of the same setting [2026-11-14T16:5[3:41.250Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-reduced-target refused: The controller currently accepts this command between 8 and 24 °C: not sent. [2026-11-14T16:55:34.297Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target: 13 [2026-11-14T17:01:17.605Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target: 16 [2026-11-14T17:01:19.145Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target 17 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T17:01:21.885Z] [INFO] [bsblan] BSB-LAN hc2-reduced-target: 17 [2026-11-14T17:01:29.661Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 13 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T17:01:30.280Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The controller currently accepts this command between 17 and 25 °C: not sent. [2026-11-14T17:01:32.035Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 23.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T17:01:32.132Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The controller currently accepts this command between 17 and 25 °C: not sent. [2026-11-14T17:01:32.855Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 22.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T17:01:32.953Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T17:01:33.069Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 23.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T17:01:33.174Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T17:01:34.215Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 23.5 [2026-11-14T17:01:34.620Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 23.5 waiting: another command to BSB-LAN is running, sent after it [202[6-11-14T17:01:37.234Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 22.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T17:01:37.234Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T17:01:37.922Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 22 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T17:01:38.449Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T17:01:38.579Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 21.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T17:01:39.421Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 21 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T17:01:39.422Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T17:01:39.500Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T17:01:41.343Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 21 [2026-11-14T17:01:43.394Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 19.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T17:01:47.159Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 19.5 [2026-11-14T17:01:47.201Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 17.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T17:01:47.614Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 19.5 (queued): done [2026-11-14T17:01:49.926Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 18 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T17:01:49.927Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T17:01:50.306Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 17.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T17:01:50.306Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T17:01:51.395Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 17.5 [2026-11-14T17:01:55.881Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 16 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T17:01:57.766Z] [INFO] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint not sent: replaced by a newer value of the same setting [2026-11-14T17:01:59.594Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The regulator currently accepts this setting between 17 and 25 °C: not sent. [2026-11-14T17:02:03.097Z] [INFO] [bsblan] BSB-LAN hc2-setpoint: 17 [2026-11-14T17:02:05.363Z] [INFO] [bsblan] BSB-LAN hc2-setpoint 16.5 waiting: another command to BSB-LAN is running, sent after it [2026-11-14T17:02:07.819Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The regulator currently accepts this setting between 17 and 25 °C: not sent. [2026-11-14T17:02:10.514Z] [WARN] Command ext:ext-lm1lc3n7-gladys-bsblan:bsblan:14335c0afa90:hc2-setpoint refused: The regulator currently accepts this setting between 17 and 25 °C: not sent. ```

Written with the help of Claude (Anthropic’s AI); the logs and screenshot come from my installation.

No problem to do tests, I told you last month I have an installation that allows to validate the integration :slightly_smiling_face:

I will put the BSB LAN integration into service on another installation with a heat pump and hot water production, I will give you feedback, especially to validate the hot water production that I don’t have on my installation.

Next Step: have you considered proposing a widget?
Like the one proposed by @Will_71 with his integration, I will put it into service on a Vaillant boiler Intégration domotique ebusd, gratuite et open source | Gladys Assistant

Thanks for your work!

Thanks @XDECO for these « brute » tests and the full log, it helped a lot! It’s in the v0.4.0 : Release v0.4.0 · LM1LC3N7/gladys-bsblan · GitHub (it will arrive in the store at the next indexer update).

1. Rejections state where the limits come from. Each rejection gives the requested value and the parameter that sets each limit, for example: « 28.5 °C setpoint rejected: the regulator accepts it between 17 °C (reduced setpoint, 1012) and 25 °C (maximum comfort, 1016); not sent. » It’s the same for circuit 1 (710 to 716), hot water, and the integration ceilings. The requested value is also in the WARN line of the log.

2. Rejections « between 5 and 35 °C ». They came from the integration’s own limit: a value outside of 5-35 had indeed arrived. The most likely explanation: when you type a setpoint on the keyboard in the card, Gladys also sends the intermediate values (« 2 » before « 22.5 »). This is not a defect of the integration, but the message now displays the received value, making it visible.

3. The 3 minutes of rejection after your modification of 1016. The integration does not cache any limit: each command reads 1010 to 1016. During these 3 minutes, the reduced setpoint (1012) was above the maximum comfort (1016), and the comfort setpoint range was therefore empty. The rejection now names the two conflicting parameters, and the next command passes as soon as the setting is corrected.

4. Writing the closest limit. I preferred not to do this: the integration never writes any value other than the one requested. It rejects with a clear message, so that a scene does not silently set a different setpoint than the one intended.

5. The slider bounded by BSB-LAN limits. This is not possible for now: changing the min/max of a device after its creation requires going through Discovery again. It’s noted in the documentation.

6. The widget. There is now a « BSB-LAN » widget for the dashboard, read-only. It displays the temperatures (circuit ambient, outdoor, hot water), then for each circuit the mode, the comfort and reduced setpoints and the state, and the hot water. A change is visible in about ten seconds. If BSB-LAN no longer responds, it says so instead of displaying old values.

As before, everything was tested on a fake BSB-LAN built from your logs, not on a real one. Your feedback on the installation with PAC and hot water will be precious, especially for the hot water.

Hello, @lmilcent

Thank you for the new version of the integration, it’s much better!

What works well

  • The setpoint changes are correctly passed to both circuits.
  • The test for writing a value out of bounds works: the command is refused and the log gives a clear message, with the requested value and the BSB-LAN parameters that set the limits:
[2026-11-15T19:09:46.838Z] [WARN] ... hc2-reduced-target 2 refused: Setpoint of 2 °C refused: the controller accepts it between 8 °C (frost protection setpoint, 1014) and 21 °C (comfort setpoint, 1010) according to the last reading; not sent.
  • After a voluntary BSB-LAN outage, commands are refused with an explicit message (parameters 710 to 716 not read), and the integration retries after 30 seconds instead of waiting the full interval.

Two issues after a complete reconfiguration
I deleted and reconfigured the integration from scratch, checking all the fields.

  1. Parameter 1042 no longer appears.
    I can no longer find it in the options or in the devices, although it was there before. On BSB-LAN, the page for circuit 2 displays « 1042 Heating circuit 2

  2. An additional parameter added does not appear.
    I added parameter 1020 (heating curve for circuit 2) in the additional parameters. It is accepted, but no device or function appears in the list of Gladys devices. For comparison, when I add a parameter already managed by the integration, the message indicates that it is already present.
    BSB-LAN reads this parameter correctly: « 1020 Heating circuit 2 - Heating curve: 1.46 ».

I can provide the full log of the reconfiguration if needed.

(Written with the help of Claude, the AI from Anthropic; the tests and logs come from my installation.)

Thanks!

Thanks @XDECO for your feedback, glad the messages are clearer!

For your two points:

1020 doesn’t appear. The integration reads it well (1.46) and suggests it in Discovery. But Gladys only adds a new value to an already created device if you click on “Update” on that device, in the Discovery tab of the integration. The integration didn’t mention this, it’s now fixed.

1042 has disappeared. The integration doesn’t read 1042 on its own. It was very likely in your old additional settings, and it was removed with the old configuration when you deleted the integration.

To find them again:

  1. Put 1042 (and 1020 if it’s not there anymore) back in Additional Settings, then save.
  2. Go to the Discovery tab of the integration and click on “Update” on your BSB-LAN device.

In v0.4.1 (Release v0.4.1 · LM1LC3N7/gladys-bsblan · GitHub, at the next indexer run), the integration state tells you this on its own. It lists the additional settings read but not yet in the device, with the instruction “Update”. It also lists those for which BSB-LAN provides nothing usable, with the reason: unknown regulator parameter, “—”, unreadable value…

Let me know if 1042 and 1020 come back after that!

Hello @lmilcent,

You’re right, I got the wrong parameter, sorry. The one that no longer appeared after reconfiguration is not 1042 but the 8774 « Resulting Departure Temperature Setpoint CC2 ».

In the device list, I had « Departure Setpoint » (circuit 1, 8744) and « Departure Temperature (circuit 2) », but not « Departure Setpoint (circuit 2) ».

Cause found
At the time of configuration, circuit 2 was in protection mode (1000 = 0). The boiler then does not calculate a departure setpoint, and BSB-LAN returned for this parameter:

"8774": { "name": "Resulting Departure Temperature Setpoint CC2", "error": 0, "value": "---", "payload": "010000", ... }

I checked: when I put circuit 2 into service (Reduced mode), 8774 took a value (47.8 °C), and the « Update » button appeared in Gladys to add parameter 8774 to the device.

BSB-LAN response (/JQ=1000,8774,8773) after switching to Reduced mode
{
  "1000": {
    "name": "Operating mode",
    "dataType_name": "ENUM",
    "dataType_family": "ENUM",
    "destination": 0,
    "error": 0,
    "value": "2",
    "desc": "Reduced",
    "payload": "0002",
    "dataType": 1,
    "readwrite": 0,
    "unit": ""
  },
  "8774": {
    "name": "Resulting Departure Temperature Setpoint CC2",
    "dataType_name": "TEMP",
    "dataType_family": "VALS",
    "destination": 0,
    "error": 0,
    "value": "47.8",
    "desc": "",
    "payload": "000BF2",
    "precision": 0.1,
    "dataType": 0,
    "readwrite": 1,
    "unit": "°C"
  },
  "8773": {
    "name": "Heating circuit 2 departure temperature",
    "dataType_name": "TEMP",
    "dataType_family": "VALS",
    "destination": 0,
    "error": 0,
    "value": "34.5",
    "desc": "",
    "payload": "0008A1",
    "precision": 0.1,
    "dataType": 0,
    "readwrite": 1,
    "unit": "°C"
  }
}

The feature is therefore not created as long as the parameter is « — », and it is offered via the update button as soon as it has a value.

Suggestion
Would it be possible to create the feature during configuration, with an empty state until there is a value? Otherwise, if you configure the integration while a circuit is in protection (for example in summer, or for an unoccupied holiday home like mine), the departure setpoint only appears once the circuit is put back into heating, and you have to remember to click on « Update ».

Additional parameter: OK
Adding an additional parameter now works. Test carried out with the heating curve of circuit 2 (1020, value 1.46): it is well created and comes back in Gladys.

Thanks again for your responsiveness!

(Written with the help of Claude, the AI of Anthropic; the tests come from my installation.)

Thanks for this very precise analysis, you found the cause. Version 0.4.2 of the BSB-LAN integration is published (in the store at the next indexer pass, or update from GitHub) and takes your suggestion into account.

  • A command that BSB-LAN gives to « — » (protected circuit, for example your 8774) now has its functionality as soon as it is configured, empty until the first value. Nothing is published as long as there is no value, never 0.
  • The same applies to an additional parameter set to « — », if BSB-LAN provides its type.
  • Gladys does not know how to clear a value: if a command goes back to « — » (circuit back in protection), Gladys keeps the last value received. The status indicates this, parameter by parameter.
  • No command is sent to a command without a re-read value. Going into protection and cutting off hot water remain possible.

For an already created device, click once on « Update » in the Discovery tab: the status reminds you if a command is missing.

A request to check a point I couldn’t see: when circuit 2 is in protection, can you send me the complete response of /JQ=8774 (with all its fields)? Your message showed the value « — », but not whether BSB-LAN also provides the type and unit in this case.