Hi @arovik, do you have any screenshot so I can be sure what you are talking about, in particular what you mean by “not showing correct”?
But I see now in insights that there are actually two different fan speed measurements.
one is called “current fan speed” and the other is called just “fan speed”, but what is the current fan speed showing? looks like its variating between 0 and 1 (edit: it probably shows if the fan is active or not) Might be better to have “fan speed” on the screen in my screenshot?
Ok, that’s the issue I had in mind, I created a ticket for Athom nearly 2 months ago: Capability logo well displayed on iOS app but not displayed on web app · Issue #374 · athombv/homey-apps-sdk-issues · GitHub since the issue is not app-related but Homey-related.
I´m not talking about the logo. I’m talking about the output of “current fan speed” vs “fan speed”. “Current fan speed” seems to have only two values: 1 or 0, while fan speed shows the actual fan speed the AC is set to. The page I’m referring to should show the last one instead if the active/not active status
Another question: the power output given, is that actual or just a guess?
Ok, I understand better.
Both values come from the MELCloud API:
- power isn’t very reliable because MELCloud doesn’t handle it very well (no real time, approximation…), but that’s the value from the MELCloud system and not my guess or calculation
- actual fan speed is handled differently than fan speed and is a separate value in the MELCloud API: indeed it’s most often 0 or 1 because MELCloud devices can reduce the speed according to the measured room temperature; as far as I know the maximum value is 6 and happen at the very beginning of fast speeds
To sum up: both values come from MELCloud API and receive no treatment in Homey.
ok thanks. But regarding the power measurement. The “total energy” is that also an approximation, or is that a direct number from a counter in the unit? Also, do you know something of the new melcloud solution “melcloud home”, can we get that by buying a new wifi-adapter, and will you make an app for that aswell?
Everything is raw data from the MELCloud API (which should rely on unit metrics, I guess).
As far as I know, the new app MELCloud Home app also relies on the MELCloud API but displays data in a new user interface, so data should be exactly the same.
it looks like a new backend aswell. you can’t login with your current melcloud credentials
@arovik, MELCloud | Homey should fix your value issue (but not the display one).
About MELCloud Home: I’m not aware of it, and since there’s no user interface accessible from the Internet (as far as I know), it’s not possible to see which the new APIs would be. So I won’t be able to publish a new app – and wouldn’t have time for it anyway.
It’s true that there are two fan speed values. The one called “Fan speed” is a value that you can modify (for my heatpump the value corespond to the following, 0= auto, 1=low, 2=lowmedium, 3=medium, 4=mediumhigh, 5=high). The value “current fan speed” is a value that correspond to the actual fan speed and can not be set (for example if you set the “fan speed” to auto, you will see what the fan is actually running at. For me it varies between 0 and 5 (0= off, 1=low, 2=lowmedium, 3=medium, 4=mediumhigh, 5=high), but I can only see this in the insight since there is something funky with the custom capabilities, like @OlivierZal mentioned.
Anyone else experiencing problems? My unit hasn’t reported in for two days (or so the official app says), but seems to be working fine when I use the remote.
No issue on my side. If the official app is also affected but not with the remote, it might be a local communication (Wi-Fi) issue.
Tried to find information about update frequency of the app data, but couldn’t find any.
How often is the api called and does it do a full refresh of all values?
Before it was every minute, but a MELCloud update started to block API updates up to 2 hours because of this frequency (see above in this thread, it was 1 year ago). After many tries, it has been set to 5 minutes and no more issue since.
And yes it’s a full refresh.
Thanks. Turns out I “just” needed a complete reset of the network adapter and then a new inclusion in the wifi network. 
