Smart Home Energy Monitor by Fusion Energy

Energy
63

See my post above. I have it working with no internet access for several months now, but there are a few caveats. Namely the app is useless — it’s a cloud app so once you set the private IP or block access the app can’t do anything but the unit continues to report to local mqtt server.

Second caveat is that every ~16 days the unit stops reporting and has to be power cycled. This could just be a firmware bug — is anyone else seeing the same behavior, or is it related to being cut from cloud? I’ll need to put it back on the internet to use the app to check the version / updates.

Update: I am on firmware 3.0.0 and evidently that’s the latest version it could find.

64

Confirmed - support said that the newer 2-second version is not pushed out automatically to all units. They were able to update mine remotely upon request.

65

Are you able to power cycle this remotely or do you have it wired to a switch?

66

It is wired to two breakers in the panel. You can toggle the breakers to power cycle it. Not sure about the remote capability as my unit is still back-ordered.

1 Like
67

Wanta thank everyone who shared getting this setup made my life a lot easier.
Ill need to reach out to support to update the firmware.

Question, what do I need to add to the config to limit the decimals to 2 digits?

SEMMETER

68

This is from my mqtt.xml

 # - name: "Temperature"
   # unique_id: 0xa4c13856845c234a_temperaturef_zigbee2mqtt
   # state_topic: "zigbee2mqtt/Soil Sensor"
   # unit_of_measurement: "\u00b0F"
   # suggested_display_precision: 1
   # device_class: temperature
   # state_class: measurement
   # value_template: "{{ value_json.temperature }}"
   # device:
     # manufacturer: "Tuya"
     # name: "Soil Sensor"
     # model: "Soil sensor"
     # identifiers: "zigbee2mqtt_0xa4c13856845c234a"

suggested_display_precision: 2 is what you need

1 Like
69

Thanks for the tip but with suggested_display_precision: 2 was still getting the long decimals.

I did change…

value_template: "{{ value_json.sense[17][0] | float | multiply(0.1) }}"

To…

value_template: "{{ value_json.sense[17][0] | float | multiply(0.1) | round(2) }}"

Adding the
| round(2)
on the template seems to be doing the trick.

Now just waiting on support for the new firmware.

2 Likes
70

Having some issues getting up and running. YAML is complete and “checks” out.

I assume the app login and HA broker login are the same and the app uses the broker IP (assumed to be the HA IP).

Do all MAC addresses in the yaml need to be updated with the MAC displayed in the app?

Kinda stuck.

71

In the app, open the device settings and click Home Assistant. Enable the custom MQTT “Use your own server” and enter the “URL” of your broker (not just the IP address) as shown below, and the username and password for your broker login (if you are using HAOS, I believe this will be your HA login) and click Confirm.

device-settings
device-settings296×640 59.3 KB
mqtt-settings
mqtt-settings296×640 53.8 KB

Assuming you have MQTT setup correctly in HA, then go to Settings → Devices and Services → MQTT → Configure. Where it says “Topic to subscribe to” enter SEMMETER/# and click START LISTENING.Within 30 seconds you should see an entry like the one below. The MAC shown on the first line is the MAC that should be used for all the YAML sensor definitions. If you don’t want to define sensors manually you can run the script I posted above.

Message 0 received on SEMMETER/8CBFEA09F9DC/HA at 7:32 PM:
{
    "sense": [
        [
            1172,
            0,
            0,
            0,
            0
        ],
        [
            1172,
            79,
            9248,
            19,
            0
        ],
...
2 Likes
72

Finally got it.

Need to use HA credentials, port 1883, and the HA IP in MQTT re-configuration, then set the same in the SEMMETER app. The key was port 1883.

Or you can use mqtt001.tumblevd.com as the broker URL in the MQTT re-configuration and set the cloud option in the app. Same credentials and port across HA and the app.

Hope this helps.

2 Likes
73

One more time want to thank anyone who has posted in this thread for making my life easier getting this set up. Not sure where I was having issues or what I was doing first time I set this up with the MQTT yaml but this time around went smooth as butter on pancakes.

I had bought this and the Refoss em16 about the same time and forgot to return one of them so still have both. Had the Refoss installed and dont get me wrong was happy, but then I came across this thread and saw the new firmware and possible two second publish.

Firmware just updated tonight pushed through from Support and This Is Nice.

I do have the MQTT set up in config And ran the script posted higher up so probably dont need the extra yaml in the config or the script but either way this is working better than what I had before and didnt have to flash anything. Highly recommend.

3 Likes
74

I’m still on the fence about ordering one of these Fusion Energy SEM-16 models. One is on sale at Amazon right now but it’s fulfilled by 3rd party vendor instead of Amazon meaning I’m SOL and it’s on my nickel to return a defective item. I tried contacting the vendor to find out which model revision they are selling but I get no response from them. Doesn’t give me a warm fuzzy and I don’t want to be out $300

I already have an AEOTEC Z-Wave energy monitor on the mains but I want a little more insight as to what 240VAC devices are consuming and when.

In your experiences is it worth grabbing one of these considering I won’t be giving the SEM-16 internet access and will try setting it up with my local MQTT server and integrating with my HA Energy tracking? I want something that is stand-alone, relatively easy to get working, and reliable on my HA setup. I don’t want a new hobby trying to keep a basket case with nominal support running. I don’t want to be soldering onto motherboards and re-flashing firmwares.

75

Their app is pretty good, and you can use both cloud and HA if you choose their MQTT server. One of the selling points is the out of box HA/MQTT support and you don’t need to solder anything.

1 Like
76

I just ordered one from Amazon- $125 for the 16-50A sensors. Shows sold by Fusion Energy.

1 Like
77

I bought two, one for main and one for subpanel, a couple weeks back. They’re expected may 14th. Excited to try it out, the replies in here definitely gave me more confidence to do so.

78

SEM-Meter is back in stock on Amazon for overnight delivery, but my order placed a few weeks ago still shows shipping day May 18. I will probably cancel my old order and place new order to get it sooner. Just FYI.

1 Like
79

Just received the unit yesterday. I have set up the app and HA using their MQTT server. May go to local MQTT later but it is very helpful to use both their app and HA to trouble shoot and identify all the circuits (I have 25 circuits so I need to choose 16 to monitor).
It is pretty straightforward to use their MQTT server. Just need to add a bridge in the Mosquitto Broker. I have a perl script to generate the mqtt.yaml file which was then included in the configuration.yaml. I can share my setup if anybody is interested.

1 Like
80

The bottom of the app screen has the “Balance” percentage which is the circuits not monitored by the CTs. 52% means a lot of adjustments are needed :slight_smile:

IMG_8610
IMG_8610611×1323 146 KB

Screenshot 2025-05-08 090007
Screenshot 2025-05-08 090007695×952 51.2 KB

81

I purchased this device and received it earlier in the week.

I haven’t installed it in my panel yet. I opened it up and confirmed I also have the newer ESP32-S3 version. I was able to connect wires to the header (gnd, 3v3, tx, rx, gpio0) and extract the stock firmware from the device. The TX on the header goes to the RX on the chip, and RX to TX.

Just a word of warning - I created an account on their SEM Meter Android app a earlier in the week and added my device (still no sensors connected). Yesterday, I updated their Android app to the latest version (1.2.4) and when I login I’m now seeing someone else’s data! :exploding_head: I no longer see my device and it even shows another user’s phone number and email address. I downgraded to 1.2.0 via APK and was able to see my device again. I contacted support who both thanked me and apologised in broken English and said they are working on a fix ASAP.

We clearly need to get this out of the cloud. I plan on keeping my probes on the header to do some more digging. I need to add my local MQTT information and also need to request the newest firmware version. I’d like to see how that is being delivered (is this via MQTT?)

If anyone else wants to help out in this effort, shoot me a message.

82

Here is the FCC filings. May have some useful info.