Add Proxon Heating System to HA via Modbus

I just uploaded the “Proxon” part of the dashboard to Github. (Dashboard_new.yaml)
Some automations are no more necessary.
and you need the integrations

  • bubble card
  • vertical stack-in card
  • button-card
  • card-mod
  • Theme bubble (not mandatory)

The topic about “Modbus schreiben”: I didn’t ask the support if there is a way to do that by myself. I was writing a message via the contact form and they called me back next morning and told me, that they have changed it remotely to “2”. So just give it a try.

1 Like

just checked your repo, but found only the old dashboard :confused:

Hmmmm… don’t know what went wrong again.
now it should be available

now its there. thx so much!

no problem. just ask in case of questions.
I tried to have the information as compact as possible, since I wanted to use the same stack on my “home-page” as bubble-popup.
e.g. the temperatures. When I touch the temperature button, the temperature popup appears.

home-page


temperature popup

on the mobile phone it looks even better.
BR
Steffen

ne update available on GitHub (GitHub - Stroett/HA_config_Proxon)
…for those who are interested in…

2 Likes

You see this is what I asked some months ago. For me it is also read only but I don’t really bother right now. I just switch the PTCs individually.

@Stroett - Hi, would you have any idea why my modbus connection using Waveshare Industrial USB to RS485 Converter is not working? I tried so many things I found but none are working.

Hi Rick,
sorry, I am also not the expert. I just used the parameter which was posted in this thread and it was working from the beginning.

1 Like

Hey Rick99,
sorry for late response.
I just used the USB Adapter for troubleshooting purpose (in general Im using the Ethernet version).
So far I remembered only connecting the wires to these 3 pins, was fine.
Than it worked for me in the modus testing tool as also direct in home assistant.

1 Like

Hello,

In your Github Project i think you missed your Binary Sensors for all Rooms:

binary_sensor.proxon_heizelement_status_*

if i dont set this via template or in one of the automations the Dashboard crash, i ficed this for my rooms with this.

- platform: template
  sensors:
    proxon_heizelement_status_wohnzimmer:
      friendly_name: "Proxon Heizelement Status Wohnzimmer"
      value_template: "{{ is_state('switch.proxon_heizelement_wohnzimmer', 'on') }}"
    proxon_heizelement_status_vanessa:
      friendly_name: "Proxon Heizelement Status Vanessa"
      value_template: "{{ is_state('switch.proxon_heizelement_vanessa', 'on') }}"
    proxon_heizelement_status_jan:
      friendly_name: "Proxon Heizelement Status Jan"
      value_template: "{{ is_state('switch.proxon_heizelement_jan', 'on') }}"
    proxon_heizelement_status_emma:
      friendly_name: "Proxon Heizelement Status Emma"
      value_template: "{{ is_state('switch.proxon_heizelement_emma', 'on') }}"
    proxon_heizelement_status_leoni:
      friendly_name: "Proxon Heizelement Status Leoni"
      value_template: "{{ is_state('switch.proxon_heizelement_leoni', 'on') }}"
    proxon_heizelement_status_flur:
      friendly_name: "Proxon Heizelement Status Flur"
      value_template: "{{ is_state('switch.proxon_heizelement_flur', 'on') }}"
    proxon_heizelement_status_schlafzimmer:
      friendly_name: "Proxon Heizelement Status Schlafzimmer"
      value_template: "{{ is_state('switch.proxon_heizelement_schlafzimmer', 'on') }}"

best regards Jan

Hi Jan,
you are right. Missed that in the configuration.yaml.
Should be now added on GitHub.

But you are not completely right. :wink:
The status is not, if the heating is allowed to turn on, but if its currently heating. That’s why the following templates should be correct.

- binary_sensor:
    - name: Proxon Heizelement Status Wohnzimmer
      state: "{% if states('sensor.proxon_heizelement_status') | int | bitwise_and(1) %}on{% else %}off{% endif %}"
      unique_id: proxon_heizelement_status_Wohnzimmer

    - name: Proxon Heizelement Status Flur
      state: "{% if states('sensor.proxon_heizelement_status') | int | bitwise_and(2) %}on{% else %}off{% endif %}"
      unique_id: proxon_heizelement_status_Flur

    - name: Proxon Heizelement Status Buero
      state: "{% if states('sensor.proxon_heizelement_status') | int | bitwise_and(4) %}on{% else %}off{% endif %}"
      unique_id: proxon_heizelement_status_Buero

    - name: Proxon Heizelement Status Schlafzimmer
      state: "{% if states('sensor.proxon_heizelement_status') | int | bitwise_and(8) %}on{% else %}off{% endif %}"
      unique_id: proxon_heizelement_status_Schlafzimmer

    - name: Proxon Heizelement Status Eline
      state: "{% if states('sensor.proxon_heizelement_status') | int | bitwise_and(16) %}on{% else %}off{% endif %}"
      unique_id: proxon_heizelement_status_Eline

    - name: Proxon Heizelement Status Lean
      state: "{% if states('sensor.proxon_heizelement_status') | int | bitwise_and(32) %}on{% else %}off{% endif %}"
      unique_id: proxon_heizelement_status_Lean
      
    - name: Proxon Heizelement Status Hobbyraum
      state: "{% if states('sensor.proxon_heizelement_status') | int | bitwise_and(64) %}on{% else %}off{% endif %}"
      unique_id: proxon_heizelement_status_hobbyraum

for that you need in addition the following sensor via modes

#PTC's
    - name: "Proxon Heizelement Status"
      unique_id: proxon_heizelement_status
      address: 574
      scan_interval: 15
      data_type: int16
      input_type: input
      slave: 41

For questions, just ask
BR
Steffen

Hi and thanks for sharing,
the address 574 is in my Case (Proxon FWT from Year 2021) 4x0574 Freitag #2 Zeit Minuten An ZL069:Zeitprogramm Luftmenge, so its part of the time-program…

Can you share some more informaition about the modbus address? Is it this one? Heizmodul 1 Relaistest T12:Test Binär “Bit9:R10
Bit8:R9
Bit7:R8
Bit6:R7
Bit5:R6
Bit4:R5
Bit3:R4
Bit2:R3
Bit1:R2
Bit0:R1”

Thanks alot

Hi there,

great job all of you did here to connect the FWT to HomeAssistant. After reading very much, I thoght I give it a try. I have a FWT 2-R which seems not to be connected to the T300.

And I have another board on top of the unit:

X6 is already occupied by two cables (shouldn’t that be three?). X7 is free (but only has 2 pins).

Can I connect my waveshare-adapter also to X6?
Is the USB of any use?

I also sent an inquiry to Zimmermann, I keep you updated.

Best regards,
Heiko

1 Like

I also have this:

Perhaps the 2nd Bus?

Hallo @PeterSehrLustig,
hallo @Stroett,

indeed I was wondering about this as well. For me it’s not clear, how to differentiate about the different tabs in the Excel-Sheet.
On Tab “Holding Register” there is at the address 4x0574 the value of “Freitag #2 …:” (like Peter said). But on the tab “Input Register” there is at the address 3x0574 the value of “Heizmodul 1 Relais Status”.

(at least I have no idea what’s the difference between these two excel tabs - sorry).

Has anyone a hint? Thanks in advance.

Best regards, Charly

Hallo all,

I have an additional question regarding the switch proxon_heizelemente_global. What does this switch do? Does this switch activate all heating elements?
Nothing happens in the Proxon-App :man_shrugging:
Or do I have the problem with R/W (modbus write modus)?
Thanks in advance.

Best regards, Charly

Hi Charly,

this switch allows the heating elements to heat or not, depending on their own status.
Means … if the switch “proxon_heizelemente_global” is off, no all heating elements are off.
If the global switch is on, the elements are on or off depending to their own status.
Does it help?

and about the other question:
as I mentioned in the response message to Peter…
These are different register types. It’s explained on Wiki. I am also no expert in modbus

Oh … I am sorry. I totally missed your response
It is this one
image
Relais status

AHHHH now after reading the message from charty …
He is right. Yup were looking in the wrong register. You hav to differentiate between holding and input register.
Don’t ask about more details :slight_smile: But this is also important the the config file. There you tell the input type … see below