Very nice. I use the standard history graph which can be updated only every 5 minutes. I will try the min graph.
Sending data every 2 seconds â will it cause the HA to crash?
I donât think so. The data package is pretty small. It doesnât seem to have any effect on my min PC based HA. But if you are running a very slow system like RPi 3, it may slow things down but it should not crash the system.
Thanks you ,I really hope the item arrives soon.
sorry im new to HA how I can download this file? I tried to tutorial of the apps 4 time and I didnt get it to work. anyone willing to help me on discord would be really appreciated https://discord.gg/tMprpcNg shau#6120 i can buy you a coffee
Thanks for sharing this, have mine up and working! Although one of my mains didnât work so I changed it from [16] to [18] in the code having to do with which phase. I think their manual must be wrong because even their app shows me on C phase, but when hooking the connectors up it showed Ant to left, then two mains and empty 3.5m plug. shrug It works, and I wasnât going to go open my panel back up in the rain when I could just modify the YAML.
I would recommend everyone configure this to use your local MQTT server and not use the vendorâs MQTT server for Home Assistant. In addition, when you get it all configured, I would also recommend you block the device from the Internet.
By doing so, that will prevent it from showing data in their SEM-Meter app, but it also protects your device.
Iâve been reverse engineering this thing in order to potentially put ESPHome on it, and there are some security flaws with how it works.
2 Likes
I got it wrong the first time too. The manual is correct. The one closest to the ANT is the C phase, as it is labelled on the box and the manual. Yes, using [18] instead of [16] should fix it. One of the pictures in the manual does show they use the two plugs closest to the ANT which would have been B and C.
1 Like
Did you contact the seller about the security flaws? SERVICEfe AT outlook.com
They have been extremely cool with my several contacts with them. Not everyone reads this forum, and fixing it at the source is the answer.
LOL glad to see I wasnât the only one. I was just scanning the manual while installing, saw the a photo with orientation and it does show B & C connected. At that point I just ignored the writing on the case itself.
I also sent them an email asking of any problem running it on C for now, they said no. They are also sending me a free antennae extension as my panel is super crowded at the bottom, and the antennae sticks out about 1.5 inches, so I will fix it when i put that on.
Again thanks for sharing those YAML files.
I contacted them weeks ago when their frontend app was showing me other userâs data. I did not contact them about my recent discovery of how insecure their system architecture is. I doubt they will be âextremely coolâ of hearing that.
Given its a rather unknown company, low profit margins on IOT devices, and the work involved to fix this, I have my doubts they would bother. Security is not really their top concern based on the fact they released a version of the Android app that showed you other userâs data.
Oh, no!!! You got to see someoneâs dryer wattage. Bugs happen. Google leaked users data for months, and covered it up. Microsoft has been owned by Russia more times than I can count. And so has pretty much every company Iâm going to bet. The correct thing to do is report the issues to them, and then you have done the right thing. Iâll be muting you and this topic.
What kind of security issues did you find? I donât care too much if people can get hold of my electricity usage data, but it would be a big concern if they can log in or take control of the SEM METER box and use it as a jumping board to access my local network.
Unfortunately Itâs exactly this. Someone can replace the factory firmware OTA with their own firmware. A bad actor could brick everyoneâs device right now if you donât have it blocked.
For me, this is my easy way to put EspHome on the box without cracking it open again. 
Yeh, lots of devices have this issue. We can request the support to add a setting to disable automatic OTA update to mitigate this issue. Right now, the firmware update is controlled by them only.
Right now, the firmware update is controlled by them only.
Thatâs what Iâm saying - this is not true. I could push an update to any device. They arenât controlling this securely.
I see what youâre saying though - there should be a preference to not automatically accept updates. However, if that was setup today, that would also prevent the vendor from making automatic security updates.
Kind of a âdummyâ question here⌠can someone explain the âenergyInâ sensor data to me?
I understand the Total Power reading. (Realtime). 1200+ kWh?? I barely use 1200kWh a month! ⌠am I missing a zero somewhere?
value_template: "{{ value_json.sense[16][3] | float | multiply(0.001) + value_json.sense[17][3] | float | multiply(0.001) + value_json.sense[18][3] | float | multiply(0.001)}}"
It is total energy used since last reset (or from first use). The formula is correct. It could be that the data was not zero when YOU started to use it. Either the device has been used before or the factory testing or QA didnât reset it before shipping. You can live with it or create Utility Meter to start counting it from zero.
Ahh ok so this is historical data. Iâve been using it for several months now, which would then account for 1200+kWh. Is there a way to reset from my end? Iâm guessing it would be the âDelete Dataâ option on the device settings in the app? And/Or is there a way to do this on a schedule?
Last time my firmware was updated and the energy numbers were reset to 0, but I am not aware of a way to reset it myself. If you send an email to the support and give them your SN, they should be able to reset it for you on the backend.
I have hourly/daily/weekly/monthly/quarterly/yearly Utility Meter entities set up for all circuits and total usage (see the utility_meter.yaml file I posted earlier), so I really donât care about the raw numbers.