My Millheat things are red!
Been like this for a week or so.
The Mill Api thing throws this:
COMMUNICATION_ERROR
Error login: Server responded with error to request LoginRequest/login: 3501/account not exist/login failed, domain(810), name(MYUSER@MYEMAIL.com)
Cant seem to access the Millheat api website either, even if their server status website does not indicate any issues they know of.
Any other users experiencing the same?
Roar
Same problem with my setup
Geir
Its their old api being shut down, and us users not upgraded to the firmware that supports the New api in time. I did upgrade one device, but then it was not supported by openHAB anymore. Mill sent me 4 wifi sockets for free, so it solved it in a very estetically non pleasing way. But it works with the mill lan binding now.
I guess I should pitch in since I am the codeowner of the binding.
Mill has changed the API enough times that the binding is now defunct. As I don’t use these panel heaters for other than as a backup if other heating sources fail, I’ve prioritized maintaining other bindings over this one (which I’d be suprised is used by anyone else except us already in this thread). But I’d be happy to review a PR to make it functional again.
Super! The stupid thing from Mills side is that the migrated devices are not fully equiped with the functions of a v3 device, hence it lacks the lan-api, I believe. My migrated oven worked in the mill app, but neither on the openHAB mill binding or the mill lan binding/api. Feels a bit like they abandoned the older devices without even trying to keep them usable for folks like us 
Sounds like what most companies do these days. It’s also one of the reasons why I never buy things that rely on “cloud APIs”. I know that means that they can basically disable the device at any time, and they will when they think it’s time to force you to buy something new.
I’m the author of the “Mill LAN” binding, so if it’s anything I can do with it, please let me know. But, if they have no local API, there’s not much that can be done, sadly. Does the LAN binding “see” them at all, or are they “completely invisible”? I’m thinking that even if they don’t implement the REST API, they might announce their presence using mDNS for example.
Absolutely no response on the lan binding or the rest api, so the only option is the wall plug. In other words, could use any old oven.
I’m glad to hear that the Wi-Fi sockets work with the LAN binding. I have none, so I never got to test that. I’m guessing that automatic discovery don’t work for them, because I have no idea what data they present. So, if you could do a discovery and paste the warning that is logged, I should be able to add support for auto-discovery to the LAN binding.