Improvemt: Add power off/on possibility for the heatpump(bosch compress 3800i ew) about ems-esp32

[MichaelDvP]

I think using bool as on/off is better, but with we have only 1=on/0=off, so we have to find a name that makes clear the option on/true/1 shuts the heatpump down. What about shutdown as name?

[MichaelDvP]

Yes it is, i've found the typo in the shutdown registering. Will push a new build.

[mattfro]

Much better, thanks @MichaelDvP :)
Shutdown also works, on= shuts down the pump and off= turns it on. :)

[mattfro]

Shutdown is fine.
Not possible to invert bool, I mean like have a tag in ems-esp that you want to invert it? Maybe only for one situation it's too much work. Of course I can always do that in hass... so for me it's not a big deal.

[proddy]

@MichaelDvP we could ENUM as a new type, with a list of options, in this case it would be '1, 0'

[MichaelDvP]

Not possible to invert bool,

Sure, we can add a new type BOOL_INV, but is it worth for a single entity?

we could ENUM as a new type

Yes, this should work, but still a bit confusing when using enum as number option, then it's the only entity with on=0.
Also i think power_onoff is not a good name, it's not switching the power, it just stops the pump. For modules we have always the enable entity, maybe here we can use disable?
@mattfro What is the Bosch name in manual and UI of the thermostat for this option?

[mattfro]

Not possible to invert bool,

Sure, we can add a new type BOOL_INV, but is it worth for a single entity?

Yeah, that is the question :)

Yes, this should work, but still a bit confusing when using enum as number option, then it's the only entity with on=0. Also i think power_onoff is not a good name, it's not switching the power, it just stops the pump. For modules we have always the enable entity, maybe here we can use disable? @mattfro What is the Bosch name in manual and UI of the thermostat for this option?

Hmm... bosch name in manual, what thermostat option are you thinking about? Not sure If I understand what you mean...
Are you talking what it's called when I turn off the pump?
If that is the case, it's: "Turn off the heatpump" and then when it's turned off, it ask "turn on the heatpump?"

[MichaelDvP]

it's: "Turn off the heatpump" and then when it's turned off, it ask "turn on the heatpump?"

Changing the entity name is not possible for us, this will give a lot of issues with homeassistant. I prefere a bool state with name disable or shutdown, what is your preference or suggestion? Also you can rename the entity later in the customization., but for a bool the state on will be send a one to the bus and stops the heatpump.

[mattfro]

I don't really have any preference as long as I know what it does :) Bool is fine by me also and name shutdown as you mention is fine.

Here is how it looks like, In Swedish, basically: Shut down heatpump

And the next, Turn off(No/Yes), When heatpump is turned off, heatpump and display will turn off. In off state the antifreeze??prevention is going to be off. To reactivate it touch the display.

Something like that :)

So when it's off, similar window will popup and ask if you want to start the heatpump(yes/no)

[mattfro]

So will this be in, in 3.7?
In that case we can close this ticket...
I can see shutdown entity, but it's hidden. I guess it's because it has no value or am I mistaken?

Found when using customize entity

[proddy]

Entities were initially designed in EMS-ESP for both reading and/or writing. Then we introduced commands like 'reset'. In this case the shutdown is a command (there is no value to read).

@MichaelDvP shall we introduce a new type in the WebUI for commands (DeviceValueType::CMD)?

[MichaelDvP]

It is in 3.7dev and telegram 484 is fetched and has other values. It is not a command telegram. The value should show up.

@proddy For DeviceValueType::CMD we need to know the byte length. Custom entities show in dashboard when writeable, also without value to match such a case we need a cmd only.

[proddy]

@mattfro are you still not seeing a value for hpshutdown ?

[mattfro]

@proddy yep...

[proddy]

@MichaelDvP what shall we do here? It looks like shutdown is an entity with no value set, so it can't be invoked.

[MichaelDvP]

We can change the type to DeviceValueType::CMD

[mattfro]

@MichaelDvP I tried your latest build, it just seems to restart all the time. The one you build 10-15 min ago.

[MichaelDvP]

Can not reproduce, downloaded both bin-files (esp32 and esp32S3) from github and flashed them, both working here.
Try power-on-reset. If not successful check with serial terminal the boot messages.

[mattfro]

Did not see anything else the few seconds I have... only something about ipv6.
If I manage to load the official dev.10 it works again. Need to see if I can get serial connection...

it just reboot's without any information.

and not sure, if it matters but I don't have ipv6 in my network.

[mattfro]

Seems to work when it's not connected to the pump...
Did not have a laptop that I could use so I disconnected it and connected it to a stationary pc.
�[0m�[0;92m�[1mems-esp�[0m:$ ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0xc (RTC_SW_CPU_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
Saved PC:0x40377b18
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fce3808,len:0x39c
load:0x403c9700,len:0x9bc
load:0x403cc700,len:0x28dc
SHA-256 comparison failed:
Calculated: 9477899d59fa5164e630d8218cb3994031873358e9105b31f53911d2dfd36c72
Expected: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Attempting to boot anyway...
entry 0x403c98c0
E (516) esp_core_dump_flash: No core dump partition found!
E (516) esp_core_dump_flash: No core dump partition found!
┌──────────────────────────────────────────┐
│ �[1mEMS-ESP version 3.7.0-dev.10�[22m │
│ │
│ �[4mhelp�[0m to show available commands │
│ �[4msu�[0m to access admin commands │
│ │
│ �[0;92m�[4mhttps://github.com/emsesp/EMS-ESP32�[0m │
│ │
└──────────────────────────────────────────┘
�[0;92m�[1mems-esp�[0m:$ [ 762][E][Preferences.cpp:42] begin(): nvs_flash_init_partition failed: OTHER
[ 764][E][vfs_api.cpp:105] open(): /littlefs/tmp_upload does not exist, no permits for creation
�[0G�[K000+00:00:00.000 I 0: [shell] �[0;33mUser session opened on console ttyS0
�[0m000+00:00:00.000 I 1: [emsesp] �[0;33mStarting EMS-ESP version 3.7.0-dev.10 from partition app1
�[0m000+00:00:00.000 I 2: [emsesp] �[0;33mLast system reset reason Core0: Software reset CPU, Core1: Software reset CPU
�[0m000+00:00:00.000 I 3: [emsesp] �[0;33mLoading board profile S32S3
�[0m000+00:00:00.000 I 4: [emsesp] �[0;33mStarting Scheduler service
�[0m000+00:00:00.000 I 5: [emsesp] �[0;33mStarting Custom Entity service
�[0m000+00:00:00.000 I 6: [temperaturesensor] �[0;33mStarting Temperature Sensor service
�[0m000+00:00:00.000 I 7: [emsesp] �[0;33mLoaded EMS device library (120 records)
�[0m�[0;92m�[1mems-esp�[0m:$ �[0G�[K000+00:00:02.716 I 8: [emsesp] �[0;33mSetting WiFi Tx Power to 11.0 dBm
�[0m�[0;92m�[1mems-esp�[0m:$ �[0G�[K000+00:00:02.734 I 9: [emsesp] �[0;33mWiFi connected (IP=192.168.1.63, hostname=ems-esp, TxPower=11.0 dBm)
�[0m�[0;92m�[1mems-esp�[0m:$ �[0G�[K000+00:00:02.758 I 10: [emsesp] �[0;33mStarting mDNS Responder service
�[0m000+00:00:02.758 I 11: [emsesp] �[0;33mStarting NTP service
�[0m�[0;92m�[1mems-esp�[0m:$ �[0G�[K000+00:00:02.834 I 12: [mqtt] �[0;33mMQTT connected
�[0m�[0;92m�[1mems-esp�[0m:$ �[0G�[K000+00:00:04.571 I 13: [emsesp] �[0;33mLocalIPv6=fe80:0000:0000:0000:eeda:3bff:fe46:9464
�[0m�[0;92m�[1mems-esp�[0m:$ �[0G�[K000+00:00:07.571 I 14: [emsesp] �[0;33mLocalIPv6=fe80:0000:0000:0000:eeda:3bff:fe46:9464

[proddy]

it's either an out of bounds error or out of memory error that is causing the EMS-ESP to crash and restart.

[MichaelDvP]

Looks like normal boot, i can not see a reboot with stack registers.
Does the crash happen after the 7 sec uptime?
Could only be the register of bool CMD shutdown, have to check, my boiler does not have this entity.

[mattfro]

yes it looks exactly like that... it would just be a reboot without any reason. It's no exactly 7 seconds, sometimes a bit longer sometimes shorter. @MichaelDvP could you make a new build without shutdown of the latest? Just to be sure it's not that. Which is a bit strange if it would cause it to reboot.

[mattfro]

So, it's time to close this one also then? ;)

[proddy]

yes!