-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
60 devices - TDM extremely slow - not usable #185
Comments
Finally, someone with a lot of hardware :) First of all, TasmoAdmin works in a completely different manner connection-wise. Also TDM pulls (and internally updates) much more stuff from Tasmota. Are you able to prepare the venv for TDM and run some debug/tests for me from console? |
Sure can. Just guide me through the process as I'm not familiar with the console (unless you are talking about the Tasmota console) . Fyi I am running Windows 10. Thx |
Had to create a few custom bins so I have a number of tools already installed (IOplatform, VB, etc.) But not an expert so will need some guidance. |
@homeseer666 Do you already have a Python interpreter on your computer ? @jziolkowski If you don't have a Windows computer handy, I can do it : VENV Python 3.8 + latest TDM source tree ? |
Python 3.10.2 installed, had to use it for esptool.py/ PYFlasher. |
@barbudor please provide the zip, that would make it easier. TIA |
@homeseer666 As per @jziolkowski suggestion, please find here a lkink to download a ZIP with latest TDM source + minimum Python env Thanks |
Sounds good, should have time later this evening or tomorrow, will report back. Thx |
All set. (venv) C:\xxxxxxxxxxxxxxxx\tdm_venv>python tdm.py |
my bad, it's |
Originally thought this was the problem but it was also returning an error.... (venv) C:\xxxxxxxxxxxxxx\tdm_venv>python tdmgr.py |
Strange. I just deleted my original tdm_env folder, restored from the zip and it works |
@homeseer666 did you activate the venv? |
the |
yes I did , (venv) marker is there. |
I have/had the same problem. I needed to change the code a little because I am not using %prefix% at all in any of my 42 tasmota devices. Due to the changes TDM subscibed to '#' 42 times. This seems to start 42 times a request with each receiving mqtt entry. First I try-ed to fix it by removing duplicate entry's in the mqtt queue and the lwts list. I was hitting over 100.000 entry's in the mqtt queue. Now I hard coded subscribe to just '#' only ones. That seems to work for me but sometimes it still get's very slow. btw, I love your program!! |
Can you show me a line from debug that can back the claim that it subbed to "#" 40 times? |
2022-02-17 17:05:57 [INFO] ### TDM START ### My devices look like (only showing 2): [5C-CF-7F-2C-19-AC] [A0-20-A6-26-74-DD] So they only have %topic% and no %prefix% |
Which is totally wrong |
also pls paste your discovery topics |
Remember I changed some code in order to make the program work without the %prefix%. Discovery topics: %topic%/%prefix% Changes:
|
You removed the whole logic behind finding duplicate topics. That's why there are duplicated subscriptions. |
I did that after I found out that there were duplicate topics. I just wanted to say that if you have duplicated topics the program gets very slow. |
Well, duh :) |
:-) No problem, you are more then welcome. |
Back to my original request; still interested to troubleshoot ? |
HI @homeseer666 |
still at the same place, getting this error when runnning tdmgr.py: (venv) C:\Users\xxx\Downloads\tdm_venv>python tdmgr.py |
While in the venv, can you please try to re-install dependencies: |
It's in the project wiki |
ok let me check |
Ok got it. Do you have a personal account I can send this to? lots of details in there. |
let's start with the basics now. autodiscovery patterns and log entries related to subscription topics |
Here's the output from the last startup: 2022-03-04 16:52:29 [INFO] ### TDM START ### |
I deleted the original user/TDM folder in order to get the base config/data from scratch; here it is. 2022-03-05 13:14:35 [INFO] ### TDM START ### |
Just my 2 cents: I figured out this project does not run with Python 3.10 on Windows. Also experienced some of the above errors while installing requirements but ultimately also failing to run the application. Works fine with Python 3.9.12 on Windows 10 except for the PyQt5 version issue. Seems 5.14.2 is only binary-compatible with older Python versions, see this Stackoverflow discussion |
I removed the fix of using 5.14.2 The packages have been updated and latest versions do work in general with less issues now. |
Is there a new release to test these changes ? don't see anything new on Github, thx. |
No, this only relevant when you use the Python version. The compiled versions are working. |
Anything planned to fix the slowness/freezing issues described above in Windows ? |
@homeseer666 I recognize your username from discord. Please contact me directly, we need to set up a live session for that |
@homeseer666 it's been ages but I've gotten back to development. I've fixed this issue in the current development branch. Just be aware that this version stores config in new location and I didn't make a migration mechanism. The config is saved in ~/.config/tdm/tdm.ini on Mac/Linux, and <USER_DIR>\AppData\Roaming\tdm\tdm.ini on Windows |
Thanks, will try to test and report back. |
Happy to see you back @jziolkowski 😄 About configuration, a way to switch between different configurations would be nice, like specifiying an alternate config file or config folder on the command line would be nice. |
@barbudor let's move it to separate discussion |
Just to be clear, I see release 0.2.13 updated 6 days ago; should I test this the one ? |
the change is in the develop branch. can you pull and run it? if not, I can compile an .exe from development |
I already have a working uncompiled version from last summer which I manually run from a venv; |
https://github.com/jziolkowski/tdm/actions/runs/3670837944 at the very bottom there is a zipped file including all builds of the latest develop. Please give it a shot. Notice: TDM stores config file in a different place now. At windows it's |
Thanks, much appreciated, will test and report back, cheers |
Works! Thank you |
BTW just something for the wishlist : abilty to add custom columns to the main screen/device list ex: recently had to manually change teleperiod,wattres,ampres,voltres and energyres on a number of energy monitoring devices, this would have proven useful to target the correct devices and push the change to the right ones. Thx again! |
So glad to hear!
I started working on supporting native tasmota discovery, it's blazing fast.
Please give it a try while I'll think of a way to make it configurable in GUI... https://github.com/jziolkowski/tdm/wiki/View-mode-customization
I'll add this to the roadmap |
However, in the latest develop version there is a change in where the config files are located On Linux/Unix it's |
The columns are added but not populated, am I missing something? Thanks [Views] |
just a quick follow up on the above as it would be very useful; [Views] |
Closing this one as adding custom columns is overlapping with #242. The original issue was fixed. |
I have about 60 active Tasmota devices;
TDM works but seems to be in a perpetual scanning/discovery state, making the app unusable;
App starts populating fields, then hangs, doesn't respond for several minutes, then back for a second or two.
Can't click menus or takes forever to respond, etc.
I've tried playing around with all parameters, disabled telemetry, etc.
I also installed TasmoAdmin, and it works smoothly so really seems to be app related;
I'd prefer the TDM interface if I manage to get it working.
Let me know what you think and how I should troubleshoot this,
Thanks!
The text was updated successfully, but these errors were encountered: