I have six wifi sockets connected to a Homey running app version 2.3.9. Today the temperature is updated only 2-3 times, an I do not know if it controls the temperature correctly. The Mill app has the same problem. Anyone who has seen the same problem?
Another Homey running 2.4.7 works fine.
When will the first one be automatically updated to the latest app version?
Most likely, one of your Homeys have the /test version installed. There is currently a newer version of the app if you install the test version. ![]()
That is right. The one in trouble has 2.3.9. How do I upgrade to 2.4.7 manually?
I made an upgrade, but it made no change. I have tried to unplug / plug two units. After this they appear as disconnected borh in Homey and the Mill app, although the green light shows they are connected.
It sounds like you’re encountering some connectivity issues. First off, it’s essential that your devices are connected to Mill’s API and available there without any problems. If they’re showing as disconnected in both Homey and the Mill app despite the green light indicating a connection, I’d recommend trying to reset each heater individually. After the reset, re-add them to the Mill mobile app and check if that resolves the issue.
Sometimes, reconnecting them from scratch can help clear up any lingering connectivity or configuration problems. Let me know if this works for you or if you need any further assistance! ![]()
![]()
At around 2AM it all started working again. It seems like there have been a server problem.
Thank you for your advice.
When I try to exclude my gen3, connected via cloud, from HomeKit, I get the following error
Cannot read properties of undefined (reading ‘includes’)
On another note, is it possible, if using the local API, to change the IP address of the device that is saved in Homey? IIRC, it is currently not possible? So if the IP changes, I would have to re-add the device?
I have several Gen 3 Mill ovens that I am controlling with Homey using the community app. However, I have a problem I hope is solvable.
The only way I have found that the ovens work with Homey is to use the Mill app to set the ovens to override and continuously in Comfort mode.
The problem is that the default behaviour in the homey app when you short tap on a device is to turn it on or off. When you turn the oven off and then on again in Homey, the oven defaults to the Mill program setting, and not continuously in comfort mode. While in the program setting, I can no longer control the oven and any flows break. The only way to reliably get the oven working again is to use the Mill app to set the oven back in to comfort mode. This is a big problem. Is there a better way to solve this?
I’m not sure what to take from the screenshot you provided. Generally, the homey error messages lacks a lot of useful information, as “Cannot read properties of undefined (reading ‘includes’)” tells me virtually nothing. You could try to create a diagnostics report, but I’m afraid it won’t help. It looks like you’re using the HomeKit experiment from the Homey settings? I have never tried this, and therefore I have no knowledge about this feature. I’ve been using HomeKitty as long as I’ve used HomeKit with Homey, without any issues at all. I would recommend taking a look at it, and consider changing.
Regarding your question about IP addresses. At the moment, changing the device IP address is not supported. This is mainly because you absolutely should reserve a static IP address for each heater, instead of letting your router/heater decide for it self. If this is something people are having issues with, due to restrictions from ISP or due to other technical-related issues, I can definitely consider changing this setting, so you are allowed to change the device IP address. ![]()
If i missed any of your questions, please let me know! ![]()
Hi there!
Thanks for bringing up this issue with the Gen 3 Mill ovens and Homey. I’ve taken a look at the code, and while I’m not entirely sure if this is the root cause of the problem, it seems there might be a connection. The onCapabilityOnOff function in the Mill V2 driver appears to handle the oven’s on/off state, and it sets the oven to either “Control individually” or “Off” mode. This could be why the oven reverts to the Mill program settings when turned off and on again via Homey.
I’m planning to take a closer look at this as soon as I can to see if we can maintain the oven in “Comfort” mode even after being turned off and on again through Homey. This might require some adjustments in the code.
Also, I’ve created a wiki for all my Homey apps, which I recommend you and others to check out for more information about the app and its usage. Here’s the general link: Coderax Wiki and the direct link to the Mill Heating page: Mill Heating on Coderax Wiki.
I’ll keep you updated on any progress!
Yeah, unfortunately the error is quite ambiguous. I’ve started to migrate some things to HomeKitty, hence why I want to exclude it from the homey HomeKit ![]()
Is the source code of this available somewhere, so I could try to debug it myself?
I’ve got a static dhcp lease on my heaters, but I am never done working on my network, and at times restructure my network and then the subnets I use. So it would be really nice to be able to update the IP without having to re-add the heater to Homey, and then break all workflows.
Just a nice to have feature in my eyes.
You’re right, it is a nice feature to have. As I mentioned, I purposely set this setting as a label, not allowing the value to change. I honestly thought this was a setting people wouldn’t care about, but clearly I was wrong.
I’ll have the setting changed to a textfield, which you can change. I do have to add a check after the settings are changed, which pings the heater for status. I guess I could let you change the heater IP address, and if the check fails, it would return to the original one. If there’s no error, it’ll change successfully. Does this sound like something you could be able to manage with? ![]()
Regarding the source code, it’s located on GitHub. If you do locate the issue, feel free to improve or fix it, and open a pull request. ![]()
Awesome, thanks. I’ll take a look at the code and see if I can debug the issue more.
Hi!
Does this app support the oil radiators?
I have this one: OIL2000WIFI3
As stated in the thread’s first post:
I have now opened a pull request, it was a quite straight forward fix. changedKeys was undefined. So I just threw in a check to ensure that changedKeys exists before checking for includes.
ok, should I interpret that as no? its not supported?
No. In theory, the app supports ALL Mill Heaters. As long as you have app-control through the Mill-app, they should also work with Homey.
ok, thanks for reply, looking forward to using the app
