Grott 3.0.0 now available in Alpha branche!!!!! #613
Replies: 29 comments 93 replies
-
|
new dependency |
Beta Was this translation helpful? Give feedback.
-
|
Working fine with https://github.com/muppet3000/homeassistant-grott |
Beta Was this translation helpful? Give feedback.
-
|
Hi There, working fine here. Two SPF5000es inverters. No issues whatsoever. Confirm also the sending of commands is working fine. Awesome job as usual. PS - let me know if you need any tests with "auto" and the SPF inverters. |
Beta Was this translation helpful? Give feedback.
-
|
I know it is in another thread, but just to make it clear here also, if you set |
Beta Was this translation helpful? Give feedback.
-
|
HI Johan, I Might have found a bug, but I am unsure. I have two SPF inverters and noticed one of them (the same always) sometimes the updates gets stalled for 5-6 minutes as the other is fine, reporting every 10 seconds. This never ever happened before, so I am suspecting that might be something with the new version. I have debug log, any clues of what i should search for to debug? This doesn't happens always. Since i changed versions i caught it happening twice as because i put the icon in my homeassistant to turn red in case something's wrong with the inverters. It might have happened more. Ah one more thing, it goes back and start to report without any intervention... |
Beta Was this translation helpful? Give feedback.
-
|
It happens also with the first inverter. I have restarted Grott service for the first time. Nothing strange in the log though. When it stops reporting, i have pinged the inverters and they are reachable. |
Beta Was this translation helpful? Give feedback.
-
|
If you have the log lets see if we can try to debug it. I will change my update frequentie ( now 2 minutes) to see if it also happens with my 2 inverters. Can you send the log to grott@ledidobe.nl? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @tabascoz I send some question via email but you can reply it here also. Is the inverter coming back after circa 5 minutes (300 seconds)? I have build in a mechanism that if a inverter is not sending information anymore then after (now a pre-defined) timeout, Grott will remove the connection. After that the inverter needs to reinitialize again. If this is working, then we can at least shorten the time of the stall by making this timeout configurable. At this moment I have not found the reason why your inverter stops sending or Grott stops receiving. (at least that is what I am seeing at this moment. For know I think it has to do with (network) timings, but I have to see if I can create a good test environment. Is it possible for you to change the update time (by example to 30 seconds) to see if become stable then? if we found what causes the problem we can fix it. The idea of grott 3.0.0 with adding more multithreading (a thread per inverter/datalogger) was to make things faster (make an even higher update frequency possible) and more stable. I am not convinced we already achieved this at this moment. But be aware it is the 0.0 version so there maybe some issues/challenges. |
Beta Was this translation helpful? Give feedback.
-
|
Ok lets see what happens. I am running now with the 0.1 interval for days and had now real issues with the inverter. I lost contact ones with the growatt server (running in server mode with passthrough enabled). |
Beta Was this translation helpful? Give feedback.
-
|
Hi Fernando, I have not found anything yet. To be honest it was also hard to test for me while the days with sun and working inverter were very limited and I need a "live" environment to test with (not possible in the evening). The challenge now is that with a lot of sunny days I do not seem to have a real problem. My Grott v3 stopped working only once in the last 3 weeks. I will look again at your log data and will try to replay it. But it is not an easy problem to solve. Just to be sure do your run Grott as native application or in a docker container or as add-on to Home Assistent. The good news is I now have a Raspberry Pi running HA so I am able to perform additional test for HA. |
Beta Was this translation helpful? Give feedback.
-
|
Ho Fernado, Yes that might be the problem (see also #637). I think that if there is a network instability and the connection is still there but not working properly/intermittent that can cause delays or errors in Grott. I am working on improving the connection cleanup routines (I detected that this behave different in my develop/test Windows environment then under Linux, my "production" environment). In this update cycle I will also look if I can improve the connection / thread health check that is already there to see if we can detect this delays and can cleanup/restart the connection if necessary. This is really advanced (network) programming, nice challenge! |
Beta Was this translation helpful? Give feedback.
-
|
@tabascoz are you able to change the python code? in grottserver.py there is a statement: This is the wait time before grott (grottserver) wait before it will cleanup a "dead" connection. 300 means it will wait for 5 minutes (the default update frequency). If you make this lower the connection will be closed earlier and a new connection will be created as soon the inverter will start communication. Maybe this can solve your problem. I will make this parameter configurable in the next version. |
Beta Was this translation helpful? Give feedback.
-
|
If I do netstat -ant | grep 8086 I see a lot of connections with influxdb. Most of them are in time_wait status and comming from node-red. I do not think this is a good status but it doesn't seem to be a problem. I do not have a lot connections comming from grott to influx. Is it possible that something else in your netwerk is blocking influx? I agree that the raise systemexit maybe is not the best solution if influxdb fails. I will do some additional testing on that and change it in the next release. |
Beta Was this translation helpful? Give feedback.
-
|
Oh sorry I still thought it was related to influxdb. I will upload 3.1 to the alpha branch today. I changed the connection cleanup routine totally. Maybe that fixes things. It is strange that I have no issues. But at this moment I run only with 1 inverter (but used 2 until 3 weeks ago). Just to be sure,how does your configuration looks like (#inverters, type, datalogger_type etc). What I can do if this is not working, is making the data handling part also a separate thread so it will block the normal grott (grottserver) processing flow. |
Beta Was this translation helpful? Give feedback.
-
|
Wow Fernando you pointed me to something I had forgotten. I disabled the CRC testing in Grottserver ( I do not remember when and why, probably for testing). I will enable it again. And it will give a debug message then. What I also realized that Grott/Grottserver is ignoring records that it does not recognize as Growatt records, but does not write a debug message at that moment. I changed some things and have it running it test now. If it works fine I will published it (probably tomorrow evening). It should work fine in 2.8.3 btw. It would be very strange and difficult to debug if your data is being crippled by some interfering signal. But I can tell you also some stories about my new MIN TL-XH inverter and some strange things happening there with suddenly appearing earth leaks that are hard to solve. |
Beta Was this translation helpful? Give feedback.
-
|
If possible switch to 3.1. I made a redesign of the session cleanup routine that should make Grottserver more stable. With the changes I posted today CRC checking is switched on again and I add some addition record testing The debug messages you can expect:
|
Beta Was this translation helpful? Give feedback.
-
|
inverter: 5000MTL-S grott 3.1.0 proxy mode working fine (data to mqtt is ok and data in HA) |
Beta Was this translation helpful? Give feedback.
-
|
Oke thanks. THAT make things more clearing but I think I have to log more
record information to debug.
I have to change grott for that. I will let you know when it is available
(and hope you want to test it)
Op vr 2 mei 2025, 13:05 schreef WimBra ***@***.***>:
… Can you download the version I published yesterday
just done that.
this is the debug out of the command line:
...
2025-05-02 12:59:35,095 - grottconf - INFO: Grott external record whitelist 'recwl.txt' not found
2025-05-02 12:59:35,095 - grottconf - DEBUG: - Grott records whitelisted :
{'5219', '0105', '501b', '0116', '5216', '5119', '0103', '5250', '5103',
'5129', '5229', '5150', '5016', '5050', '5005', '0120', '5116', '5004', '5104',
'5105', '5003', '0104', '0150', '5019', '0119'}
2025-05-02 12:59:35,096 - grottserver - INFO: Grottserver inititialisation started, grottserver version 3.1.0_250430
2025-05-02 12:59:35,096 - grottserver - INFO: Grott server started
2025-05-02 12:59:35,096 - grottserver - INFO: mode: server
2025-05-02 12:59:35,101 - grottserver - INFO: GrottHttpserver - Ready to listen at: 0.0.0.0:5782
2025-05-02 12:59:35,101 - grottserver - INFO: Grottserver - Ready to listen at: 0.0.0.0:5279
2025-05-02 12:59:35,102 - grottserver - INFO: GrottHttpserver - server listening
2025-05-02 12:59:35,102 - grottserver - INFO: Grottserver - server listening
2025-05-02 12:59:35,102 - grottserver - INFO: GrottHttpserver - Response interval wait time: 0.5
2025-05-02 12:59:35,103 - grottserver - INFO: GrottHttpserver - Datalogger ResponseWait: 5
2025-05-02 12:59:35,103 - grottserver - INFO: GrottHttpserver - Inverter ResponseWait: 10
2025-05-02 12:59:35,394 - grottserver - DEBUG: handle_readble_socket, input received on socket : <socket.socket fd=5, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('0.0.0.0', 5279)>
2025-05-02 12:59:35,394 - grottserver - DEBUG: handle_readable_socket, no connection with peer yet, will be established
2025-05-02 12:59:35,394 - grottserver - DEBUG: handle_new_connection, new connection request received:
<socket.socket fd=5, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('0.0.0.0', 5279)>
2025-05-02 12:59:35,395 - grottserver - DEBUG: handle_new_connection, send queue created for: 192.168.50.15_43083
2025-05-02 12:59:35,444 - grottserver - INFO: forward, connection with growatt server established: server.growatt.com:5279
2025-05-02 12:59:35,444 - grottserver - DEBUG: forward, socket: <socket.socket fd=7, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('192.168.50.42', 46160), raddr=('47.254.130.145', 5279)>
2025-05-02 12:59:35,445 - grottserver - DEBUG: [thread: forward_192.168.50.42:46160] starting
2025-05-02 12:59:35,445 - grottserver - DEBUG: [thread: client_192.168.50.15:43083] starting
2025-05-02 12:59:35,445 - grottserver - DEBUG: handle_readble_socket, input received on socket : <socket.socket fd=6, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('192.168.50.42', 5279), raddr=('192.168.50.15', 43083)>
2025-05-02 12:59:35,446 - grottserver - DEBUG: start message buffer processing
2025-05-02 12:59:35,446 - grottserver - DEBUG: Invalid Record (length) detected
2025-05-02 12:59:36,649 - grottserver - DEBUG: handle_readble_socket, input received on socket : <socket.socket fd=6, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('192.168.50.42', 5279), raddr=('192.168.50.15', 43083)>
2025-05-02 12:59:36,650 - grottserver - DEBUG: start message buffer processing
2025-05-02 12:59:36,650 - grottserver - DEBUG: Invalid Record (length) detected
2025-05-02 13:00:16,589 - grottserver - DEBUG: handle_readble_socket, input received on socket : <socket.socket fd=6, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('192.168.50.42', 5279), raddr=('192.168.50.15', 43083)>
2025-05-02 13:00:16,590 - grottserver - DEBUG: start message buffer processing
2025-05-02 13:00:16,590 - grottserver - DEBUG: Invalid Record (length) detected
2025-05-02 13:00:35,160 - grottserver - DEBUG: Main, available connections:
2025-05-02 13:00:35,167 - grottserver - DEBUG: pconn(fd=4, family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, laddr=addr(ip='0.0.0.0', port=5782), raddr=(), status='LISTEN')
2025-05-02 13:00:35,167 - grottserver - DEBUG: pconn(fd=5, family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, laddr=addr(ip='0.0.0.0', port=5279), raddr=(), status='LISTEN')
2025-05-02 13:00:35,167 - grottserver - DEBUG: pconn(fd=6, family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, laddr=addr(ip='192.168.50.42', port=5279), raddr=addr(ip='192.168.50.15', port=43083), status='ESTABLISHED')
2025-05-02 13:00:35,168 - grottserver - DEBUG: pconn(fd=7, family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, laddr=addr(ip='192.168.50.42', port=46160), raddr=addr(ip='47.254.130.145', port=5279), status='ESTABLISHED')
2025-05-02 13:00:35,168 - grottserver - DEBUG: Main, available threads:
2025-05-02 13:00:35,168 - grottserver - DEBUG: - MainThread
2025-05-02 13:00:35,169 - grottserver - DEBUG: - httpserver_0.0.0.0:5782
2025-05-02 13:00:35,169 - grottserver - DEBUG: - conserver_0.0.0.0:5279
2025-05-02 13:00:35,170 - grottserver - DEBUG: - forward_192.168.50.42:46160
2025-05-02 13:00:35,170 - grottserver - DEBUG: - client_192.168.50.15:43083
2025-05-02 13:00:36,761 - grottserver - DEBUG: handle_readble_socket, input received on socket : <socket.socket fd=6, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('192.168.50.42', 5279), raddr=('192.168.50.15', 43083)>
2025-05-02 13:00:36,762 - grottserver - DEBUG: start message buffer processing
2025-05-02 13:00:36,762 - grottserver - DEBUG: Invalid Record (length) detected
2025-05-02 13:01:16,702 - grottserver - DEBUG: handle_readble_socket, input received on socket : <socket.socket fd=6, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('192.168.50.42', 5279), raddr=('192.168.50.15', 43083)>
2025-05-02 13:01:16,703 - grottserver - DEBUG: start message buffer processing
2025-05-02 13:01:16,703 - grottserver - DEBUG: Invalid Record (length) detected
2025-05-02 13:01:35,185 - grottserver - DEBUG: Main, available connections:
2025-05-02 13:01:35,191 - grottserver - DEBUG: pconn(fd=4, family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, laddr=addr(ip='0.0.0.0', port=5782), raddr=(), status='LISTEN')
2025-05-02 13:01:35,191 - grottserver - DEBUG: pconn(fd=5, family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, laddr=addr(ip='0.0.0.0', port=5279), raddr=(), status='LISTEN')
2025-05-02 13:01:35,192 - grottserver - DEBUG: pconn(fd=6, family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, laddr=addr(ip='192.168.50.42', port=5279), raddr=addr(ip='192.168.50.15', port=43083), status='ESTABLISHED')
2025-05-02 13:01:35,192 - grottserver - DEBUG: pconn(fd=7, family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, laddr=addr(ip='192.168.50.42', port=46160), raddr=addr(ip='47.254.130.145', port=5279), status='ESTABLISHED')
2025-05-02 13:01:35,193 - grottserver - DEBUG: Main, available threads:
2025-05-02 13:01:35,193 - grottserver - DEBUG: - MainThread
2025-05-02 13:01:35,193 - grottserver - DEBUG: - httpserver_0.0.0.0:5782
2025-05-02 13:01:35,194 - grottserver - DEBUG: - conserver_0.0.0.0:5279
2025-05-02 13:01:35,194 - grottserver - DEBUG: - forward_192.168.50.42:46160
2025-05-02 13:01:35,195 - grottserver - DEBUG: - client_192.168.50.15:43083
2025-05-02 13:01:36,874 - grottserver - DEBUG: handle_readble_socket, input received on socket : <socket.socket fd=6, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('192.168.50.42', 5279), raddr=('192.168.50.15', 43083)>
2025-05-02 13:01:36,875 - grottserver - DEBUG: start message buffer processing
2025-05-02 13:01:36,875 - grottserver - DEBUG: Invalid Record (length) detected
—
Reply to this email directly, view it on GitHub
<#613 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD56LCWNUJA3N6Z3V42CDKT24NGPDAVCNFSM6AAAAABTHFCXWWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMBRGMYDGOA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hi Fernando did you sent the log? I have not received it yet (I think).
Op vr 2 mei 2025, 12:35 schreef Fernando Cunha ***@***.***>:
… I increased the log to DEBUGV and will send you the new file. Here's
another catch i think may be relevant
mai 02 11:32:33 note grott[277693]: 2025-05-02 11:32:33,582 - grottserver - WARNING: handle_readble_socket, empty read, close connection
mai 02 11:32:33 note grott[277693]: 2025-05-02 11:32:33,582 - grottserver - DEBUG: Close Connection for socket: <socket.socket fd=9, family=2, type=1, proto=0, laddr=('192.168.51.103', 5279), raddr=('192.168.51.103', 47976)>
mai 02 11:32:33 note grott[277693]: 2025-05-02 11:32:33,582 - grottserver - DEBUGV: retrieve connection information
mai 02 11:32:33 note grott[277693]: 2025-05-02 11:32:33,582 - grottserver - DEBUG: Close Connection for socket: <socket.socket fd=9, family=2, type=1, proto=0, laddr=('192.168.51.103', 5279), raddr=('192.168.51.103', 47976)>
mai 02 11:32:33 note grott[277693]: 2025-05-02 11:32:33,582 - grottserver - DEBUGV: clean connection queues
mai 02 11:32:33 note grott[277693]: 2025-05-02 11:32:33,582 - grottserver - DEBUGV: clean Passthrough connection queues
mai 02 11:32:33 note grott[277693]: 2025-05-02 11:32:33,582 - grottserver - DEBUGV: clean connection queues error: cannot access local variable 'pt_qname' where it is not associated with a value
mai 02 11:32:33 note grott[277693]: 2025-05-02 11:32:33,582 - grottserver - WARNING: handle_readble_socket, ConnectionResetError exception: cannot access local variable 'pt_socket' where it is not associated with a value
mai 02 11:32:33 note grott[277693]: 2025-05-02 11:32:33,582 - grottserver - DEBUG: Close Connection for socket: <socket.socket [closed] fd=-1, family=2, type=1, proto=0>
mai 02 11:32:33 note grott[277693]: 2025-05-02 11:32:33,582 - grottserver - DEBUGV: retrieve connection information
mai 02 11:32:33 note grott[277693]: 2025-05-02 11:32:33,582 - grottserver - DEBUG: Close Connection for socket: <socket.socket [closed] fd=-1, family=2, type=1, proto=0>
mai 02 11:32:33 note grott[277693]: 2025-05-02 11:32:33,582 - grottserver - DEBUGV: clean connection queues
mai 02 11:32:33 note grott[277693]: 2025-05-02 11:32:33,582 - grottserver - DEBUGV: clean connection queues error: cannot access local variable 'qname' where it is not associated with a value
mai 02 11:32:33 note grott[277693]: 2025-05-02 11:32:33,583 - grottserver - DEBUGV: clean Passthrough connection queues
mai 02 11:32:33 note grott[277693]: 2025-05-02 11:32:33,583 - grottserver - DEBUGV: clean connection queues error: cannot access local variable 'pt_qname' where it is not associated with a value
mai 02 11:32:33 note grott[277693]: 2025-05-02 11:32:33,583 - grottserver - WARNING: handle_readble_socket, generic exception: cannot access local variable 'pt_socket' where it is not associated with a value
—
Reply to this email directly, view it on GitHub
<#613 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD56LCSYYQN327ZB5HFH3OD24NC6XAVCNFSM6AAAAABTHFCXWWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMBRGI3TSNA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I swapped from beta 2.8.3 to the new alpha version : 3.1.0_20250406 both stand alone installs directly on Linux. Only tried the proxy mode for Alpha so far as I noticed that my energy dashboard in HA was not updating energy used from the battery or energy to the battery. I have tracked it down to differences between versions, see below: Stable and Beta versions: etouser_tod Alpha versions: etousertod FYI I am using a SPH inverter and have swapped back to the beta 2.8.3 for now. Were these changes intended? |
Beta Was this translation helpful? Give feedback.
-
|
@johanmeijer think i got it ! ;) I started debugging all functions, from handle_readable_socket(), process_data() and finally procdata() and I found myself back to influxdb issue. I enabled more debugging and found that the influxdb code was never active when the issue happened. Sometimes MQTT publish.single gets stalled, doesn't return any errors and cause Grott to stop responding for that socket. The timeout routine takes care about it but it stays with close_wait for a great time and they pile up with time. I was not able to destroy the sockets, that would fix the issue. Maybe because the thread is hang waiting for the mqtt publish function to return. I'm trying now to create a threaded call with 1sec timeout and will post the results as soon as I do some more testing. BTW it was a great opportunity for me to learn python and now i think i understand like 15% of your code. Great work Johan! Glad to contribute to a project i've been using for so long Cheers |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your hard work, @johanmeijer. For anyone interested, I’ve created a Docker image for the Alpha branch of Grott. Below is the And here’s a basic Note: You must mount the Also, as previously mentioned by @donaldwpage: |
Beta Was this translation helpful? Give feedback.
-
|
@johanmeijer wanted to provide some feedback. I fired up @egguy alpha channel home-assistant add-on that includes Grott3.0.0. Working great in server mode! SPH5000 here, with SDM630 smart meter. Single phase inverter, three phase meter. Could never get the 2nd and 3rd phase information before but magically started working with the upgrade. Was able to set my interval register (and get it to stick) now and super happy with 1minute interval vs the old 5min. Massive thankyou to @egguy and @johanmeijer for your combined efforts. |
Beta Was this translation helpful? Give feedback.
-
|
Currently testing Alpha 3.x to my Growatt 5000UE. Grott 2.7.8 was working fine, but in Grottserver Alpha i get nothing but invalid record length detected. Sample of the plain data from grott 2.7.8 at the bottom Sample og plain data captured from grott 2.7.8: |
Beta Was this translation helpful? Give feedback.
-
|
@pw-h So it works in proxy mode, not in server mode. Luckily we now have data to test with from the proxy run. I activated the record checking in grottserver again (it was always on in grottproxy) but it does not seem to work well for voor type 02 records. This is an older record format that does not have CRC checking, different from the one I have, but that is ok it should work, Grott should not perform CRC checking. If you specify auto. The record layout is build by Grott (based on the register information in the record). It will ignore the T02NNNN.json layout (to be more specific all Txxxxx.json layouts). I am going to test (and hopefully fix) it. |
Beta Was this translation helpful? Give feedback.
-
|
@pw-h it should be fixed in version 3.2.1 |
Beta Was this translation helpful? Give feedback.
-
|
I cannot get api calls to work. http://10.0.0.80:5782/inverter gives me: but http://10.0.0.80:5782/inverter?command=regall&inverterid=02 gives me I don't know what to enter for 'inverterid' , "AH24030766" and "RX04020003" don't work either. |
Beta Was this translation helpful? Give feedback.
-
|
Been a while since something happened here. Have plans changed? |
Beta Was this translation helpful? Give feedback.
-
|
Ok I am here (again!?). Last months I have not been able to do a lot with Grott because of other priorities (rebuilding 3 houses ;) ). I have to say for me there was no urgent reason while I am running V3 now for a couple of months with no problems (min 3600TL-XH with ARK batteries). I am planning to start developing / problem solving again the coming weeks with V3 as basis. For me priority is to set battery load priorities so I can make optimal use of the configuration and keeping costs in control. For me this has no real priority while in the Netherlands we have some special rules for netting used against delivered KWH. But this will end in 2027 and my contract with my current fixed contract with VattenFall will end mid 2026 (two moments I have to take into account). I will start with looking at the issues and after that I will try to build a smart control mode in Grott. |
Beta Was this translation helpful? Give feedback.



Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The new 3.0.0 version of grott is available in the alpha branche (under development!!!)
What is new in 3.0.0
How to use:
If you do not change grott.ini Grott and grottserver can be used in the same way as in previous releases (backwards compatible) !
But....
You have to install PSUTIL package:
New options at startup:
loglevel is python loglevel, see below which are available
option -v will still work and is equal to -l debug
New settings in grott.ini:
[Generic]
Specify mode (sniff/proxy/server/serversa)
New section added to define grottserver settings (works also in grottserver standalone)
[Server]
advanced settings only for debug or advanced tuning!!!!!
Beta Was this translation helpful? Give feedback.
All reactions