Plugin for Ubiquiti WiFi power outlets (mPower)

---

Hi folks,
in the past weeks I have developed a Pimatic plugin for controlling the Ubiquiti WiFi power outlets also known as mPower (https://www.ubnt.com/mfi/mpower/). For me the plugin works great and I hope that this plugin will also be helpful for other Pimatic users.

You can download the plugin from https://github.com/lnaundorf/pimatic-mpower or directly via npm from https://www.npmjs.com/package/pimatic-mpower.

Feel free to give feedback about the plugin and I hope it will be listed on the Pimatic plugin page so it can be directly installed from Pimatic.

Could you update the Dependence in package.json? So it can be installed in the upcoming pimatic v0.9

"pimatic": ">=0.8.0 <1.0.0"

Created PR https://github.com/lnaundorf/pimatic-mpower/pull/1

EDIT: Interesting product, btw. Do you know whether or not the mPower outlets are sold in Europe?

Thanks for the feedback, I have merged your pull request into the code.

The mPower outlets are also sold in europe, since I live in Germany I only have the european versions. The problem is that the US-version only supports 110 Volt devices while the EU-Version only supports 220 Volt devices. Further, the EU Pro-Version has only 6 ports compared to the 8 ports of the US Pro-Version but aside from the volt limitations and the different socket types they look identical.

There are also very interesting in-wall outlets and power switches in the Ubiquiti mPower series (https://www.ubnt.com/mfi/inwall/) which seam to support the same API as the other mPower outlets and it looks to me that the in-wall switches can be used with my plugin with minimal changes. But unfortunately, they are only available in the 110 Volt US-version, I hope that these products will also come to the european market in a special 220 Volt version.

https://www.ubnt.com/distributors/#europe

In Germany: http://www.notebooksbilliger.de/ubiquiti+mfi+mpower+pro/eqsqid/487903d2-711d-4de8-be55-2beb2d3c027a

@Flop2006 & @lnaundorf Thanks for the info!

Thanks for this plugin, will try this when I get my power outlet

Just got my mPower Pro and plugin works great!
Only thing is that the graphs are divided over 2 lines, would be nicer if they all were on 1 line.

@Cryonic90: Thanks for the feedback. If you want to hide some of the attributes in the web-GUI or just disable some of the graphs you can use the “xAttributeOptions” in the device configuration options as described in https://github.com/lnaundorf/pimatic-mpower#web-gui-customization.

Since the attributes “current”, “voltage”, “powerfactor” and “energy” dont seem to be important for most people I think they should be disabled in the plugin by default and there should be further configuration options to explicitly enable these attributes. Then everything will fit one one line with the default settings. I hope I have time in the next days to update the plugin accordingly.

I agree with that, I’m one of the guys who actually is interested in the energy consumption and current/voltage.
Another thing is that in the web-gui of the socket there’s a total counter for all of the sockets combined. Is it possible to include this one in the plugin too?

Another thing I see in the messages is a lot of the following messages:
warn [pimatic-mpower]: Error while parsing WebSocket message for 192.168.0.107: SyntaxError: Unexpected token {
Are you already aware of that?

Thanks for the feedback. A combined device for multiple or all ports of a power outlet sounds like a nice feature and is definitely is on my list for the next release.

I have also seen the warnings for invalid webSocket messages for 2 of my 3 power outlets. The problem seems to be that the power outlets sends two JSON formatted strings in one single message and this cannot be parsed correctly. For now this does not seem to be a big problem, as the power outlet sends one message per second and in the case of a parsing error the counter is just updated one second later than expected.
Even in the original Ubiquiti webSocket JavaScript code for the web-GUI of the mPower outlet they do a try-catch in the parsing step and don’t update the GUI if something went wrong. Maybe the only “fix” I can offer is to not log anything if a message cannot be parsed correctly.