With version 5.24.4.0 of mcsMQTT the ability to control Emporia smartplugs is now possible. Emporia is cloud-based so this is not a first-choice smartplug, but for those who are using Emporia for energy management it provides a same-familiy solution.
Initial integration of Emporia with HS was discussed at Emporia Vue Energy Monitor and mqtt and Homeseer - HomeSeer Message Board This thread (or mcsMQTT.pdf) needs to be followed for guidance on setting up the contact with the Emporia cloud server.
The updated plugin can be found at mcsMQTT Change Log (HS4 & HS3) - HomeSeer Message Board . This is build upon version 5.24.3.5 that is available via HS updater.
The outlet in HS looks like a single feature with On and Off buttons. Status is updated when button / event control is used. Status is updated periodically to local control of the outlet is reflected in HS.
An extract from mcsMQTT is provided below which shows how to setup the Emporia Outlet.
If an Emporia outlet is being used and the desire is to also control this outlet from HS then an “A”ssociation will need to be made on the Topic that reports the outlet state and some changes made on the Edit tab.
The Topic is provided in the same URL endpoint that is used to determine the Gid and will end with “outletOn” such as row 1 in Figure 117. Once “A”ssociated with the “A” checkbox then the HS Ref will be assigned and the Edit tab accessed by clicking on it. There needs to be a publish topic defined so the HS buttons will be created and the VSP modified for case sensitivity and to change True/False from Emporia to On/Off in HS. These edits are shown in Figure 119.
The URL endpoint on the Cloud Page URL tab also needs to be changed from polling the single endpoint to get usages to also poll the devices endpoint to get the outlet status. This is done by using the name of the publist file for the endpoint rather than the explicit single endpoint. See Figure 118.
An example \data\mcsMQTT\Emoria.pub file contents is shown below where Gid shown in red will be user dependent. Note multiple Gids are entered with “+” separator such as 123456+654321.
Initial integration of Emporia with HS was discussed at Emporia Vue Energy Monitor and mqtt and Homeseer - HomeSeer Message Board This thread (or mcsMQTT.pdf) needs to be followed for guidance on setting up the contact with the Emporia cloud server.
The updated plugin can be found at mcsMQTT Change Log (HS4 & HS3) - HomeSeer Message Board . This is build upon version 5.24.3.5 that is available via HS updater.
The outlet in HS looks like a single feature with On and Off buttons. Status is updated when button / event control is used. Status is updated periodically to local control of the outlet is reflected in HS.
An extract from mcsMQTT is provided below which shows how to setup the Emporia Outlet.
If an Emporia outlet is being used and the desire is to also control this outlet from HS then an “A”ssociation will need to be made on the Topic that reports the outlet state and some changes made on the Edit tab.
The Topic is provided in the same URL endpoint that is used to determine the Gid and will end with “outletOn” such as row 1 in Figure 117. Once “A”ssociated with the “A” checkbox then the HS Ref will be assigned and the Edit tab accessed by clicking on it. There needs to be a publish topic defined so the HS buttons will be created and the VSP modified for case sensitivity and to change True/False from Emporia to On/Off in HS. These edits are shown in Figure 119.
The URL endpoint on the Cloud Page URL tab also needs to be changed from polling the single endpoint to get usages to also poll the devices endpoint to get the outlet status. This is done by using the name of the publist file for the endpoint rather than the explicit single endpoint. See Figure 118.
An example \data\mcsMQTT\Emoria.pub file contents is shown below where Gid shown in red will be user dependent. Note multiple Gids are entered with “+” separator such as 123456+654321.
Code:
$$1:=URL/https://api.emporiaenergy.com
$$2:
$$3:
$$4:
$$1:/AppAPI?apiMethod\=getDeviceListUsages&deviceGids\={/AppAPI?apiMethod\=getDeviceListUsages&deviceGids\={130000+121000+132000}&instant\=$$UTCYEAR:-$$UTCMONTH:-$$UTCDAY:T$$UTCHOUR::$$UTCMINUTE::$$UTCSECOND:.0Z&scale\=1MI N&energyUnit\=KilowattHours}&instant\=$$UTCYEAR:-$$UTCMONTH:-$$UTCDAY:T$$UTCHOUR::$$UTCMINUTE::$$UTCSECOND:.0Z&scale\=1MI N&energyUnit\=KilowattHours=
$$1:/customers/devices=