Welcome Asgard users!

[gekkekoe]

The first batch has been shipped and I would like to thank and welcome the new users. Please post your questions and remarks in this section.

Quick Links:

• Install dashboard
• Install other firmware. Download asgard*-ota.bin variant and go to http://esp_ip, upload the asgard*-ota.bin at the bottom of the page

Please consult the manual and if something is not clear, please ask here.

[nicodenekamp]

At the moment I’m using the M5Stack Atom Lite S3 for the esphome-ecodan-hp application. I’m using the source code and compile / upload from a Raspberry Pi4. Monitoring and control is done using Home Assistant running on another Raspberry Pi5.

Now I ordered the Asgard Hardware and I want to remain compiling / upload from my Raspberry Pi4.

I want to use the Asgard Hardware because I want to switch to the Virtual Thermostat (0.1 oC), being more accurate than the wireless Mitsubishi PAR-WT60R-E thermostat (0.5 oC).

I think this is possible by means of the following modification in ecodan-esphome.yaml:

#esp32: !include confs/esp32s3.yaml # confs/esp32.yaml, for regular board
esp32: !include confs/asgard.yaml # confs/asgard.yaml, for asgard board

Already performed “esphome config ecodan-esphome.yaml” and “esphome compile ecodan-esphome.yaml” with the modified ecodan-esphome.yaml and both commands succeeded without warnings / errors.

So now I could connect the Asgard to my Rapsberry Pi4 with an USB cable and upload the compiled esphome-ecodan-hp application.

Is this so correct or am I missing something?

As a first step I want to replace the M5Stack Atom Lite S3 by the Asgard without using the Virtual Thermostat and when that conversion is performed correctly than remover the PAR-WT60R-E thermostat and use the Virtual Thermostat over IN1.

[gekkekoe]

You have a couple of options. If you already have configured an ip for asgard, then its not needed to flash over usb. Only initial flash, but since I already pre-flashed the firmware this is not needed anymore once you have configured wifi.

You can just flash over network:

esphome upload --device ip_address ecodan-esphome.yaml

Please monitor the main yaml for changes and some ordering is important too. For example

packages:
  remote_package:
    url: https://github.com/gekkekoe/esphome-ecodan-hp/
    ref: main
    refresh: always
    files: [ 
            confs/base.yaml,            # required
            confs/energy.yaml,            # required
            confs/cpu-monitoring.yaml,    # recommended
            confs/request-codes.yaml,   # disable if your unit does not support request codes (service menu)
            confs/auto-adaptive.yaml,    # recommended, define before board def
            confs/asgard.yaml,

Please note that the auto-adaptive needs to be include before the board definition (asgard.yaml)

You can also use the binaries and use esphome to do the logging. Or the newly created html tool to record logging: https://github.com/gekkekoe/esphome-ecodan-hp/blob/main/docs/faq.md#5-how-can-i-monitor-logs

[schumch]

I there a process to add the asgard in HA with the same name like the old esp? To avoid loss of data in HA from the old esp?
Give Asgard the same name and ip?

[schumch]

Yes, in1 and in6 is wirred.

In HA there is no option for zone 2:

[gekkekoe]

It's a global setting, the z2 controls should not be there in the html, ignore it for now. It works right AA ?

[gekkekoe]

@schumch It makes more sense to allow it per zone, so I enabled it in the back-end for z1/z2.
You can try manual pre-release: https://github.com/gekkekoe/esphome-ecodan-hp/releases/tag/2025-02-17.03
Please test if it works properly (I don't have 2 zone, so its a bit hard to test). At the bottom of the stand alone mode, there's a Manual upload button for manual firmware upgrades

[schumch]

Ok. Thanks. Will try later.
Yes, I think everything works fine at the moment. Just a bit confused

[schumch]

Hi, short feedback: Everthing looks fine with the firmware 17.03 for my zone 2 setup.

[sinisa200]

I installed it and it works well for now. I also connected the virtual thermostat, but I had to set switch SW2/1 to ON on the control board.

[gekkekoe]

Yes, this is correct, I did document it ;-)

It took a while, but you finally got it!

[jamessimpson007]

Hi, thanks very much, I've just received mine and so far so good!

Quick query please. I've followed the above instructions and have got it working in HA, but I can't figure out how to get it into the ESPHome Builder addon. Does this matter? I had a few other manually configured bits and pieces here in the main YAML file and was expecting to do the same for this device, is this possible / necessary? If I hook it up via USB C and set it up as a new device will it just wipe it?

Thanks

[gekkekoe]

No ESPHome builder is not needed. You will get OTA pushed by me, so no more self compile. You can of course compile yourself, but that's only needed if you are using a non standard configuration.

The devices comes pre-flashed with a firmware, just configure it and its good to go

I did just update the documentation secion

[jamessimpson007]

Ah okay thanks. I had been editing the YAML to add in some extra sensors with WiFi info etc but I could live without those.

However I was using a local version of zone1.yaml to enable me to get rid of the cooling functions from the operating mode drop down menu, as my system doesn't have them. Is there an easier way to do this? Or if not how would I go about manually compiling it please? Thanks for your help.

[gekkekoe]

Ah, then you need to compile from source. See manual https://github.com/gekkekoe/esphome-ecodan-hp/blob/main/docs/build-from-source.md

Via the new stand alone mode, I do dynamically enable/disable zone 2. I guess I could add filtering based on heating/cooling capabilities there as well (In HA we cannot dynamically adjust stuff runtime). But you probably want more logging and then HA is the way to go.

Or use the default and make a dashboard without the cooling sensors...

[jamessimpson007]

Great, thanks again

[jamessimpson007]

Sorry, another query. I'm unable to get heating to commence, I get an error on the FTC6:

Code: J0
Unit FTC Address:0

Fault code "JO 403" as reported by Asgard

I've tried resetting it and rebooting the whole system from a full power down. Any suggestions please??

[schumch]

I think your Dip switches are set to remote thermostat. Dip 2.1.

I think I had have the same issue. But can't remember at full.
My issue was that a had use a cnrf thermostat (with the other esp project) and swapped to asgard with virtual thermostat. And dissemble all of that cnrf stuff. But I forgot to change dip 2.1 to off

[jamessimpson007]

Ah ha. Thanks. I forgot to switch SW1-8 to off!

[schumch]

Good! Sorry, SW1-8 not 2-1

[gekkekoe]

Thank you @schumch for helping out!
I will add a note for users migrating from CNRF. You basically need to do the reverse of https://github.com/gekkekoe/esphome-ecodan-remote-thermostat?tab=readme-ov-file#installation but I have updated the documentation

[skl1961]

Hi, I have just received the Asgard print, and I am going to replace my Atom S3 soon. I would like to hear what others use as "virtual thermostat" ? And could I have like 3 virtual thermostats to control zone 1 on my heatpump ? I am going to get rid of my wireless Mitsubishi thermostat but would like more than one thermostat. Thx.

[gekkekoe]

Eventually only one signal can be sent to the heatpump. Normally if you would like to use more temp sensors is to aggregate them (for example use an average)

There can only be one master per zone, I think the mitsubishi wireless works like this as well.

[nicodenekamp]

I'm using the Asgard with Virtual Thermostat and removed the Mitsubishi wireless thermostat.
As input for the Virtual Thermostat I use a Sonoff SNZB-02D, it works with an hysteresis of 0.2C but in combination with an defined hysteresis of 0.1C for the Vitual Thermostat it works for me fine.