I already spent many hours trying to reproduce your issues back in januari. Unfortunately I could not, so I am unable to offer any new insights. Maybe someone with a comparable setup can help? Btw: i would not consider replacing the plugin directory a “clean install”. The files in the plug-in dir ...

Update: deleted everything in the iDetect folder, reinstalled the Beta without the logging on in the iDetect sheet, all ok again with 192.168.2.1#type=aimesh_json I don't get it ........ This is how the install must go, but why then the installs with the errors? If you switch back and forth between ...

I changed my router to Asus XT8. I'm still running into issues using type=aimesh_json. It used to be fool-proof, not so much anymore. Thats why I was wondering about the Beta The beta uses the newer DomoticzEx framework to manage the Domoticz devices. There have also been some structural changes ...

Is there any planning for the beta to be released? we are not running domoticz to control nuclear power plants ;) My wife and kids think otherwise, when it does not work, it's 'rubbish' and they don't want to have it in their house. So like a nuclair plant, it has to work all the time, or we get a ...

Is there any planning for the beta to be released? I have been testing it for a while because it looked like something was causing a memory leak. However, on my setup the Domoticz memory usage indeed rises the first few days but then stabilizes. I don't know if there is any relation with the plugin ...

Looks like your Fritzbox is not allowing the login at these times. iDetect doesn’t do anything different around 22:00, so I would look at the Fritzbox configuration. Any maintancance (update) jobs on the Fritzbox at 22:00? Maybe some timed blocking rules?

After looking at a more detailed debug log I noticed that (at least in the log) the onconnect sent content is different when you select xlm of http as the protocol (other protocols I tested look the same as the xml protocol below, so it is the http that is different from the rest). When configuring ...

I am trying to write a plugin that reads the XML alertstream of a Hikvision security camera and I want to use the connection object offered by the plugin framework to do so. I know how to solve this using requests, but I want to see if plugins behave better if they avoid using additional modules ...

The error returned, after quite a number of time restarting and trouble shooting of another error. I then simply deleted the iDetect and reinstalled the app and it is running again without error. And it all worked again. That is what I call strange. Very strange indeed. Nothing is stored or changed ...

I reset everything by deleting the previous iDetect and installing it with: sudo git clone -b DomoticzEx-based-beta https://github.com/d-EScape/Domoticz_iDetect.git iDetect guess what, no errors ......... and I see that the frequency of logging with all the data from the router has increased to ...

I increased the timeout in ssh_tracker from 5 --> 10 and 3 --> 6. def getfromssh(self, tracker_cli, alltimeout=10, sshtimeout=6): Same result: 2024-01-30 09:44:42.269 IDetect: 192.168.2.1 Timed poll starting like clockwork. 2 threads active (including me) 2024-01-30 09:44:42.269 IDetect: 192.168.2 ...

Where can I find the timeout? They are hard coded in ssh_tracker.py. Just search for timeout in the file. Have you tried if resetting the nuc has a different effect than only restarting Domoticz? Since the plug-in first worked and failed after a Domoticz restart, it might be a clue if that is ...

After a restart the error is coming again. It is functioning properly. 2024-01-29 11:33:11.884 IDetect: 192.168.2.1 ====> SSH tried for 12 milliseconds. 2024-01-29 11:33:11.884 IDetect: 192.168.2.1 Could not be polled 2024-01-29 11:33:11.884 Status: IDetect: 192.168.2.1 ====> SSH resetting ...

Did you do the python test from the command line of the nuc or from within the running docker container? The docker container is a separate environment, so the test will tell you nothing if you only run it from the normal cli. To get a shell in the running docker container you first need to get the ...

I tried running the beta again .... and it worked after deleting the previous devices. It is working: only with the logging on! and it still gets "Error: IDetect: 192.168.2.1 ====> SSH failed with exception: Timeout opening channel." Strange that it would work with those error messages. Are you ...

Sorry, my test results were with the beta. I just retested with the 2.4 version, password based authentication and tracker config: "192.168.2.1#type=aimesh_json". Still works. As expected, since the beta is also back to using paramiko. Switching between versions 2.4 and 2.5(the beta) should not lead ...

Thanks for sharing the log in pm. It shows two errors, but only one is relevant. As far as I can tell we can ignore this IndexError, because it seems te be an error in the paramiko error handling. Comparable to (or even the same as) https://github.com/paramiko/paramiko/issues/20 During handling of ...

1. "with the tracker 192.168.2.1#ssh=brcrl" So ssh is working! That is promising. It is returning an error message from the routers cli. That's because you just told it to run the command brctl without any command line arguments. "192.168.2.1#type=brctl" might have worked. Did you restart Domoticz ...

IDetect: 192.168.2.1 ====> SSH failed with exception: Timeout opening channel The only thing I can tell from this one line of information is that it does not look like authentication is the issue here. There seems te be no connection between Domoticz and the router. This is not related to the ...

Yes, build 15836 and in settings I have accept new hardware devices enabled. I can disable and enable? Just tried it same errors .... And why is the enable for 5 minutes red ..... also tried it, pressed allow for 5 minutes and did an update, same errors. I did run the Beta .... deleted it and ...