Could you do me one favor and share me the API output of your SDM630 to be sure that I get all the right data from the voltages? I dont have the kwh meter myself so not sure if I get it right.
Hm no voltage there yet. What firmware is your SDM630?
Seeking activate_voltage_l1_v etc
Like:
|active_voltage_l1_v|Number|The active voltage for phase 1 in volt|
|active_voltage_l2_v|Number|The active voltage for phase 2 in volt|
|active_voltage_l3_v|Number|The active voltage for phase 3 in volt|
I am Duco, developer at HomeWizard. Thanks for reporting the issue about mDNS and the quick heads-up towards us. We have discovered the issue and implemented a fix, the latest firmware (5.05) will be rolled out shortly to the devices that are running 5.04. Your device should be updated within 48 hours.
If you want to update your 5.04 device now, you can select ‘Settings’ → Meters → P1 Meter → ‘…’ → Check for updates.
With the v3.2.22 app some of my devices go either offline (when they are not according to homewizard app), and some report power values when not being used at all (fi powerplug washing machine). My report for debugging is 70e4cb2b-7abd-4eac-ba3f-c0208cde5b9c
I’ve now updated to the latest beta, see if that fixes things by coincidence
Well I see wifi / connection issues and your energy meter gives weird readings maybe due to corrupted json payloads Homey pulls.
2024-01-19T11:42:29.325Z [err] [ManagerDrivers] [Driver:energy] [Device:69de3e8c-4532-4c88-9afa-ece18ab266b6] SyntaxError: Unexpected token u in JSON at position 0
2024-01-19T11:42:29.711Z [err] [ManagerDrivers] [Driver:energy_socket] [Device:eeea40a5-99e6-4ebf-ab13-6d2aec63c282] FetchError: request to http://172.16.11.136/api/v1/data failed, reason: connect EHOSTUNREACH 172.16.11.136:80
at ClientRequest. (/node_modules/node-fetch/lib/index.js:1491:11)
at ClientRequest.emit (node:events:526:28)
at Socket.socketErrorListener (node:_http_client:442:9)
at Socket.emit (node:events:526:28)
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
type: ‘system’,
errno: ‘EHOSTUNREACH’,
code: ‘EHOSTUNREACH’
}