Skip to content
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

Pre release 0.1.6 available #144

Closed
roleoroleo opened this issue Apr 20, 2023 · 11 comments
Closed

Pre release 0.1.6 available #144

roleoroleo opened this issue Apr 20, 2023 · 11 comments
Labels

Comments

@roleoroleo
Copy link
Owner

Please test the new pre-release:
https://github.com/roleoroleo/sonoff-hack/releases/tag/0.1.6

Below the changelog:

Bump devcontainer build to Debian 11 (thanks to @darkxst)
Bump gsoap to 2.8.104 and update mirrors (thanks to @darkxst)
Bump openssl to 1.1.1s (thanks to @darkxst)
Optimize gsoap build (thanks to @darkxst)
Optimise openssl build (thanks to @darkxst)
Remove broken Dockerfile and link it to the one used by devcontainers (thanks to @darkxst)
Fix scope for ONVIF Profile S (thanks to @darkxst)
Set Github actions to use a specific image (thanks to @darkxst)
Add missing mqtt-config
Add mqtt request to dump full configuration
Add timeout to sql insert and update
Fix onvif scope in service.sh
Complete rewrite of mqtt-sonoff (removed mqtt-config)
Add missing option for ir control
Change options from lower case to upper case
Move motion callback to a thread
Improve debug
Add ha discovery for switches and selects
Activate command line option for discovery
Add -a option to mqtt-sonoff if discovery is enabled
Enable rmdir in busybox
Add configurable ftp-port to ftppush.sh (thanks to @couriersud)
Enable rmdir in busybox (thanks to @couriersud)
Add inotifyd to busybox
Add new motion detection mode through inotify

@roleoroleo
Copy link
Owner Author

Has anyone tried this version?
Do the changes made for motion detection work properly?

@gewinh
Copy link

gewinh commented May 1, 2023

I did try this a few times,. I did get everything to work except the motion_detector sensor in HA setting motion location to 0 or 2 wasn't reflected in the UI after reboot as in the problem in 0.1.5. However the detector sensor status was unavailable in 0.1.6 whereas in 0.1.5 it worked OK. Tried a number of times deleting everything fro HA rebooting and adding again still couldn't get the motion detector to work. I could get it to work in 0.1.5 with this firmware setting the motion location to 0. I'm using the YiHack for the integration in HA.
Firmware Version 0.1.6
Base Version V5520.2053.0505build20230320
Model GK-200MP2-B

@darkxst
Copy link
Contributor

darkxst commented May 1, 2023

I'm testing on GK-200MP2-B. MQTT seems to be completely broken with location=2 for me.

My camera is also boot looping whenever I enable motion detection, need to investigate further, but I think it was doing this on 0.1.5 also.

@gewinh
Copy link

gewinh commented May 1, 2023

I have found that with 0.1.5 on the GK-200MP2-B and GK-200MP2C I have to disable "snapshot for recorded video" in the webui before I can get stability. I have quite a few of these cameras running 0.1.5 with this disabled and integrated into HA. They seem solid, while just doing motion activated recording to the SD card. I use SCP to copy off/delete the previous days recording each night on these cameras and have turned off the ftp. Haven't had any unplanned reboots.
With 0.1.6 as stated above, with the same config. I cannot get the mqtt motion sensor to work.

@roleoroleo
Copy link
Owner Author

I can't test the whole chain.
But if I set 2, when I create the file /tmp/colinkPushNotice with a touch, the event is fired properly.

@darkxst
Copy link
Contributor

darkxst commented May 1, 2023

OK, I was running beta of HA, there is some bug parsing MQTT messages currently. I downgraded back to stable release and its all working well with location 2.

@gewinh thanks that seems to have fixed the boot loops

@darkxst
Copy link
Contributor

darkxst commented May 1, 2023

There maybe an issue with motion sensitivity setting. This value is sent when turning off motion detection in the web UI.

Logger: homeassistant.components.mqtt.select
Source: components/mqtt/select.py:152
Integration: MQTT ([documentation](https://www.home-assistant.io/integrations/mqtt), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+mqtt%22))
First occurred: May 1, 2023 at 10:40:24 PM (2 occurrences)
Last logged: May 1, 2023 at 10:42:43 PM

Invalid option for select.sensitivity: 'OFF' (valid options: ['LOW', 'MEDIUM', 'HIGH'])

@roleoroleo
Copy link
Owner Author

Yes, I know.
I will remove the mqtt feedback for this message.

@darkxst
Copy link
Contributor

darkxst commented May 4, 2023

I will remove the mqtt feedback for this message.

or just update the HA Select to also support off (sensitivity 0), same should be done in the webui in that case. mqtt-sonoff is only thing that currently has the 'off' option.

@roleoroleo
Copy link
Owner Author

You are right.
But I don't know what happens when the user selects Motion=on and Sensitivity=off.

Copy link

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.

@github-actions github-actions bot added the Stale label Mar 31, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants