rodney2250 (OP)
Jr. Member
 Offline
Activity: 177
Merit: 2
|
 |
May 21, 2018, 06:10:28 AM |
|
On my cell now so it’s hard to read the traces.
So is phoenixminer working properly now?
Wrt the config, do you have a “,” after the end of each rig line? Could you send me your config?
It's working properly, but only with 3 rigs. Any more and it throws errors. I've tried with and without the "," after the last rig line and all others have a "," after them. Forgot to mention, I sent a link to my config via PM. Config looks ok. But didn't you say you desktop miner only had 2 GPUs? It's currently configured with 3. Are you running the same version of PhoenixMiner on all miners? If nothing else works then please send me a full trace together with the use config file, plus the http output of your "desktop" rig. |
|
|
|
|
tradersblog
Newbie
Offline
Activity: 12
Merit: 0
|
|
May 21, 2018, 07:15:47 AM |
|
Now it runs endless and when I interrupt I got this: pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -c "info"
^CTraceback (most recent call last):
File "external/tplink.py", line 71, in <module>
sock_tcp.connect((ip, port))
File "/usr/lib/python2.7/socket.py", line 224, in meth
return getattr(self._sock,name)(*args)
KeyboardInterrupt
pi@grafpi ~/dashboard $
I meant after creating the new version of tplink2.0, could you run it and send me the output? >python external/tplink2.0.py -t 192.168.0.4 -c "info" running with new tplink code gives me this error: INFO: 2018/05/20 17:42:06 tplink.go:43: Running tplink external script!
INFO: 2018/05/20 17:42:06 rig-monitor.go:40: New rig monitor job received: rig03,claymore,label_nanopool_etc,label_nanopool,http://192.168.0.7:3333,6,29,,tplink,//192.168.0.4,750,75
INFO: 2018/05/20 17:42:06 rig-monitor.go:76: Connection to rig rig03 OK.
INFO: 2018/05/20 17:42:06 claymore.go:142: Miner(claymore) response is 12 lines long.
INFO: 2018/05/20 17:42:06 claymore.go:152: Parsing of rig rig03 output finished!
ERROR: 2018/05/20 17:42:17 tplink.go:144: Could not run tplink.py script. Failed with exit status 1
ERROR: 2018/05/20 17:42:17 tplink.go:46: TPlink script execution failed!
[/quote] Ok. Try to run this one from the command line directly: https://pastebin.com/Z42cBYkv[/quote] Great ! Seems that it works now !!! pi@grafpi ~/dashboard $ python external/tplink2.py -t 192.168.0.4 -c "info"
Sent: {"system":{"get_sysinfo":{}}}
Received: {"system":{"get_sysinfo":{"sw_ver":"1.5.2 Build 180130 Rel.085820","h w_ver":"2.0","type":"IOT.SMARTPLUGSWITCH","model":"HS110(EU)","mac":"AC:84:C6:28:FE:3B","dev_name":"Smart Wi-Fi Plug With Energy Monitoring","alias":"Miner_03", "relay_state":1,"on_time":39060,"active_mode":"none","feature":"TIM:ENE","updating":0,"icon_hash":"","rssi":-70,"led_off":0,"longitude_i":102173,"latitude_i":45 5489,"hwId":"044A516EE63C875F9458DA25C2CCC5A0","fwId":"0000000000000000000000000 0000000","deviceId":"80061172C69E621EEF611E4FEE268A5019E24312","oemId":"1998A14D AA86E4E001FD7CAF42868B5E","next_action":{"type":-1},"err_code":0}}}
pi@grafpi ~/dashboard $ python external/tplink2.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"voltage_mv":225082,"current_ma":2321,"power_mw":517381,"total_wh":5651,"err_code":0}}}
|
|
|
|
|
rodney2250 (OP)
Jr. Member
Offline
Activity: 177
Merit: 2
|
|
May 21, 2018, 11:25:03 AM |
|
Now it runs endless and when I interrupt I got this: pi@grafpi ~/dashboard $ python external/tplink.py -t 192.168.0.4 -c "info"
^CTraceback (most recent call last):
File "external/tplink.py", line 71, in <module>
sock_tcp.connect((ip, port))
File "/usr/lib/python2.7/socket.py", line 224, in meth
return getattr(self._sock,name)(*args)
KeyboardInterrupt
pi@grafpi ~/dashboard $
I meant after creating the new version of tplink2.0, could you run it and send me the output? >python external/tplink2.0.py -t 192.168.0.4 -c "info" running with new tplink code gives me this error: INFO: 2018/05/20 17:42:06 tplink.go:43: Running tplink external script!
INFO: 2018/05/20 17:42:06 rig-monitor.go:40: New rig monitor job received: rig03,claymore,label_nanopool_etc,label_nanopool,http://192.168.0.7:3333,6,29,,tplink,//192.168.0.4,750,75
INFO: 2018/05/20 17:42:06 rig-monitor.go:76: Connection to rig rig03 OK.
INFO: 2018/05/20 17:42:06 claymore.go:142: Miner(claymore) response is 12 lines long.
INFO: 2018/05/20 17:42:06 claymore.go:152: Parsing of rig rig03 output finished!
ERROR: 2018/05/20 17:42:17 tplink.go:144: Could not run tplink.py script. Failed with exit status 1
ERROR: 2018/05/20 17:42:17 tplink.go:46: TPlink script execution failed!
Ok. Try to run this one from the command line directly: https://pastebin.com/Z42cBYkv[/quote] Great ! Seems that it works now !!! pi@grafpi ~/dashboard $ python external/tplink2.py -t 192.168.0.4 -c "info"
Sent: {"system":{"get_sysinfo":{}}}
Received: {"system":{"get_sysinfo":{"sw_ver":"1.5.2 Build 180130 Rel.085820","h w_ver":"2.0","type":"IOT.SMARTPLUGSWITCH","model":"HS110(EU)","mac":"AC:84:C6:28:FE:3B","dev_name":"Smart Wi-Fi Plug With Energy Monitoring","alias":"Miner_03", "relay_state":1,"on_time":39060,"active_mode":"none","feature":"TIM:ENE","updating":0,"icon_hash":"","rssi":-70,"led_off":0,"longitude_i":102173,"latitude_i":45 5489,"hwId":"044A516EE63C875F9458DA25C2CCC5A0","fwId":"0000000000000000000000000 0000000","deviceId":"80061172C69E621EEF611E4FEE268A5019E24312","oemId":"1998A14D AA86E4E001FD7CAF42868B5E","next_action":{"type":-1},"err_code":0}}}
pi@grafpi ~/dashboard $ python external/tplink2.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"voltage_mv":225082,"current_ma":2321,"power_mw":517381,"total_wh":5651,"err_code":0}}}
[/quote] I PM'd you. The latest 2.1d14 version should fix the data insertion into influx |
|
|
|
|
tradersblog
Newbie
Offline
Activity: 12
Merit: 0
|
|
May 21, 2018, 02:37:00 PM |
|
Ok. Try to run this one from the command line directly: https://pastebin.com/Z42cBYkv[/quote] Great ! Seems that it works now !!! pi@grafpi ~/dashboard $ python external/tplink2.py -t 192.168.0.4 -c "info"
Sent: {"system":{"get_sysinfo":{}}}
Received: {"system":{"get_sysinfo":{"sw_ver":"1.5.2 Build 180130 Rel.085820","h w_ver":"2.0","type":"IOT.SMARTPLUGSWITCH","model":"HS110(EU)","mac":"AC:84:C6:28:FE:3B","dev_name":"Smart Wi-Fi Plug With Energy Monitoring","alias":"Miner_03", "relay_state":1,"on_time":39060,"active_mode":"none","feature":"TIM:ENE","updating":0,"icon_hash":"","rssi":-70,"led_off":0,"longitude_i":102173,"latitude_i":45 5489,"hwId":"044A516EE63C875F9458DA25C2CCC5A0","fwId":"0000000000000000000000000 0000000","deviceId":"80061172C69E621EEF611E4FEE268A5019E24312","oemId":"1998A14D AA86E4E001FD7CAF42868B5E","next_action":{"type":-1},"err_code":0}}}
pi@grafpi ~/dashboard $ python external/tplink2.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"voltage_mv":225082,"current_ma":2321,"power_mw":517381,"total_wh":5651,"err_code":0}}}
[/quote] I PM'd you. The latest 2.1d14 version should fix the data insertion into influx [/quote] I tried with v 2.1d14 and this are the results: 1) python file "tplink.py" works 2) grm process says : "...response from rig decoded" 3) in grafana "power_usage" is still 0 |
|
|
|
|
rodney2250 (OP)
Jr. Member
Offline
Activity: 177
Merit: 2
|
|
May 21, 2018, 02:42:18 PM |
|
Great ! Seems that it works now !!! pi@grafpi ~/dashboard $ python external/tplink2.py -t 192.168.0.4 -c "info"
Sent: {"system":{"get_sysinfo":{}}}
Received: {"system":{"get_sysinfo":{"sw_ver":"1.5.2 Build 180130 Rel.085820","h w_ver":"2.0","type":"IOT.SMARTPLUGSWITCH","model":"HS110(EU)","mac":"AC:84:C6:28:FE:3B","dev_name":"Smart Wi-Fi Plug With Energy Monitoring","alias":"Miner_03", "relay_state":1,"on_time":39060,"active_mode":"none","feature":"TIM:ENE","updating":0,"icon_hash":"","rssi":-70,"led_off":0,"longitude_i":102173,"latitude_i":45 5489,"hwId":"044A516EE63C875F9458DA25C2CCC5A0","fwId":"0000000000000000000000000 0000000","deviceId":"80061172C69E621EEF611E4FEE268A5019E24312","oemId":"1998A14D AA86E4E001FD7CAF42868B5E","next_action":{"type":-1},"err_code":0}}}
pi@grafpi ~/dashboard $ python external/tplink2.py -t 192.168.0.4 -j '{"emeter":{"get_realtime":{}}}'
Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"voltage_mv":225082,"current_ma":2321,"power_mw":517381,"total_wh":5651,"err_code":0}}}
[/quote] I PM'd you. The latest 2.1d14 version should fix the data insertion into influx [/quote] I tried with v 2.1d14 and this are the results: 1) python file "tplink.py" works 2) grm process says : "...response from rig decoded" 3) in grafana "power_usage" is still 0 [/quote] ok. I don't have a 2.0 hw version of the plug so we need to troubleshoot this on a trial and error basis ... Which OS are you using? |
|
|
|
|
iLLNiSS
Newbie
Offline
Activity: 30
Merit: 0
|
|
May 21, 2018, 03:04:26 PM |
|
Config looks ok. But didn't you say you desktop miner only had 2 GPUs? It's currently configured with 3.
Are you running the same version of PhoenixMiner on all miners?
If nothing else works then please send me a full trace together with the use config file, plus the http output of your "desktop" rig.
That was the case originally, but I've since added another card to it. Here is the html output from phoenix: https://pastebin.com/m4WEtyrRHere is the trace with JUST that desktop miner enabled (it seems as though it is the only one causing the problem. Any combination of the miners works until I reenable the desktop in the config: https://pastebin.com/Y6UkYAkZThe only difference I can make out from the output of the desktop rig versus the other miner rigs is the desktop rig has incorrect shares while the miner rigs have rejected shares. I reset the desktop miner to get fresh stats and it now runs fine. All of my miners show up in grafana and the console is error free now. So it would seem as though there is an issue somewhere with how your code handles the incorrect shares (rejected shares are different and working okay). |
|
|
|
|
rodney2250 (OP)
Jr. Member
Offline
Activity: 177
Merit: 2
|
|
May 21, 2018, 03:18:48 PM |
|
Config looks ok. But didn't you say you desktop miner only had 2 GPUs? It's currently configured with 3.
Are you running the same version of PhoenixMiner on all miners?
If nothing else works then please send me a full trace together with the use config file, plus the http output of your "desktop" rig.
That was the case originally, but I've since added another card to it. Here is the html output from phoenix: https://pastebin.com/m4WEtyrRHere is the trace with JUST that desktop miner enabled (it seems as though it is the only one causing the problem. Any combination of the miners works until I reenable the desktop in the config: https://pastebin.com/Y6UkYAkZThe only difference I can make out from the output of the desktop rig versus the other miner rigs is the desktop rig has incorrect shares while the miner rigs have rejected shares. I reset the desktop miner to get fresh stats and it now runs fine. All of my miners show up in grafana and the console is error free now. So it would seem as though there is an issue somewhere with how your code handles the incorrect shares (rejected shares are different and working okay). Got it. Now I am able to reproduce it. |
|
|
|
|
rodney2250 (OP)
Jr. Member
Offline
Activity: 177
Merit: 2
|
|
May 21, 2018, 03:38:03 PM |
|
Config looks ok. But didn't you say you desktop miner only had 2 GPUs? It's currently configured with 3.
Are you running the same version of PhoenixMiner on all miners?
If nothing else works then please send me a full trace together with the use config file, plus the http output of your "desktop" rig.
That was the case originally, but I've since added another card to it. Here is the html output from phoenix: https://pastebin.com/m4WEtyrRHere is the trace with JUST that desktop miner enabled (it seems as though it is the only one causing the problem. Any combination of the miners works until I reenable the desktop in the config: https://pastebin.com/Y6UkYAkZThe only difference I can make out from the output of the desktop rig versus the other miner rigs is the desktop rig has incorrect shares while the miner rigs have rejected shares. I reset the desktop miner to get fresh stats and it now runs fine. All of my miners show up in grafana and the console is error free now. So it would seem as though there is an issue somewhere with how your code handles the incorrect shares (rejected shares are different and working okay). Try version 2.1.d15 |
|
|
|
|
iLLNiSS
Newbie
Offline
Activity: 30
Merit: 0
|
|
May 21, 2018, 03:43:13 PM |
|
Try version 2.1.d15
Thanks! I'll respond with an update if an incorrect pops up again. |
|
|
|
|
tradersblog
Newbie
Offline
Activity: 12
Merit: 0
|
|
May 21, 2018, 07:14:46 PM |
|
I tried with v 2.1d14 and this are the results: 1) python file "tplink.py" works 2) grm process says : "...response from rig decoded" 3) in grafana "power_usage" is still 0 ok. I don't have a 2.0 hw version of the plug so we need to troubleshoot
this on a trial and error basis ...
Which OS are you using?
I'm using raspbian pi@grafpi ~ $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)" NAME="Raspbian GNU/Linux" VERSION_ID="8" VERSION="8 (jessie)" ID=raspbian ID_LIKE=debian HOME_URL=" http://www.raspbian.org/" SUPPORT_URL=" http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL=" http://www.raspbian.org/RaspbianBugs" Python 2.7.9 Is there a way to check how the script is saving the decoded info ? because the info from tplink are retrieved... We are so close! I noticed that your output of tplink.py is different from mine! Your example: You should get something like this: Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}
My output: Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"voltage_mv":221694,"current_ma":2360,"power_mw":518328,"total_wh":11976,"err_code":0}}}
names of parameters are different... |
|
|
|
|
rodney2250 (OP)
Jr. Member
Offline
Activity: 177
Merit: 2
|
|
May 21, 2018, 08:02:10 PM |
|
I tried with v 2.1d14 and this are the results: 1) python file "tplink.py" works 2) grm process says : "...response from rig decoded" 3) in grafana "power_usage" is still 0 ok. I don't have a 2.0 hw version of the plug so we need to troubleshoot
this on a trial and error basis ...
Which OS are you using?
I'm using raspbian pi@grafpi ~ $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)" NAME="Raspbian GNU/Linux" VERSION_ID="8" VERSION="8 (jessie)" ID=raspbian ID_LIKE=debian HOME_URL=" http://www.raspbian.org/" SUPPORT_URL=" http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL=" http://www.raspbian.org/RaspbianBugs" Python 2.7.9 Is there a way to check how the script is saving the decoded info ? because the info from tplink are retrieved... We are so close! I noticed that your output of tplink.py is different from mine! Your example: You should get something like this: Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}
My output: Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"voltage_mv":221694,"current_ma":2360,"power_mw":518328,"total_wh":11976,"err_code":0}}}
names of parameters are different... Yes, I had already coded that part but as I cannot test it .... Could you check test version 2.1.d14a I have added extra tracing info |
|
|
|
|
tradersblog
Newbie
Offline
Activity: 12
Merit: 0
|
|
May 21, 2018, 09:09:34 PM |
|
I tried with v 2.1d14 and this are the results: 1) python file "tplink.py" works 2) grm process says : "...response from rig decoded" 3) in grafana "power_usage" is still 0 ok. I don't have a 2.0 hw version of the plug so we need to troubleshoot
this on a trial and error basis ...
Which OS are you using?
I'm using raspbian pi@grafpi ~ $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)" NAME="Raspbian GNU/Linux" VERSION_ID="8" VERSION="8 (jessie)" ID=raspbian ID_LIKE=debian HOME_URL=" http://www.raspbian.org/" SUPPORT_URL=" http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL=" http://www.raspbian.org/RaspbianBugs" Python 2.7.9 Is there a way to check how the script is saving the decoded info ? because the info from tplink are retrieved... We are so close! I noticed that your output of tplink.py is different from mine! Your example: You should get something like this: Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}
My output: Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"voltage_mv":221694,"current_ma":2360,"power_mw":518328,"total_wh":11976,"err_code":0}}}
names of parameters are different... Yes, I had already coded that part but as I cannot test it .... Could you check test version 2.1.d14a I have added extra tracing info Still 0s in grafana, but the grm message is slightly different: INFO: 2018/05/21 21:03:01 tplink.go:39: TPlink script execution succeeded! INFO: 2018/05/21 21:03:01 tplink.go:66: TPlink smart-plug response for rig03 rig decoded! version 2.0 517792 |
|
|
|
|
rodney2250 (OP)
Jr. Member
Offline
Activity: 177
Merit: 2
|
|
May 21, 2018, 09:11:02 PM |
|
I tried with v 2.1d14 and this are the results: 1) python file "tplink.py" works 2) grm process says : "...response from rig decoded" 3) in grafana "power_usage" is still 0 ok. I don't have a 2.0 hw version of the plug so we need to troubleshoot
this on a trial and error basis ...
Which OS are you using?
I'm using raspbian pi@grafpi ~ $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)" NAME="Raspbian GNU/Linux" VERSION_ID="8" VERSION="8 (jessie)" ID=raspbian ID_LIKE=debian HOME_URL=" http://www.raspbian.org/" SUPPORT_URL=" http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL=" http://www.raspbian.org/RaspbianBugs" Python 2.7.9 Is there a way to check how the script is saving the decoded info ? because the info from tplink are retrieved... We are so close! I noticed that your output of tplink.py is different from mine! Your example: You should get something like this: Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}
My output: Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"voltage_mv":221694,"current_ma":2360,"power_mw":518328,"total_wh":11976,"err_code":0}}}
names of parameters are different... Yes, I had already coded that part but as I cannot test it .... Could you check test version 2.1.d14a I have added extra tracing info Still 0s in grafana, but the grm message is slightly different: INFO: 2018/05/21 21:03:01 tplink.go:39: TPlink script execution succeeded! INFO: 2018/05/21 21:03:01 tplink.go:66: TPlink smart-plug response for rig03 rig decoded! version 2.0 517792 OK. I am going to fix the tracing using one of my production rigs/smart plugs. Tomorrow I'll provide you another build. |
|
|
|
|
iLLNiSS
Newbie
Offline
Activity: 30
Merit: 0
|
|
May 21, 2018, 11:52:15 PM |
|
So another issue I'm finding is the program seems to quit after about an hour (longest it's ran for me is 1.5hr). The last entry is: ERROR: 2018/05/21 21:27:49 influxdb.go:39: DBDaemon could not write record batch to influxDB...
I can fire the app back up and it runs fine. Any ideas? |
|
|
|
|
rodney2250 (OP)
Jr. Member
Offline
Activity: 177
Merit: 2
|
|
May 22, 2018, 04:26:45 AM |
|
So another issue I'm finding is the program seems to quit after about an hour (longest it's ran for me is 1.5hr). The last entry is: ERROR: 2018/05/21 21:27:49 influxdb.go:39: DBDaemon could not write record batch to influxDB...
I can fire the app back up and it runs fine. Any ideas? I had that problem before. Are you running it on a laptop? Check your power settings. |
|
|
|
|
tradersblog
Newbie
Offline
Activity: 12
Merit: 0
|
|
May 22, 2018, 01:51:46 PM |
|
I tried with v 2.1d14 and this are the results: 1) python file "tplink.py" works 2) grm process says : "...response from rig decoded" 3) in grafana "power_usage" is still 0 ok. I don't have a 2.0 hw version of the plug so we need to troubleshoot
this on a trial and error basis ...
Which OS are you using?
I'm using raspbian pi@grafpi ~ $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)" NAME="Raspbian GNU/Linux" VERSION_ID="8" VERSION="8 (jessie)" ID=raspbian ID_LIKE=debian HOME_URL=" http://www.raspbian.org/" SUPPORT_URL=" http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL=" http://www.raspbian.org/RaspbianBugs" Python 2.7.9 Is there a way to check how the script is saving the decoded info ? because the info from tplink are retrieved... We are so close! I noticed that your output of tplink.py is different from mine! Your example: You should get something like this: Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}
My output: Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"voltage_mv":221694,"current_ma":2360,"power_mw":518328,"total_wh":11976,"err_code":0}}}
names of parameters are different... Yes, I had already coded that part but as I cannot test it .... Could you check test version 2.1.d14a I have added extra tracing info Still 0s in grafana, but the grm message is slightly different: INFO: 2018/05/21 21:03:01 tplink.go:39: TPlink script execution succeeded! INFO: 2018/05/21 21:03:01 tplink.go:66: TPlink smart-plug response for rig03 rig decoded! version 2.0 517792 OK. I am going to fix the tracing using one of my production rigs/smart plugs. Tomorrow I'll provide you another build. Thanks a lot! Now I got values in grafana, but I cannot understand them: 1) selecting "power_usage" mean 1m >> 258 2) selecting "power_usage" last 1m >> 362 here is my dashboard >> https://snapshot.raintank.io/dashboard/snapshot/KxLC269ZD4h3x2fxtHLEgDVkKHN4nP5Eand this is my python output: Sent: {"emeter":{"get_realtime":{}}} Received: {"emeter":{"get_realtime":{"voltage_mv":226559,"current_ma":2310,"power_mw":518346,"total_wh":21482,"err_code":0}}} 226 volts OK 518 Whats OK (4 RX 570 GPU) |
|
|
|
|
rodney2250 (OP)
Jr. Member
Offline
Activity: 177
Merit: 2
|
|
May 22, 2018, 02:11:20 PM |
|
I tried with v 2.1d14 and this are the results: 1) python file "tplink.py" works 2) grm process says : "...response from rig decoded" 3) in grafana "power_usage" is still 0 ok. I don't have a 2.0 hw version of the plug so we need to troubleshoot
this on a trial and error basis ...
Which OS are you using?
I'm using raspbian pi@grafpi ~ $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)" NAME="Raspbian GNU/Linux" VERSION_ID="8" VERSION="8 (jessie)" ID=raspbian ID_LIKE=debian HOME_URL=" http://www.raspbian.org/" SUPPORT_URL=" http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL=" http://www.raspbian.org/RaspbianBugs" Python 2.7.9 Is there a way to check how the script is saving the decoded info ? because the info from tplink are retrieved... We are so close! I noticed that your output of tplink.py is different from mine! Your example: You should get something like this: Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"current":4.879063,"voltage":222.073153,"power":1068.699166,"total":2252.117000,"err_code":0}}}
My output: Sent: {"emeter":{"get_realtime":{}}}
Received: {"emeter":{"get_realtime":{"voltage_mv":221694,"current_ma":2360,"power_mw":518328,"total_wh":11976,"err_code":0}}}
names of parameters are different... Yes, I had already coded that part but as I cannot test it .... Could you check test version 2.1.d14a I have added extra tracing info Still 0s in grafana, but the grm message is slightly different: INFO: 2018/05/21 21:03:01 tplink.go:39: TPlink script execution succeeded! INFO: 2018/05/21 21:03:01 tplink.go:66: TPlink smart-plug response for rig03 rig decoded! version 2.0 517792 OK. I am going to fix the tracing using one of my production rigs/smart plugs. Tomorrow I'll provide you another build. Thanks a lot! Now I got values in grafana, but I cannot understand them: 1) selecting "power_usage" mean 1m >> 258 2) selecting "power_usage" last 1m >> 362 here is my dashboard >> https://snapshot.raintank.io/dashboard/snapshot/KxLC269ZD4h3x2fxtHLEgDVkKHN4nP5Eand this is my python output: Sent: {"emeter":{"get_realtime":{}}} Received: {"emeter":{"get_realtime":{"voltage_mv":226559,"current_ma":2310,"power_mw":518346,"total_wh":21482,"err_code":0}}} 226 volts OK 518 Whats OK (4 RX 570 GPU) Have you check the power detail template dashboard? Are the values showed there correct? |
|
|
|
|
tradersblog
Newbie
Offline
Activity: 12
Merit: 0
|
|
May 22, 2018, 03:00:18 PM |
|
OK. I am going to fix the tracing using one of my production rigs/smart plugs. Tomorrow I'll provide you another build.
Thanks a lot! Now I got values in grafana, but I cannot understand them: 1) selecting "power_usage" mean 1m >> 258 2) selecting "power_usage" last 1m >> 362 here is my dashboard >> https://snapshot.raintank.io/dashboard/snapshot/KxLC269ZD4h3x2fxtHLEgDVkKHN4nP5Eand this is my python output: Sent: {"emeter":{"get_realtime":{}}} Received: {"emeter":{"get_realtime":{"voltage_mv":226559,"current_ma":2310,"power_mw":518346,"total_wh":21482,"err_code":0}}} 226 volts OK 518 Whats OK (4 RX 570 GPU) [/quote] Have you check the power detail template dashboard? Are the values showed there correct? [/quote] I've uploaded the txt file of the output of the influxdb query >> http://textuploader.com/dfy1ecan you create a grm developing channel in telegram ? it's more simple to communicate with frequent messages and attachements... |
|
|
|
|
rodney2250 (OP)
Jr. Member
Offline
Activity: 177
Merit: 2
|
|
May 22, 2018, 05:58:32 PM
Last edit: May 22, 2018, 06:42:58 PM by rodney2250 |
|
Hi all, I have created a telegram group for the rigmonitor community. Here's the link: https://t.me/joinchat/IuYcwBKqbGqIeXpw9sfq7Qrodneymo |
|
|
|
|
iLLNiSS
Newbie
Offline
Activity: 30
Merit: 0
|
|
May 22, 2018, 10:08:47 PM |
|
So another issue I'm finding is the program seems to quit after about an hour (longest it's ran for me is 1.5hr). The last entry is: ERROR: 2018/05/21 21:27:49 influxdb.go:39: DBDaemon could not write record batch to influxDB...
I can fire the app back up and it runs fine. Any ideas? I had that problem before. Are you running it on a laptop? Check your power settings. Nah, on an RPI. |
|
|
|
|
|
