jerrythafast / se-logger Goto Github PK

One of my optimisers died and I got a replacement, however after installing the new optimizer, the data of this optimizer is no longer recognized by se-logger. After some debugging, I found that this new optimizer generates messages of a different type.
My old optimizers use type 0x0080 (length 13), but this new optimizer uses type 0x0082 (length 15).
Can you add support for this new type?
As far as I can see the data format for the first 13 bytes is compatible with type 0x0080. I don't know what the extra 2 bytes are for.

Hi!

I’m having trouble extracting the key from my SolarEdge inverter. When I run the code it comes up with a Syntax error on the inverter ID. I have uses all possible inverter ID’s but can’t get it to work.

I'm having some trouble to migrate se-logger to a new Debian version.
It is working fine on Debian 9.13 (stretch)
With python 2.7.13
Se-logger version is 0.10

My new Debian version is 11 (bullseye)
With Python 3.9.2
And se-logger version 0.17 (the latest)

The problem is that the package 'python3-crypto' does not exist anymore.

Package python3-crypto is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'python3-crypto' has no installation candidate

Do you have a solution for this?

Dag Jerrythefast,
U heeft te maken met een complete noob op gebied van programmeren.
In uw config.sample.py heeft u het over deze te kopiëren naar config.py...
Nu de domme vraag, waar moet ik deze dan heen kopiëren/plaatsen?
Ik loop hier vast op.
Met zoeken kom ik diverse van deze op mijn raspberry tegen.
Ik draai nu Raspbian.

BVD
WIm

Any plans to port to 3?

As noted here, the tcpdump binary may be located in different places. A possible solution is provided in the next message in that thread, by doing this:

TCPDUMP=`whereis -b tcpdump | awk '{print $2}'` if [[ -z "$TCPDUMP" ]]; then echo "tcpdump not found" exit 1 fi

Loop tegen het volgend probleem aan.
Traceback (most recent call last):
File "/opt/se-logger/liveupdate.py", line 24, in
import struct, sys, MySQLdb, time
ModuleNotFoundError: No module named 'MySQLdb'

Na heel wat zoeken blijkt dat MySQLdb niet door python 3... word ondersteund. Is dat ook zo?

Ik gebruik versie 0.0.15

Wim

It seems that my inverter creates inverter messages of length 266, which results in these messages being ignored by the parser.
if I replace this line:
elif type == 0x0011 and length in (200, 264): # 3ph inverter
by this one:
elif type == 0x0011 and length in (200, 264, 266): # 3ph inverter
parsing seems to work again.

Hi Jerrythafast,

An update for pvoutput, because it accepts

• no data older then 14 days
• no more then 30 lines max

$q = $db->query(
'SELECT timestamp, p_active, temperature, v_ac, se_day ' .
'FROM (' .
'SELECT ' .
'timestamp, p_active, temperature, v_ac, ' .
'@curdate := FROM_UNIXTIME(timestamp, "%Y%m%d") date, ' .
'@prevsum := IF(@prevdate = @curdate, @prevsum + de_day, de_day) se_day, ' .
'@prevdate := @curdate date2 ' .
'FROM telemetry_inverter ' .
'JOIN (SELECT @prevsum := 0, @curdate := NULL, @prevdate := NULL) vars ' .
'WHERE timestamp >= (SELECT IFNULL(UNIX_TIMESTAMP(FROM_UNIXTIME(pvo_last_live, "%Y%m%d")), 0) FROM live_update) ' .
'ORDER BY timestamp' .
') x ' .
'WHERE timestamp > (SELECT pvo_last_live FROM live_update) AND timestamp > UNIX_TIMESTAMP(now() - INTERVAL 14 DAY) ' .
'LIMIT 30');