Supported Eco-Cute ?
Closed this issue · 38 comments
Hello everyone.
Is this integration supported Eco-Cute(electricWaterHeater) ?
I moved to new house 1 month ago and I am using an Eco-Cute first time for me.
My Eco-cute is Mitsubishi SRT-S466A+RMCB-H6SE-T and after connecting to this integration, 17 sensor entities working.
But, there are no sensors for power consumption there and no entities for operation.
I would like to know this is normal behavior or I have failed to connect.
If anyone has ever connected an Eco-Cute, I would appreciate a reply as to how it behaves.
Thank you.
Hi There. The pychonet library doesn't have a module for ElectricWaterHeater. When I get a chance I will create one sometime in the next week. In the meantime can you switch on debugging of the custom component and post the log output here?
Hello !
Thanks for your reply.
This custom component is very useful for me and I appreciate your great work.
I have just enabled debug logging of this custom component.
I am not used to reporting HA debug logs but I will try that this weekend.
Are there any operations that should be performed during logging?
Do I need to extract the logs with a specific word?
I would be very happy if this custom component supported Eco-cute, but prioritise time with your family.
Thanks.
Hello! Just go to Settings -> System -> Logs and copy the text into a text file and attach here.
Hi. I have stared work on this a little bit. I would still like to see your logs, but when you get a chance can you:
-> go to HACS -> Integrations
-> click ECHONETLite platform
-> click the three dots in the top right corner
-> click redownload
-> select 'show beta versions'
-> select 'master' version.
-> Download.
This will give you the latest working version which is running the updated pychonet library with support for your Electric Water Heater.
Let me know what sensors are working for your Eco-Cute, and post me those logs!
Hello!
There doesn't seem to be much information on this integration - is this the right log?
If you need the full log, I can upload it at a later date.
231217log.txt
Thank you for the update.
I will install the beta version now and give you feedback at a later date.
Thanks
I have installed the master version. It is not clear if the items are exactly the same, but 17 sensors are available as before.
Available sensors are as follows
Automatic bath water heating mode setting
Automatic water heating setting
Bath operation status monitor
Bath water temperature setting
Bath water volume setting 3
Daytime reheating permission setting
Hot water supply status
Manual bath hot water addition function setting
Manual slight bath water temperature lowering function setting
Measured amount of water remaining in tank
Measured temperature of water in water heater
Operation status
Tank capacity
Tank operation mode setting
Temperature of supplied water setting
Water heater status
Water heating temperature setting
I will upload the logs after a few days, but is there anything I should do for verify?
Mislabelled. Sorry.
@sympapa Can you try my edge branch? It is not a stable version yet, so please make a full backup before trying it. If everything goes well, the sensor, switch, select, and time input entities will be configured.
For the Number input entity, we need to define a setting in ENL_OP_CODES in const.py, but we haven't configured it yet.
Hello!
Thank you for your comments.
Is your edge branch the same as Version 3.8.0-beta4 or is it different?
I had updated to Version 3.8.0-beta4 before I noticed your comment.
After updating to Version 3.8.0-beta4, four entities have been added.
Two are Number input entities and the other two are selector entities.
One of the selector entities is "tankOperationMode", which can be set to standard/saving/extra.
The other is "automaticWaterHeating", which is "unknown" and does not work.
And "cumulativeElectricEnergy" does not exist yet.
I will restore the full backup once because I have the same problem as #165 after the update, but feel free to request me if there is anything I can verify.
Thanks !
@sympapa The double registration issue has been fixed in 3.8.0-Beta5. Currently edge and beta are the same.
Entities with Unknown data may have valid specifications, but the data may not actually be published.
Power measurement is not yet implemented.
For now, I would like to see what kind of data form your device, so please try the following.
- Enable debug logging on the echonetlite integration page.
- Restart HA.
After about an hour, you can disable debug logging and download the logs. Please attach the log as a file.
@sympapa Support for Electric water heater is almost complete in Version 3.8.0-beta6. However, it has not been tested on an actual device.
Please help us with the operation verification! 🤝
@nao-pon
After my recent comment, I restored the full backup to go back to 3.8.0-beta4 and updated to 3.8.0-beta6 today, but issue #165 occurred.
Five Mitsubishi air conditioners doesn't have that problem, but Sharp air conditioner and Omron solar power conditioner have that problem.
I have created so many sensors from Omron solar entities, that it would take a lot of time to reconfigure them from scratch.
So sorry, I have restored backup again and I have not checked the behaviour related to the Ecocute in 3.8.0-beta6.
Are there any solutions for this issue?
To avoid issue #165, you must update from Version 3.7.9 or earlier to Version 3.8.0-beta5 or later.
However, if you remove the device yourself in the future and reconfigure it, the same problem will occur only once.
If possible, we recommend removing and reconfiguring the device at this stage. Even if you do that, the entity ID will remain the same and the prediction will not affect previous history, automation, etc. Please perform a full backup and then try again.
@nao-pon
Hello !
Thank you for your reply.
Unfortunately, after installing Beta-6, the entity ID has changed as a result of removing and reconfiguring the Omron solar.
My Omron solar power conditioner is "KP-MU1P-SET" and there are two devices on one IP address.
At version 3.8.0-beta4 or earlier they were "Omron_solar_panel_metering" and "Omron_solar_power_generation".(not changed from the default)
But, the result of the reconfiguration on 3.8.0-Beta6 is "KP-MU1P" for both devices.
I decided to manually reconfiguration using a new name the previously created sensors.
Due to the time required for this work, testing of the Ecocute will be carried out at a later date.
Please wait for a while.
The amount of ecocute entities has been reduced from 21 to 20 on 3.8.0-beta6.
The number of numeric input entities has increased from two to three and the 2 selector entities ("tankOperationMode","automaticWaterHeating") has been lost.
Thanks.
@nao-pon
In 3.8.0-beta6, the Omron solar entities seems to has problems that it did not has before.
One example, the unit for "measured_cumulative_amount_of_electric_energy_normal_direction" should be "Wh", but is instead "kWh".
I restored the backup again.
But, I foolishly hadn't thought to test it on the other Raspberry Pi. 😵
I have set up a test environment and will upload the logs in the today.👍
I tested the Ecocute on 3.8.0-beta6.
- The three numeric input entities seems to working fine.
- 2 selector entities ("tankOperationMode","automaticWaterHeating") has been lost.
- "cumulativeElectricEnergy" still does not exist.
Maybe the data for "tankOperationMode" and "automaticWaterHeating" are published.
The selector options for "tankOperationMode" are "standard/saving/extra" and those for "automaticWaterHeating" are "auto/manualHeating/manualNoHeating".
Please find the log in the attachment.
The name of the Eco-Cute is "Mitsubishi Electric GT-WLNA2".
home-assistant_echonetlite_2024-02-11T00-59-58.805Z.log
Thank you😀
@sympapa The definitions of "Expected electric energy at daytime heating shifttime 1" and "Consumption of electric energy per hour 1" were missing, so I added them. Can you try it on my edge version?
Also, there seems to be no problem with Input Select, but what exactly is it? Entities that are not visible may be visible by clearing the browser cache and reloading.
@nao-pon
Hello!
I tried clearing my browser cache, but that didn't improve.
I also searched for the entities "Mitsubishi Electric GT-WLNA2" but still not found that 2 input select entities.
Sensor entities of "tankOperationMode" and "automaticWaterHeating" are exist and working, but the input select entities does not exist.
These are on 3.8.0-beta6.
I will try the Edge version at a later date.
Thank you !
In 3.8.0-beta6, the Omron solar entities seems to has problems that it did not has before.
One example, the unit for "measured_cumulative_amount_of_electric_energy_normal_direction" should be "Wh", but is instead "kWh".
According to the ECHONET Lite specifications, the unit is "kWh". According to your logs for example
- Measured cumulative amount of electric energy (normal direction) 0xc0(192): 2994871
- Measured cumulative amount of electric energy (reverse direction) 0xc1(193): 332202
- Unit for cumulative amounts of electric energy 0xc2(194): 0.001
Therefore, normal direction: 2994871 x 0.001 = 2,994.871 kWh. Is this value (cumulative measurement value) incorrect?
According to the ECHONET Lite specifications, the unit is "kWh". According to your logs for example
OK, I understood that the specification is "kWh".
At that time, the "measured_cumulative_amount_of_electric_energy_normal_direction" was 1000 times higher than before (and the automatically calculated electricity costs were also 1000 times higher), but there is no problem with the current test environment.
Maybe I was wrong 😅
If the same problem occurs, I will create a other "New issue".
Thank you !
I have tried your Edge version.
The results of a test are as follows.
It was not possible to device configure the Eco-Cute with the default settings.
If the "Maximum number of properties for batch requests" is changed to 30, the device configuration was successful.
input number entities (other than "temperature_of_supplied_water_setting") can be input and are successfully reflected to the device.
But, the results of operations from the device side are not reflected in those entities.
"temperature_of_supplied_water_setting", entered value is often not reflected to the device but rarely are.
The results of operations from the device side may or may not be reflected to the entity.
(input.select) "Automatic water heating setting" seems to working fine in both directions.
"cumulativeElectricEnergy" does not exist yet.
For entities with status "unknown", my Ecocute may not support them.
Please find the log in the attachment.
[home-assistant_echonetlite_2024-02-17T06-39-28.721Z.log]
(https://github.com/scottyphillips/echonetlite_homeassistant/files/14317988/home-assistant_echonetlite_2024-02-17T06-39-28.721Z.log)
The hot water temperature setting was changed from a maximum of 70°C to 90°C. You can try it on edge 75602ce.
Looking at the log, it seems that reception from the device is unstable. If possible, restarting the device may improve the situation.
@nao-pon
Hi !
I have tried the current latest version@your edge version. (Where can I find the version?)
It is not certain, but rebooting the Raspberry Pi seems to have improved reception.
The device configuration could be done with the default settings.
Test result are below.
No entity has a status of "unknown", all entities has value.
"Automatic bath water heating mode setting" input select entity does not exist, it has been lost.
"cumulativeElectricEnergy" still does not exist.
The "ecocute_temperature_of_supplied_water_setting" input select entity working fine in both directions.
Three input number entities seems to working fine in both directions.
*The "temperature_of_supplied_water_setting" input number entity does not work above 50°C, but this may be due to Ecocute specifications.
Something similar was mentioned in the following pages.
https://qiita.com/banban525/items/520caead4f5f8dbb9ced
Sorry, other checks have not been made, or it is not even clear which operation on the Eco-Cute side are linked to which entities in the first place.
Please find the log in the attachment.
home-assistant_echonetlite_2024-02-17T21-54-49.032Z.log
"Automatic bath water heating mode setting" input select entity does not exist, it has been lost.
According to the logs, there should be no particular problem, so I don't know the cause. It may have been unstable during setup...
The available data seems to be working for the most part. However, there was a problem where the input entity and sensor entity overlapped, so I fixed it with edge (ba75b12).
The installed version of edge is displayed on the HACS screen.
Hello !
I have tried "e8edc15".
This time there are two logs.
I tried to configure and delete the Eco-Cute 10 times with the default settings, but the "Automatic bath water heating mode setting" input select entity does not appear with the default settings.
But, if set the "Maximum number of properties for batch requests" to "30" and reload, the "Automatic bath water heating mode setting" input select entity appears.
On the other hand, if the "Maximum number of properties for batch requests" is left at "30", the status of most entities are "unknown".
After that, after setting the 'Maximum number of properties for batch requests' to "1", ecocute could no longer be configured.
These are the operations in the first log.
home-assistant_echonetlite_2024-02-22T22-36-10.310Z.log
Next, the HA was restarted, the Eco-Cute was configured, the "Maximum number of properties for batch requests" was set to "30" and reloaded, "Automatic bath water heating mode setting" input select entity appeared.
Then set the "Maximum number of properties for batch requests" to ”10" and reload, the status of all entities started to working.
These are the operations in the 2nd log.
home-assistant_echonetlite_2024-02-22T23-10-12.776Z.log
That means, if one configuration step is added, the most entities working fine.
I have a question.
"CumulativeElectricEnergy" does not exist yet, Has that been implemented yet?
When "CumulativeElectricEnergy" is working, I want to try it on my main HA environment.😉
Thank you !
@sympapa Thank you for your cooperation in the verification!
I updated edge. The cause of the unstable status of batch requests is not clear, but I tried setting an interval of 500ms when sending batch requests. I also believe that "Measured cumulative power consumption" is also enabled.
@nao-pon
Hello !
Is that update "8e43f33", right?
I tried it and the result was the same as "e8edc15".
home-assistant_echonetlite_2024-02-24T00-25-17.076Z.log
"Automatic bath water heating mode setting" input select entity is not appeared when first configured.
"Maximum number of properties for batch requests" was set to "30" and reloaded, it appeared.
"Measured cumulative power consumption" still does not exist.
Please let me know if there is anything I should verify.
Thanks !
@nao-pon
I tried "73e6482"
There is indeed a "Measured cumulative power consumption".
I will do a bit of detailed testing on this version and if there are no major problems I will install it in my main HA environment.
Thank you !
@nao-pon
I have started testing "73e6482" on my main HA environment.
I had a bit of trouble resolving the Omron Solar entity id changed due to issue #165, but everything(incl. Eco-cute) seems to working fine.
But, even in the main HA environment there are problems related to "batch request".
I have a question.
Is that No "unit" in the following three sensor entities for Eco-cute due to the Echonet Lite specifications?
- Measured amount of water remaining in tank
- Measured temperature of water in water heater
- Tank capacity
If that is due to the Echonet Lite specification, I will creat a sensor entities to add the units in my HA.
Thanks!
@sympapa That's because it wasn't configured. I added and marched on setting the unit of measurement for the missing sensor. 👍
Hello!
I have been using '3013fce' in my main HA environment from 5 days ago.
A Mitsubishi Eco-Cute, Omron Solar power conditioner, 4 Mitsubishi air conditioners and one SHARP air conditioner are connected.
As far as I am used, there are no problems other than the "batch request" problem when configure the Eco-Cute.
It has been very useful, thank you😉
I think this "support of Ecocute" can go to the next phase.
If there is something I can help, please feel free to let me know.
Thank you!
The version I wrote in my previous comment was a mistake.
"e1f0568" is correct.
It is still working fine today for Eco-cute.
Thanks.
This has been fixed in version 3.8.0 and will be closed. Thanks! 👍