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

HYSTERESE_WW not working correctly? #143

Closed
zimbo86 opened this issue Mar 5, 2025 · 6 comments
Closed

HYSTERESE_WW not working correctly? #143

zimbo86 opened this issue Mar 5, 2025 · 6 comments

Comments

@zimbo86
Copy link

zimbo86 commented Mar 5, 2025

Can you pleas check parameter HYSTERESE_WW
In my case this does not work properly.
Also when I change the value on the WP itself it does not update the sensor value.

more infos:
On a reboot of ESP the correct value is shown.
When I update it externally the value is not updated.
When I update via ESP sensor the write action seems not to work. there is a sensor update scheduled 10s after the write action, in this case the correct value is shown, also if previously changed externally.

So two things:

  1. The write action does not work
  2. The value does not refresh periodically
@kr0ner
Copy link
Owner

kr0ner commented Mar 6, 2025

Image

Works for me 🤷

Edit: not enough coffee it seems ...

@kr0ner
Copy link
Owner

kr0ner commented Mar 6, 2025

So there is no special setting for HYSTERESE_WW ... it uses wp_number template, which means all numbers should be broken in a similar way.

@kr0ner
Copy link
Owner

kr0ner commented Mar 6, 2025

Also we are subscribed for updates:

  on_boot:
    priority: -100
    then:
      - lambda: |-
          CallbackHandler::instance().addCallbacks({std::make_pair(Kessel,Property::k${property}),
                                                    std::make_pair(Manager,Property::k${property})},[](const SimpleVariant& value){
              id(${property}).publish_state(value);
          });
          queueRequest(${target}, Property::k${property});

@kr0ner
Copy link
Owner

kr0ner commented Mar 6, 2025

I did not try setting the value on the display of the headpump yet.
Are you on latest master?

@zimbo86
Copy link
Author

zimbo86 commented Mar 6, 2025

thanks for testing.
I pulled the latest wp_number.yaml - no difference.
Just wanted to check if its a general bug.

in my case i changed the name to dhw_hysterese. It is 3.0 atm.

[07:40:21][D][number:054]: 'dhw_hysterese' - Setting number value
[07:40:21][D][number:113]:   **New number value: 3.100000**
[07:40:21][I][Number:024]: Setting new value 3.100000 for dhw_hysterese
[07:40:21][D][canbus:035]: send standard id=0x6a2 rtr=FALSE size=7
[07:40:21][I][QUEUE:115]: Scheduling request for data from Kessel for dhw_hysterese in 10 seconds
[07:40:21][D][number:012]: 'dhw_hysterese': Sending state 3.100000
[07:40:26][D][esp32.preferences:114]: Saving 1 preferences to flash...
[07:40:26][D][esp32.preferences:143]: Saving 1 preferences to flash: 1 cached, 0 written, 0 failed
[07:40:31][I][Communication:157]: Message received: Read/Write ID 0xd2 0x22(0x6a2) for property dhw_hysterese (0x0140) with raw value: **30**
[07:40:31][D][number:012]: 'dhw_hysterese': Sending state 3.000000



and youre right, it happens to all numbers.

@zimbo86
Copy link
Author

zimbo86 commented Mar 6, 2025

ok, got it. at least the cause.
All wp_numbers going to "Kessel" (and therefore target is not specified) wont work.
Appending target:"Kessel" makes the sensor working again.

dhw_hysterese: !include { file: wp_number.yaml, vars: { property: "dhw_hysterese" , min: "2.0", max: "10.0", step: "0.1", unit: "K", icon: "mdi:plus-minus-variant", target: "Kessel"}}

Maybe because I modified wp_number.yaml a bit and added icon, unit and mode:

defaults:
  target: "Kessel"
  step: "1"
  min: "0"
  max: "100"
  unit: ""
  icon: "mdi:valve"
  mode: "box"

number:
  - platform: template
    name: ${property}
    id: ${property}
    unit_of_measurement: ${unit}
    mode: ${mode}
    icon: ${icon}

But I dont see the cause why it should stopping ${target} to work.
However thats not an issue for your project ;)

@zimbo86 zimbo86 closed this as completed Mar 6, 2025
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