Page 5 of 7

Re: Remeha eTwist

Posted: Thursday 08 February 2024 19:12
by Tuk90
hendrikenrenny wrote: Wednesday 07 February 2024 22:16 Hi,

Great this plugin! I have been waiting for it since a long time.

Would it be possible in the next update to include the entry and back flow temperature (aanvoer en retour) of the heating? Those temperatures could help to optimize the heating.

Thanks!

Hendrik
As far as I know those values are not available via the API. If they are please let me know how they are called or show me the JSON response and I will add it.

Re: Remeha eTwist

Posted: Monday 12 February 2024 18:02
by bwbboot
Thanks for all the great latest updates!

Do you think you might be able to add the EnergyDelivery value as well?

Re: Remeha eTwist

Posted: Monday 12 February 2024 21:07
by Tuk90
bwbboot wrote: Monday 12 February 2024 18:02 Thanks for all the great latest updates!

Do you think you might be able to add the EnergyDelivery value as well?
Why would you want to have those?

Re: Remeha eTwist

Posted: Monday 12 February 2024 21:14
by bwbboot
Because it shows how much kWh heat was delivered by the Heatpump vs the kWh electricity consumed.

Re: Remeha eTwist

Posted: Monday 12 February 2024 21:48
by Tuk90
bwbboot wrote: Monday 12 February 2024 21:14 Because it shows how much kWh heat was delivered by the Heatpump vs the kWh electricity consumed.
Ok, and in the same way I solved it for the energy consumed?

Re: Remeha eTwist

Posted: Monday 12 February 2024 22:02
by bwbboot
Yes please. And once again many thanks for getting this all started!

Re: Remeha eTwist

Posted: Sunday 25 February 2024 20:57
by Tuk90
bwbboot wrote: Monday 12 February 2024 22:02 Yes please. And once again many thanks for getting this all started!
Hi,

It took some time but I got it implemented, it is not yet on the main branch but you can test it already: https://github.com/tuk90/RemehaHome-Dom ... yGenerated

ps. for the people that are reading this in the current main branch it is also possible to set the mode of the thermostat to manual, scheduling, temporary override and frostprotection :).

Re: Remeha eTwist

Posted: Monday 26 February 2024 21:02
by bwbboot
Thank you for the latest update. Just installed!

Re: Remeha eTwist

Posted: Tuesday 01 October 2024 19:45
by bwbboot
Seems something has changed a while ago at Remeha. Log is now being spammed with these messages below.

2024-10-01 18:02:44.182 Error: Remeha Home: Error making GET request: 500 Server Error: Internal Server Error for url: https://api.bdrthermea.net/Mobile/api/homes/dashboard
2024-10-01 19:05:51.445 Error: Remeha Home hardware (56) thread seems to have ended unexpectedly
2024-10-01 19:06:05.446 Error: Remeha Home hardware (56) thread seems to have ended unexpectedly
2024-10-01 19:06:19.448 Error: Remeha Home hardware (56) thread seems to have ended unexpectedly
2024-10-01 19:06:24.182 Error: Remeha Home: Error making GET request: 500 Server Error: Internal Server Error for url: https://api.bdrthermea.net/Mobile/api/homes/dashboard

Running Domoticz Version: 2024.7

Re: Remeha eTwist

Posted: Wednesday 02 October 2024 16:22
by gizmocuz
I have these as well, but it is still working

Re: Remeha eTwist

Posted: Friday 04 October 2024 10:24
by Tuk90
Error 500 are the best :). I saw them before like half a year a go but there seem to be a lot right now. It seems like a general server thingy so not sure if we can do anything to ‘fix’ this. I also do not see big holes in my data, I could reduce the amount of polling but 120 per hour is not outrageous.

Re: Remeha eTwist

Posted: Sunday 06 October 2024 13:42
by manjh
Tuk90 wrote: Sunday 25 February 2024 20:57
bwbboot wrote: Monday 12 February 2024 22:02 Yes please. And once again many thanks for getting this all started!
Hi,

It took some time but I got it implemented, it is not yet on the main branch but you can test it already: https://github.com/tuk90/RemehaHome-Dom ... yGenerated

ps. for the people that are reading this in the current main branch it is also possible to set the mode of the thermostat to manual, scheduling, temporary override and frostprotection :).
Has the package been moved? When I follow this link I get a "not found" error...

Re: Remeha eTwist

Posted: Sunday 06 October 2024 13:52
by Tuk90
manjh wrote: Sunday 06 October 2024 13:42
Tuk90 wrote: Sunday 25 February 2024 20:57
bwbboot wrote: Monday 12 February 2024 22:02 Yes please. And once again many thanks for getting this all started!
Hi,

It took some time but I got it implemented, it is not yet on the main branch but you can test it already: https://github.com/tuk90/RemehaHome-Dom ... yGenerated

ps. for the people that are reading this in the current main branch it is also possible to set the mode of the thermostat to manual, scheduling, temporary override and frostprotection :).
Has the package been moved? When I follow this link I get a "not found" error...
That was a link to a branch that does not exist anymore. This is the link to master https://github.com/tuk90/RemehaHome-Domoticz

Re: Remeha eTwist

Posted: Saturday 14 December 2024 18:13
by RolandJ
Thanks for this plugin. Works great!
Would it be possible to add the COP value? This in present in the app nowadays. Would be nice to log these values in Domoticz.

Re: Remeha eTwist

Posted: Thursday 02 January 2025 12:41
by SimHelm
First of all thanks for the plugin!

I am using it with the eTwist RF thermostat, it seems to work correctly, although I get this error message in the log:
Error: RemehaHome: Error making GET request: 7

Any idea what is causing this?

Re: Remeha eTwist

Posted: Thursday 02 January 2025 13:23
by gizmocuz
Is this all the time, or sometimes?

I suppose the poll interval is still set to 1 minute or lower (2 or 5)
If it is set shorter, try starting with setting this to 1 minute.

It could also be that the API backend had issues

Re: Remeha eTwist

Posted: Saturday 11 January 2025 12:26
by Tuk90
RolandJ wrote: Saturday 14 December 2024 18:13 Thanks for this plugin. Works great!
Would it be possible to add the COP value? This in present in the app nowadays. Would be nice to log these values in Domoticz.
Hi Roland,

Is it returned via the API? If so I can add it

Re: Remeha eTwist

Posted: Saturday 11 January 2025 16:41
by RolandJ
This I don't know. How can I check this?

Re: Remeha eTwist

Posted: Saturday 11 January 2025 21:09
by Tuk90
RolandJ wrote: Saturday 11 January 2025 16:41 This I don't know. How can I check this?
In the same repo is a file that’s called remehatest.py. You can use it to test calls or to get a bearer token and use it in Postman to ‘explore’ the endpoints.

Re: Remeha eTwist

Posted: Sunday 12 January 2025 14:55
by Tuk90
I did a check myself and the value is also available via the API, it is not a COP value but a SCOP value.

It is listed in the https://api.bdrthermea.net/Mobile/api/a ... 00:00.000Z endpoint.

The response looks like this

Code: Select all

{
    "startDateTimeUsed": "2025-01-01T00:00:00+00:00",
    "endDateTimeUsed": "2025-01-03T00:00:00+00:00",
    "data": [
        {
            "timeStamp": "2025-01-01T00:00:00+00:00",
            "heatingEnergyConsumed": 13.00,
            "hotWaterEnergyConsumed": 0,
            "coolingEnergyConsumed": 0,
            "heatingEnergyDelivered": 53.00,
            "hotWaterEnergyDelivered": 0,
            "coolingEnergyDelivered": 0,
            "producerPerformanceStatistics": {
                "producers": [
                    {
                        "isMigratedFromLegacy": false,
                        "instanceWithinDevice": 1,
                        "deviceIndex": "",
                        "producerType": "HeatPumpAirSource",
                        "energyType": "Electric",
                        "energyConsumptionCH": 12.00,
                        "energyConsumptionDHW": 0,
                        "energyConsumptionCooling": 0,
                        "energyConsumptionTotal": 12.00,
                        "energyProductionCH": 52.00,
                        "energyProductionDHW": 0,
                        "energyProductionCooling": 0,
                        "energyProductionTotal": 52.00,
                        "seasonalEfficiency": 3.40000
                    },
                    {
                        "isMigratedFromLegacy": false,
                        "instanceWithinDevice": 2,
                        "deviceIndex": "",
                        "producerType": "GasBoiler",
                        "energyType": "NaturalGas",
                        "energyConsumptionCH": 1.00,
                        "energyConsumptionDHW": 0,
                        "energyConsumptionCooling": 0,
                        "energyConsumptionTotal": 1.00,
                        "energyProductionCH": 0,
                        "energyProductionDHW": 0,
                        "energyProductionCooling": 0,
                        "energyProductionTotal": 0,
                        "seasonalEfficiency": null
                    }
                ]
            }
        },
        {
            "timeStamp": "2025-01-02T00:00:00+00:00",
            "heatingEnergyConsumed": 8.00,
            "hotWaterEnergyConsumed": 0,
            "coolingEnergyConsumed": 0,
            "heatingEnergyDelivered": 31.00,
            "hotWaterEnergyDelivered": 0,
            "coolingEnergyDelivered": 0,
            "producerPerformanceStatistics": {
                "producers": [
                    {
                        "isMigratedFromLegacy": false,
                        "instanceWithinDevice": 1,
                        "deviceIndex": "",
                        "producerType": "HeatPumpAirSource",
                        "energyType": "Electric",
                        "energyConsumptionCH": 8.00,
                        "energyConsumptionDHW": 0,
                        "energyConsumptionCooling": 0,
                        "energyConsumptionTotal": 8.00,
                        "energyProductionCH": 31.00,
                        "energyProductionDHW": 0,
                        "energyProductionCooling": 0,
                        "energyProductionTotal": 31.00,
                        "seasonalEfficiency": 3.40000
                    },
                    {
                        "isMigratedFromLegacy": false,
                        "instanceWithinDevice": 2,
                        "deviceIndex": "",
                        "producerType": "GasBoiler",
                        "energyType": "NaturalGas",
                        "energyConsumptionCH": 0,
                        "energyConsumptionDHW": 0,
                        "energyConsumptionCooling": 0,
                        "energyConsumptionTotal": 0,
                        "energyProductionCH": 0,
                        "energyProductionDHW": 0,
                        "energyProductionCooling": 0,
                        "energyProductionTotal": 0,
                        "seasonalEfficiency": null
                    }
                ]
            }
        }
The value you are looking for is the seasonalEfficiency, these are the data for me for two days. As you can see the seasonalEfficiency is only calculated for the energyType of Electric which makes sense. But it is not the COP of that day. For example my cop of the first on januay would be 52/12 = 4.33 but the seasonalEfficiency is 3.4 and it does not change per day. I can add it in the code but the value does not seem really helpfull. Maybe it is better to create a dzvents script that calculates the COP based to the daily EnergyConsumption and EnergyDelivery. If you do want to have it any thoughts on what kind of device it should be? I think only a custom sensor would make sense.

I have a Elga ace hybrid heatpump maybe you see different stuff if you have an all electric heatpump, if so please share the response body with me.