It seems Kumo, weirdly still works in Celsius, even though a completely separate setup from the rest of us in Aus and Europe. So conversions between the values the driver receives and the Kumo servers seem to be something we (you) need to accept. I'll see what I can find in some of the other drivers on other HA platforms to see if the have done anything to account for this.
The best I can offer is for someone handy with sniffing HTTP comm's in the U.S., comparing the calls between the Kumo App and my drivers somehow, seeing if they behave differently with different temp calls. Otherwise we might just have to wait for local control.... Hmmm...
That is interesting. Although I am not a proper coder, I am reasonably good at following directions/tutorial if it is available about how to sniff the network traffic and get you the data you need to investigate. I am running a mac. The homebridge equivalent to your software had the same behavior and it scared me enough to turn it off.
@user410 - I have made a small tweak to the driver to hopefully handle the issue you saw recently, relating to your Zone configuration. If you want to check it out feel free to update the code and change your Zones back to how they were, or leave it the way you have it now.
I updated the code, removed the kumo devixes from hubitat, and reaadded them after putting the minisplits back into zones and the zones till do not show up after putting in the login credentials. There is no longer an error in the hubitat logs, but the child devices don't autopopulate as they should. Logs PM'd
Sorry to miss this if it's been mentioned in the thread, but by local do you mean potentially sending commands to Melview through local ip rather than through the cloud? This would be an added bonus if so, as I bought the melview device a few days ago thinking I was stuck with cloud only...
I've ordered a melview wifi adapter for a work project to control a split ac system and use hubitat to create some more complex rules (potentially averaging room temp sensors) to change the temperature of the room to a certain profile over a 24h period. Yeh it won't be a professional solution but it offers simplicity to implement, cost affective, and can have powerful rules that may later also include humidity control..
Also I'm assuming that this minor difference (F instead of S) in model number won't be an issue and potentially just a revision? Seeing it uses melcloud still?
I am assuming the same, from the brief search of Google results....
Mostly no.... Certainly no in the sense that by local control I was literally referring to our friends in the U.S. using Mitsubishi's Kumo platform. From my research and development of these drivers the only two options I have seen with totally (*) local control is the Kumo-based setup in the U.S. and the IntesisHome adaptors for us down here, with IntesisHome supported via another Community HE driver. So I was referring to the long talked about on / off work I have been doing to get local control working for those in the U.S., based on Fraser Sim's Kumo drivers on HomeBridge.
(*) = Commands and status updates are local, but I believe authentication and retrieval of unit details still require the cloud periodically...
The glimmer of hope for us is the work that NovaGL and Wob76
But it would appear the only option we have is to send commands previously sent via the cloud directly to the unit, more so to improve the speed of changes, rather than removing the dependence on the cloud entirely. I may consider some pre-defined commands that could be issued locally, but it will be a while before I get to that.
For those in Europe, unfortunately I have not been able to find any reference to the option for local control... Happy to hear of any information people find in this space... Unless I am forgetting something someone has suggested.... been plenty of conversations in this space over the last few years...
Seems that driver isn't as active as yours so I will stick with melview for now as I'm concerned about things breaking with the cloud. I don't need speed, but need reasonable reliability which I assume the melview cloud offers. I've already ordered the device to trial but wouldn't shut away from buying both adapters (intesis as well) if it comes to it.
My unit arrived already. Installed it, including apps and software... So it seems that from the device page it quickly updates in the Mitsubishi app. But the change takes quite a while, what feels like 20 seconds odd for the unit to respond. Assuming this is a limitation of the Mitsubishi cloud? Do others get this lengthy delay as well? I'm fine with it as long as it's reliable (Mitsubishi cloudbthst is), just curious.
Your drivers work great though it seems so thanks.
When I first installed the driver, I had the same issue. In fact, at first I thought maybe it wasn't working while it took so long to even turn on and adjust temperatures. Less than an hour later all the delays stopped and the system for me at least has been very responsive since. 3+ weeks into using the driver and I couldn't be happier and as I said, it's been responsive! But I'm on the US Kumo Cloud and not melview Cloud.
I would agree with that assessment as well, mine probably behaves in the same way I expect. It is also something I am pretty sure NovaGL talks about on the GitHub page I linked earlier, citing it as the main benefit of using the local control option available on MelView. They would issue a command to the MelView cloud API, get the XML back and send that XML directly to the unit in order to achieve a quicker change in the settings.
Glad to hear you got it setup, including the drivers.
I have set some rules up in hubitat however have some concerns there are problems.
If I go into the Mitsubishi app and set the temperature to 20 degrees, on auto, and low fan then it appears the unit is set correctly.
If I then send a set point command from hubitat of say 25 degrees (from device page) the temperature doesn't always update in the Mitsubishi app.
If I set the fan speed to high on hubitat device page it seems to update in the Mitsubishi app quickly for the fan speed only. And the fan eventually changes. Same for the mode commands.
At the moment it seems it's only the temperature command that isn't working fairly often. It does work occasionally though I just haven't managed to reproduce yet.
It seems auto mode uses the heating point set point (not the average). Just asking, not a problem.
I'll do some more exploration, but just in case it's been seen before. I'll start with setting the temp in Mitsubishi app to 16 and hubitat to then send 32 degrees. Then wait a while and see if the change worked and just wasn't reflected in the app properly. I know the fan and mode is though.
Thanks for the feedback @peterbrown77.pb. I can try to take a look in the next week or two, but any more testing results would be great. I can't say I change the temp that often via HE.
I do know that the ac is actually set at the Mitsubishi app screen temperature value, not what hubitat sends as I sent auto 16 degrees in app with medium fan. Then sent 30 degrees in hubitat device page and also high fan (maybe auto even I can't recall) and the ac fan adjusted but the temperature was obviously targeting 16 degrees still (same as the app).
I'll turn debugging on and report back as well
Maybe others may be able to comment if they see the fan consistently update in the app when changed in hubitat device page, but not consistently for the heat mode temperature. Maybe I'm a unique case but I can't see why I would be when the other functions work.
Seems it knows that the temperature set point in the mitsubishi app is 31 degrees. Tries to send 17 degrees auto from hubitat. But next time you can still see that your driver still sees it as 31 degrees (which it is in reality and in the Mitsubishi app still) and tried to change it to 17 dgerees again (unsuccessfully).
I'm sure I could explain that better so let me know if that isnt clear enough, well more well structured.
Ok. It seems that the fan changes regardless of other settings. So fan works as expected.
If I change just the temperature in hubitat then the apps temp set point doesn't change.
If I change the mode only then the mode changes in app.
If I set both the temperature and mode different in hubitat than they are in the all then they both update. So to see a change in the app I have to change the mode as well.
I should by Fraser Sim a beer one day.... Maybe once I get the local control finished...
