I think they're talking about if you want to integrate MyQ with other services you need to pay for their subscription. But that feature requires both engineering and ongoing hosting services from Chamberlain... so I don't know but it feels justified to have to pay a subscription for it.
Using MyQ through their own app is free. If anything that seems like a deal to not have to pay subscription.
Location: NY, USA
Remote: Yes
Willing to relocate: No
Technologies: PHP, Laravel, React, Vue, .NET (C#, VB.NET), Encompass, Sage 200
Résumé/CV: https://1drv.ms/b/s!AnIhOsRqHCywhKEa4MXKn2JXOXV9qg
Email: marnold1@pm.me
9 years of work experience in the software/web-app development space. Looking for Laravel-based, salaried, permanent work, but open to whatever comes along.
I built mine to learn Angular, then ported it over to React. I had some help building some customization options like color/background selection, and have it set up so you can log in to GitHub and backup/restore your bookmarks to a Gist.
I've been working in the software/web development industry for 7 years now - looking for new and exciting challenges. Proficient in full-stack web development and VB.NET/C# winforms, with some recent work being UWP.
Looks like it's using this package here [1] to gather the information. It lists support for Linux, macOS, "partial Windows", FreeBSD, OpenBSD, NetBSD and SunOS.
There's a compatibility table for the data you can access on each system.
This is correct. I have it currently deployed on an Arch setup, but I've also tested it on other flavors of Linux.
Tried testing on Windows as well, which is when I came across the issues with compatibility. Technically, it should still work for most of the graphs. The library just doesn't reliably give proper values for I/O (disk and network). There is also an additional Windows edge case where it does not return proper CPU temp values on AMD Ryzen CPUs.
So it could still work, with the simple workaround of not displaying those graphs on Windows, but since Windows was not exactly my intended use case anyway, I didn't really address it with the intention of doing so if / when it was needed.
If anyone reading this is serious about deploying on Windows, let me know.