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.

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

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.

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
        ],
...
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.

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.

2 Likes