Using Acetec_EvoControl.json template compared to ordinary Modbus template

[bjorn444]

Hi,

I just tried using Protocol Wizard v0.7.0 but reverted back to using modbus. I'm trying to to use the Acetec_EvoControl.json template for the FTX (Heat recovery ventilation (HRV) compared to my Modbus template, see below.

General problems:

• I would want to edit the template using the text editor, but I cannot seems to find the exported template to the local files. I think that's me not knowing really where to look using the Studio Code Server integration, could someone please help?
• Cannot seem to find the UI Card for adding to the UI as described in the documentation, is that also your experience? I'd like to read the efficiency of the rotor on address 1142 but for some reason I cannot, neither using the protocol wizard or modbus.

Problems using Acetec_EvoControl.json template:

• Cannot set the entities to "Climate" to entities/units, which I'd like to do. Would that be possible to adjust? I'd for instance like to use the fan mode to set the ventilation speed, primarily using the "Comfort" and "Forced" ventilation. I succeeded setting the modes using the Value mapping (got errors) setting it up, that the "Device Class" and "State class" were undefined (if memory serves), but those were not changed during the setting of the Value mapping. In any case, when displaying the "Mode Set" entity, I could not display the value, but I got a drop down meny for choosing between the items in the JSON definition.

Problems using own modbus template:

• Since I can only set one address for the temp setting, I cannot change temperatures for the different fan modes, which have different addresses (211 for "Comfort" and 212 for "Forced"), in addition to that, the scaling cannot be changed between the set temperature of address 211, which is to be read as an integer while the address 1110 has to be scaled.

Modbus template:

modbus:

• name: ftx_system
  type: tcp
  host: 192.168.1.34
  port: 502
  climates:
  • name: Acetec FTX
    address: 1110
    precision: 1
    fan_mode_register:
    address: 1010
    values:
    state_fan_off: 1
    state_fan_on: 0
    state_fan_medium: 3
    state_fan_high: 4
    input_type: holding
    max_temp: 40
    min_temp: 10
    target_temp_register: 211
    temp_step: 1
    temperature_unit: C
    unique_id: 59dd4936-cb63-4443-9c33-04f9d768045b
    sensors:
  • name: Fraanluftstemperatur_ftx
    unique_id: 5ed42446-0ce6-46d0-8216-8f38e92577d0
    unit_of_measurement: °C
    address: 1111
    scale: 0.1
    precision: 1
    state_class: measurement
    device_class: temperature
  • name: Uteluftstemperatur_ftx
    unique_id: 0db0007d-4ac1-47ec-b607-6ef73b543afb
    unit_of_measurement: °C
    address: 1112
    scale: 0.1
    precision: 1
    state_class: measurement
    device_class: temperature
  • name: Days to service_ftx
    address: 1124
    state_class: measurement
    unique_id: fe8c1954-ae6a-46cc-b860-b86f52a96093
  • name: rotor_RPM_ftx
    unique_id: aaff4525-ccfc-423a-b6a4-b8735617d25c
    unit_of_measurement: rpm
    address: 1140
    scale: 0.1
    precision: 1
    state_class: measurement
  • name: rotor_efficiency_ftx
    unique_id: f104f862-0963-4844-908d-e2e62987f2ae
    unit_of_measurement: "%"
    address: 1142
    input_type: input
    state_class: measurement
  • name: till_luft_fan_percentage_ftx
    unique_id: 4d93396a-2de9-4031-9bd2-7ba58c2021b2
    unit_of_measurement: "%"
    address: 1150
    state_class: measurement
  • name: till_luft_fan_rpm_ftx
    unique_id: e6fd8b14-c1d2-476e-8f9e-96ae93814212
    unit_of_measurement: rpm
    address: 1151
    state_class: measurement
  • name: fraan_luft_fan_percentage_ftx
    unique_id: 6149cbff-b73f-40f0-becb-57cb2e62bc7e
    unit_of_measurement: "%"
    address: 1160
    state_class: measurement
  • name: fraan_luft_fan_rpm_ftx
    unique_id: 2e442740-4ef9-42ac-a3d9-e52b1d18320d
    unit_of_measurement: rpm
    address: 1161
    state_class: measurement
  • name: summa_effektuttag_percentage_ftx
    unique_id: a982d2a3-c2e4-4e3f-8fc5-933f3aba9b83
    unit_of_measurement: "%"
    address: 1202
    state_class: measurement
  • name: summa_effektuttag_eftervärme_percentage_ftx
    unique_id: de655fc1-252d-4b81-89cd-12d7dcac7564
    unit_of_measurement: "%"
    address: 1204
    state_class: measurement
  • name: driftTidAggregat_ftx
    unique_id: 93479a33-8765-4f29-a9e1-6a6ec7c01fcd
    unit_of_measurement: "h"
    address: 1200
    state_class: measurement
    switches:
  • name: eftervärme_el_ftx
    unique_id: e4db20d1-7931-44c5-8f01-46a55910060f
    address: 240
    command_off: 0
    command_on: 2

[partach]

Not sure if this would classify as an issue regarding the software. Did you consult the readme / wiki here on github?

How do you normally edit for example configuration.yaml? you can install HA add-on / App visual code studio for example or another text editor via addons (now named Apps in newer versions i think). You can use SSH to log into HA target and use nano (linux cmd line editor). Or use Winscp.. (if you are a Windows fan this is maybe a good option for you? Many options :)

[bjorn444]

Hi

No, maybe not an issue with the software, maybe not. Except it seems not possible to create the card in Lovelace.

Yes, I did consult the wiki. Maybe the question is a bit incoherent and has many roots, my ignorance is certainly one of them. I guess what I’m asking is:

• would it be possible to use climate as a type of entity/unit? To me, for my usage, that seems like the best type for this type of equipment.
  • Would that be doable in editing the template file installed, though I haven’t been able to locate it?
  • if not possible to define a climate entity within Protocol Wizard, would a solution perhaps be to use the returned entities and use a template outside of Protocol Wizard?