It control not working

[gmcaesar]

Can not turn on or off or lights from web or HA

[roleoroleo]

Please, explain me better.

[darkxst]

I never got the IR led to work in my testing previously (directly via SQL).

However I did find that can control the visible (Status) LED's with the following (empty) file /dayun/mtd/cfg/disable_ledshow

Might be worth adding that to the Web UI

[gmcaesar]

I see the IR controls in the web UI but they seem to have no effect, I they always are in auto mode no matter what I do in the settings

[darkxst]

@gmcaesar What camera model do you have? I just tested on my GK-200MP2-B and IR lamp control is working via Web UI. What I described earlier was probably tested on the S-CAM model, which has the status LED on the face of the camera.

[gmcaesar]

I have the same as you the Sonoff B

On Tue, Feb 21, 2023 at 7:14 PM Tim L @.***> wrote:

@gmcaesar https://github.com/gmcaesar What camera model do you have? I just tested on my GK-200MP2-B and IR lamp control is working via Web UI. What I described earlier was probably tested on the S-CAM model, which has the status LED on the face of the camera.

— Reply to this email directly, view it on GitHub https://github.com/roleoroleo/sonoff-hack/issues/136#issuecomment-1439379027, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHA3WWXVJOB6HKIDJE76VLTWYWACLANCNFSM6AAAAAAVAXR4PI . You are receiving this because you were mentioned.Message ID: @.***>

[roleoroleo]

With my GK-200MP2B it works, but a reboot is needed.

[gewinh]

The IR control on the webui does not seem to have any effect on the GK-200MP2C. If I change the setting to off on the webui and do a save it reverts back to auto. If I reboot the camera it always comes back set to auto. Base Version V0525.1.412build20220712, firmware 0.1.5. The IR lamps stay on regardless. It would be nice to be able to turn them off, one of my cameras faces a window and the IR lamps just reflect back.

[roleoroleo]

Please try to send the command 2-3 times. Maybe the sql update fails because the table is locked.

[gewinh]

I gave that a try using the webui, going from auto to off. I did get the ui to save the off state, but after a reboot of the camera it reverted back to auto. I tried this 3 times, each time the state was saved as off but after a reboot it reverted to auto.

[roleoroleo]

Ok, try to check if the param is saved running this statement: # sqlite3 /mnt/mtd/db/ipcsys.db "select * from t_sys_param where c_param_name=\"InfraredLamp\";" Both afer the webui command and after a reboot.

[gewinh]

Thanks for you ongoing support. I tried the database query. The reply was a value of 2 for the InfraredLamp, the value of 2 was always the same regardless of how many times I tried to change the IR LED setting, whether I saved it, rebooted after saving, refreshing the web page etc. I thought it might be related to the web upgrade from 0.1.4 to 0.1.5 so I reflashed the SD from scratch with 0.1.5 and reconfigured it. Trying the test to change the IR lamp gave the same result ie 2 from the database. I thought the camera might be too busy during the test to write a new value to the database, so I set privacy on and disabled ftp, then did the test again and got the same result.

[roleoroleo]

2 means "auto". Please, try these new files: cgi.tgz

[gewinh]

Thanks I will give it a try, I did run the command sqlite3 /mnt/mtd/db/ipcsys.db "update t_sys_param set c_param_value=1 where c_param_name=\"InfraredLamp\";" from you camera_settings.sh and it did update the db so when I used your query above it results in a value of 1. Even after a reboot the value is 1, although the webui still says auto.

[gewinh]

OK so I used the command sqlite3 /mnt/mtd/db/ipcsys.db "update t_sys_param set c_param_value=2 where c_param_name=\"InfraredLamp\";" to set the camera back to auto. I checked the value in the db and it was set at 2. I rebooted the camera then renamed camera_setting.sh and set_configs.sh in the www/cgi-bin folder then copied your 2 new files into that folder. Reboot camera and tried to use the webui to change from auto to off. After saving the change to off a db query showed the value still set at 2. after a reboot the value was still 2. I am at a loss your db command in camera_settings.sh is correct and I can manually change the value. It looks to me like a problem passing the value from the webui to the camera_settings.sh script. Hope this helps.

[gewinh]

Sorry to be using up your time. I finally figured some of it out. It was to do with passing the parameter from the webui. I use ubuntu 22.04 as my desktop with brave as my default browser. All the problems I described were described using brave to access the webui, I haven't had problems before. When I switched to chrome to run the cameras webui, the update from auto to off runs fine and the query on the database shows a change from 2 to 1, do need a reboot to turn off the IR.. Don't understand why Brave would fiddle with passing parameters to a local web server, or maybe some sort of caching thing? So status is with your new files and a chrome as the browser the IR can get turned off and on. I tried on another camera with chrome and it allowed me to change the setting in the database with the webui, but on reboot the IR was still physically on but the database showed 1 for the parameter. Same model camera same firmware. Tomorrow I will flash the sd again and try from scratch, as the camera that worked was the newly flashed sd from this morning.

[roleoroleo]

It could be a cache problem. Cam you try to force a clean of the cache?

[gewinh]

The saga continues. I have not gone back to Brave and cleared the cache, but have been using chrome or firefox. These browsers(at the moment) let me change the IR led field and save it and the change is correct when I query the database. The problem now is even though I have the IR led set to off and the database has a value of 1, the LED still is on regardless of reboot, and changing again(ie reset to auto, save, reboot, set to off, save, reboot. The IR light is always still on at night. This is with fresh install of 0.1.5 on 2 separate cameras. I did notice something strange though on the fresh install of 0.1.5 on the sd card I didn't reset the camera but just restarted. The default value that came up for IR led on first boot was "off" not "auto", it must be retaining some info in the camera from the previous settings. There is something definitely wrong in the passing of this parameter to ultimately set the camera operations. I will give it one last try tomorrow, doing a full reset on one of the cameras, a new 0.1.5 sd using chrome. Am I correct in assuming the changes you made to the 2 news scripts just related to timeout on the database updates, so if the parameters are being written correctly to the database then these changes will not fix the current problem. I have one camera out of 3 where I have successfully got the IR light off at night, same model and firmware as the others but I cannot reproduce this.

[darkxst]

Sonoff-hack only updates the database, the rest is done by Sonoffs software.

[gewinh]

OK after another day of testing on 3 cameras I have got to the position I wanted ie I can turn off the IR, run the camera with motion detection recording, ftping the actionrecords to a server, have them integrated to Home assistant and can activate privacy on inside cameras when home. I thought I would document my process in case others had the same problems. All cameras are GK-200MP2C I reset all cameras and upgraded from V0525.1.276build20201103 to V0525.1.412build20220712 (not sure the firmware upgrade was the reason for the fix), got each camera on the network with ewelink and set, hostname, motion recording on, sensitivity low and night vision off in ewelink. Flashed the sd card with 0.1.5, restarted the camera with the sdcard in, used the webui (in chrome)to configure all other setting (I have snapshot for recorded video off and swapfile on), checking in the webui that IRled was also off and motion detection was also on. In my case I found both motion detection and the IR led could not be set first from the webui and get reproducible results, it was always better to set these in ewelink first. There was definitely no motion detection, action recording happening without setting it first in ewelink. Once I had everything working OK I then turned on Disable Cloud. Hope this helps, sorry I couldn't get to the definite cause of these issues, but at least I have a work around. The Sonoff Hack software is great for these cameras, there are a lot of variable camera model, firmware etc. etc. it looks like just have to work through some workflow personality issues with certain combinations.

[roleoroleo]

I'm trying a different approach to change settings.

About mirror, instead of writing sql database directly, I'm trying to send an IPC message (UDP packet) to devctrl. It seems working.

About IR it's possible to create these tmp files to control IR behavior:

[root@sonoff-hack]# touch /tmp/manualControl_autoIR
[root@sonoff-hack]# touch /tmp/manualControl_darkIR
[root@sonoff-hack]# touch /tmp/manualControl_brightIR

In both cases the change is in real time.

[roleoroleo]

Check this commit: https://github.com/roleoroleo/sonoff-hack/commit/a08e4c889da022ac35cae4b9660668d56e0be6a5

[gewinh]

Looking great, I see what you are doing in the ipc section for the IR problem. I am building some new GK-200P2C cameras next week at my son's place with HA, happy to field test 0.1.6beta if you can point me to an early release with these changes.

[roleoroleo]

Here it is: GK-200MP2C_0.1.5.tar.gz

[gewinh]

sorry haven't had much time. I did test the above copy of firmware on a GK-200MP2C running V0525.1.412build20220712, the IR controls worked without a reboot almost perfectly. The auto to on or off worked. The on to off and back to on worked. Unfortunately you could not get back from either on or off to auto, when you did the save of a change from on to auto for example it would revert to on, never stay on auto. (hope that is clear). Also couldn't put my finger on the reason, but did seem to have more issues with camera stability eg. camera going off line, disconnecting from mqtt and restarting. Not sure any of the changes use more memory or stress the cpu more. Playing with disabling ftp copy of action records and removing ftp . I now have a process running on a server nightly that uses scp to copy the days action records, then delete them from the camera. I am hoping just to give the camera less to do during the day to try and improve stability. The swap file option doesn't seem to help, I actually worry that the extra IO to the SD may be detrimental to the stability. Thanks again for the support.

[roleoroleo]

Thanks for your feedback. Meanwhile I fixed a lot of problems. I will send a new beta.

[roleoroleo]

Here it is: GK-200MP2C_0.1.5.tar.gz

[gewinh]

Thanks I'll give it a try. While your improving things, A couple of other things I found about the release from last week, but didn't mention, was that the privacy switch works for the camera.XXXXX_cam entity when displaying in HA but not for the webrtc stream rtsp://192.XXX.XXX.XXX:554 ...., this did work in the original 0.1.5 version. Also for the original 0.1.5 and the one from last week, the PTZ web interface is a pull your hair out challenge, if you want to use it to move the camera a reasonable distance and establish a setpoint to go to on boot. The camera freezes, reboots etc. Tried the solutions mentioned previously without success. The yi_hack.ptz service in HA works a lot better. I know I am getting off topic on this particular issue, but not sure whether to open new issues for these things.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.