jlama / powertagd Goto Github PK

hello, I'm starting with home assistant and I installed zigbe2mptt with mosquito. I noted that I need to flash my Sonoff E dongle to detect my Powertags. But the steps below are rather vague for a novice like me. Could you detail step by step what needs to be done? THANKS

Hey, i dont know if the issue is on my side, but i can't figure out how to compile either this repo or the other forked repos that have MQTT support of some sorts.

My plan is to run the powertagd directly on Proxmox, but i just cant compile it. The error is the following:

root@proxmox:~/powertagd/src# make
cc -g -O1 -fno-omit-frame-pointer -Wall -Wno-unused-function -c -o ash.o ash.c
In file included from ash.c:12:
util.h:153:13: error: static declaration of ‘arc4random_buf’ follows non-static declaration
153 | static void arc4random_buf(void *buf, size_t nbytes)
| ^~~~~~~~~~~~~~
In file included from ash.c:5:
/usr/include/stdlib.h:542:13: note: previous declaration of ‘arc4random_buf’ with type ‘void(void *, size_t)’ {aka ‘void(void *, long unsigned int)’}
542 | extern void arc4random_buf (void *__buf, size_t __size)
| ^~~~~~~~~~~~~~
util.h:159:17: error: static declaration of ‘arc4random’ follows non-static declaration
159 | static uint32_t arc4random(void)
| ^~~~~~~~~~
/usr/include/stdlib.h:538:19: note: previous declaration of ‘arc4random’ with type ‘__uint32_t(void)’ {aka ‘unsigned int(void)’}
538 | extern __uint32_t arc4random (void)
| ^~~~~~~~~~
make: *** [Makefile:38: ash.o] Error 1

I already tried to compile other forks but there are a lot of other references missing (cJSON or mosquitto on @SeanHood or @fdamm fork)

Hi
I have the following error :

➜  src git:(master) ✗ ./powertagd -d /dev/cu.usbmodem202208161432461 create 26
[INFO] tty: opening '/dev/cu.usbmodem202208161432461' at 115200 bauds
[INFO] ash: connected to NCP
[INFO] ezsp: EZSPv9, stack type 2 (mesh), version 7.1.3.0
[INFO] ezsp: xNCP manufacturer: 0xbaba, version: 0x1000
[INFO] ezsp: registering gateway endpoint
[INFO] ezsp: registering Green Power endpoint
ZigBee network successfully created!
    channel:  26
    TX power: +0 dBm
    PAN id:   0x1ae2
[WARN] ash: got NAK but no data was sent, ignoring
[ ERR] ezsp: no reply to EZSP_CUSTOM_FRAME

What does it means ? Is it possible that I'm not running your firmware ?
I have tried to flash with the ezsp tool, but hang during reset.
So I have followed this doc : https://sonoff.tech/wp-content/uploads/2022/11/SONOFF-Zigbee-3.0-USB-dongle-plus-firmware-flashing-.pdf

@jlama do you think there's any way to make exactly the same mods on zigbee2mqtt to support the powertags as you doing now?

Noticed the description mentioned upcoming MQTT support and just wanted to let it be known that it would be a welcome feature. Dont run your firmware at the moment (or own a Dongle) but if it would support MQTT directly to Home Assistant i would really appreciate that.

Seems this is the only hope or apprcoach that would support having the PowerTags be paired to HA at the moment, been looking for almost a year for a solution to this.

Hello,
Do we still need a dedicated router (like a philips hue light) with this firmware ?
In others terms : can we run with only one sonoff dongle and multiple powertags?

Thanks

Hi,

I've given up on pairing my 3P R9 power tags trough a hue smart switch and z2m, and now trying your solution.

I understand all the steps in the QuickStart guide, but step 2 "build powertagd with make". Could you "noobify" this step for me :-)?

Another question: What app do you use in HA to process the file it spits out, when everything is up and running? Was looking around in my influxDB addon, but failed to locate a locale file import.

Hello,
Maybe a dummy question : how to pick up the best channel ?

Here is my result of energy scan, but I don't know if I have to pick the one with higher or lower dBm ...

Starting energy scan...
Energy scan result: channel 11: -72 dBm
Energy scan result: channel 12: -73 dBm
Energy scan result: channel 13: -36 dBm
Energy scan result: channel 14: -33 dBm
Energy scan result: channel 15: -37 dBm
Energy scan result: channel 16: -50 dBm
Energy scan result: channel 17: -40 dBm
Energy scan result: channel 18: -40 dBm
Energy scan result: channel 19: -49 dBm
Energy scan result: channel 20: -50 dBm
Energy scan result: channel 21: -76 dBm
Energy scan result: channel 22: -79 dBm
Energy scan result: channel 23: -80 dBm
Energy scan result: channel 24: -80 dBm
Energy scan result: channel 25: -72 dBm
Energy scan result: channel 26: -27 dBm

Thanks

Hi,
Just a questions - do you know hard it would be to support EFR32MG13 based devices ?
I have the [POPP ZB-Stick (Zigbee) device.
Thanks,
Nicolai

Hello,

i tested your update, i uploaded the new firmware to the sonoff stick.
[INFO] ash: connected to NCP [INFO] ezsp: EZSPv9, stack type 2 (mesh), version 7.1.3.0 [INFO] ezsp: xNCP manufacturer: 0xbaba, version: 0x1000 [INFO] ezsp: registering gateway endpoint [INFO] ezsp: registering Green Power endpoint [INFO] ezsp: initializing network... [INFO] ezsp: stack state changed to EMBER_NETWORK_UP [INFO] ezsp: network joined as coordinator node on channel 12 (PAN: 0xb24b, TX power: 0 dBm) [INFO] PowerTag 0xe201b4d1: changing flow direction to downstream pi@ubuntu:~/powertagd-master/src$ ./powertagd -d /dev/ttyACM0

it does not change the direction:

powertag,id=0xe201b4d1 power_factor=**-68**,energy_received=17115.28,0x4013=704000,energy_p1_rx=9925.86,0x410f=413499,energy_p2_rx=3627.00,0x420f=145711,energy_p3_rx=3562.41,0x430f=144790 1676805823 powertag,id=0xe201b4d1 **voltage_p1=225.60,voltage_p2=224.50,voltage_p3=222.50,voltage_phase_ab=389.60,voltage_phase_bc=388.20,voltage_phase_ac=387.20,current_p1=1.14,current_p2=0.22,current_p3=1.84,total_power_active=**-472**,power_p1_active=-128,power_p2_active=**-16**,power_p3_active=-327,total_power_apparent=718,** 1676805828

on all values are a minus... ?

Hello,
Can this firmware run with a standard network, with multiple sensor/router/... and linked to a tools like zigbee2mqtt ?

I can see that the functionality for leaving a network is not implemented yet so do you have any tips on how to actually un-pair a powertag once it is paired with your solution? I don't have a gateway so I cannot go that route. Power-cycle it a few times? If so, how many? I tried power-cycling it a couple of times (4-5) but it seems to still be associated with the network created with powertagd. I have an R9M20 if that helps.

Hello!

I working with your Code and implement MQTT support, but actually i have some questions.

1. how can i configure the direction bit of the powertag? (Up or Down Direction) ?
2. how can i send a blink bit to the powertag to find it where it is? is there a option?

powertag,id=0xe201b4d1 power_factor=-72,energy_delivered=1.13,0x4000=330,energy_p1_tx=0.00,0x410d=0,energy_p2_tx=0.00,0x420d=0,energy_p3_tx=1.13,0x430d=330

powertag,id=0xe201b4d1 voltage_p1=220.00,voltage_p2=222.30,voltage_p3=221.40,voltage_phase_ab=382.90,voltage_phase_bc=383.20,voltage_phase_ac=383.40,current_p1=1.90,current_p2=0.21,current_p3=0.41,total_power_active=-407,power_p1_active=-370,power_p2_active=-15,power_p3_active=-20,total_power_apparent=558,

i think, while the direction is not correctly set, my powertags says a power_factory with minus?
what are total_power_active ? Watts?

thank you :)

Hello,

I have some Schneider Electric PowerTags and i become this message:

[code]
[INFO] tty: opening '/dev/ttyACM0' at 115200 bauds
[INFO] ash: connected to NCP
[INFO] ezsp: EZSPv9, stack type 2 (mesh), version 7.1.3.0
[INFO] ezsp: xNCP manufacturer: 0xbaba, version: 0x1000
[INFO] ezsp: registering gateway endpoint
[INFO] ezsp: registering Green Power endpoint
[INFO] ezsp: initializing network...
[INFO] ezsp: stack state changed to EMBER_NETWORK_UP
[INFO] ezsp: network joined as coordinator node on channel 24 (PAN: 0x690e, TX power: 0 dBm)
[WARN] gp: could not decrypt or validate GPF
[WARN] gp: could not decrypt or validate GPF

[/code]

It seems right now that it just rotates through all the sensors and ships the data to the MQTT broker as fast as it can, and sometimes this granularity is super awesome of course, but in regular situations having it rotate through once every 10 seconds is probably enough to have some overview of the situation. I guess I could try to omit committing all this data to the InfluxDB as the data rapidly fills up the storage space otherwise.
Happy to take any input to make this change, maybe an easy "sleep" or "delay" somewhere in the code (my GO knowledge is sadly lacking, but I was able to tweak it to work in the first place).
Other than that I want to give a huge thanks for getting this setup as it was the one missing piece to get the sensors into Home Assistant for better tracking than I ever had in the Schneider Controller setup.