-
Notifications
You must be signed in to change notification settings - Fork 101
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
Works on DG-MYQ #84
Comments
Well I managed to get a bit further:
|
For snapshot, you can get it from URL, there is a patch to apply: #64 |
Cool, will try that. Some progress from my side: network available detection is now much more reliable (used to be just a sleep in which it work in most cases. But not all....). Suddenly the camera does not log EVENTs anymore. (not using patched p2pcam). Probably I unintendedly changed something in a config. Anyone with some info on eg |
OK, so here is the the first release of my fork of this project: https://goo.gl/pYPF4r
Download https://goo.gl/pYPF4r NOTE: ONLY the persistent hack (ie. where you do not need the SD card for R/W capable cameras) is tested to be working. Instructions: (note 192.168.1.117 is my camera IP, adapt to your own) If you do not need Domoticz logging, you have to comment out two lines in the /home/p2pcam.sh script. These lines are marked with "#Comment out next line if NO Domoticz logging is needed" Configure Domoticz logging: |
One of my friend asked about finding UART port on T821-B0 board, I thought that the 3 holes on right edge could be the the serial port ? maybe it's not mandatory to find that to use modded fw ... |
You do not need a telnet session via the uart (which indeed is the 3 pinholes). Just use the sd to hack and start a telnet session to the ip address. |
I also have a DG-MYQ with the same firmware (3.2.8.0121) but unfortunately mine is read-only! Any workaround for this? |
just got my DG-MYQ. Tried your sdcard hack. Snapshot: |
Finally got around to play with my DG-MYQ camera I bought almost 6 months ago. Without sound - Small picturertsp://admin:@192.168.0.11:8001 Without sound - Large picturertsp://admin:@192.168.0.11:8001/tcp/av0_0 With Sound - Small picturertsp://admin:@192.168.0.11:8001/0/av0 I am new to telnet, so don't really know how I should go about testing if I can do anything useful with it. My version is 3.3.0.0803 Don't really know what to do. I really don't want to use it with the cloud when I can't change password for neither telnet or rtsp streams. And I can't seem to find the option where I can let it on my WiFi but cut it off from the outside world, but that would be ideal, since I am goind to use RTSP. Do you have any tips for a novice like myself? |
You can change the rstp password, with official firmware and an INI file. |
Thank you, it changed the password successfully. But all the streams are in black and white now though. |
Maybe that's the night view? |
Might be. Thought the night vision only toggled when it was dark in the room. It is night where I am though, but it's been dark outside since I started fiddling around with it. And I haven't turned the lights out in the room. |
I have updated it with the new password and it got rolled back to an earlier version while doing that. I thought I would try and update it through the app to see what version I would get. I now have version: 3.2.8.0121. Which is the same as you have gotten it to work with, but webui and snapshot still doesn't work, and it still connects to the cloud. The version I got after updating password was something like: 3.1.x something. So I might just try to update the password again to see if it will work with that version. Something else did happen though, now port 554 is open with the RTSP stream. And port 80 is open for http traffic. When I go to IP/cgi-bin/webui it shows a login popup. But admin/ and root/cxlinux does not work. |
I just figured out they're a more easy way to change the password. But anyway, what results do you get when you extract the readonly zip from this git to a tf card and place in your camera? EDIT: I also know why your vision is black and white.
But I get better results with
|
I have now tried that, and it is still black and white. It is not because it is night, because I have tried to put it in a dark place, and the IR turns on and for some reason it turns back to regular color. But as soon as it is sunny or the light is turned back on, it goes back to black and white. these links: I had already tried both readonly and readwrite from this repo, but nothing did the trick. |
If the camera keeps connecting to the cloud, then the hack was not applied. |
I tried the readonly hack from this git, and that seems to have worked. It does not connect to the cloud but the RTSP streams still work. However, the picture is in black and white. Do you know why this has happened? I have even tried to reset the device completely and connected it to the WiFi through the app. It is still in black and white. Is this just going to stay b&w forever? |
I just tried to apply new firmware and I got the same result, like night mode is reversed.
Looks like it works again now! |
Yes, I have also found out it is because the night mode is reversed. I tried following another tutorial on YT that had the same problem but with the M1Q model, but that didn't do the trick. I'm sorry to be a burden even more, but I haven't really worked with FTP before. Can you give me a quick recap of how to FTP into it and change the hwcfg.ini? And do I have to have the read/write or read-only hack on it, to FTP into it? |
The m1q tutorial doesn't work, you mean flipping the lens right? |
Exactly, that is the tutorial I tried, but as you say, it is a software bug. |
You should have the readonly hack installed, then it's working fine. Port 21 indeed. |
Thank you. I have done this now. My hwcfg.ini looks the same as what you wrote. But now it doesn't go to night mode. Do you have the same issue? When I put a finger over it, it lights up all the red lights around the lens, but it doesn't make the clicking noise it does when turning to night mode, and it stays in colored picture. My guess is, it is because we deleted the line ir_detect_type 2 option in the cfg file. |
I have tried to play around with the settings in hwcfg.ini now. I have tried setting 'ir_detect_type' to 0, 1 and 2. On 0 and 1 nothing happens at all, it does not detect night mode, but it is at least not reversed. I have looked into why the webui manual IR on/off doesn't work. I can see when I telnet into the camera and run 'gio', it comes up with: gio -di 49 / gio -do 49 1 / gio -s 49 0 /gio -g 49 |
You know the webui is at port 8080 right? |
Yes I know. The webui also shows up. But I can't turn on/off the IR with the buttons on the webui. |
Ok good. Try to use the webui file from edsub Just copy the file webui to your sdcard and overwrite, then you get more buttons and these should work. |
I thought about that. But I compared the two files. They are almost identical. What shows up when you telnet into it and type gio? Just to know if it is normal that it only responds with gio 49, because the webui turns on/off gio 46. |
Sorry for the late reply, this is my output of gio
I flashed an older version of p2pcam btw, and night/day works fine for me.
|
I will check the version when I get home. Where did you find the older version? And did you flash it by just putting it on a sdcard like the hack and changing password? |
It was this one: Just flash it indeed |
Thank you. I will try it out later tonight and post the version after. Hopefully it fixes the reversed night mode. |
After I used that firmware, something has gone wrong. I took out the sdcard after it said successful, put in my pc again, and it contained a text file with the name ERROR. In this text file it says "Copy hwcfg.ini failed.", it connects to my wifi, and I can use rtsp, but with no password. I have used telnet to look if it indeed did fail the copy, and it did. There are no hwcfg.ini in the /home directory. I can then put the readonly hack on the sd card, and I can conncet over ftp. But when I try to tansfer the hwcfg.ini to the /home folder, it says "1 file failed". Is there a way I can recreate the file directly on the camera over ftp or telnet or something? I have tried both the MYQ password changing firmware and the GUUDGO firmware you just send, multiple times. Every time I get the error text file returned in the sd card. I have tried resetting the camera, that did not help. So now I am really screwed. It is now version 3.1.0.0824 |
Very strange, in my case it worked just fine! |
Yes I still have access. The telnet works fine, and if I put the Readonly Hack on, it also starts the ftp server. Did not know wget and vi was accessible through telnet. Will give that a go. |
Yes, I was just experimenting and you can also just update the p2pcam by going to the home folder, delete old p2pcam.tar.gz and wget another one from a server you've uploaded it to. Good luck! |
I think I bricked it. I tried to make the hwcfg.ini with vi, but that said no more room on device when I tried to save it. I then tried wget, but that said the same thing. I then tried updating it through the app, to see if I could get it back to normal to start over, but it never stopped updating and now it doesn't connect to wifi, and if I hold the reset button it doesn't do anything neither... I tried putting the firmware on the sd card and boot it with that in it, but nothing happens. So I think this is a lost cause by now. :( |
Use a serial connection and then you can revive it for sure. I guess you didn't backup your firmware? |
No I didn't back it up. I don't know where the rx, tx and gnd pins are. I was going to try and flash the .bin file from the changing password folder. But can't find the pins. |
https://github.com/yuvadm/DG-M1Q Here is the serial connection setup, 3 pins on the side |
My MYQ doesn't have those. It has some smaller ones that look like it, but not exactly where those are located. I found someone saying the three pins next to the sdcard is rx/gnd/tx, but just tried with the ftdi adapter, and it couldn't flash it. Not an expert with flashing through ftdi adapter, but do I not need the 3v pin as well? Or can i just connect gnd->gnd / rx->tx / tx->rx and flash it that way? |
The MYQ indeed has the serial port located next to the SD-Card slot (see: link) 3.3v is not needed and may even damage the camera if connected. |
@AnthonMS Have you tried to make it work again and got any success? |
I am in the process of verifying correct funcioning on a DG-MYQ camera.
The ReadOnly works as described (although FTP connection failed)
It even looks like the R/W version works as well (at least in SD card mode, FTP too!!).
All versions had issues with the sync time (ntpd -q -p 0.uk.pool.ntp.org) a change to 0.rhel.pool.ntp.org seems to solve, so probably not a camera issue but something on the ntp server side....
verification not finalised.
I am also looking for a way
To be continued
The text was updated successfully, but these errors were encountered: