Doorbell from Action (LSC Smart Connect)

[EddyG]

Got myself a doorbell as mentioned here: viewtopic.php?p=275351#p275351
Art.nr. 3003046 970790.1 v1.0 It has firmware V5.0.5 inside.
I saw that in the LSC app there is a menu 'Onvif' so I decide to set that to ON.
I tried to get a stream based on Onvif and port 8000 into my Synology Surveillance Station with username/password -> admin/admin and IT WORKED!!!
Now I have to do some work to get the stream url to get it into Domoticz.
And I am looking for a way to get a doorbell device activated when the button on the LSC doorbell is pressed.

[HansOtten]

This worked for me: use the ONVIFER application to find the image url

- Install ONVIF IP Camera Monitor (Play Store, Android for me)
- Find the camera and make it work with the user and admin of the camera
- Scroll down and see the snapshot image url
- Fill this in Add Camera

[EddyG]

Tried it, but it does not work. No url.
I got (temporarily) my doorbell ringing by using Tasker on my phone, but that is not a permanent solution.

[EddyG]

Got the RTSP stream

Code: Select all

rtsp://admin:[email protected]:8554/Streaming/Channels/101
rtsp://admin:[email protected]:8554/Streaming/Channels/102

First one is 1920 x 1080 and the second one is 640 x 360
The last one is suitable for display in Domoticz
Searching further....

[Pauls]

@EddyG: in which menu did you find the ONVIF function?

Greetings,

Paul

[EddyG]

in the LSC Smart Connect App. Select the doorbell and then the 3 dots in the upper right corner.

[stack]

To Connect with mqtt change logparser like this.

if contains "$BUF" "--motion detection alarm --"; then
#echo "motion detected"
/mnt/mmc01/mosquitto_pub -h 192.168.178.239 -m '{ "idx" : 341, "nvalue" : 0, "svalue" : "90.0" }' -t 'domoticz/in'
elif contains "$BUF" "##doorbell_push 3"; then
#echo "doorbell push button"
/mnt/mmc01/mosquitto_pub -h 192.168.178.239 -m '{ "idx" : 341, "nvalue" : 0, "svalue" : "91.0" }' -t 'domoticz/in'
#else
#echo "Unknown cmd: $BUF"
fi
echo $BUF >> $DEBUG_FILE
done
}

main

First thing to do is the hack!
https://github.com/guino/BazzDoorbell/issues/2

[EddyG]

Tnx, but it seems I am stuck. I have version 5.0.5, what version are you on.
See: https://github.com/guino/BazzDoorbell/issues/38

[stack]

ppstrong-c51-tuya2_lcs-2.9.6.20200628

Looks like that your version ,not the hack supported see comment Guino.

I am sorry to say that if your device doesn't return anything under /proc/cmdline it is likely NOT running linux (runs RTOS) and there's no mod available to make MJPEG/SNAP work in RTOS. RTOS seems to be common for 5.x firmware right now.

[hoeby]

And I am looking for a way to get a doorbell device activated when the button on the LSC doorbell is pressed.

For people who have this doorbell, they have 433mhz inside which controls a chime.
The doorbell is sold by many sellers with each having there own name, but it is the same hardware.
I used ESPHOME on a ESP8266 which reacts on this 433mhz command and send a mqtt message to domoticz.
No firmware flash on the doorbell necessary.

Made it with ESPHOME, because the 433mhz is a 64bit signal. ESPHOME can receive this
Tried it with ESPEASY, but that uses the default rcswitch library, which supports max. 32 bits

[EddyG]

Made it with ESPHOME, because the 433mhz is a 64bit signal. ESPHOME can receive this
Tried it with ESPEASY, but that uses the default rcswitch library, which supports max. 32 bits

What are you using to receive the 433mHz signal?

[hoeby]

i am using a HopeRF RFM210LCF-A 433Mhz RF Receiver
It has an antenne pin, but without antenne the range is already +/- 10 meters

There are cheap "433Mhz RF transmitter and receiver link kit" on the market.
The transmitter works good. But the receiver, throw it in the bin. Range of 1 meter, antenne added makes no difference

This is the one you need to throw in the bin


This one i use

[EddyG]

Tnx, I have a RFLink, have to look if I can rebuild that with a esp8266 and ESPHOME, or otherwise build just a new one.

[hoeby]

I tried the Aurel (which is on the rf link) to control with espeasy.
It has a special way on startup. But i couldn't get it to work. But that is to my skills, because on the rf-link it works.
After that i went for the separate devices.

Then i discoverted that the rcswitch library doesn't support more then 32 bit. In the issue list on github i a post with modifications to 64 bits. I tried it, but no signal received from the doorbell. After that i tried esphome, because on tweakers i found a post that somebody got a binary code out of.

Unfortunally esphome has a mindset for homeassistant.
A lot of information is with home assistant. But it also works without. I used a pi zero for the esphome dashboard, to make the .yaml files. And a wemos d1 is for the receiver-hardware.

When you want to add a modified library to esphome, that is possible. Add it in the .yaml file. It will be installed. When you need to change something in this installed library. It is in de config directory, which is made when you do an install. There is a hidden directory in de config directory, where the libraries are installed

[EddyG]

Thanks for the info.
I have Home Assistant running in a docker container on a RPi4 (doing nothing, because Domoticz is in control). That is not so convenient for this setup.
So I will take a RPi3B+ to setup a full blown Home Assistant with supervisor, because that seems quite a hassle on docker.

[hoeby]

For me it exactly the same.
Homeassistant in docker, without the supervisor, which is normal for the docker version. I went for the pi zero, it had nothing to do. Only esphome is on the zero. It has to low specs for Homeassistant (and domoticz).

Please, keep us updated, how it went.
And if (and how) you got the aurel working

[EddyG]

Finally got my HomeAssistant running on a RPi3 with Ubuntu 20.04 lts with aarch64 in a docker container with supervisor.
This is the script I used: https://github.com/home-assistant/supervised-installer
Now the rest.....

[EddyG]

My RPi3B (without the +, and the only spare I have) could not handle Ubuntu 20.04 with HomeAssistant so I had to switch to DietPi with aarch64.
See how that goes....

[EddyG]

I decided to follow an other road.
For many years now I have a PiAware running on a Raspbery Pi 2B, which is up and running for more then 3 years now without being down.

28.10.2021_10.17.24_REC.png (4.33 KiB) Viewed 20607 times

I use a RTL dongle to receive airtraffic information. I have a spare dongle which was intended to be used to receive my 433MHz temperature device.
I already did some experiments with rtl_433 to receive those and that works, I got all my temperature devices and a lot more.
I almost replaced my old KaKu devices with Zigbee or Zwave, so soon I will make the switch from RFlink to this RTL dongle.
I already got reception of the Doorbell from Action on 433.900.000 Hz.
The only thing I got to do now is decode the received bits. Bit pattern is received, only decode or acknowledge that a certain bit stream is the doorbell.
Will see how that goes.....

[hoeby]

I was looking for adding a plugin for espeasy, for this doorbell.
I got the code from the doorbell, but not working in the plugin. It looks like the doorbell has a preamble, which the rcswitch library doesn't know what to do with. Therefor i get, everytime i push, different results.

In search for a solutions, i found the rtl433 option. looks interesting, so get us informed.
Also thinking about using ESPhome as a gateway. There is a 433 to mqtt gateway, but this only works with devices which are recognized.
I thinking about using the ESPhome to transfer all received 433 codes. And use nodered to make the filter.
The same for the other way around. That domoticz sends a json command to the nodered->ESPhome and that one send the code.