I am having the same issue. I have also run nmap against the device and I see the same 2 ports open as you.
Annoyingly, I did have access via SSH but it seemed to hang as I was transferring the serialgateway.bin across. I rebooted the device and I haven’t been able to access it since.
Do you think it is possible that they performed an OTA upgrade and switched off the SSH server?
I still have serial access and I would be really grateful of any pointers
I’ve just managed to restart the ssh server. Connected via serial, if you run:
cat /tuya/ssh_monitor.sh
you’ll see what looks like a script which puts dropbear to sleep for extended periods of time for each failed login. But at the end there is the command to fire up dropbear again:
I have been running flashed lidl gateway for few weeks now. It goes offline every now and then (because I’ve setup an automation if the device goes offline). But The main problem is that I can’t change the Lidl E27 and GU10 bulbs colours. It shows the colour pallet but doesn’t do anything.
I am thinking to revert back to the factory firmware but I didn’t take the backup (for my sins).
Any ideas how to revert back to the lidl firmware?
hello im trying to use the script above but zigbee are unreachable until I change back to the original file from the guide, can you spot what I am doing wrong?
//remove old file
rm ./tuya/tuya_start.sh
//make new file
cat >/tuya/tuya_start.sh <<EOF
#!/bin/sh
while true; do
pgrep -x serialgateway >/dev/null
if [[ $? -ne 0 ]] ; then
echo “Restarting SerialGateway: $(date)” >> /var/log/serialgateway.txt
/tuya/serialgateway &
fi
sleep 30
done &
EOF
//set permissions just in case
chmod 755 /tuya/tuya_start.sh
reboot
it looks like it should work and I just cant figure it out.
do I have to make /var/log/serialgateway.txt myself or will it be created?
or something else? any and all ideas are welcome
Thank You!!!
and its kind of but not really working
it reads 1 when its connected, and when its not connected I get a error message in the log saying the command failed… and it stays 1
this is what I ended up with I added " ESTABLISHED" just to make sure it was connected and not just trying to connect
if u use this just make sure that you add or remove enough spaces " " between 8888 and ESTABLISHED so it can get a match, this should be 35 chars long in total
Hello,
I try and try, but I fail.
I get the same error over and over again when entering the KEK code:
What am i doing wrong?
C:\Users\Milan>lidl_auskey_decode.py
Enter KEK hex string line> 39713448 4B4F666C 367C7943
526C3A39
Traceback (most recent call last):
File "C:\Python32\SCRIPTS\lidl_auskey_decode.py", line 54, in <module>
kek = _decode_kek(_get_bytes(input("Enter KEK hex string line>")))
File "C:\Python32\SCRIPTS\lidl_auskey_decode.py", line 52, in _get_bytes
return unhexlify(a[0] if len(a)==1 else a[1])
TypeError: 'str' does not support the buffer interface
Thank you, on my pc it doesnt accept the string, so it must have been something wrong.
Can you please tell me whith which program do you work?
I have 3.2 python, and use that script.
Error i get:
(base) C:\Python32>lidl_auskey_decode.py
Enter KEK hex string line>397134484B4F666C367C7943526C3A39
Traceback (most recent call last):
File "C:\Python32\lidl_auskey_decode.py", line 54, in <module>
kek = _decode_kek(_get_bytes(input("Enter KEK hex string line>")))
File "C:\Python32\lidl_auskey_decode.py", line 52, in _get_bytes
return unhexlify(a[0] if len(a)==1 else a[1])
TypeError: 'str' does not support the buffer interface