Hi again
I almost get it running for my Cetetherm Pioneer , tried to reinstall your app but then this time I got this screen and the system looks like it can not pass this , what have happen
Thank you for the sceenshot, I understand the issue better now.
In order for me to check the issue, would you please share your device with me?
In order to share your device -
- Browse to MyUplink site
- Choose “System Profile” from the top menu
- Choose “Security” from the left menu
- Add my email as a user
I promise not to change any setting of your device, I just want to take a look and see why the add-device flow is not working properly.
Hi Gal , very thankful for help as one of the first user of this new product , actually I think it is a good idea to also get an Icon up for the Cetetherm Pioneer smart system in your app . I copied this email to my friend at the R&D at Cetetherm and now more of the technical details so we can move forward quicker if we find problems that I can not help with . My problem is that it is not clear for me why the values I have access to are not updating. I only want to read the values of a graph called Homey Pro and maybe it is not the correct flow I have . It is hard to know what trigger a change of the “Inomhustemperatur” (in house temperature ", is it a change of 1 degree celsius or 0.1 degree Celcius or a specific time or what ?)
Here is one example
I believe that the following value is the only one that is provided by the MyUplink for the Cetetherm Pioneer system:
- Aktuell utetemperatur (BT1)
- Medeltemperatur (BT1)
- Börvärde rumstemperatur system 1
- Systemtryck
- Styrande rumsgivare
- Inomhustemperatur, extern
- Inomhustemperatur
- Relativ luftfuktighet
- Energianvändning varmvatten [senaste dygnet per timme]
- Energianvändning värme [senaste dygnet per timme]
- Energianvändning varmvatten [föregående dag]
- Energianvändning värme [föregående dag]
- Energianvändning [föregående dag]
- Förhållande uppvärmning [föregående dag]
- Varmvattenförhållande [föregående dag]
In oredr to assist, I will need to see your device.
Will you be able to add me to your device, as I mentioned here?
Hi @Lars_Herrnsdorf ,
Thanks for sharing the device with me.
I can confirm that the list of datapoints that are exposed by your device are the following:
- Current outd temp (BT1)
- Average temperature (BT1)
- Set point value room temp system 1
- Operating pressure
- Controlling room sensor
- Indoor temperature, external
- Indoor temperature
- Relative humidity
- Energy consumption hot water [most recent 24 hour period per hour]
- Energy consumption heating [most recent 24 hour period per hour]
- Energy consumption hot water [previous day]
- Energy consumption heating [previous day]
- Energy consumption [previous day]
- Ratio heating [previous day]
- Hot water conditions [previous day]
This correlates to the list you provided in your post.
I can also confirm that I do see some datapoint values changing from time to time. For example, the “relative humidity” datapoint is frequently updated, and I can see its changing a bit every minute:
They way the system works is that every exactly 60 seconds, I query the device for all the available datapoints values (I am using the /v2/devices//points API), and if a value has changed, I am triggering an event that will cause the “Datapoint has changed” flowcard to trigger.
As for your question “why the values I have access to are not updating” - can you give a specific datapoint that should have been updated, but was not updated?
You should check both the Capability value in Homey, For example, this one:
And compare it to the same value on the MyUplink website, for example:
If you see that Homey capability value is showing a different value than MyUplink website, something is wrong - send me those pictures and I will try to figure out why is the difference.
Thank You, I also get updates simulator that you show.
Quick feedback, I belive that the reason to that the temperature values is nor updated frequently is that cetetherm o lying provides integer change not decimals, I should talk to my friend at R&D at Cetetherm
Den ons 13 nov. 2024 11:18Gal Carmeli via Homey Community Forum <notifications@athom.discoursemail.com> skrev:
Thanks to the developer(s) for this great app!
I have a Nibe F730. I have added “status: (10)” as a datapoint hoping it would display how man kw extra the heater was using when it was running.
In the Nibe INFO Menu (3.3 tillsatsinfo) “status” displays either “från” (not running) or the current consumtpion in kw. In homey however, something else is shown.
When not running, this app in Homey will show 1500.00 kw and when running, the reported value is reasonable, but still inflated, e.x. when Nibe say 1kw, this app it may show 10.70 kw. For this, i simply think the data wrongly calculated. Dividing by 10 will give more sensible values.
Hi @John_Johansson,
I can take a look at your device. If you want me to do that, please add me as a user to your device in the following way:
- Browse to MyUplink site
- Choose “System Profile” from the top menu
- Choose “Security” from the left menu
- Add my email as a user
I promise not to change any setting of your device, I just want to take a look and see the datapoint values.
Hi John and welcome to the community!
Just like you, I also have a Nibe F730 and I have also tried to find the right datapoints for the various internal power stages.
I used the myUplink API and got a complete list out off my F730. The list was long, but with this I was able to identify that the datapoint named as “Int elec add heat” is not the various power stages, but means the following (in summary);
"parameterId": "49993", "parameterName": "Int elec add heat",
"value": "0", "text": "Alarm",
"value": "1", "text": "Alarm",
"value": "2", "text": "Active",
"value": "3", "text": "Off",
"value": "4", "text": "Blocked",
"value": "5", "text": "Off",
"value": "6", "text": "Active"
I have two datapoints called “status:”.
"parameterId": "50095", "parameterName": "status:",
and
"parameterId": "50113", "parameterName": "status:",
When the complete parameter list for my F730 is loaded into Gal_Carmeli’s excellent app Nibe MyUplink, it renames the last datapoint “status:” to “status: (1)”. (if there had been more, the next one would have been named “status: (2)” etc.
According to the loaded list, the datapoint called “status:” means the following (in summary);
"parameterId": "50095", "parameterName": "status:", "parameterUnit": "min",
"value": "15000", "text": "starts",
"value": "15001", "text": "runs",
"value": "15003", "text": "off",
"value": "15004", "text": "hot water",
"value": "15005", "text": "heating",
"value": "15006", "text": "pool",
"value": "10480", "text": "incomp. hp",
"value": "10065", "text": "Comm.fault In",
"value": "10066", "text": "Communication fault with PCA Input.",
"value": "10067", "text": "Communication fault with PCA Input.",
"value": "10068", "text": "Com.flt Base",
"value": "10069", "text": "Communication fault with PCA Base.",
"value": "10070", "text": "Communication fault with PCA Base.",
"value": "10162", "text": "Sens flt:BT18",
"value": "15971", "text": "incomp. inv.",
"value": "10177", "text": "Sens flt:BT14",
"value": "10071", "text": "HP alarm",
"value": "10072", "text": "High pressure alarm",
"value": "10073", "text": "High pressure alarm",
"value": "10074", "text": "LP alarm",
"value": "10075", "text": "Low pressure alarm",
"value": "10076", "text": "Low pressure alarm",
"value": "10077", "text": "Comm.flt MC",
"value": "10078", "text": "Comm.flt with PCA Motor Controller",
"value": "10079", "text": "Communication fault with PCA Motor Controller.",
"value": "10080", "text": "MP alarm",
"value": "10081", "text": "Motor protection alarm",
"value": "10082", "text": "Motor protection alarm",
"value": "10083", "text": "Sensor flt:BT1",
"value": "10084", "text": "Sensor fault: BT1 outdoor sensor",
"value": "10085", "text": "Sensor fault: BT1 outdoor sensor",
"value": "10086", "text": "Sensor flt:BT2",
"value": "10087", "text": "Sensor fault: BT2 flow line sensor 1",
"value": "10088", "text": "Sensor fault: BT2 flow line sensor 1",
"value": "10089", "text": "Sens flt:BT12",
"value": "10090", "text": "Sensor fault: BT12 condenser out",
"value": "10091", "text": "Sensor fault: BT12 condenser out",
"value": "10092", "text": "Sensor flt:BT3",
"value": "10095", "text": "Sensor flt:BT6",
"value": "10154", "text": "internal electrical addition",
"value": "10183", "text": "L exh.temp",
"value": "10203", "text": "Sensor flt:BT7",
"value": "10187", "text": "Defrosting",
"value": "15117", "text": "blocked",
"value": "16528", "text": "Inverter fault",
"value": "10068", "text": "Com.flt Base",
"value": "10311", "text": "Inverter I",
"value": "10314", "text": "Inverter II",
"value": "10317", "text": "Inverter III",
"value": "10110", "text": "Hot gas alarm",
"value": "10116", "text": "TB alarm",
"value": "10122", "text": "Hi cond. out",
"value": "10276", "text": "Err: BT63",
"value": "10293", "text": "serial no",
"value": "10296", "text": "software",
"value": "11176", "text": "comm.err hp",
"value": "15117", "text": "blocked",
"value": "15629", "text": "ext control",
"value": "15966", "text": "Pres.alarm",
"value": "15971", "text": "incomp. inv.",
"value": "16537", "text": "Soft-start flt",
"value": "16659", "text": "Acc. block.",
"value": "15468", "text": "initiating",
"value": "11165", "text": "pool 2",
"value": "11174", "text": "com.err.slave",
"value": "15985", "text": "Com.flt GP12",
"value": "16541", "text": "not docked",
The datapoint named “status: (1)” (“parameterId”: “50113”, “parameterName”: “status:”, “parameterUnit”: “kW”) should, according to the loaded list, contain roughly the same as "status: ”, BUT after logging various data points, I have started to see a pattern;
The difference between “status:” and “status: (1)” is that “status: (1)” display the following values;
1500, 1512, 0-6
I interpret this as;
1500 = Off
1512 = Blocked
I interpret 0-6 as either kW or what power stage the F730 runs on.
This answer got long and it is my assumptions made on my F730, but I hope it can be of some help.
If you or anyone else finds inaccuracies in the above or additional useful information, please share.
1 Like
Great looking into, This adds so much context and understanding of how the app works.
My values have been more in line with this, the past couple of days compared to when I originally added the datapoint “status: (1)”. It now shows either the correct value of kw used, or 1500 kw when not running. And that makes sense, reading your post, the value 1500 corresponds to off.
@Gal_Carmeli How can we make use of this, is there a way to manipulate the value, so that 1500 equals 0 ?
Thanks!
You have been added.
The risk is that it is model-specific and then there may be many different interpretations to be made in the app…?
It would have helped a bit if the app gave not only the value, but also the “text”, for example on the datapoint “status:” the value 15000 means “starts”. It is in the JSON file, so it would have been good if @Gal_Carmeli in its excellent app could read out both the value and, if there is an text associated with the value, also present the text in its own variable/tag. Then you can, for example, on the card “The datapoint [Datapoint] has changed” output, not only the [#]Datapoint Value, but also the associated [a]Datapoint Text.
1 Like
@John_Johansson , @Krisstenswe -
I investigated it for a while.
I am not sure I completely unedrsatnd the conclusion saying that 1500 means off.
Here is all the information that the device is providing me on that specific datapoint:
{
"category": "F730 Cu 3x400V",
"parameterId": "50113",
"parameterName": "status:",
"parameterUnit": "kW",
"writable": false,
"timestamp": "2024-11-25T22:22:15+00:00",
"value": 1512.0,
"strVal": "1512kW",
"smartHomeCategories": [],
"minValue": null,
"maxValue": null,
"stepValue": 1.0,
"enumValues": [
{
"value": "15000",
"text": "starts",
"icon": ""
},
{
"value": "15001",
"text": "runs",
"icon": ""
},
{
"value": "15003",
"text": "off",
"icon": ""
},
{
"value": "15004",
"text": "hot water",
"icon": ""
},
{
"value": "15005",
"text": "heating",
"icon": ""
},
{
"value": "15006",
"text": "pool",
"icon": ""
},
{
"value": "10480",
"text": "incomp. hp",
"icon": ""
},
{
"value": "10065",
"text": "Comm.fault In",
"icon": ""
},
{
"value": "10066",
"text": "Communication fault with PCA Input.",
"icon": ""
},
{
"value": "10067",
"text": "Communication fault with PCA Input.",
"icon": ""
},
{
"value": "10068",
"text": "Com.flt Base",
"icon": ""
},
{
"value": "10069",
"text": "Communication fault with PCA Base.",
"icon": ""
},
{
"value": "10070",
"text": "Communication fault with PCA Base.",
"icon": ""
},
{
"value": "10162",
"text": "Sens flt:BT18",
"icon": ""
},
{
"value": "15971",
"text": "incomp. inv.",
"icon": ""
},
{
"value": "10177",
"text": "Sens flt:BT14",
"icon": ""
},
{
"value": "10071",
"text": "HP alarm",
"icon": ""
},
{
"value": "10072",
"text": "High pressure alarm",
"icon": ""
},
{
"value": "10073",
"text": "High pressure alarm",
"icon": ""
},
{
"value": "10074",
"text": "LP alarm",
"icon": ""
},
{
"value": "10075",
"text": "Low pressure alarm",
"icon": ""
},
{
"value": "10076",
"text": "Low pressure alarm",
"icon": ""
},
{
"value": "10077",
"text": "Comm.flt MC",
"icon": ""
},
{
"value": "10078",
"text": "Comm.flt with PCA Motor Controller",
"icon": ""
},
{
"value": "10079",
"text": "Communication fault with PCA Motor Controller.",
"icon": ""
},
{
"value": "10080",
"text": "MP alarm",
"icon": ""
},
{
"value": "10081",
"text": "Motor protection alarm",
"icon": ""
},
{
"value": "10082",
"text": "Motor protection alarm",
"icon": ""
},
{
"value": "10083",
"text": "Sensor flt:BT1",
"icon": ""
},
{
"value": "10084",
"text": "Sensor fault: BT1 outdoor sensor",
"icon": ""
},
{
"value": "10085",
"text": "Sensor fault: BT1 outdoor sensor",
"icon": ""
},
{
"value": "10086",
"text": "Sensor flt:BT2",
"icon": ""
},
{
"value": "10087",
"text": "Sensor fault: BT2 flow line sensor 1",
"icon": ""
},
{
"value": "10088",
"text": "Sensor fault: BT2 flow line sensor 1",
"icon": ""
},
{
"value": "10089",
"text": "Sens flt:BT12",
"icon": ""
},
{
"value": "10090",
"text": "Sensor fault: BT12 condenser out",
"icon": ""
},
{
"value": "10091",
"text": "Sensor fault: BT12 condenser out",
"icon": ""
},
{
"value": "10092",
"text": "Sensor flt:BT3",
"icon": ""
},
{
"value": "10095",
"text": "Sensor flt:BT6",
"icon": ""
},
{
"value": "10154",
"text": "internal electrical addition",
"icon": ""
},
{
"value": "10183",
"text": "L exh.temp",
"icon": ""
},
{
"value": "10203",
"text": "Sensor flt:BT7",
"icon": ""
},
{
"value": "10187",
"text": "Defrosting",
"icon": ""
},
{
"value": "15117",
"text": "blocked",
"icon": ""
},
{
"value": "16528",
"text": "Inverter fault",
"icon": ""
},
{
"value": "10068",
"text": "Com.flt Base",
"icon": ""
},
{
"value": "10311",
"text": "Inverter I",
"icon": ""
},
{
"value": "10314",
"text": "Inverter II",
"icon": ""
},
{
"value": "10317",
"text": "Inverter III",
"icon": ""
},
{
"value": "10110",
"text": "Hot gas alarm",
"icon": ""
},
{
"value": "10116",
"text": "TB alarm",
"icon": ""
},
{
"value": "10122",
"text": "Hi cond. out",
"icon": ""
},
{
"value": "10276",
"text": "Err: BT63",
"icon": ""
},
{
"value": "10293",
"text": "serial no",
"icon": ""
},
{
"value": "10296",
"text": "software",
"icon": ""
},
{
"value": "11176",
"text": "comm.err hp",
"icon": ""
},
{
"value": "15117",
"text": "blocked",
"icon": ""
},
{
"value": "15629",
"text": "ext control",
"icon": ""
},
{
"value": "15966",
"text": "Pres.alarm",
"icon": ""
},
{
"value": "15971",
"text": "incomp. inv.",
"icon": ""
},
{
"value": "16537",
"text": "Soft-start flt",
"icon": ""
},
{
"value": "16659",
"text": "Acc. block.",
"icon": ""
},
{
"value": "15468",
"text": "initiating",
"icon": ""
},
{
"value": "11165",
"text": "pool 2",
"icon": ""
},
{
"value": "11174",
"text": "com.err.slave",
"icon": ""
},
{
"value": "15985",
"text": "Com.flt GP12",
"icon": ""
},
{
"value": "16541",
"text": "not docked",
"icon": ""
}
],
"scaleValue": "0.1",
"zoneId": null
}
As far as I understand, this means that any value below 10,000 is considered as the real consumptop (so 1,500 means it currently consumes 1,500).
Above 10,000 theer are “special” values. For example, the value of 15,003 means “off”.
(please notice the number of digits on each number, because its confusing).
Before we undersatnd if and how to implement this in the app, is this what you also see on your device?
1 Like
Yes, we are talking about the same datapoint “status:”, parameter id 50113, which is called “status: (1)” in the app.
The problem with this datapoint (“status:”, parameter id 50113) is that it does not show what it is stated that it should show. For example, it never shows 15000 (starts) or 15005 (heating), but it always shows one of the following: 1500, 1512, 0, 1, 2, 3, 4, 5, 6. I have never received any other values than these .
I have come to this conclusion after logging the values and then comparing them with the values in the app from myUplink.
For example, when the myUplink app showed “Blocked” on electricity addition, 1512 was shown in this data point.
However, the second data point “status:”, parameter id 50095, behaves as described in the JSON file, ie;
“value”: “15000”, “text”: “starts”,
“value”: “15001”, “text”: “runs”,
“value”: “15003”, “text”: “off”,
“value”: “15004”, “text”: “hot water”,
“value”: “15005”, “text”: “heating”,
and so on…
I have also logged this and compared it with the myUplink app and it is correct.
I’m currently trying to arrange a better logging functionality, so I can better track all the interesting data points…
1 Like
I guess the main problem of this is the fact that I need all my datapoints to be numeric. I have many places in which you can numerically work on a datapoint capability (for example, a condition saying if the value is larger than X), and therefore - I can not put any text to these capabilities values in case of a pre-defined value.
But trying to further address this - can’t you do it of the flow level? So you can add a condition card saying that if the value is 1500, you can know that the device is off, and your flow can act accordingly.
Would that work?
1 Like
No problem - I’ve solved it for now for my logging data by reading the entire JSON file for my F730 through the myUplink API.
I use your app to be able to trigger in a flow when a data point has changed and from there break it down with the help of some HomeyScripts.
So currently I’m logging data and trying to figure myself out on my F730 and right now I have no suggestions for changes to the app. Thnx!
1 Like
Great. Good luck, let me know if any further assistance is required.
2 Likes
Hi, I’m new here on Homey and not a expert. I’m trying to connect my NIBE F1145 to see some insights. But it doesn’t work. It says: “no new devices found”. Has anyone experience in doing so? Does it require a premium subscription?
@Joost_de_Baaij -
Premium subscription is not required.
On app settings, please make sure you UNCHECK the “legacy mode”, and you use your username/password that is used on the MyUplink website.
It should look like this:
If it still doesn’t work for you, please send me diagnostics report (App settings → Send Diagnostic Report)
Hi Gal, thanks for the tip. I did what you said. That was succesfully and I connected my heatpump. Do you have a tip that I can relate the energy from my heat pump is shown in a energie-dashboard?
