jvdz wrote: ↑Saturday 02 January 2021 11:30
Did you also check the contents of dtg.log.errors as I expect the lua script has errors?
Hmm it seems like there are a few errors...
/usr/bin/lua5.2: error loading module 'ssl.core' from file '/usr/local/lib/lua/5.2/ssl.so':
libssl.so.1.0.0: cannot open shared object file: No such file or directory
stack traceback:
[C]: in ?
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl.lua:7: in main chunk
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl/https.lua:10: in main chunk
[C]: in function 'require'
/home/pi/dtgbot/dtgbot.lua:132: in main chunk
[C]: in ?
/usr/bin/lua5.2: error loading module 'ssl.core' from file '/usr/local/lib/lua/5.2/ssl.so':
libssl.so.1.0.0: cannot open shared object file: No such file or directory
stack traceback:
[C]: in ?
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl.lua:7: in main chunk
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl/https.lua:10: in main chunk
[C]: in function 'require'
/home/pi/dtgbot/dtgbot.lua:132: in main chunk
[C]: in ?
/usr/bin/lua5.2: error loading module 'ssl.core' from file '/usr/local/lib/lua/5.2/ssl.so':
libssl.so.1.0.0: cannot open shared object file: No such file or directory
stack traceback:
[C]: in ?
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl.lua:7: in main chunk
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl/https.lua:10: in main chunk
[C]: in function 'require'
/home/pi/dtgbot/dtgbot.lua:132: in main chunk
[C]: in ?
/usr/bin/lua5.2: error loading module 'ssl.core' from file '/usr/local/lib/lua/5.2/ssl.so':
libssl.so.1.0.0: cannot open shared object file: No such file or directory
stack traceback:
[C]: in ?
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl.lua:7: in main chunk
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl/https.lua:10: in main chunk
[C]: in function 'require'
/home/pi/dtgbot/dtgbot.lua:132: in main chunk
[C]: in ?
/usr/bin/lua5.2: error loading module 'ssl.core' from file '/usr/local/lib/lua/5.2/ssl.so':
pi@Domoticz:~ $ sudo apt install lua-socket
Reading package lists... Done
Building dependency tree
Reading state information... Done
lua-socket is already the newest version (3.0~rc1+git+ac3201d-4).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
/usr/bin/lua5.2: error loading module 'ssl.core' from file '/usr/local/lib/lua/5.2/ssl.so':
libssl.so.1.0.0: cannot open shared object file: No such file or directory
stack traceback:
[C]: in ?
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl.lua:7: in main chunk
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl/https.lua:10: in main chunk
[C]: in function 'require'
/home/pi/dtgbot/dtgbot.lua:132: in main chunk
[C]: in ?
/usr/bin/lua5.2: error loading module 'ssl.core' from file '/usr/local/lib/lua/5.2/ssl.so':
libssl.so.1.0.0: cannot open shared object file: No such file or directory
stack traceback:
[C]: in ?
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl.lua:7: in main chunk
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl/https.lua:10: in main chunk
[C]: in function 'require'
/home/pi/dtgbot/dtgbot.lua:132: in main chunk
[C]: in ?
/usr/bin/lua5.2: error loading module 'ssl.core' from file '/usr/local/lib/lua/5.2/ssl.so':
libssl.so.1.0.0: cannot open shared object file: No such file or directory
stack traceback:
[C]: in ?
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl.lua:7: in main chunk
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl/https.lua:10: in main chunk
[C]: in function 'require'
/home/pi/dtgbot/dtgbot.lua:132: in main chunk
[C]: in ?
/usr/bin/lua5.2: error loading module 'ssl.core' from file '/usr/local/lib/lua/5.2/ssl.so':
libssl.so.1.0.0: cannot open shared object file: No such file or directory
stack traceback:
[C]: in ?
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl.lua:7: in main chunk
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl/https.lua:10: in main chunk
[C]: in function 'require'
/home/pi/dtgbot/dtgbot.lua:132: in main chunk
[C]: in ?
/usr/bin/lua5.2: error loading module 'ssl.core' from file '/usr/local/lib/lua/5.2/ssl.so':
I guess you also installed the "old" version as defined in the Wiki to "/usr/local/lib/lua/5.2/"?
Could you remove that version as it seems to use that.
jvdz wrote: ↑Saturday 02 January 2021 13:34
I guess you also installed the "old" version as defined in the Wiki to "/usr/local/lib/lua/5.2/"?
Could you remove that version as it seems to use that.
Cant seem to remove it (using sudo rm) but is denied...
jvdz wrote: ↑Saturday 02 January 2021 13:34
I guess you also installed the "old" version as defined in the Wiki to "/usr/local/lib/lua/5.2/"?
Could you remove that version as it seems to use that.
Cant seem to remove it (using sudo rm) but is denied...
This is harder than I thought.....
I've removed the folder and installed it back but same errors..
jvdz wrote: ↑Saturday 02 January 2021 18:25
Your shouldn't be getting this error anymore:
from file '/usr/local/lib/lua/5.2/ssl.so'. ?
Still getting the next errors.
When I go to /usr/local/lib/lua/5.2/ the file ssl.so is there and in the map socket there's the file ssl.core.
/usr/bin/lua5.2: error loading module 'ssl.core' from file '/usr/local/lib/lua/5.2/ssl.so':
libssl.so.1.0.0: cannot open shared object file: No such file or directory
stack traceback:
[C]: in ?
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl.lua:7: in main chunk
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl/https.lua:10: in main chunk
[C]: in function 'require'
/home/pi/dtgbot/dtgbot.lua:132: in main chunk
[C]: in ?
/usr/bin/lua5.2: error loading module 'ssl.core' from file '/usr/local/lib/lua/5.2/ssl.so':
libssl.so.1.0.0: cannot open shared object file: No such file or directory
stack traceback:
[C]: in ?
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl.lua:7: in main chunk
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl/https.lua:10: in main chunk
[C]: in function 'require'
/home/pi/dtgbot/dtgbot.lua:132: in main chunk
[C]: in ?
jvdz wrote: ↑Sunday 03 January 2021 11:01
I thought you had removed these files you installed manually: '/usr/local/lib/lua/5.2/ssl.so' ?
It seems they are still there?
My bad.. thought the file was corrupted so removed it and installed a fresh copy..
Should I also delete the ssl.core?
/usr/bin/lua5.2: /usr/local/share/lua/5.2/ssl.lua:7: module 'ssl.core' not found:
no field package.preload['ssl.core']
no file '/usr/local/share/lua/5.2/ssl/core.lua'
no file '/usr/local/share/lua/5.2/ssl/core/init.lua'
no file '/usr/local/lib/lua/5.2/ssl/core.lua'
no file '/usr/local/lib/lua/5.2/ssl/core/init.lua'
no file '/usr/share/lua/5.2/ssl/core.lua'
no file '/usr/share/lua/5.2/ssl/core/init.lua'
no file './ssl/core.lua'
no file '/usr/local/lib/lua/5.2/ssl/core.so'
no file '/usr/lib/arm-linux-gnueabihf/lua/5.2/ssl/core.so'
no file '/usr/lib/lua/5.2/ssl/core.so'
no file '/usr/local/lib/lua/5.2/loadall.so'
no file './ssl/core.so'
no file '/usr/local/lib/lua/5.2/ssl.so'
no file '/usr/lib/arm-linux-gnueabihf/lua/5.2/ssl.so'
no file '/usr/lib/lua/5.2/ssl.so'
no file '/usr/local/lib/lua/5.2/loadall.so'
no file './ssl.so'
stack traceback:
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl.lua:7: in main chunk
[C]: in function 'require'
/usr/local/share/lua/5.2/ssl/https.lua:10: in main chunk
[C]: in function 'require'
/home/pi/dtgbot/dtgbot.lua:132: in main chunk
[C]: in ?
pi@domo:/var/tmp $ cat dtb.log.errors
/usr/bin/lua5.2: error loading module 'ssl.core' from file '/usr/local/lib/lua/5.2/ssl.so':
libssl.so.1.0.0: cannot open shared object file: No such file or directory
I found on this long thread a person that solved the issue by removing the lua folder in /usr/local/lib & /usr/local/shared & installed the LUA lib
I think this a dtgbot problem.
When I send the command "systemstatus" I get the responses I im looking for, but then I get another reply that I do not want to see.
How do I stop Recieved Message 3...
pi@domo:/var/tmp $ cat dtb.log.errors
/usr/bin/lua5.2: error loading module 'ssl.core' from file '/usr/local/lib/lua/5.2/ssl.so':
libssl.so.1.0.0: cannot open shared object file: No such file or directory
I found on this long thread a person that solved the issue by removing the lua folder in /usr/local/lib & /usr/local/shared & installed the LUA lib
Welsyntoffie wrote: ↑Tuesday 27 July 2021 16:41
I think this a dtgbot problem.
When I send the command "systemstatus" I get the responses I im looking for, but then I get another reply that I do not want to see.
How do I stop Recieved Message 3...
Have you made changes to the bash file systemstatus.sh in directory dtgbot/bash ?
You can also check the file SystemStatus.txt in the defined $TempFileDir in the setup file to see what the text was at the time the Telegram was send.
jvdz wrote: ↑Tuesday 27 July 2021 19:13
Have you made changes to the bash file systemstatus.sh in directory dtgbot/bash ?
You can also check the file SystemStatus.txt in the defined $TempFileDir in the setup file to see what the text was at the time the Telegram was send.
I only changed the rid in systemstatus.sh.
Even before I changed the id's I received the 3rd message, for that reason I thought is was because it could not find the id's
temperature.sh is Unmodified and also gives me a 3rd unwanted message
The text file is normal, there is nothing else inside the text file...
-CPU temperature: 37°C
-CPU Usage: 8.06 %
-Memory Usage: 35.06 %
-UpTime: 19.67 h
-Domoticz update available! (version 13191)
Well it looks like a part of the response from the CURL command if send in a reply, but don't understand why that would happen.
As you can see in the BASH file: It sends the content of the text file with a curl command to your TelegramID.
jvdz wrote: ↑Tuesday 27 July 2021 20:49
Well it looks like a part of the response from the CURL command if send in a reply, but don't understand why that would happen.
As you can see in the BASH file: It sends the content of the text file with a curl command to your TelegramID.
Yes, both the first responses is as what I would expect.
If you look at this manual/info https://www.domoticz.com/wiki/Telegram_ ... ctionality then that person never receives his responses as a reply but rather as a new message. I followed all the instruction from the wiki except for installing the CLI part of telegram.
I was thinking that their might be some debug switch that is On that also sends the raw string to see the full CURL but can not find anything ragarding that.
jvdz wrote: ↑Tuesday 27 July 2021 20:49
Well it looks like a part of the response from the CURL command if send in a reply, but don't understand why that would happen.
As you can see in the BASH file: It sends the content of the text file with a curl command to your TelegramID.
So I removed the last line (72) in the BASH file that sends the message. As expected I do not get any message except for the one saying gathering data...
Removing that line aswell (11) then I get a message Reply done. and nothing alse. Only 1 message
Adding line 72 back then I get the extra garbage message after the correct message.