hallo
I am using A6c module ....i need help in capturing an image from the camera and i need to send it to email id ......i am beginner in this field ....
@canyouhearmenow I didn't see my version of the sketch, but then I saw that the column sk_version was commented out.
I added again this missing column. I don't use revision, only version.
I saw also that the api_version of my repeaters were not reported. I added support for this to the code.
The sqlite db is filling up with all these mqtt messages.
Do you clean up this after some time?
Great work, thanks for putting it online
I have two Dooya motors DT82TN with a DC2760 remote control, which is 433MHz.
After a lot of investigations and experiments, I got them working with Domoticz (running on a Raspberry Pi), using the following:
A Broadlink RM2 (RM Pro+) which supports 433MHz. The official Broadlink app is cloudbased and can "learn" the codes to operate the Dooya, but I abandoned this since I want integration with my domotica system, not just another app on my phone.
The software at https://github.com/mjg59/python-broadlink works with Broadlink devices, but does not integrate well with the RM2. So, I only use this for my thermostat, not for the Dooya curtains.
The "official" Domoticz plugin described at https://www.domoticz.com/wiki/Plugins/BroadlinkRM2.html is an old version, that is not supported any more - as stated at the top of the page.
The "zak45" Domoticz plugin that works is described at https://www.domoticz.com/forum/viewtopic.php?f=65&t=33223#p251517 to be downloaded at zak45's Nextcloud drive: https://synnas.publicvm.com:4430/s/Czn9r8G8QwrZ7ji
This latter plugin is not easy to use, and has special added webpages to Domoticz. It is however able to use the RM2 to "learn" IR and RF codes from the UI of Domoticz. However, there is a bug due to which the learning of RF codes does not work from the UI.
I was able to use the command line on the RaspberryPi with the above given plugins to detect Broadlink devices. And this way, I could also learn the 4 RF codes I needed for my 2 curtains: open/close for each. This gave me the code as some numbers, which I stored in a text file.
Since the IR learning works, I used this to learn 4 commands, and then looked where these codes were stored on the Raspberry, and replaced them with the RF codes. This was easy.
Just a tip: I used Dolphin with fish://raspberrypi/ to browse and edit the files on the Raspberry from my desktop PC.
@Zwer2k my expectations seem correct. I created a bug report that also includes a rudimentary workaround.
https://github.com/mysensors/MySensors/issues/1496#issue-968399284
Yveaux created this issue in mysensors/MySensors
open
Incompatible with Arduino core for ESP8266 version 3
#1496
@adamf663 sorry for delay! I am focusing on mostly software at the moment. So nothing to show so far i'll be posting as soon as the project moves forward again please read on !!!
@MasMat thanks a lot for your suggestions. As suggested first it is more than probably a case of rights/permissions.
There are many ways to launch a script at startup but in my case some deamons were started via "root" and some others via "user".
As stated before, all worked perfectly when logged under "user" (pi).
So, to summarise:
rc.local didn't work
crontab didn't work
.bashrc didn't work
These might work in the end but i'm not brainy enought to get to it.
Then came "systemctl" !
First create a .service file
$ sudo nano /etc/systemd/system/doorbell.service
[Unit]
Description=My test service
After=multi-user.target
[Service]
Type=simple
Restart=always
ExecStart=/usr/bin/python /home/pi/doorbell02.py
[Install]
WantedBy=multi-user.target
#WantedBy=default.target -> test this if previous doesn't work
Reload all daemons to check if your new .service file is ok
Then allow your new service file to be loaded at boot
Last, check if loading worked. If status returns "active" then it's a win
$ sudo systemctl daemon-reload
$ sudo systemctl --user enable doorbell.service
$ sudo systemctl --user start doorbell.service
$ systemctl --user is-active doorbell.service
Last step: systemctl loads these services at loggin by default (as in : enter user and password). I need it to start automaticaly with no human input. systelctl offers a way to load services without loggin for a given user :
$ loginctl user-status pi
Check status with
$ loginctl user-status pi
If status returns "linger: yes" then it's (once again) a win
Thanks again @MasMat for suggesting paths to investigate
That's it for now, i'll be back on the hardware point of view next time !
