I just installed your custom integration and it seems to work properly. I’m using it with a Schluter Ditra Heat (customerId = 3).
However, pressing one of the two buttons in the Lovelace layout gives this error message: climate/set_hvac_mode. OJMicrolineThermostat.async_set_hvac_mode() got an unexpected keyword argument 'hvac_mode'
I will give further feedback when I have things to add.
The set hvac mode hasnt really been implemented (yet), it just sets the preset to schedule I think. I dont think its possible to tell the thermostat to ‘heat’ or ‘auto’. It just switches on/off based on the temperature?
The problem is the values don’t make any sense to me (yet!), but I haven’t really had the time to dive into that part yet. I’ve just updated the code and for me it’s working pretty well now
Hello, at this time I have basic consumption from thermostats…it’s based on API data download via configuration.yaml. However, I can’t put the current date in the payload, so it’s only for manual editing. I suppose this can be solved directly in python, but I’m not good at it yet.
but problem is here: payload: ‘{“APIKEY”: “f219aab4-9ac0-4343-8422-b72203e2fac9”,“DateTime”: “2023-01-08”,“History”: 0,“ThermostatID”: “140092”,“ViewType”: 4}’
I need change date by actual date, but payload doesnt support templates. Any ideas?
Finally I use utility_meter for calculate energy consumption. Its work nice
I think you can dow something like: now().strftime("%Y-%m-%d"), so these values are correctly interpreted? then maybe I can include them in the package.
Stupid question do not exist Getting the api key is quite a challenge. I did it by unpacking an android APK, adding a SSL Certificate provided by Charles network sniffer, repacked the apk and ran the app through an android emulator on my macbook. Then used Charles to sniff the network traffic and get the api key from the headers… not so easy at all:sweat_smile:
What is your provider? Have you tried the api keys shared here? I am using the SWATT App on the iphone. I can share the api key im using it you want, just sent me a dm.
Anybody had luck with CustomerId of 23 (Comfort Heat - Australia) ?
The Android app seems to be hitting owd5-r1099-app.ojelectronics.com but having tried this url and others above I can’t seem to login. I have tried CustomerId and ClientSWVersion quoted and non-quoted via the Swagger page, but keep getting the following
Hi all. I have just stumbled onto “OJ Microline Thermostat” integration in HACS. I am running the Australian version of the MWD5 (Thermotouch WiFi 5235W).
I accepted the default host and user id parameters, and filled the API key from post 72
f219aab4-9ac0-4343-8422-b72203e2fac9
and added my user name and password from the app.
It loaded immediately and at first look, most, if not all, entities are available. EDIT: interactions seem okay, next project is to look at automations.
I have tried the various host names mentioned here (see below) and on GitHub with the API Key from the same places, with various customer ID (99, 111, the one from the SWATT App)
All of them return “Invalid authentication”. I don’t have an Android Phone to try and sniff what host it is using, is there any other way to get this working?