[_Jens_]

Hi,

some time ago, i’ve updated my RaspberryPi and after the update, i’ve got some problems with sending to a Elro 800 Switch.

The Raspberry:
Raspberry 2 running Raspbian Stretch, with pilight 7 (compiled by myself from the git repository / the development-branch) and the following kernel version:
Linux raspberrypi 4.4.50+ #970 Mon Feb 20 19:12:50 GMT 2017 armv6l GNU/Linux
(I’ve downgraded the kernel to 4.4.50 after some comments in this forum).

The Problem itself:
I’m sending like normal via pilight-send and nothing happened:

Code:

root@raspberrypi:~# pilight-send -p elro_800_switch -s 12 -u 1 --off
root@raspberrypi:~#

I’ve checked with pilight-recieve and everything looked fine.

Code:

// After the pilight-send command
root@raspberrypi:~# pilight-receive
{
    "origin": "sender",
    "protocol": "elro_800_switch",
    "message": {
        "systemcode": 12,
        "unitcode": 1,
        "state": "on"
    },
    "repeat": 1,
    "uuid": "0000-00-0f-13-392616"
}

// With my remote:
{
    "message": {
        "systemcode": 12,
        "unitcode": 1,
        "state": "off"
    },
    "origin": "receiver",
    "protocol": "elro_800_switch",
    "uuid": "0000-00-0f-13-392616",
    "repeats": 2
}

Everything should be working - but the switch doesn’t react.

Just to make source, that there is no problem problem with the 433 MHz sender, i’ve replaced it … still no success. I’ve compiled 433Utils (with wirinpi) and used it with a small sample code to send the on/off commands … and the switch worked.

After the test with 433Utils, it seems that there aren’t any problem with the hardware and hardware / 433gpio setting in /etc/pilight/config.json should be correct - because it’s the same GPIO-port numbers i’ve used for 433Utils.

Did somebody have any idea about this problem?

[Naga]

Not really a solution but a comment:

Linux raspberrypi 4.4.50+ #970 Mon Feb 20 19:12:50 GMT 2017 armv6l GNU/Linux
(I’ve downgraded the kernel to 4.4.50 after some comments in this forum).

I've been running rpi3 with 4.9.43-v7+(stretch) and pilight nightly just fine for weeks.



Did you tried running the nightly or using another gpio for the sender?
The problem happened to me after I screwed around with rewrite / dev and stable at the same time - ended up setting the rpi3 up from scratch which has done the trick for me.

[_Jens_]

Did you tried running the nightly or using another gpio for the sender?

yes, i’ve tried wiringPi PIN 2 instead of PIN 0 … but it doesn’t made any difference.

The problem happened to me after I screwed around with rewrite / dev and stable at the same time - ended up setting the rpi3 up from scratch which has done the trick for me.

that was, what i’ve tested yesterday. I’ve made a completely fresh installation with pilight nightly-branch and compiled it from the git source (development branch). :-/

[curlymo]

Please post the config you're using and the pilight version.

[_Jens_]

Please post the config you're using and the pilight version.

thank’s for your help.

I’ve just turned the raspberry upside down and … it wasn’t a Raspberry 2, i’ve used my old Raspberry1B over a year ago for the plight-installation.

I’ve changed the config to „raspberrypi1b1“ and voila - pilight is sending again. :-)

Just a small idea: Maybe it make sense to let pilight-daemon check the setting based on /proc/cpuinfo (http://elinux.org/RPi_HardwareHistory). :-)

[pilino1234]

Just a small idea: Maybe it make sense to let pilight-daemon check the setting based on /proc/cpuinfo (http://elinux.org/RPi_HardwareHistory). :-)

The problem is that the underlying GPIO interfacing library, wiringX, supports more devices than just the RPi and its different models (and thus, pilight does, too). In fact, wiringX used to run autodetection of the platform we were running on until there were too many platforms which were indistinguishable despite featuring differing GPIO hardware, and thus the feature was removed because it lead to a lot of problems.