MELCloud Binding Mitubishi

Add-ons Bindings
,
102

From what I read it seems enough to just change the value in the configuration of the Thing.
I assume the people that experienced this issue and changed the value to atleast 360 or 600 seconds no longer have the error, correct?

I got a chance to do a quick check of the code and we only use a fixed interval of 60 seconds for checking the connection and connect again when the connection is no longer active.
If nobody is experiencing any issues after changing the Thing values it might still be good that I change this values to also 360 seconds but this would make it less urgent…

I can’t recall if we set the default for the Thing or if it’s a system setting, will also check that.

2 Likes
103

do you have other systems accessing the MELCloud API besides openHAB frequently (the MELCloud app, other automation systems, …)?

1 Like
104

First I tried with 600 sec were the system worked nice again, after the MELcoud service came back.
Now the last days I tried with even longer polling-time for the device-thing. It is now 3600 sec, but a test-rule for sending me a telegram-message on each “last-communiication” is sending more unregular, but still 3-4 time per hour. I had expected 1 message each hour (3600 sec).
I am not sending any commands to the heatpump, as the desired temperatur is kept constant right now. But the room-temperatur-item is updated once in a while and more often than 3600 sec.
I have installed the MELcloud app on my Android-phone, too. But normally not using it, so that app deep-sleeing and should not generate any traffic to the cloud.

105

I am also facing this issue for a few days now. I am using Openhab 4.0.3.

The error messages “Login error, reason: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $” occurs always once per minute, independently what has been set for pollingInterval in the things file. Also after modifying and rebooting.

When stopping the melcloud binding, waiting for one hour and it starting again, the error message occurs immediately.
So, the proposed workaround does not help on my side.

106

not sure how you configured it but there is also a connection check which is fixed at 60 seconds. This reconnects if not connected already, it’s possible this is why you get variable results.
I will probably change this to also 300 seconds.

2 Likes
107

You need to wait more than 1 hour. Some say 3 hours some say longer.
If the ban hasn’t been lifted it’s normal that you get the error immediately as we can’t login to MELCloud.
Before activating the binding again, try to connect and login to MELCloud via their website (from the same network as openHAB is running). If that works, you can enable the binding again.

1 Like
108

I have 2 units. I was getting the login error and disabling the MelCloud account for several hours and reenabling it worked but I was locked out very quickly. Now configured 300s polling interval on each… It’s been a few hours since I made this change and still working. Thanks, everyone, for the advice!

109

Thank you very much, the needed procedure became clearer by your description. Now it works again :slight_smile:

1 Like
110

Just as a feedback. Putting the pollingInterval to 600s definitely works. Its running fine for several days now. Thank you for the information.

111

Initially I had set my 3 AC indoor units to poll every 600 seconds - then lowered them to 360s each. Been working for a week now.

112

Hello to all,

I have been struggling to find a working config for my 5 ac units. I already tried setting the time to 300, 600 and even 900 but eventually it keeps failing.

Can someone give me some directions on this?

I am running the latest stable release of OpenHAB.

Thank you for your time.

Best regards.

113

Hello Ricardo. It is not a matter of timing. The issue is that melcloud is off line due to issues with the servers. Several clients are complaining about the loss of connection and impossibility of controlling their units either with the app or other home automations systems due to the fact everything relies on the cloud service. So you need to wait to configure your system.

114

since a couple of hours I see this error:

grafik
grafik1528×814 53.1 KB

Does anybody else facing the same problem?

115

Hello, yes I had the same issue. But after a couple of hours it worked again.

116

Feature Request (wish :slight_smile: )

Is there a chance to add the vane direction as additional channel?
Currently there are vane horizontal and vertical but no possibility to set the direction.

My Mitsubishi AC does have a slowly rotating infrared sensor that can identify persons in the room and keep the airstream away from persons in the room.
Sometimes I would like to be able to switch the directions of the airstream (possible values could be: left, center, right, wide, away-from-person, to person).

That would be nice :smiley:

Best, Kai

117

hmm, I can set direction, auto and swing for both horiontal and vertical vanes with sendCommand . What do you need different?

e.g.
… COvarmepumpe3_VaneVertical.sendCommand(2)
else COvarmepumpe3_VaneVertical.sendCommand(7) // Auto 0 / Swing 7
…
mvh Andreas

118

Thanks for your answer, Andreas.
You are talking about the “WIDE VAN button” (in red), right? This is available and working.

I am interested in the “DIRECTION” command which I highlighted in yellow

grafik
grafik864×1206 255 KB

regards, Kai

119

So I had updated openHAB from release build 4.2.0 to 4.2.1 yesterday and the melcloud account handler stopped working.
I reverted back to 4.2.0 and it’s fine again.

2024-08-09 18:47:53.861 [ERROR] [core.thing.internal.ThingManagerImpl] - Exception occurred while calling thing handler factory 'org.openhab.binding.melcloud.internal.MelCloudHandlerFactory@1fecf485': Cannot invoke "org.openhab.binding.m
java.lang.NullPointerException: Cannot invoke "org.openhab.binding.melcloud.internal.api.MelCloudConnection.isConnected()" because "this.connection" is null
<------>at org.openhab.binding.melcloud.internal.handler.MelCloudAccountHandler.isConnected(MelCloudAccountHandler.java:127) ~[?:?]
<------>at org.openhab.binding.melcloud.internal.handler.MelCloudAccountHandler.connectIfNotConnected(MelCloudAccountHandler.java:121) ~[?:?]
<------>at org.openhab.binding.melcloud.internal.handler.MelCloudAccountHandler.getDeviceList(MelCloudAccountHandler.java:96) ~[?:?]
<------>at org.openhab.binding.melcloud.internal.discovery.MelCloudDiscoveryService.discoverDevices(MelCloudDiscoveryService.java:89) ~[?:?]
<------>at org.openhab.binding.melcloud.internal.discovery.MelCloudDiscoveryService.startBackgroundDiscovery(MelCloudDiscoveryService.java:65) ~[?:?]
<------>at org.openhab.core.config.discovery.AbstractThingHandlerDiscoveryService.initialize(AbstractThingHandlerDiscoveryService.java:119) ~[?:?]
<------>at org.openhab.core.thing.binding.BaseThingHandlerFactory$RegisteredThingHandlerService.initializeService(BaseThingHandlerFactory.java:395) ~[?:?]
<------>at org.openhab.core.thing.binding.BaseThingHandlerFactory.registerThingHandlerService(BaseThingHandlerFactory.java:208) ~[?:?]
<------>at org.openhab.core.thing.binding.BaseThingHandlerFactory.registerServices(BaseThingHandlerFactory.java:160) ~[?:?]
<------>at org.openhab.core.thing.binding.BaseThingHandlerFactory.registerHandler(BaseThingHandlerFactory.java:147) ~[?:?]
<------>at org.openhab.core.thing.internal.ThingManagerImpl.doRegisterHandler(ThingManagerImpl.java:531) ~[?:?]
<------>at org.openhab.core.thing.internal.ThingManagerImpl.registerHandler(ThingManagerImpl.java:512) ~[?:?]
<------>at org.openhab.core.thing.internal.ThingManagerImpl.registerAndInitializeHandler(ThingManagerImpl.java:927) ~[?:?]
<------>at org.openhab.core.thing.internal.ThingManagerImpl.checkMissingPrerequisites(ThingManagerImpl.java:1124) ~[?:?]
<------>at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?]
<------>at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [?:?]
<------>at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [?:?]
<------>at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
<------>at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
<------>at java.lang.Thread.run(Thread.java:840) [?:?]
120

I had the same problem

121

Same here… When trying to setup binding it says:

HANDLER_REGISTERING_ERROR

Cannot invoke “org.openhab.binding.melcloud.internal.api.MelCloudConnection.isConnected()” because “this.connection” is null