Answered my own question (after contacting OJ Electronics Support), seems that when using the OWD5 App (instead of SWATT) the Customer ID is 1 (instead of 99),
So it works using the default Host Name.
Hopefully this is useful for anyone in the same position.
Has anyone gotten nice steady readings from the thermostat?
All the data since installation has been like this. I have now netwatch in place in my router to ping the thermostat and ocd5.azurewebsites.net to see if there is a pattern in link downs related to cut graph data.
Hi Robbin,
I too use the SWATT app with the MWD5 thermostats on android however, I’m only new to HA and are still setting up my devices. could you please send the API and any info you could provide that may help? Thank you in anticipation for your reply.
Thanks for this integration. I’ve set it up as above and overall it works well.
However one issue is it doesn’t display the scheduled heating mode correctly. It shows the scheduled increase in set point at the wrong time of day, and doesn’t update the set point up to heating occurring when it’s on, despite the thermostat showing the correct temp (see screenshots). Anyone seen similar behaviour or a way to fix it?