Domoticz

Have you made steps with tasmota?

I got the code from the doorbell with a simple-rc-scanner
But it looks there is a pre-sample in the code. Which rswitch can not work with (by default). The esphome code can work with it. But it goes to far for me, to get those esphome coding in a modified rcswitch code.
If you have any idea, i would be happy to hear.

hoeby wrote:
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

@hoeby
Could you please provide the yaml-code for this solution? I am not yet familiar with ESPHOME, but would like to give this a try.

EddyG wrote: ↑Sunday 11 July 2021 15:37 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....

Hello !
I try to connect my doorbell to motioneye with those settings but impossible to do this.
Even in vlc impossible to display someting.
PLease, could you explain how to do ? Thanks in advance.
Best Regards
Jean

In motioneye you have a wrong ip/port written. Don't know if that is the problem, but try it

You have: 192.169.0.14/8554
This must be: 192.168.0.14:8554

Also try in motion eye to keep the username and password empty. And place those in the url, like eddy posted.

I have a foscam doorbell. That only works with user/password in the url, not by adding them in there own fields

EddyG wrote: ↑Sunday 11 July 2021 15:37 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....

Thanks for your answer.
I tried with your two solution and that is the results : I don't know if your are using the smart connect LSC smart doorbell 1080HD with Module MCU V2.10.5 ?

thanks for you help again

Best regards

Jean

In the first post I state which version I am using. It seems one of the latest version which is not susceptible for the hacks found on the Internet.
These are the streams that I found with this version.

Last weeks i was modifying the zigbee network with sonoff zigbee coordinators.
I also saw that they have a RF bridge. Ordered one to try and see if it works that beautiful as the zigbee coordinators.

I reflashed it with tasmota and portisch firmware.
After that, the doorbell works without other modifications to the rf bridge.

This is the result it gives when pushing the button.
The "Data" is the unique code for the doorbell With that result, you can make rules in de tasmota, to do things.
This rule triggers an idx device in domoticz (mqtt needs to be setup in the tasmota)
- Change 303631 to the code your doorbells gives you
- Change 64 to the idx number of your domoticz device.
You have to make something in domoticz, to set the IDX back to off. This rule, doesn't send an off command After adding the rule, do this command, to enable the rule When doing no rules, but getting the code in Nodered, it looks like when putting a debug behind a mqtt input Information how to flash:
https://tasmota.github.io/docs/devices/ ... ridge-433/

The device

Hello,

Did you succeed to access remotely to this doorbell using an app like TinyCam ?
I have correctly acces with this app to my doorbell by using a wifi connection, therefore when I switch to a 4G connection on my phone, it doesn't work anymore.
The port redirection on my routeur on both ONVIF and RTSP have been done. I used 8000 and 554 as redirection ports parameters.

Is it possible that the doorbell is made to allow acces only with the same wifi connection and not from the outside ?
Note that I have other Tapo cameras that work perfectly on both wifi and 4G connections.

Thanks for you help.

Hi

i find way to have MQTT push when button push with firmware 5.0.5

Add doorbell to Tuya APP on iOS or android

first create account on

https://iot.tuya.com

After create Cloud Project

On your project add devices Link Tuya App

Use data center from your region

You must App Account with 1 device

After note Authorization Key

Access ID/Client ID and Access Secret/Client Secret

now install

https://github.com/jasonacox/tinytuya

and start

python -m tinytuya wizard
You must write
API Key it's Access ID/Client ID
Secret it's Access Secret/Client Secret
DeviceID. you find in app Tuya
Region eu for me

With that you can have key for your device id

[
{
"name": "Visiophone Wifi",
"key": "e177111111111",
"id": "bf5ad111111111"
}
]


Now install
https://github.com/TheAgentK/tuya-mqtt

setup config.json for mqtt setting
And with tinytuya you have create devices.json rename in devices.conf and put in folder tuya-mqtt

and start

DEBUG=tuya-mqtt:* ./tuya-mqtt.js


And after each button push you can see message like that

tuya-mqtt:state MQTT DPS JSON: tuya/visiophone_wifi/dps/state -> {"244":"0"} +67ms
tuya-mqtt:state MQTT DPS244: tuya/visiophone_wifi/dps/244/state -> 0 +1ms
tuya-mqtt:tuyapi Received JSON data from device bf5ada2f1c3c05e3cfi86t -> {"244":"0"} +16s
tuya-mqtt:state MQTT DPS JSON: tuya/visiophone_wifi/dps/state -> {"244":"0"} +16s
tuya-mqtt:state MQTT DPS244: tuya/visiophone_wifi/dps/244/state -> 0 +2ms
tuya-mqtt:tuyapi Received JSON data from device bf5ada2f1c3c05e3cfi86t -> {"244":"0"} +12s
tuya-mqtt:state MQTT DPS JSON: tuya/visiophone_wifi/dps/state -> {"244":"0"} +12s
tuya-mqtt:state MQTT DPS244: tuya/visiophone_wifi/dps/244/state -> 0 +1ms

{"244":"0"} is when button push