[rajd]

And you didn't notice that the config.json contains the same information as the hardware and settings?

I would suggest reading the pilight manual for the latest config structure.

Ah yes, I should have mentioned... the configuration as mentioned above didn't exist until 24 hours ago and was the result of some heavy Googling .

I've reverted back to basic configuration: which looks like this:

Code:

{
        "devices": {},
        "rules": {},
        "gui": {},
        "settings": {
                "log-level": 6,
                "pid-file": "/var/run/pilight.pid",
                "log-file": "/var/log/pilight.log",
                "webserver-enable": 1,
                "webserver-root": "/usr/local/share/pilight/",
                "webserver-http-port": 5001,
                "webserver-cache": 1
        },
        "hardware": {
                "433lirc": {
                        "socket": "/dev/lirc0"
                }
        },
        "registry": {
                "pilight": {
                        "version": {
                                "current": "7.0"
                        }
                }
        }
}

Still no result though. Could it be the RPI3 causing problems, given this board is more or less brand new?

[wo_rasp]

The Pi3 is working with pilight


Gesendet von iPhone mit Tapatalk

[Niek]

You write that you wired up your receiver this way:

Code:

GND -> RPI Pin #06 (Ground)
DATA -> RPI Pin #12 (GPIO18 / GPIO_GEN1)
DRE -> NC
VCC -> RPI Pin #02 (5V)

If you really did that, the receiver is putting 5 volts on the GPIO pin, which may have destroyed that pin, since it may only have 3.3. volts (no overvoltage protection).

You should never connect a 5 volt device to a GPIO pin without some kind of levelshifting.
Furthermore it is recommended to use a filter. If you do that like described in the Wiki, that also solves the voltage level problem.

[wo_rasp]

Sorry folks, i picked up that conversation on my mobile.
We are discussing here a 1 year old thread .... and the user was never online after March 9th, 2016