💬 Building a Raspberry Pi Gateway
-
@gohan Thanks! I seem to have the serial stuff working well (but haven't yet put it into production) so I think I'll go that way for now. I definitely need to look into mqtt at some point though.
-
Ofc it has its PROs and CONs but I believe it is the way to go for the future.
-
I compiled the gateway for spi1 because I have a display using spi0. Two problems I came across:
- the master branch doesn't work. It compiles, it seems to work but it never receives anything.
- the development branch works but I needed to define the right cs-pin even if I redirected the pin in config.txt (with
dtoverlay=spi1-1cs,cs0_pin=16)
The following configure worked for me:
./configure --spi-driver=SPIDEV --spi-spidev-device=/dev/spidev1.0 --my-rf24-cs-pin=36 --my-rf24-ce-pin=33 --my-rf24-irq-pin=31
-
For the ones having problems with the stable build (Version 2.1.1), always getting "mysgw: !TSM:INIT:TSP FAIL":
Seems there is a bug, you have to install "development" (Version 2.2.0)
Maybe someone adds an note on top of the tutorial, so others won´t also spend hours in searching for the problem on their Pi/Hardware.
-
So far it looks to me it is something related to the latest versions of Linux since it was working on older releases
-
@gohan ah okay wasn´t aware of it, as the dev channel worked I assumed the bug at MySensors.
However, would be awesome if there were a little hint in the tutorial. Took plenty of time to find out it was an software incompability
-
A little hint in the tutorial would have saved me a lot of time too.
-
I added a comment; I hope my English is sufficiently clear
-
Today my rPi gateway (2.1.1 stable) completely stopped working as a service (cli surprisingly worked), I thought that could be some debian update so I switched to devel, but when building it I get this:
LINUX_ARCH_RASPBERRYPI -DMY_PORT=5003 -DMY_RX_MESSAGE_BUFFER_FEATURE -DMY_RF24_IRQ_PIN=18 -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/BCM/bcm2835.c -o build/drivers/BCM/bcm2835.o
drivers/BCM/bcm2835.c: In function ‘bcm2835_delayMicroseconds’:
drivers/BCM/bcm2835.c:441:40: error: expected ‘)’ before ‘PRIu64’
printf("bcm2835_delayMicroseconds %" PRIu64 "\n", micros);
^
drivers/BCM/bcm2835.c:441:40: warning: spurious trailing ‘%’ in format [-Wformat=]
Makefile:102: recipe for target 'build/drivers/BCM/bcm2835.o' failed
make: *** [build/drivers/BCM/bcm2835.o] Error 1Is this normal? I used the same configure was working before.
-
@Sergio-Rius a fix is available at https://github.com/mysensors/MySensors/pull/983
It is a one line change so you can just add it manually
-
Thaaanksss! I'll give it a go
-
@mfalkvidd Mmmmm... that worked, but now I'm always getting "mysgw: !TSM:INIT:TSP FAIL" as stated avobe. But I'm on development.
Wait, seems that after the 8'th intent it's working. I'll let him go and see.
-
I'm afraid that after some time it stops working. I get in Domoticz:
2017-11-12 19:17:01.744 MySensors: trying to connect to: 127.0.0.1:5003
2017-11-12 19:17:02.744 TCP: Connection problem (Unable to connect to specified IP/Port)
2017-11-12 19:17:02.744 TCP: Reconnecting in 30 seconds...Over and over again.
$ sudo systemctl status mysgw.service
● mysgw.service - MySensors Gateway daemon
Loaded: loaded (/etc/systemd/system/mysgw.service; enabled)
Active: failed (Result: signal) since dom 2017-11-12 19:16:53 CET; 5min ago
Process: 491 ExecStart=/usr/local/bin/mysgw (code=killed, signal=SEGV)
Main PID: 491 (code=killed, signal=SEGV)
nov 12 19:16:47 Domoticz systemd[1]: Started MySensors Gateway daemon.
nov 12 19:16:48 Domoticz mysgw[491]: Starting gateway...
nov 12 19:16:48 Domoticz mysgw[491]: Protocol version - 2.2.0-rc.1
nov 12 19:16:53 Domoticz systemd[1]: mysgw.service: main process exited, code=killed, status=11/SEGV
nov 12 19:16:53 Domoticz systemd[1]: Unit mysgw.service entered failed state.But it seems Domoticz being crashing it.
If I do restart the service, Domoticz picks it and works for a while.2017-11-12 19:24:17.562 TCP: Connection problem (Unable to connect to specified IP/Port)
2017-11-12 19:24:17.562 TCP: Reconnecting in 30 seconds...
2017-11-12 19:24:47.565 TCP: Reconnecting...
2017-11-12 19:24:47.565 MySensors: connected to: 127.0.0.1:5003
2017-11-12 19:24:48.566 MySensors: Gateway Ready...
2017-11-12 19:24:48.566 MySensors: Gateway Version: 2.2.0-rc.1
2017-11-12 19:24:49.566 MySensors: Gateway Version: 2.2.0-rc.1Is there any further log for exactly seeing what is the crash cause?
EDIT: Also it seems that there's any comunication at all. I only get internal heartbeats on MysController.
-
Did you get the latest version from development branch?
-
@gohan Yep! I exactly ran this command:
git clone https://github.com/mysensors/MySensors.git --branch development && cd MySensorsI'm now powering off my rPi for changing the PA+LNA radio for a standard one and bypassing the power regulator.
EDIT: I've done the above tasks and still getting strange things. It may be Domoticz as:
2017-11-12 19:44:37.634 MySensors: trying to connect to: 127.0.0.1:5003
2017-11-12 19:44:37.638 RFXCOM: Using serial port: /dev/ttyUSB0
2017-11-12 19:44:38.213
2017-11-12 19:44:38.288 Error: RFXCOM: Invalid data received!....
2017-11-12 19:44:38.635 MySensors: connected to: 127.0.0.1:5003
2017-11-12 19:44:38.635 MySensors: Gateway Ready...
2017-11-12 19:44:39.635 MySensors: Gateway Version: 2.2.0-rc.1
2017-11-12 19:44:39.635 MySensors: Gateway Version: 2.2.0-rc.1
...
2017-11-12 20:26:00.153 Error: Scheduler thread seems to have ended unexpectedly
2017-11-12 20:26:00.154 Error: MySGW_NRF hardware (9) thread seems to have ended unexpectedly
2017-11-12 20:26:00.154 Error: RFXCOM hardware (15) thread seems to have ended unexpectedly
2017-11-12 20:26:00.154 Error: RFXCOM hardware (15) nothing received for more than 30 Minutes!....
2017-11-12 20:26:01.155 Error: Restarting: RFXCOM
2017-11-12 20:26:01.707 RFXCOM: Serial Worker stopped...
2017-11-12 20:26:02.722 RFXCOM: Using serial port: /dev/ttyUSB0
2017-11-12 20:26:03.297
2017-11-12 20:26:03.372 Error: RFXCOM: Invalid data received!....
2017-11-12 20:26:16.745 (RFXCOM) Temp + Humidity (Biblioteca [TH])
2017-11-12 20:26:48.745 Error: PROXY: timeout occurred, reconnecting
2017-11-12 20:26:54.716 (MySGW_NRF) Temp (Temp)
2017-11-12 20:26:54.717 (MySGW_NRF) Temp + Humidity (TempHum)
...
and stabilized
-
If you keep a myscontroller connected to the gateway, does it stays connected or does it get disconnected at the same time as domoticz? Also try to run the gateway from console with debug enabled so you can actually see what it is doing
-
Possibly same problem with Domoticz here too. Using a directly attached NRF24 radio to a Raspberry Pi Zero W.
I tried to remake using the latest dev code, and got this error:
gcc -MT build/drivers/BCM/bcm2835.o -MMD -MP -march=armv6zk -mtune=arm1176jzf-s -mfpu=vfp -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_LINUX -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_PORT=5003 -DMY_RF24_PA_LEVEL=RF24_PA_LOW -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/BCM/bcm2835.c -o build/drivers/BCM/bcm2835.o drivers/BCM/bcm2835.c: In function ‘bcm2835_delayMicroseconds’: drivers/BCM/bcm2835.c:441:40: error: expected ‘)’ before ‘PRIu64’ printf("bcm2835_delayMicroseconds %" PRIu64 "\n", micros); ^ drivers/BCM/bcm2835.c:441:40: warning: spurious trailing ‘%’ in format [-Wformat=] Makefile:102: recipe for target 'build/drivers/BCM/bcm2835.o' failed make: *** [build/drivers/BCM/bcm2835.o] Error 1// commenting out the problem allowed make to finish:
//if (debug) { // /* Cant access sytem timers in debug mode */ // printf("bcm2835_delayMicroseconds %" PRIu64 "\n", micros); // return; //}This is my config:
./configure --my-transport=nrf24 --my-rf24-pa-level=RF24_PA_LOW --my-gateway=ethernet --my-port=5003
-
Hello all!
I'm trying to build a gateway with a Raspberry pi2, ethernet and Domoticz.
It looks like the gateway is beeing built ok and seems to run fine but nodes can not communicate with it.
I have read most of the postings here but I can not find any solution.
Hope you guys can help? Please!I run raspbian (Jessie) pi@raspberrypi:~/MySensors/bin $ uname -a Linux raspberrypi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/LinuxUsing master branch
https://www.mysensors.org/build/raspberry git clone https://github.com/mysensors/MySensors.git --branch masterConfiguring like this
pi@raspberrypi:~/MySensors $ ./configure --my-gateway=ethernet --my-port=5003 --my-transport=nrf24 --my-rf24-ce-pin=22 --my-rf24-cs-pin=24 [SECTION] Detecting target machine. [OK] machine detected: SoC=unknown, Type=unknown, CPU=armv7l. [SECTION] Checking GPIO Sysfs. [OK] /sys/class/gpio/export found [SECTION] Detecting SPI driver. [OK] SPI driver detected:SPIDEV. [SECTION] Detecting init system. [OK] init system detected: systemd. [SECTION] Saving configuration. [SECTION] Cleaning previous builds. [OK] Finished.Obs! No Raspberry identification, why not? Maybe that is the culprit?
After make I start the gateway and get this:pi@raspberrypi:~/MySensors $ cd bin pi@raspberrypi:~/MySensors/bin $ sudo ./mysgw -d mysgw: Starting gateway... mysgw: Protocol version - 2.1.1 mysgw: MCO:BGN:INIT GW,CP=RNNG---,VER=2.1.1 mysgw: TSM:INIT mysgw: TSF:WUR:MS=0 mysgw: TSM:INIT:TSP OK mysgw: TSM:INIT:GW MODE mysgw: TSM:READY:ID=0,PAR=0,DIS=0 mysgw: MCO:REG:NOT NEEDED mysgw: Listening for connections on 0.0.0.0:5003 mysgw: MCO:BGN:STP mysgw: MCO:BGN:INIT OK,TSP=1 mysgw: New connection from 127.0.0.1 mysgw: Client 0 connected mysgw: Client 0: 0;0;3;0;2; mysgw: Client 0: 0;0;3;0;2;Get Version mysgw: Client 0: 0;0;3;0;18;PINGSeems nice and dandy and Domoticz connecting fine.
Trying with this example node:#define MY_RADIO_NRF24 #define MY_RF24_PA_LEVEL RF24_PA_LOW #define MY_DEBUG #define MY_NODE_ID 42 //#define MY_DEBUG_VERBOSE_RF24 #define MY_BAUD_RATE 9600 #include <MySensors.h> #include<Arduino.h> #define OPEN 1 #define CLOSE 0 #define CHILD_ID 1 MyMessage msg(CHILD_ID, V_TRIPPED); uint8_t value = OPEN; void setup() { Serial.print("setup()\n"); } void presentation() { sendSketchInfo("Door", "2.1.1"); present(CHILD_ID, S_DOOR); Serial.print("presentation()\n"); } void loop() { value = value == OPEN ? CLOSE : OPEN; send(msg.set(value)); Serial.print("message sent"); Serial.print(value + "\n"); sleep(1000); }And recieve this when running:
--- Miniterm on /dev/ttyUSB0 9600,8,N,1 --- --- Quit: Ctrl+C | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H --- 0 MCO:BGN:INIT NODE,CP=RNNNA--,VER=2.1.1 40 TSM:INIT 55 TSF:WUR:MS=0 77 TSM:INIT:TSP OK 96 TSM:INIT:STATID=42 120 TSF:SID:OK,ID=42 141 TSM:FPAR 190 TSF:MSG:SEND,42-42-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK: 2267 !TSM:FPAR:NO REPLY 2291 TSM:FPAR 2340 TSF:MSG:SEND,42-42-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK: 4417 !TSM:FPAR:NO REPLY 4442 TSM:FPAR 4491 TSF:MSG:SEND,42-42-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK: 6569 !TSM:FPAR:NO REPLY 6594 TSM:FPAR 6643 TSF:MSG:SEND,42-42-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK: 8720 !TSM:FPAR:FAIL 8740 TSM:FAIL:CNT=1 8761 TSM:FAIL:PDTAnd no output in gateway either.
Both radio modules using capacitors.What have I missed?
Thanks, Andreas!
-
I tried for months to get a stable working nrf24 attached to pi to act as a gw and controller.
In the end I gave up and now have a 3.3V 8MHz pro mini gw attached to the pi. I took 0v and 5v from the pi (via a 3.3v buck converter) and serial tx and rx. Only 4 wires needed and has been as stable as can be for over a week now.
Maybe help someone with the same unsolveable problems?
-
@aglock I put a note on the raspberry gateway page to use latest development in case of problems with stable. Did you try?
-
@gohan yes. Interesting though when I used git to switch between branches it said all files where the same?
Do you think the fault is in the gateway somehow?
-
@gohan Tried it again
configure now recognizes the rpi:pi@raspberrypi:~/mys_dev $ ./configure --my-gateway=ethernet --my-port=5003 --my-transport=nrf24 --my-rf24-ce-pin=22 --my-rf24-cs-pin=24 [SECTION] Detecting target machine. [OK] machine detected: SoC=BCM2836, Type=rpi2, CPU=armv7l. [SECTION] Detecting SPI driver. [OK] SPI driver detected:BCM. [SECTION] Detecting init system. [OK] init system detected: systemd. [SECTION] Saving configuration. [SECTION] Cleaning previous builds. [OK] Finished.But make fails with the following error:
-I./core -I./drivers/Linux -I./drivers/BCM -c drivers/BCM/bcm2835.c -o build/drivers/BCM/bcm2835.o drivers/BCM/bcm2835.c: In function ‘bcm2835_delayMicroseconds’: drivers/BCM/bcm2835.c:441:40: error: expected ‘)’ before ‘PRIu64’ printf("bcm2835_delayMicroseconds %" PRIu64 "\n", micros); ^ drivers/BCM/bcm2835.c:441:40: warning: spurious trailing ‘%’ in format [-Wformat=] Makefile:102: recipe for target 'build/drivers/BCM/bcm2835.o' failed make: *** [build/drivers/BCM/bcm2835.o] Error 1 pi@raspberrypi:~/mys_dev $What to do about it?
-
-
@mfalkvidd Wow, thanks that works!
-
Got mysensors gateway working on gpio of my Pi again using ./configure --my-transport=nrf24 --my-rf24-irq-pin=15 --my-leds-err-pin=12 --my-leds-rx-pin=16 --my-leds-tx-pin=18 --my-gateway=ethernet --my-port=5003
However on tx or tx always the two leds connected to pin 16 and 18 are lit. More people with the same problem?
-
@Woeka There is (on Arduino Gateway) a function named "DEFINE INVERSE BLINK". Try to search for same for PI....
-
Can we use the "debug ota log" features with the raspberryPi gateway ??
My node is not accessible and runs MYSBootloader.
My gateway is raspberryPI.Now, I need to update the firmware on my node. Via MYSController, no problems, upload runs like a charm.
But how to do for debugging my sketch ? Some bugs appear...... , I need to take a look on some vars values.
Usually, I use the serial port with serial.print(some vars).
Which alternative I have to use without serial port, only OTA features ?Thanks for the great work !!
-
Unless you are using an esp8266, I don't think you can remote debug a pro mini. @sundberg84 is working on a serial logger to microsd card, maybe it could help you in some way
-
In fact, I do not need to log, but need to look what's happen in my sketch.
The new "OTALog" function, MY_OTA_LOG_SENDER_FEATURE or MY_DEBUG_OTA seems to be the good way.
From the docs, it allows to send a debug message to another node or gateway via OTA.But how to got the debug message from OTA node, on the gateway side (RaspberryPi) ?
-
@romeo01 said in
Building a Raspberry Pi Gateway:MY_DEBUG_OTA
I'd start reading from here https://www.mysensors.org/apidocs-beta/group__SerialDebugGrpPub.html#ga6bd5956352d3a184a0cb02783b8d35ff
-
@gohan said in
Building a Raspberry Pi Gateway:@romeo01 said in
Building a Raspberry Pi Gateway:MY_DEBUG_OTA
I'd start reading from here https://www.mysensors.org/apidocs-beta/group__SerialDebugGrpPub.html#ga6bd5956352d3a184a0cb02783b8d35ff
Well, you found the starting point !
MY_OTA_LOG_SENDER_FEATURE & MY_DEBUG_OTA are enabled on my OTA node.
Again the same question: What I have to do on the gateway side ?
Is it possible with the raspberry Gateway ?I'm still looking for debugging my sketch in remote. I need to have a look on the debug messages. I reminder, the node is not accessible and runs MYSbootloader.
-
If I understood well, you need to set a target node ID that will receive the debug and then make a node with that ID in order to get the debug messages
-
Exactly, but I would like to use the gateway (raspberry) as target.
Is that possible ?
If yes, how to display the debug message on the gateway.
I have an access to my gateway only via SSH.
-
I have no idea if can do it, but you could just have a node connected to USB port of the rpi and do a "cat" on the USB port and you can read the debug from the node
-
Is it possible to build a gateway that is MQTT, but also listens on port 5003? I want to send my data up to AWS IoT, but I also need port 5003 for Vera integration.
-
You can use node-red to bridge the ethernet gateway and the aws service. Are you sure vera plug in doesn't support mqtt?
-
@gohan, there are two MQTT plugins for the Vera with varying capabilities. But, the mysensors plugin for Vera doesn't appear to support MQTT at all. I could probably get one of those MQTT plugins working, but I'm not sure how stable they are. I hate installing unstable plugins and having them crash LUUP. I need to maintain a positive WAF (Wife Acceptance Factor), and broken HA doesn't help with that.
-
I guess node-red is the best option for you
-
Hi
I start build MySensors Gateway on my Rpi3. I use radio RFM69HW and connected it as show on page to GPIO.
https://www.mysensors.org/build/raspberry
I build it by command:
./configure --my-transport=rfm69 --my-rfm69-frequency=868 --my-is-rfm69hw --my-gateway=serial --my-serial-is-pty --my-serial-pty=/dev/ttyUSB1Then make. But in Domoticz when i run and add to hardware i have error:
2017-12-27 17:05:09.419 MySensors: Using serial port: /dev/ttyUSB1
2017-12-27 17:05:09.419 MySensors: Gateway Version: 2.2.0-rc.2
2017-12-27 17:05:09.420 Error: Serial Port closed!... Error: End of file
2017-12-27 17:05:10.419 MySensors: retrying in 30 seconds...
2017-12-27 17:05:39.422 MySensors: Using serial port: /dev/ttyUSB1
2017-12-27 17:05:39.422 Error: Serial Port closed!... Error: End of file
2017-12-27 17:05:40.422 MySensors: retrying in 30 seconds...
2017-12-27 17:06:09.425 MySensors: Using serial port: /dev/ttyUSB1
2017-12-27 17:06:09.425 Error: Serial Port closed!... Error: End of file
2017-12-27 17:06:10.425 MySensors: retrying in 30 seconds...
2017-12-27 17:06:39.427 MySensors: Using serial port: /dev/ttyUSB1
2017-12-27 17:06:39.428 Error: Serial Port closed!... Error: End of file
2017-12-27 17:06:40.428 MySensors: retrying in 30 seconds...
2017-12-27 17:07:09.430 MySensors: Using serial port: /dev/ttyUSB1
2017-12-27 17:07:09.430 Error: Serial Port closed!... Error: End of fileport ttyUSB1 is empty as i check.
Please help me where is the problem...
-
-
mysgw: Starting gateway...
mysgw: Protocol version - 2.2.0-rc2
mysgw: MCO:BGN:INIT GW,CP=RNNG---,VER=2.2.0-rc2
mysgw: TSF:LRT:OK
mysgw: TSM:INIT
mysgw: TSF:WUR:MS=0
mysgw: TSM:INIT:TSP OK
mysgw: TSM:INIT:GW MODE
mysgw: TSM:READY:ID=0,PAR=0,DIS=0
mysgw: MCO:REG:NOT NEEDED
mysgw: MCO:BGN:STP
mysgw: MCO:BGN:INIT OK,TSP=1
-
@pepson thanks. Nothing strange there. Anything i teresting in var/log/syslog after enabling debug output?
-
Dec 27 21:11:48 domoticz systemd[1]: Stopping User Manager for UID 1000... Dec 27 21:11:48 domoticz systemd[715]: Stopped target Default. Dec 27 21:11:48 domoticz systemd[715]: Stopped target Basic System. Dec 27 21:11:48 domoticz systemd[715]: Stopped target Sockets. Dec 27 21:11:48 domoticz systemd[715]: Closed GnuPG cryptographic agent (access for web browsers). Dec 27 21:11:48 domoticz systemd[715]: Stopped target Paths. Dec 27 21:11:48 domoticz systemd[715]: Closed GnuPG cryptographic agent and passphrase cache (restricted). Dec 27 21:11:48 domoticz systemd[715]: Closed GnuPG cryptographic agent and passphrase cache. Dec 27 21:11:48 domoticz systemd[715]: Stopped target Timers. Dec 27 21:11:48 domoticz systemd[715]: Closed GnuPG cryptographic agent (ssh-agent emulation). Dec 27 21:11:48 domoticz systemd[715]: Reached target Shutdown. Dec 27 21:11:48 domoticz systemd[715]: Starting Exit the Session... Dec 27 21:11:48 domoticz systemd[715]: Received SIGRTMIN+24 from PID 800 (kill). Dec 27 21:11:48 domoticz systemd[1]: Stopped User Manager for UID 1000. Dec 27 21:11:48 domoticz systemd[1]: Removed slice User Slice of pi. Dec 27 21:11:54 domoticz systemd[1]: Stopping Save/Restore Sound Card State... Dec 27 21:11:54 domoticz systemd[1]: Unmounting RPC Pipe File System... Dec 27 21:11:54 domoticz systemd[1]: Stopped target Graphical Interface. Dec 27 21:12:27 domoticz systemd-modules-load[125]: Inserted module 'i2c_dev' Dec 27 21:12:27 domoticz fake-hwclock[115]: Wed 27 Dec 20:12:25 UTC 2017 Dec 27 21:12:27 domoticz systemd[1]: Mounted Configuration File System. Dec 27 21:12:27 domoticz systemd[1]: Started Apply Kernel Variables. Dec 27 21:12:27 domoticz systemd-fsck[127]: e2fsck 1.43.4 (31-Jan-2017) Dec 27 21:12:27 domoticz systemd[1]: Started Create Static Device Nodes in /dev. Dec 27 21:12:27 domoticz systemd[1]: Starting udev Kernel Device Manager... Dec 27 21:12:27 domoticz systemd-fsck[127]: rootfs: clean, 54121/474240 files, 431837/1933824 blocks Dec 27 21:12:27 domoticz systemd[1]: Started File System Check on Root Device. Dec 27 21:12:27 domoticz systemd[1]: Starting Remount Root and Kernel File Systems... Dec 27 21:12:27 domoticz systemd[1]: Started Remount Root and Kernel File Systems. Dec 27 21:12:27 domoticz systemd[1]: Starting Load/Save Random Seed... Dec 27 21:12:27 domoticz systemd[1]: Starting udev Coldplug all Devices... Dec 27 21:12:27 domoticz systemd[1]: Starting Flush Journal to Persistent Storage... Dec 27 21:12:27 domoticz systemd[1]: Started Flush Journal to Persistent Storage. Dec 27 21:12:27 domoticz systemd[1]: Started Load/Save Random Seed. Dec 27 21:12:27 domoticz systemd[1]: Started udev Kernel Device Manager. Dec 27 21:12:27 domoticz systemd[1]: Started Set the console keyboard layout. Dec 27 21:12:27 domoticz systemd[1]: Reached target Local File Systems (Pre). Dec 27 21:12:27 domoticz systemd[1]: Started udev Coldplug all Devices. Dec 27 21:12:27 domoticz systemd[1]: Starting Show Plymouth Boot Screen... Dec 27 21:12:27 domoticz systemd[1]: Received SIGRTMIN+20 from PID 190 (plymouthd). Dec 27 21:12:27 domoticz systemd[1]: Started Show Plymouth Boot Screen. Dec 27 21:12:27 domoticz systemd[1]: Found device /dev/disk/by-partuuid/e80766f2-01. Dec 27 21:12:27 domoticz systemd[1]: Starting File System Check on /dev/disk/by-partuuid/e80766f2-01... Dec 27 21:12:27 domoticz systemd[1]: Started Forward Password Requests to Plymouth Directory Watch. Dec 27 21:12:27 domoticz systemd[1]: Reached target Encrypted Volumes. Dec 27 21:12:27 domoticz systemd[1]: Reached target Paths. Dec 27 21:12:27 domoticz mtp-probe: checking bus 1, device 3: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1" Dec 27 21:12:27 domoticz mtp-probe: bus: 1, device: 3 was not an MTP device Dec 27 21:12:27 domoticz systemd[1]: Reached target Sound Card. Dec 27 21:12:27 domoticz systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. Dec 27 21:12:27 domoticz systemd[1]: Starting Load/Save RF Kill Switch Status... Dec 27 21:12:27 domoticz systemd-fsck[227]: fsck.fat 4.1 (2017-01-24) Dec 27 21:12:27 domoticz systemd-fsck[227]: /dev/mmcblk0p1: 150 files, 42691/83705 clusters Dec 27 21:12:27 domoticz systemd[1]: Started File System Check on /dev/disk/by-partuuid/e80766f2-01. Dec 27 21:12:27 domoticz systemd[1]: Mounting /boot... Dec 27 21:12:27 domoticz systemd[1]: Started Load/Save RF Kill Switch Status. Dec 27 21:12:27 domoticz systemd[1]: Mounted /boot. Dec 27 21:12:27 domoticz systemd[1]: Reached target Local File Systems. Dec 27 21:12:27 domoticz systemd[1]: Starting Preprocess NFS configuration... Dec 27 21:12:27 domoticz systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... Dec 27 21:12:27 domoticz systemd[1]: Starting Set console font and keymap... Dec 27 21:12:27 domoticz systemd[1]: Starting Raise network interfaces... Dec 27 21:12:27 domoticz systemd[1]: Starting Create Volatile Files and Directories... Dec 27 21:12:27 domoticz systemd[1]: Started Tell Plymouth To Write Out Runtime Data. Dec 27 21:12:27 domoticz systemd[1]: Started Preprocess NFS configuration. Dec 27 21:12:27 domoticz systemd[1]: Reached target NFS client services. Dec 27 21:12:27 domoticz systemd[1]: Reached target Remote File Systems (Pre). Dec 27 21:12:27 domoticz systemd[1]: Reached target Remote File Systems. Dec 27 21:12:27 domoticz systemd[1]: Started Set console font and keymap. Dec 27 21:12:27 domoticz systemd[1]: Started Create Volatile Files and Directories. Dec 27 21:12:27 domoticz systemd[1]: Starting Network Time Synchronization... Dec 27 21:12:27 domoticz systemd[1]: Starting Update UTMP about System Boot/Shutdown... Dec 27 21:12:27 domoticz systemd[1]: Started Update UTMP about System Boot/Shutdown. Dec 27 21:12:27 domoticz systemd[1]: Started Raise network interfaces. Dec 27 21:12:27 domoticz systemd[1]: Started Network Time Synchronization. Dec 27 21:12:27 domoticz systemd[1]: Reached target System Initialization. Dec 27 21:12:27 domoticz systemd[1]: Started Daily Cleanup of Temporary Directories. Dec 27 21:12:27 domoticz systemd[1]: Listening on D-Bus System Message Bus Socket. Dec 27 21:12:27 domoticz systemd[1]: Listening on triggerhappy.socket. Dec 27 21:12:27 domoticz systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket. Dec 27 21:12:27 domoticz systemd[1]: Reached target Sockets. Dec 27 21:12:27 domoticz systemd[1]: Reached target Basic System. Dec 27 21:12:27 domoticz systemd[1]: Starting LSB: Start OWFS at boot time... Dec 27 21:12:27 domoticz systemd[1]: Starting Login Service... Dec 27 21:12:27 domoticz systemd[1]: Starting Avahi mDNS/DNS-SD Stack... Dec 27 21:12:27 domoticz systemd[1]: Started Regular background program processing daemon. Dec 27 21:12:27 domoticz systemd[1]: Starting LSB: Autogenerate and use a swap file... Dec 27 21:12:27 domoticz systemd[1]: Starting LSB: Switch to ondemand cpu governor (unless shift key is pressed)... Dec 27 21:12:27 domoticz systemd[1]: Starting triggerhappy global hotkey daemon... Dec 27 21:12:27 domoticz systemd[1]: Started MySensors Gateway daemon. Dec 27 21:12:27 domoticz systemd[1]: Starting System Logging Service... Dec 27 21:12:27 domoticz systemd[1]: Starting Save/Restore Sound Card State... Dec 27 21:12:27 domoticz systemd[1]: Starting dhcpcd on all interfaces... Dec 27 21:12:27 domoticz systemd[1]: Started D-Bus System Message Bus. Dec 27 21:12:27 domoticz cron[328]: (CRON) INFO (pidfile fd = 3) Dec 27 21:12:27 domoticz cron[328]: (CRON) INFO (Running @reboot jobs) Dec 27 21:12:27 domoticz thd[331]: Found socket passed from systemd Dec 27 21:12:27 domoticz dhcpcd[339]: dev: loaded udev Dec 27 21:12:27 domoticz mysgw: Starting gateway... Dec 27 21:12:27 domoticz mysgw: Protocol version - 2.2.0-rc.2 Dec 27 21:12:27 domoticz avahi-daemon[327]: Found user 'avahi' (UID 108) and group 'avahi' (GID 112). Dec 27 21:12:27 domoticz avahi-daemon[327]: Successfully dropped root privileges. Dec 27 21:12:27 domoticz avahi-daemon[327]: avahi-daemon 0.6.32 starting up. Dec 27 21:12:27 domoticz liblogging-stdlog: [origin software="rsyslogd" swVersion="8.24.0" x-pid="334" x-info="http://www.rsyslog.com"] start Dec 27 21:12:27 domoticz kernel: [ 0.000000] Booting Linux on physical CPU 0x0 Dec 27 21:12:27 domoticz kernel: [ 0.000000] Linux version 4.9.70-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #1068 SMP Mon Dec 18 22:12:55 GMT 2017 Dec 27 21:12:27 domoticz kernel: [ 0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d Dec 27 21:12:27 domoticz kernel: [ 0.000000] CPU: div instructions available: patching division code Dec 27 21:12:27 domoticz kernel: [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache Dec 27 21:12:27 domoticz kernel: [ 0.000000] OF: fdt:Machine model: Raspberry Pi 3 Model B Rev 1.2 Dec 27 21:12:27 domoticz kernel: [ 0.000000] cma: Reserved 8 MiB at 0x3dc00000 Dec 27 21:12:27 domoticz kernel: [ 0.000000] Memory policy: Data cache writealloc Dec 27 21:12:27 domoticz kernel: [ 0.000000] On node 0 totalpages: 255488 Dec 27 21:12:27 domoticz kernel: [ 0.000000] free_area_init_node: node 0, pgdat 80c6f400, node_mem_map bd336000 Dec 27 21:12:27 domoticz kernel: [ 0.000000] Normal zone: 2246 pages used for memmap Dec 27 21:12:27 domoticz kernel: [ 0.000000] Normal zone: 0 pages reserved Dec 27 21:12:27 domoticz kernel: [ 0.000000] Normal zone: 255488 pages, LIFO batch:31 Dec 27 21:12:27 domoticz kernel: [ 0.000000] percpu: Embedded 14 pages/cpu @be5b0000 s25600 r8192 d23552 u57344 Dec 27 21:12:27 domoticz kernel: [ 0.000000] pcpu-alloc: s25600 r8192 d23552 u57344 alloc=14*4096 Dec 27 21:12:27 domoticz kernel: [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 Dec 27 21:12:27 domoticz kernel: [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 253242 Dec 27 21:12:27 domoticz kernel: [ 0.000000] Kernel command line: 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3f000000 vc_mem.mem_size=0x3f600000 dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=e80766f2-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait Dec 27 21:12:27 domoticz kernel: [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes) Dec 27 21:12:27 domoticz kernel: [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Dec 27 21:12:27 domoticz kernel: [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Dec 27 21:12:27 domoticz kernel: [ 0.000000] Memory: 991096K/1021952K available (7168K kernel code, 486K rwdata, 2012K rodata, 1024K init, 770K bss, 22664K reserved, 8192K cma-reserved) Dec 27 21:12:27 domoticz kernel: [ 0.000000] Virtual kernel memory layout: Dec 27 21:12:27 domoticz kernel: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) Dec 27 21:12:27 domoticz kernel: [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB) Dec 27 21:12:27 domoticz kernel: [ 0.000000] vmalloc : 0xbe800000 - 0xff800000 (1040 MB) Dec 27 21:12:27 domoticz kernel: [ 0.000000] lowmem : 0x80000000 - 0xbe600000 ( 998 MB) Dec 27 21:12:27 domoticz kernel: [ 0.000000] modules : 0x7f000000 - 0x80000000 ( 16 MB) Dec 27 21:12:27 domoticz kernel: [ 0.000000] .text : 0x80008000 - 0x80800000 (8160 kB) Dec 27 21:12:27 domoticz kernel: [ 0.000000] .init : 0x80b00000 - 0x80c00000 (1024 kB) Dec 27 21:12:27 domoticz kernel: [ 0.000000] .data : 0x80c00000 - 0x80c798bc ( 487 kB) Dec 27 21:12:27 domoticz kernel: [ 0.000000] .bss : 0x80c7b000 - 0x80d3b9a4 ( 771 kB) Dec 27 21:12:27 domoticz kernel: [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 Dec 27 21:12:27 domoticz kernel: [ 0.000000] Hierarchical RCU implementation. Dec 27 21:12:27 domoticz kernel: [ 0.000000] Build-time adjustment of leaf fanout to 32. Dec 27 21:12:27 domoticz kernel: [ 0.000000] NR_IRQS:16 nr_irqs:16 16 Dec 27 21:12:27 domoticz kernel: [ 0.000000] arm_arch_timer: Architected cp15 timer(s) running at 19.20MHz (phys). Dec 27 21:12:27 domoticz kernel: [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns Dec 27 21:12:27 domoticz kernel: [ 0.000006] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns Dec 27 21:12:27 domoticz kernel: [ 0.000022] Switching to timer-based delay loop, resolution 52ns Dec 27 21:12:27 domoticz kernel: [ 0.000304] Console: colour dummy device 80x30 Dec 27 21:12:27 domoticz kernel: [ 0.001203] console [tty1] enabled Dec 27 21:12:27 domoticz kernel: [ 0.001250] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000) Dec 27 21:12:27 domoticz kernel: [ 0.001318] pid_max: default: 32768 minimum: 301 Dec 27 21:12:27 domoticz kernel: [ 0.001653] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) Dec 27 21:12:27 domoticz kernel: [ 0.001696] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) Dec 27 21:12:27 domoticz kernel: [ 0.002734] Disabling memory control group subsystem Dec 27 21:12:27 domoticz kernel: [ 0.002838] CPU: Testing write buffer coherency: ok Dec 27 21:12:27 domoticz kernel: [ 0.002901] ftrace: allocating 22400 entries in 66 pages Dec 27 21:12:27 domoticz kernel: [ 0.049380] CPU0: update cpu_capacity 1024 Dec 27 21:12:27 domoticz kernel: [ 0.049432] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 Dec 27 21:12:27 domoticz kernel: [ 0.049493] Setting up static identity map for 0x100000 - 0x100034 Dec 27 21:12:27 domoticz kernel: [ 0.051403] CPU1: update cpu_capacity 1024 Dec 27 21:12:27 domoticz kernel: [ 0.051410] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 Dec 27 21:12:27 domoticz kernel: [ 0.052106] CPU2: update cpu_capacity 1024 Dec 27 21:12:27 domoticz kernel: [ 0.052113] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 Dec 27 21:12:27 domoticz kernel: [ 0.052791] CPU3: update cpu_capacity 1024 Dec 27 21:12:27 domoticz kernel: [ 0.052798] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 Dec 27 21:12:27 domoticz kernel: [ 0.052887] Brought up 4 CPUs Dec 27 21:12:27 domoticz kernel: [ 0.053059] SMP: Total of 4 processors activated (153.60 BogoMIPS). Dec 27 21:12:27 domoticz kernel: [ 0.053089] CPU: All CPU(s) started in HYP mode. Dec 27 21:12:27 domoticz kernel: [ 0.053115] CPU: Virtualization extensions available. Dec 27 21:12:27 domoticz kernel: [ 0.053944] devtmpfs: initialized Dec 27 21:12:27 domoticz kernel: [ 0.065214] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4 Dec 27 21:12:27 domoticz kernel: [ 0.065538] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns Dec 27 21:12:27 domoticz kernel: [ 0.065601] futex hash table entries: 1024 (order: 4, 65536 bytes) Dec 27 21:12:27 domoticz kernel: [ 0.066163] pinctrl core: initialized pinctrl subsystem Dec 27 21:12:27 domoticz kernel: [ 0.067095] NET: Registered protocol family 16 Dec 27 21:12:27 domoticz kernel: [ 0.069334] DMA: preallocated 1024 KiB pool for atomic coherent allocations Dec 27 21:12:27 domoticz kernel: [ 0.078209] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. Dec 27 21:12:27 domoticz kernel: [ 0.078258] hw-breakpoint: maximum watchpoint size is 8 bytes. Dec 27 21:12:27 domoticz kernel: [ 0.078436] Serial: AMBA PL011 UART driver Dec 27 21:12:27 domoticz kernel: [ 0.080361] bcm2835-mbox 3f00b880.mailbox: mailbox enabled Dec 27 21:12:27 domoticz kernel: [ 0.080925] uart-pl011 3f201000.serial: could not find pctldev for node /soc/gpio@7e200000/uart0_pins, deferring probe Dec 27 21:12:27 domoticz kernel: [ 0.150223] bcm2835-dma 3f007000.dma: DMA legacy API manager at be80f000, dmachans=0x1 Dec 27 21:12:27 domoticz kernel: [ 0.152120] SCSI subsystem initialized Dec 27 21:12:27 domoticz kernel: [ 0.152301] usbcore: registered new interface driver usbfs Dec 27 21:12:27 domoticz kernel: [ 0.152411] usbcore: registered new interface driver hub Dec 27 21:12:27 domoticz kernel: [ 0.152527] usbcore: registered new device driver usb Dec 27 21:12:27 domoticz kernel: [ 0.159194] raspberrypi-firmware soc:firmware: Attached to firmware from 2017-12-01 16:17 Dec 27 21:12:27 domoticz kernel: [ 0.160594] clocksource: Switched to clocksource arch_sys_counter Dec 27 21:12:27 domoticz kernel: [ 0.207210] VFS: Disk quotas dquot_6.6.0 Dec 27 21:12:27 domoticz kernel: [ 0.207324] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Dec 27 21:12:27 domoticz kernel: [ 0.207555] FS-Cache: Loaded Dec 27 21:12:27 domoticz kernel: [ 0.207822] CacheFiles: Loaded Dec 27 21:12:27 domoticz kernel: [ 0.220056] NET: Registered protocol family 2 Dec 27 21:12:27 domoticz kernel: [ 0.220996] TCP established hash table entries: 8192 (order: 3, 32768 bytes) Dec 27 21:12:27 domoticz kernel: [ 0.221133] TCP bind hash table entries: 8192 (order: 4, 65536 bytes) Dec 27 21:12:27 domoticz kernel: [ 0.221344] TCP: Hash tables configured (established 8192 bind 8192) Dec 27 21:12:27 domoticz kernel: [ 0.221457] UDP hash table entries: 512 (order: 2, 16384 bytes) Dec 27 21:12:27 domoticz kernel: [ 0.221525] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) Dec 27 21:12:27 domoticz kernel: [ 0.221756] NET: Registered protocol family 1 Dec 27 21:12:27 domoticz kernel: [ 0.222236] RPC: Registered named UNIX socket transport module. Dec 27 21:12:27 domoticz kernel: [ 0.222269] RPC: Registered udp transport module. Dec 27 21:12:27 domoticz kernel: [ 0.222297] RPC: Registered tcp transport module. Dec 27 21:12:27 domoticz kernel: [ 0.222324] RPC: Registered tcp NFSv4.1 backchannel transport module. Dec 27 21:12:27 domoticz kernel: [ 0.223276] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available Dec 27 21:12:27 domoticz kernel: [ 0.225612] workingset: timestamp_bits=14 max_order=18 bucket_order=4 Dec 27 21:12:27 domoticz kernel: [ 0.241781] FS-Cache: Netfs 'nfs' registered for caching Dec 27 21:12:27 domoticz kernel: [ 0.242797] NFS: Registering the id_resolver key type Dec 27 21:12:27 domoticz kernel: [ 0.242860] Key type id_resolver registered Dec 27 21:12:27 domoticz kernel: [ 0.242888] Key type id_legacy registered Dec 27 21:12:27 domoticz kernel: [ 0.245340] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251) Dec 27 21:12:27 domoticz kernel: [ 0.245505] io scheduler noop registered Dec 27 21:12:27 domoticz kernel: [ 0.245535] io scheduler deadline registered (default) Dec 27 21:12:27 domoticz kernel: [ 0.245816] io scheduler cfq registered Dec 27 21:12:27 domoticz kernel: [ 0.251562] BCM2708FB: allocated DMA memory fdd10000 Dec 27 21:12:27 domoticz kernel: [ 0.251615] BCM2708FB: allocated DMA channel 0 @ be80f000 Dec 27 21:12:27 domoticz kernel: [ 0.256725] Console: switching to colour frame buffer device 82x26 Dec 27 21:12:27 domoticz kernel: [ 0.261582] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled Dec 27 21:12:27 domoticz kernel: [ 0.264453] bcm2835-rng 3f104000.rng: hwrng registered Dec 27 21:12:27 domoticz kernel: [ 0.265902] vc-mem: phys_addr:0x00000000 mem_base=0x3f000000 mem_size:0x3f600000(1014 MiB) Dec 27 21:12:27 domoticz kernel: [ 0.269187] vc-sm: Videocore shared memory driver Dec 27 21:12:27 domoticz kernel: [ 0.285964] brd: module loaded Dec 27 21:12:27 domoticz kernel: [ 0.296350] loop: module loaded Dec 27 21:12:27 domoticz kernel: [ 0.297737] Loading iSCSI transport class v2.0-870. Dec 27 21:12:27 domoticz kernel: [ 0.299603] usbcore: registered new interface driver smsc95xx Dec 27 21:12:27 domoticz kernel: [ 0.300990] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) Dec 27 21:12:27 domoticz kernel: [ 0.530382] Core Release: 2.80a Dec 27 21:12:27 domoticz kernel: [ 0.531748] Setting default values for core params Dec 27 21:12:27 domoticz kernel: [ 0.533143] Finished setting default values for core params Dec 27 21:12:27 domoticz kernel: [ 0.734883] Using Buffer DMA mode Dec 27 21:12:27 domoticz kernel: [ 0.736187] Periodic Transfer Interrupt Enhancement - disabled Dec 27 21:12:27 domoticz kernel: [ 0.737532] Multiprocessor Interrupt Enhancement - disabled Dec 27 21:12:27 domoticz kernel: [ 0.738902] OTG VER PARAM: 0, OTG VER FLAG: 0 Dec 27 21:12:27 domoticz kernel: [ 0.740281] Dedicated Tx FIFOs mode Dec 27 21:12:27 domoticz kernel: [ 0.742000] WARN::dwc_otg_hcd_init:1032: FIQ DMA bounce buffers: virt = 0xbdd04000 dma = 0xfdd04000 len=9024 Dec 27 21:12:27 domoticz kernel: [ 0.744889] FIQ FSM acceleration enabled for : Dec 27 21:12:27 domoticz kernel: [ 0.744889] Non-periodic Split Transactions Dec 27 21:12:27 domoticz kernel: [ 0.744889] Periodic Split Transactions Dec 27 21:12:27 domoticz kernel: [ 0.744889] High-Speed Isochronous Endpoints Dec 27 21:12:27 domoticz kernel: [ 0.744889] Interrupt/Control Split Transaction hack enabled Dec 27 21:12:27 domoticz kernel: [ 0.751657] dwc_otg: Microframe scheduler enabled Dec 27 21:12:27 domoticz kernel: [ 0.751707] WARN::hcd_init_fiq:459: FIQ on core 1 at 0x80590aa0 Dec 27 21:12:27 domoticz kernel: [ 0.753058] WARN::hcd_init_fiq:460: FIQ ASM at 0x80590e10 length 36 Dec 27 21:12:27 domoticz kernel: [ 0.754417] WARN::hcd_init_fiq:486: MPHI regs_base at 0xbe87a000 Dec 27 21:12:27 domoticz kernel: [ 0.755813] dwc_otg 3f980000.usb: DWC OTG Controller Dec 27 21:12:27 domoticz kernel: [ 0.757179] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1 Dec 27 21:12:27 domoticz kernel: [ 0.758567] dwc_otg 3f980000.usb: irq 62, io mem 0x00000000 Dec 27 21:12:27 domoticz kernel: [ 0.759940] Init: Port Power? op_state=1 Dec 27 21:12:27 domoticz kernel: [ 0.761277] Init: Power Port (0) Dec 27 21:12:27 domoticz kernel: [ 0.762752] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 Dec 27 21:12:27 domoticz kernel: [ 0.764101] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Dec 27 21:12:27 domoticz kernel: [ 0.765440] usb usb1: Product: DWC OTG Controller Dec 27 21:12:27 domoticz kernel: [ 0.766751] usb usb1: Manufacturer: Linux 4.9.70-v7+ dwc_otg_hcd Dec 27 21:12:27 domoticz kernel: [ 0.768074] usb usb1: SerialNumber: 3f980000.usb Dec 27 21:12:27 domoticz kernel: [ 0.770222] hub 1-0:1.0: USB hub found Dec 27 21:12:27 domoticz kernel: [ 0.771542] hub 1-0:1.0: 1 port detected Dec 27 21:12:27 domoticz kernel: [ 0.773419] dwc_otg: FIQ enabled Dec 27 21:12:27 domoticz kernel: [ 0.773423] dwc_otg: NAK holdoff enabled Dec 27 21:12:27 domoticz kernel: [ 0.773427] dwc_otg: FIQ split-transaction FSM enabled Dec 27 21:12:27 domoticz kernel: [ 0.773440] Module dwc_common_port init Dec 27 21:12:27 domoticz kernel: [ 0.773654] usbcore: registered new interface driver usb-storage Dec 27 21:12:27 domoticz kernel: [ 0.775105] mousedev: PS/2 mouse device common for all mice Dec 27 21:12:27 domoticz kernel: [ 0.777302] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer Dec 27 21:12:27 domoticz kernel: [ 0.778894] bcm2835-cpufreq: min=600000 max=1200000 Dec 27 21:12:27 domoticz kernel: [ 0.780631] sdhci: Secure Digital Host Controller Interface driver Dec 27 21:12:27 domoticz kernel: [ 0.781980] sdhci: Copyright(c) Pierre Ossman Dec 27 21:12:27 domoticz kernel: [ 0.783559] sdhost-bcm2835 3f202000.sdhost: could not get clk, deferring probe Dec 27 21:12:27 domoticz kernel: [ 0.787123] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe Dec 27 21:12:27 domoticz kernel: [ 0.788642] sdhci-pltfm: SDHCI platform and OF driver helper Dec 27 21:12:27 domoticz kernel: [ 0.792679] ledtrig-cpu: registered to indicate activity on CPUs Dec 27 21:12:27 domoticz kernel: [ 0.794296] hidraw: raw HID events driver (C) Jiri Kosina Dec 27 21:12:27 domoticz kernel: [ 0.795907] usbcore: registered new interface driver usbhid Dec 27 21:12:27 domoticz kernel: [ 0.797338] usbhid: USB HID core driver Dec 27 21:12:27 domoticz kernel: [ 0.799562] vchiq: vchiq_init_state: slot_zero = 0xbdd80000, is_master = 0 Dec 27 21:12:27 domoticz kernel: [ 0.802307] [vc_sm_connected_init]: start Dec 27 21:12:27 domoticz kernel: [ 0.805755] vc_vchi_sm_init: failed to open VCHI service (-1) Dec 27 21:12:27 domoticz kernel: [ 0.805854] [vc_sm_connected_init]: failed to initialize shared memory service Dec 27 21:12:27 domoticz kernel: [ 0.808797] [vc_sm_connected_init]: end - returning -1 Dec 27 21:12:27 domoticz kernel: [ 0.810708] Initializing XFRM netlink socket Dec 27 21:12:27 domoticz kernel: [ 0.812256] NET: Registered protocol family 17 Dec 27 21:12:27 domoticz kernel: [ 0.813912] Key type dns_resolver registered Dec 27 21:12:27 domoticz kernel: [ 0.815800] Registering SWP/SWPB emulation handler Dec 27 21:12:27 domoticz kernel: [ 0.818025] registered taskstats version 1 Dec 27 21:12:27 domoticz kernel: [ 0.824815] uart-pl011 3f201000.serial: cts_event_workaround enabled Dec 27 21:12:27 domoticz kernel: [ 0.826406] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2 Dec 27 21:12:27 domoticz kernel: [ 0.831073] sdhost: log_buf @ bdd07000 (fdd07000) Dec 27 21:12:27 domoticz kernel: [ 0.910624] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1) Dec 27 21:12:27 domoticz kernel: [ 0.914335] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0 Dec 27 21:12:27 domoticz kernel: [ 0.915839] mmc-bcm2835 3f300000.mmc: DMA channel allocated Dec 27 21:12:27 domoticz kernel: [ 0.987418] mmc0: host does not support reading read-only switch, assuming write-enable Dec 27 21:12:27 domoticz kernel: [ 0.990719] of_cfs_init Dec 27 21:12:27 domoticz kernel: [ 0.990779] Indeed it is in host mode hprt0 = 00021501 Dec 27 21:12:27 domoticz kernel: [ 0.993836] of_cfs_init: OK Dec 27 21:12:27 domoticz kernel: [ 0.995709] Waiting for root device PARTUUID=e80766f2-02... Dec 27 21:12:27 domoticz kernel: [ 1.051010] mmc0: new high speed SDHC card at address 0001 Dec 27 21:12:27 domoticz kernel: [ 1.056145] mmcblk0: mmc0:0001 00000 14.9 GiB Dec 27 21:12:27 domoticz kernel: [ 1.058962] mmcblk0: p1 p2 Dec 27 21:12:27 domoticz kernel: [ 1.069058] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) Dec 27 21:12:27 domoticz kernel: [ 1.072012] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) Dec 27 21:12:27 domoticz kernel: [ 1.072437] random: fast init done Dec 27 21:12:27 domoticz kernel: [ 1.076238] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) Dec 27 21:12:27 domoticz kernel: [ 1.080392] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) Dec 27 21:12:27 domoticz kernel: [ 1.121517] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) Dec 27 21:12:27 domoticz kernel: [ 1.124187] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. Dec 27 21:12:27 domoticz kernel: [ 1.133254] devtmpfs: mounted Dec 27 21:12:27 domoticz kernel: [ 1.136413] Freeing unused kernel memory: 1024K Dec 27 21:12:27 domoticz kernel: [ 1.173457] mmc1: new high speed SDIO card at address 0001 Dec 27 21:12:27 domoticz kernel: [ 1.190641] usb 1-1: new high-speed USB device number 2 using dwc_otg Dec 27 21:12:27 domoticz kernel: [ 1.192168] Indeed it is in host mode hprt0 = 00001101 Dec 27 21:12:27 domoticz kernel: [ 1.420944] usb 1-1: New USB device found, idVendor=0424, idProduct=9514 Dec 27 21:12:27 domoticz kernel: [ 1.422402] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Dec 27 21:12:27 domoticz kernel: [ 1.424675] hub 1-1:1.0: USB hub found Dec 27 21:12:27 domoticz kernel: [ 1.426166] hub 1-1:1.0: 5 ports detected Dec 27 21:12:27 domoticz kernel: [ 1.694677] NET: Registered protocol family 10 Dec 27 21:12:27 domoticz kernel: [ 1.706057] ip_tables: (C) 2000-2006 Netfilter Core Team Dec 27 21:12:27 domoticz kernel: [ 1.750624] usb 1-1.1: new high-speed USB device number 3 using dwc_otg Dec 27 21:12:27 domoticz kernel: [ 1.881013] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00 Dec 27 21:12:27 domoticz kernel: [ 1.882603] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Dec 27 21:12:27 domoticz kernel: [ 1.886946] smsc95xx v1.0.5 Dec 27 21:12:27 domoticz kernel: [ 1.984610] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:d4:81:2a Dec 27 21:12:27 domoticz kernel: [ 2.353008] i2c /dev entries driver
-
Dec 27 21:12:27 domoticz kernel: [ 2.675918] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) Dec 27 21:12:27 domoticz kernel: [ 3.109172] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000 Dec 27 21:12:27 domoticz kernel: [ 3.407342] brcmfmac: F1 signature read @0x18000000=0x1541a9a6 Dec 27 21:12:27 domoticz kernel: [ 3.413382] usbcore: registered new interface driver brcmfmac Dec 27 21:12:27 domoticz kernel: [ 3.601930] brcmfmac: Firmware version = wl0: Aug 7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378 Dec 27 21:12:27 domoticz kernel: [ 3.602685] brcmfmac: brcmf_c_preinit_dcmds: CLM version = API: 12.2 Data: 7.11.15 Compiler: 1.24.2 ClmImport: 1.24.1 Creation: 2014-05-26 10:53:55 Inc Data: 9.10.41 Inc Compiler: 1.29.4 Inc ClmImport: 1.36.3 Creation: 2017-08-07 00:37:47 Dec 27 21:12:27 domoticz avahi-daemon[327]: Successfully called chroot(). Dec 27 21:12:27 domoticz avahi-daemon[327]: Successfully dropped remaining capabilities. Dec 27 21:12:27 domoticz avahi-daemon[327]: No service file found in /etc/avahi/services. Dec 27 21:12:27 domoticz systemd[1]: Started Avahi mDNS/DNS-SD Stack. Dec 27 21:12:27 domoticz systemd[1]: Reached target System Time Synchronized. Dec 27 21:12:27 domoticz avahi-daemon[327]: Network interface enumeration completed. Dec 27 21:12:27 domoticz avahi-daemon[327]: Server startup complete. Host name is domoticz.local. Local service cookie is 87145466. Dec 27 21:12:27 domoticz systemd[1]: apt-daily.timer: Adding 5h 31min 57.980339s random time. Dec 27 21:12:27 domoticz systemd[1]: Started Daily apt download activities. Dec 27 21:12:27 domoticz systemd[1]: apt-daily-upgrade.timer: Adding 2min 40.737204s random time. Dec 27 21:12:27 domoticz systemd[1]: Started Daily apt upgrade and clean activities. Dec 27 21:12:27 domoticz systemd[1]: Reached target Timers. Dec 27 21:12:27 domoticz systemd[1]: Started triggerhappy global hotkey daemon. Dec 27 21:12:27 domoticz systemd[1]: Started System Logging Service. Dec 27 21:12:27 domoticz systemd[1]: Started Save/Restore Sound Card State. Dec 27 21:12:27 domoticz dhcpcd[339]: wlan0: starting wpa_supplicant Dec 27 21:12:27 domoticz dhcpcd-run-hooks[374]: wlan0: starting wpa_supplicant Dec 27 21:12:27 domoticz systemd[1]: Started Login Service. Dec 27 21:12:27 domoticz dphys-swapfile[329]: Starting dphys-swapfile swapfile setup ... Dec 27 21:12:27 domoticz raspi-config[330]: Checking if shift key is held down:Error opening '/dev/input/event*': No such file or directory Dec 27 21:12:27 domoticz raspi-config[330]: No. Switching to ondemand scaling governor. Dec 27 21:12:27 domoticz systemd[1]: Started LSB: Switch to ondemand cpu governor (unless shift key is pressed). Dec 27 21:12:27 domoticz OWFS[375]: DEFAULT: owlib.c:(208) Cannot open USB bus master Dec 27 21:12:27 domoticz OWFS[375]: DEFAULT: owlib.c:(52) No valid 1-wire buses found Dec 27 21:12:27 domoticz systemd[1]: start1wire.service: Control process exited, code=exited status=1 Dec 27 21:12:27 domoticz systemd[1]: Failed to start LSB: Start OWFS at boot time. Dec 27 21:12:27 domoticz systemd[1]: start1wire.service: Unit entered failed state. Dec 27 21:12:27 domoticz systemd[1]: start1wire.service: Failed with result 'exit-code'. Dec 27 21:12:27 domoticz dphys-swapfile[329]: want /var/swap=100MByte, checking existing: keeping it Dec 27 21:12:27 domoticz kernel: [ 4.979888] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready Dec 27 21:12:27 domoticz kernel: [ 4.979897] brcmfmac: power management disabled Dec 27 21:12:27 domoticz kernel: [ 4.987898] Adding 102396k swap on /var/swap. Priority:-1 extents:1 across:102396k SSFS Dec 27 21:12:27 domoticz dphys-swapfile[329]: done. Dec 27 21:12:27 domoticz systemd[1]: Started LSB: Autogenerate and use a swap file. Dec 27 21:12:27 domoticz dhcpcd[339]: eth0: waiting for carrier Dec 27 21:12:27 domoticz dhcpcd[339]: wlan0: waiting for carrier Dec 27 21:12:27 domoticz dhcpcd[339]: wlan0: carrier acquired Dec 27 21:12:27 domoticz kernel: [ 5.321930] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup Dec 27 21:12:27 domoticz kernel: [ 5.322223] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Dec 27 21:12:27 domoticz dhcpcd[339]: DUID 00:01:00:01:21:b0:d9:d9:b8:27:eb:81:d4:7f Dec 27 21:12:27 domoticz dhcpcd[339]: wlan0: IAID eb:81:d4:7f Dec 27 21:12:27 domoticz dhcpcd[339]: wlan0: adding address fe80::6bd:3cc7:2b64:c842 Dec 27 21:12:27 domoticz dhcpcd[339]: wlan0: carrier lost Dec 27 21:12:28 domoticz dhcpcd[339]: wlan0: deleting address fe80::6bd:3cc7:2b64:c842 Dec 27 21:12:29 domoticz dhcpcd[339]: eth0: carrier acquired Dec 27 21:12:29 domoticz kernel: [ 6.725223] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Dec 27 21:12:29 domoticz kernel: [ 6.726375] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1 Dec 27 21:12:29 domoticz dhcpcd[339]: eth0: IAID eb:d4:81:2a Dec 27 21:12:29 domoticz dhcpcd[339]: eth0: adding address fe80::7a80:6e8f:27f0:4005 Dec 27 21:12:29 domoticz dhcpcd[339]: eth0: probing address 192.168.13.5/24 Dec 27 21:12:29 domoticz dhcpcd[339]: eth0: soliciting an IPv6 router Dec 27 21:12:30 domoticz avahi-daemon[327]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::7a80:6e8f:27f0:4005. Dec 27 21:12:30 domoticz avahi-daemon[327]: New relevant interface eth0.IPv6 for mDNS. Dec 27 21:12:30 domoticz avahi-daemon[327]: Registering new address record for fe80::7a80:6e8f:27f0:4005 on eth0.*. Dec 27 21:12:34 domoticz dhcpcd[339]: eth0: using static address 192.168.13.5/24 Dec 27 21:12:34 domoticz dhcpcd[339]: eth0: adding route to 192.168.13.0/24 Dec 27 21:12:34 domoticz dhcpcd[339]: eth0: adding default route via 192.168.13.1 Dec 27 21:12:34 domoticz avahi-daemon[327]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.13.5. Dec 27 21:12:34 domoticz avahi-daemon[327]: New relevant interface eth0.IPv4 for mDNS. Dec 27 21:12:34 domoticz avahi-daemon[327]: Registering new address record for 192.168.13.5 on eth0.IPv4. Dec 27 21:12:34 domoticz dhcpcd[339]: forked to background, child pid 470 Dec 27 21:12:34 domoticz systemd[1]: Started dhcpcd on all interfaces. Dec 27 21:12:34 domoticz systemd[1]: Reached target Network. Dec 27 21:12:34 domoticz systemd[1]: Reached target Network is Online. Dec 27 21:12:34 domoticz systemd[1]: Starting LSB: Home Automation System... Dec 27 21:12:34 domoticz systemd[1]: Starting /etc/rc.local Compatibility... Dec 27 21:12:34 domoticz systemd[1]: Starting Permit User Sessions... Dec 27 21:12:34 domoticz systemd[1]: Starting OpenBSD Secure Shell server... Dec 27 21:12:34 domoticz systemd[1]: Started /etc/rc.local Compatibility. Dec 27 21:12:34 domoticz systemd[1]: Started Permit User Sessions. Dec 27 21:12:34 domoticz systemd[1]: Starting Hold until boot process finishes up... Dec 27 21:12:34 domoticz systemd[1]: Starting Terminate Plymouth Boot Screen... Dec 27 21:12:34 domoticz systemd[1]: Received SIGRTMIN+21 from PID 190 (plymouthd). Dec 27 21:12:34 domoticz systemd[1]: Started Hold until boot process finishes up. Dec 27 21:12:34 domoticz systemd[1]: Started Terminate Plymouth Boot Screen. Dec 27 21:12:34 domoticz systemd[1]: Started Getty on tty1. Dec 27 21:12:34 domoticz systemd[1]: Reached target Login Prompts. Dec 27 21:12:34 domoticz systemd[1]: Started OpenBSD Secure Shell server. Dec 27 21:12:35 domoticz domoticz.sh[471]: 2017-12-27 21:12:35.467 Domoticz V3.8796 (c)2012-2017 GizMoCuz Dec 27 21:12:35 domoticz domoticz.sh[471]: 2017-12-27 21:12:35.467 Build Hash: 2d99bbbc, Date: 2017-12-24 07:06:53 Dec 27 21:12:35 domoticz domoticz.sh[471]: 2017-12-27 21:12:35.468 Startup Path: /home/pi/domoticz/ Dec 27 21:12:35 domoticz domoticz.sh[471]: domoticz: Domoticz is starting up.... Dec 27 21:12:35 domoticz domoticz: Domoticz is starting up.... Dec 27 21:12:35 domoticz domoticz: Domoticz running... Dec 27 21:12:35 domoticz systemd[1]: Started LSB: Home Automation System. Dec 27 21:12:35 domoticz systemd[1]: Reached target Multi-User System. Dec 27 21:12:35 domoticz systemd[1]: Reached target Graphical Interface. Dec 27 21:12:35 domoticz systemd[1]: Starting Update UTMP about System Runlevel Changes... Dec 27 21:12:35 domoticz systemd[1]: Started Update UTMP about System Runlevel Changes. Dec 27 21:12:35 domoticz systemd[1]: Startup finished in 1.510s (kernel) + 11.498s (userspace) = 13.009s. Dec 27 21:12:38 domoticz kernel: [ 15.710546] uart-pl011 3f201000.serial: no DMA platform data Dec 27 21:12:42 domoticz dhcpcd[470]: eth0: no IPv6 Routers available Dec 27 21:12:53 domoticz systemd[1]: Created slice User Slice of pi. Dec 27 21:12:53 domoticz systemd[1]: Starting User Manager for UID 1000... Dec 27 21:12:53 domoticz systemd[1]: Started Session c1 of user pi. Dec 27 21:12:53 domoticz systemd[535]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Dec 27 21:12:53 domoticz systemd[535]: Listening on GnuPG cryptographic agent and passphrase cache. Dec 27 21:12:53 domoticz systemd[535]: Listening on GnuPG cryptographic agent (access for web browsers). Dec 27 21:12:53 domoticz systemd[535]: Reached target Paths. Dec 27 21:12:53 domoticz systemd[535]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Dec 27 21:12:53 domoticz systemd[535]: Reached target Sockets. Dec 27 21:12:53 domoticz systemd[535]: Reached target Timers. Dec 27 21:12:53 domoticz systemd[535]: Reached target Basic System. Dec 27 21:12:53 domoticz systemd[535]: Reached target Default. Dec 27 21:12:53 domoticz systemd[535]: Startup finished in 48ms. Dec 27 21:12:53 domoticz systemd[1]: Started User Manager for UID 1000. Dec 27 21:13:03 domoticz systemd[535]: Time has been changed Dec 27 21:13:03 domoticz systemd[1]: Time has been changed Dec 27 21:13:03 domoticz systemd-timesyncd[285]: Synchronized to time server 195.189.85.132:123 (2.debian.pool.ntp.org). Dec 27 21:13:03 domoticz systemd[1]: apt-daily.timer: Adding 8h 6min 59.681187s random time. Dec 27 21:13:03 domoticz systemd[1]: apt-daily-upgrade.timer: Adding 32min 42.364143s random time.```
-
@pepson ok, so mysgw does at least log to syslog, as seen here
Dec 27 21:12:27 domoticz mysgw: Starting gateway... Dec 27 21:12:27 domoticz mysgw: Protocol version - 2.2.0-rc.2but nothing else. I expected there to be more information, but maybe I'm just not familiar enough with the raspberry pi gateway.
-
Yes but only one time read and then start the problem.
-
Can you try building the ethernet gateway instead?
-
Ethernet work ok. But i better want serial and found bug and solution why not working serial...
-
I just wanted to make sure at least it was working OK as ethernet.
-
Problem is only on serial...
-
Please help...
-
@pepson Just a suggestion, but are you sure the Pi3 is looking at ttyUSB1, ie have you confirmed this is the Gateway serial connection ?
I am using direct serial connection to the pi3 GPIO as ttySO with Domoticz, but when I tried a USB Gateway at one point, the connection was NOT working using the expected ttyUSB quoted. I had to check the tty connections via Putty to establish the actual link...
-
But can you give me commend to build it as you use ttySO ?
-
I build it as ttySO
./configure --my-transport=rfm69 --my-rfm69-frequency=868 --my-is-rfm69hw --my-gateway=serial --my-serial-is-pty --my-serial-pty=/dev/ttySOand i have and info:
2017-12-28 15:40:21.822 MySensors: Using serial port: /dev/ttyS0
2017-12-28 15:40:21.832 Error: MySensors: Error opening serial port!
-
Then build as /dev/serial0 and the same problem. This is show in log Domoticz. One read version and port closed.
2017-12-28 15:48:14.418 MySensors: Using serial port: /dev/serial0
2017-12-28 15:48:14.418 MySensors: Gateway Version: 2.2.0-rc.2
2017-12-28 15:48:14.418 Error: Serial Port closed!... Error: End of file
2017-12-28 15:48:15.418 MySensors: retrying in 30 seconds...
-
@pepson could you post your hardware settings in Domoticz? This is what works for me:
Could you also try building the gateway without rfm69 support, to check if the problem is generic or related to rfm69. Use this:
./configure --my-transport=none --my-gateway=serial --my-serial-is-pty --my-serial-pty=/dev/ttyUSB42 make && sudo ./bin/mysgw -d
-
Hello
Thanks for your help. I start from beginning build DOmoticz on my RPi3 with clean latest image. After run in Sudo raspi-config i enable SPI and Serial , then install DOmoticz and now all works OK. Then build Mysensor Gateway and all is ok with no error in Domoticz. Works on /dev/ttyUSB42
-
But how i can build MySensors Gateway on serial with radio RFM69HW but on old version 2.1.1 ?
-
And have next problem... i build sketch on version 2.2.0-rc2 but after write to Arduino Mini Pro he is not connected to my Gateway on RPI3.
This is sketch. What is wrong ?
/* Relay with button sketch modified to work with no uplink to gateway and try to maintain sync to controller */ #define MY_DEBUG // Enable debug prints to serial monitor #define MY_RADIO_RFM69 #define MY_RFM69_FREQUENCY 868 #define MY_IS_RFM69HW #define MY_RFM69_NEW_DRIVER //#define MY_NODE_ID 203 // Node id defaults to AUTO (tries to fetch id from controller) #define MY_TRANSPORT_WAIT_READY_MS 5000 //set how long to wait for transport ready in milliseconds #define MY_REPEATER_FEATURE // Enabled repeater feature for this node #include <MySensors.h> #include <Bounce2.h> #define RELAY_PIN 5 // Arduino Digital I/O pin number for relay #define BUTTON_PIN 3 // Arduino Digital I/O pin number for button #define CHILD_ID 1 // Id of the sensor child #define RELAY_ON 1 #define RELAY_OFF 0 Bounce debouncer = Bounce(); int oldValue = 0; bool uplinkAvailable = true; bool state = false; bool requestState; bool firstStart = true; unsigned long uplinkCheckTime ; // holder for uplink checks unsigned long uplinkCheckPeriod = 30*1000; // time between checks for uplink in milliseconds unsigned long returnWait = 1000; // how long to wait for return from controller in milliseconds.. adjust as needed unsigned long oldTime = 0; unsigned long newTime = 0; MyMessage msg(CHILD_ID, V_STATUS); void setup(){ pinMode(BUTTON_PIN, INPUT_PULLUP); // Setup the button pin, Activate internal pull-up debouncer.attach(BUTTON_PIN); // After setting up the button, setup debouncer debouncer.interval(5); pinMode(RELAY_PIN, OUTPUT); // set relay pin in output mode digitalWrite(RELAY_PIN, RELAY_OFF); // Make sure relay is off when starting up } void presentation() { // Send the sketch version information to the gateway and Controller sendSketchInfo("1xRelay & Button", "2.2.0-rc2"); // Register all sensors to gw (they will be created as child devices) present(CHILD_ID, S_BINARY); } void loop(){ if (firstStart) { // this code is only run once at startup Serial.println("First run started"); requestTime(); // get time from controller wait (returnWait); // delay to allow time to return if (oldTime == 0){ // check to see if there was a return from the time request Serial.println("uplink not available"); uplinkAvailable = false; // no uplink established uplinkCheckTime = millis(); } else{ Serial.println("uplink available"); request( CHILD_ID, V_STATUS); // get status of switch on controller wait (returnWait); //wait needed to allow request to return from controller Serial.print("controller state --- "); Serial.println(requestState); if (requestState != state) { // check that controller is corectly showing the current relay state send(msg.set(state), false); // notify controller of current state } } firstStart = false; // set firstStart flag false to prevent code from running again } debouncer.update(); int value = debouncer.read(); // Get the update value if (value != oldValue && value == 0) { // check for new button push state = !state; // Toggle the state digitalWrite(RELAY_PIN, state ? RELAY_ON : RELAY_OFF); // switch the relay to the new state requestTime(); wait (returnWait); // delay to allow time to return if (oldTime != newTime){ // if times are different then uplink is available send(msg.set(state), false); oldTime = newTime; } else{ // if times are the same no uplink is available Serial.println("uplink not available"); uplinkAvailable = false; // no uplink available, set flag false uplinkCheckTime = millis(); // start the timer from now } } oldValue = value; if (!uplinkAvailable && (millis() - uplinkCheckTime > uplinkCheckPeriod) ) { // test to see if function should be called uplinkCheck(); // call uplink checking function } } /*-------------------start of functions--------------------------*/ void receive(const MyMessage &message) { if (message.type == V_STATUS) { // check to see if incoming message is for a switch switch (message.getCommand()) { // message.getCommand will give us the command type of the incomming message case C_SET: //message is a set command from controller to update relay state state = message.getBool(); // get the new state digitalWrite(RELAY_PIN, state ? RELAY_ON : RELAY_OFF); // switch relay to new state uplinkAvailable = true; // uplink established /*---- Write some debug info----*/ Serial.print("Incoming change for sensor:"); Serial.print(message.sensor); Serial.print(", New status: "); Serial.println(message.getBool()); break; case C_REQ: // message is a returning request from controller requestState = message.getBool(); // update requestState with returning state break; } } } void uplinkCheck() { requestTime(); wait (returnWait); // wait for time return.. this may need to be varied for your system if (oldTime != newTime){ Serial.println("uplink re-established"); request( CHILD_ID, V_STATUS); wait (returnWait); //wait needed to allow request to return from controller if (requestState != state) { // check that controller is corectly showing the current relay state send(msg.set(state), false); // notify controller of current state no ack uplinkAvailable = true; // uplink established oldTime = newTime; } } uplinkCheckTime = millis(); // reset the checktime Serial.println("uplinkchecktime reset"); } void receiveTime(unsigned long time) { if (firstStart){ oldTime = time; newTime = time; } else{ newTime = time; } Serial.print("time received---- " ); Serial.println(time); }```
-
@pepson Try walking in little steps trying each stage rather than running into new walls then expressing surprise at broken nose, no offence intended
Gateway and nodes, same platform, same version..... Otherwise they are speaking Chinese and Swedish hoping for somebody to explain the meaning of fubar...
-
I use the same version now 2.2.0-rc2 but when i programmed sketch to node it not connection to Gateway... That i want come back to version 2.1.1 gateway but i dont know how ? Or resolved problem Node 2.2.0-rc2 i stay on this.
But when run debug gateway show this:
pi@domoticz:~/MySensors $ sudo ./bin/mysgw -d mysgw: Starting gateway... mysgw: Protocol version - 2.2.0-rc.2 mysgw: MCO:BGN:INIT GW,CP=RPNGL---,VER=2.2.0-rc.2 mysgw: TSF:LRT:OK mysgw: TSM:INIT mysgw: TSF:WUR:MS=0 mysgw: TSM:INIT:TSP OK mysgw: TSM:INIT:GW MODE mysgw: TSM:READY:ID=0,PAR=0,DIS=0 mysgw: MCO:REG:NOT NEEDED mysgw: MCO:BGN:STP mysgw: MCO:BGN:INIT OK,TSP=1 mysgw: !TSF:SAN:FAIL mysgw: TSM:FAIL:CNT=1 mysgw: TSM:FAIL:DIS mysgw: TSF:TDI:TSL mysgw: TSM:FAIL:RE-INIT mysgw: TSM:INIT mysgw: TSM:INIT:TSP OK mysgw: TSM:INIT:GW MODEThis is sketch 2.2.0-rc2
/* Relay with button sketch modified to work with no uplink to gateway and try to maintain sync to controller */ #define MY_DEBUG // Enable debug prints to serial monitor #define MY_RADIO_RFM69 #define RFM69_868MHZ #define MY_IS_RFM69HW #define MY_RFM69_NEW_DRIVER //#define MY_NODE_ID 203 // Node id defaults to AUTO (tries to fetch id from controller) #define MY_TRANSPORT_WAIT_READY_MS 5000 //set how long to wait for transport ready in milliseconds #define MY_REPEATER_FEATURE // Enabled repeater feature for this node #include <MySensors.h> #include <Bounce2.h> #define RELAY_PIN 5 // Arduino Digital I/O pin number for relay #define BUTTON_PIN 3 // Arduino Digital I/O pin number for button #define CHILD_ID 1 // Id of the sensor child #define RELAY_ON 1 #define RELAY_OFF 0 Bounce debouncer = Bounce(); int oldValue = 0; bool uplinkAvailable = true; bool state = false; bool requestState; bool firstStart = true; unsigned long uplinkCheckTime ; // holder for uplink checks unsigned long uplinkCheckPeriod = 30*1000; // time between checks for uplink in milliseconds unsigned long returnWait = 1000; // how long to wait for return from controller in milliseconds.. adjust as needed unsigned long oldTime = 0; unsigned long newTime = 0; MyMessage msg(CHILD_ID, V_STATUS); void setup(){ pinMode(BUTTON_PIN, INPUT_PULLUP); // Setup the button pin, Activate internal pull-up debouncer.attach(BUTTON_PIN); // After setting up the button, setup debouncer debouncer.interval(5); pinMode(RELAY_PIN, OUTPUT); // set relay pin in output mode digitalWrite(RELAY_PIN, RELAY_OFF); // Make sure relay is off when starting up } void presentation() { // Send the sketch version information to the gateway and Controller sendSketchInfo("1xRelay & Button", "2.2.0-rc2"); // Register all sensors to gw (they will be created as child devices) present(CHILD_ID, S_BINARY); } void loop(){ if (firstStart) { // this code is only run once at startup Serial.println("First run started"); requestTime(); // get time from controller wait (returnWait); // delay to allow time to return if (oldTime == 0){ // check to see if there was a return from the time request Serial.println("uplink not available"); uplinkAvailable = false; // no uplink established uplinkCheckTime = millis(); } else{ Serial.println("uplink available"); request( CHILD_ID, V_STATUS); // get status of switch on controller wait (returnWait); //wait needed to allow request to return from controller Serial.print("controller state --- "); Serial.println(requestState); if (requestState != state) { // check that controller is corectly showing the current relay state send(msg.set(state), false); // notify controller of current state } } firstStart = false; // set firstStart flag false to prevent code from running again } debouncer.update(); int value = debouncer.read(); // Get the update value if (value != oldValue && value == 0) { // check for new button push state = !state; // Toggle the state digitalWrite(RELAY_PIN, state ? RELAY_ON : RELAY_OFF); // switch the relay to the new state requestTime(); wait (returnWait); // delay to allow time to return if (oldTime != newTime){ // if times are different then uplink is available send(msg.set(state), false); oldTime = newTime; } else{ // if times are the same no uplink is available Serial.println("uplink not available"); uplinkAvailable = false; // no uplink available, set flag false uplinkCheckTime = millis(); // start the timer from now } } oldValue = value; if (!uplinkAvailable && (millis() - uplinkCheckTime > uplinkCheckPeriod) ) { // test to see if function should be called uplinkCheck(); // call uplink checking function } } /*-------------------start of functions--------------------------*/ void receive(const MyMessage &message) { if (message.type == V_STATUS) { // check to see if incoming message is for a switch switch (message.getCommand()) { // message.getCommand will give us the command type of the incomming message case C_SET: //message is a set command from controller to update relay state state = message.getBool(); // get the new state digitalWrite(RELAY_PIN, state ? RELAY_ON : RELAY_OFF); // switch relay to new state uplinkAvailable = true; // uplink established /*---- Write some debug info----*/ Serial.print("Incoming change for sensor:"); Serial.print(message.sensor); Serial.print(", New status: "); Serial.println(message.getBool()); break; case C_REQ: // message is a returning request from controller requestState = message.getBool(); // update requestState with returning state break; } } } void uplinkCheck() { requestTime(); wait (returnWait); // wait for time return.. this may need to be varied for your system if (oldTime != newTime){ Serial.println("uplink re-established"); request( CHILD_ID, V_STATUS); wait (returnWait); //wait needed to allow request to return from controller if (requestState != state) { // check that controller is corectly showing the current relay state send(msg.set(state), false); // notify controller of current state no ack uplinkAvailable = true; // uplink established oldTime = newTime; } } uplinkCheckTime = millis(); // reset the checktime Serial.println("uplinkchecktime reset"); } void receiveTime(unsigned long time) { if (firstStart){ oldTime = time; newTime = time; } else{ newTime = time; } Serial.print("time received---- " ); Serial.println(time); }```
-
@pepson Let's try the baby steps I referred to earlier.
The current stable version of MySensors is 2.1. Those using 2.2 tend to be experienced people versed in programming and experimenting and problem solving, hence it is not an official release.... yet you are using it and asking for solutions... Hello ?
I am and have been for the last few months using a Pro-Mini with RFM69 as nodes and gateway using 2.1 attached to a Pi3 running Domoticz.... No problems, but slowly coming to understand most of what I am doing...
I am still on baby steps, I don't mind at all, it works.....
-
Ok but i dont know how build Gateway on version 2.1.1 because when i do step by step as show on mysensors.org it default build me version gateway 2.2.0-rc2
-
@pepson As in this page? 2.1.1 - Latest Release ?
https://www.mysensors.org/download
-
I found bug in Domoticz BETA 8796. No reconized version gateway in HARDWARE. On stable 8153 works with no problem and correct reconized version gateway 2.2.0-rc2...
And again problem with this:
CODE: SELECT ALL2017-12-28 20:01:32.587 MySensors: retrying in 30 seconds...
2017-12-28 20:02:08.752 MySensors: Using serial port: /dev/serial0
2017-12-28 20:02:08.752 MySensors: Gateway Version: 2.2.0-rc.2
2017-12-28 20:02:08.752 Error: Serial Port closed!... Error: End of file
2017-12-28 20:02:09.752 MySensors: retrying in 30 seconds...
2017-12-28 20:02:38.755 MySensors: Using serial port: /dev/serial0
2017-12-28 20:02:38.755 Error: Serial Port closed!... Error: End of file
2017-12-28 20:02:39.755 MySensors: retrying in 30 seconds...
2017-12-28 20:03:08.757 MySensors: Using serial port: /dev/serial0
2017-12-28 20:03:08.761 Error: Serial Port closed!... Error: End of file
2017-12-28 20:03:09.758 MySensors: retrying in 30 seconds...
On beta is problem.
On stable works correct.
-
This post is deleted!
-
@macvictor said in
Building a Raspberry Pi Gateway:@marceloaqno Thank's for you help. I have other question.. general I try configure my gateway to work with security & signing, but they doesn't work. Where is problem? On the bottom i send point what it do it:
Gateway:
./configure --my-gateway=mqtt --my-controller-ip-address=127.0.0.1 --my-mqtt-publish-topic-prefix=mysensors-out --my-mqtt-subscribe-topic-prefix=mysensors-in --my-mqtt-client-id=mygateway1 --my-mqtt-password=PASS --my-mqtt-user=USER --my-rf24-encryption-enabled --my-signing=software --my-signing-request-signatures --my-signing-request-gw-signatures-from-allmakesudo make installsudo systemctl enable mysgw.servicesudo systemctl start mysgw.servicesudo mysgw --gen-soft-hmac-keysudo mysgw --set-soft-hmac-key=02417628BC1573CC380...sudo mysgw --gen-soft-serial-keysudo mysgw --set-soft-serial-key=00762CD152B868F7EBsudo mysgw --gen-aes-keysudo mysgw --set-aes-key= A790AD78B2D8B4DBBB5B2C4B9DD6DAF3
Node:
- Load script
SecurityPersonalizer.ino - Uncomment and send sketch to arduino
#define USE_SOFT_SIGNING #define STORE_SOFT_KEY #define USER_SOFT_KEY #define STORE_SOFT_SERIAL #define STORE_AES_KEY #define USER_AES_KEY #define MY_SOFT_HMAC_KEY 0X2,0X41,0X76,0X28,0XBC,0X15,0X73,0XCC,0X38... #define MY_AES_KEY 0XA7,0X90,0XAD,0X78,0XB2,0XD8...- Read all value from EPROM (test save):
Personalization sketch for MySensors usage. ------------------------------------------- EEPROM configuration: SOFT_HMAC_KEY | 02417628BC1573CC380DE0FADF7C87D7D3C77272A783E6E438786A07C3A8C6CF SOFT_SERIAL | 39BB1370C289643251 AES_KEY | A790AD78B2D8B4DBBB5B2C4B9DD6DAF3 -------------------------------- Personalization is now complete.- Send sample sketch to arduino:
//!< Enable debug prints to serial monitor #define MY_DEBUG //!< Enable signing related debug prints to serial monitor #define MY_DEBUG_VERBOSE_SIGNING // Enable NRF24L01 radio type #define MY_RADIO_NRF24 // Select soft signing #define MY_SIGNING_SOFT // Enable lockdown of node if suspicious activity is detected //-->> #define MY_NODE_LOCK_FEATURE // Enable node whitelisting //#define MY_SIGNING_NODE_WHITELISTING {{.nodeId = GATEWAY_ADDRESS,.serial = {0x09,0x08,0x07,0x06,0x05,0x04,0x03,0x02,0x01}}} // Enable this if you want destination node to sign all messages sent to this node. #define MY_SIGNING_REQUEST_SIGNATURES // SETTINGS FOR MY_SIGNING_SOFT #define MY_SIGNING_SOFT_RANDOMSEED_PIN 7 //!< Unconnected analog pin for random seed // Add repeater function to this sensor #define MY_REPEATER_FEATURE #include <SPI.h> #include <MySensors.h> #include <Bounce2.h> #define RELAY_PIN 4 // Arduino Digital I/O pin number for relay #define BUTTON_PIN 3 // Arduino Digital I/O pin number for button #define CHILD_ID 1 // Id of the sensor child #define RELAY_ON 1 #define RELAY_OFF 0 Bounce debouncer = Bounce(); int oldValue = 0; bool state; MyMessage msg(CHILD_ID, V_LIGHT); void setup() { // Setup the button pinMode(BUTTON_PIN, INPUT); // Activate internal pull-up digitalWrite(BUTTON_PIN, HIGH); // After setting up the button, setup debouncer debouncer.attach(BUTTON_PIN); debouncer.interval(5); // Make sure relays are off when starting up digitalWrite(RELAY_PIN, RELAY_OFF); // Then set relay pins in output mode pinMode(RELAY_PIN, OUTPUT); // Set relay to last known state (using eeprom storage) state = loadState(CHILD_ID); digitalWrite(RELAY_PIN, state ? RELAY_ON : RELAY_OFF); } void presentation() { // Send the sketch version information to the gateway and Controller sendSketchInfo("Relay & Button", "1.0"); // Register all sensors to gw (they will be created as child devices) present(CHILD_ID, S_LIGHT, "Switch Secure Sensor", false); } /* Example on how to asynchronously check for new messages from gw */ void loop() { debouncer.update(); // Get the update value int value = debouncer.read(); // if (value != oldValue && value == 0) { send(msg.set(state ? false : true), true); // Send new state and request ack back // } // oldValue = value; delay(5000); } void receive(const MyMessage &message) { // We only expect one type of message from controller. But we better check anyway. if (message.isAck()) { Serial.println("This is an ack from gateway"); } if (message.type == V_LIGHT) { // Change relay state state = message.getBool(); digitalWrite(RELAY_PIN, state ? RELAY_ON : RELAY_OFF); // Store state in eeprom // saveState(CHILD_ID, state); // Write some debug info Serial.print("Incoming change for sensor:"); Serial.print(message.sensor); Serial.print(", New status: "); Serial.println(message.getBool()); } }And finally in Arduino Serial Monitor I see:
0 MCO:BGN:INIT REPEATER,CP=RNNRAS-,VER=2.1.1 4 TSM:INIT 5 TSF:WUR:MS=0 11 TSM:INIT:TSP OK 13 TSF:SID:OK,ID=105 15 TSM:FPAR 16 Will not sign message for destination 255 as it does not require it 58 TSF:MSG:SEND,105-105-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK: 2065 !TSM:FPAR:NO REPLY 2067 TSM:FPAR 2068 Will not sign message for destination 255 as it does not require it 2110 TSF:MSG:SEND,105-105-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK: 4117 !TSM:FPAR:NO REPLY 4119 TSM:FPAR 4120 Will not sign message for destination 255 as it does not require it 4162 TSF:MSG:SEND,105-105-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK: 6169 !TSM:FPAR:NO REPLY 6171 TSM:FPAR 6172 Will not sign message for destination 255 as it does not require it 6214 TSF:MSG:SEND,105-105-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK: 8221 !TSM:FPAR:FAIL 8222 TSM:FAIL:CNT=1 8224 TSM:FAIL:PDTand in gateway i see:
sudo mysgw -d mysgw: Starting gateway... mysgw: Protocol version - 2.1.1 mysgw: MCO:BGN:INIT GW,CP=RNNG-S-,VER=2.1.1 mysgw: TSF:LRT:OK mysgw: TSM:INIT mysgw: TSF:WUR:MS=0 mysgw: TSM:INIT:TSP OK mysgw: TSM:INIT:GW MODE mysgw: TSM:READY:ID=0,PAR=0,DIS=0 mysgw: MCO:REG:NOT NEEDED mysgw: MCO:BGN:STP mysgw: MCO:BGN:INIT OK,TSP=1 mysgw: Attempting MQTT connection... mysgw: connected to 127.0.0.1 mysgw: MQTT connected mysgw: Sending message on topic: mysensors-out/0/255/0/0/18 mysgw: TSF:MSG:READ,171-107-54,s=221,c=2,t=131,pt=4,l=25,sg=0:-1418183441 mysgw: !TSF:MSG:PVER,3=2 mysgw: TSF:MSG:READ,135-23-172,s=20,c=3,t=200,pt=7,l=25,sg=0:-0.00000178 mysgw: !TSF:MSG:PVER,1=2 mysgw: TSF:MSG:READ,34-66-89,s=168,c=1,t=9,pt=1,l=25,sg=0:56 mysgw: !TSF:MSG:PVER,1=2 mysgw: TSF:MSG:READ,223-46-240,s=112,c=5,t=192,pt=5,l=11,sg=1:1407647670 mysgw: TSF:MSG:REL MSG mysgw: !TSF:RTE:240 UNKNOWN mysgw: !TSF:MSG:SEND,223-0-240-240,s=112,c=5,t=192,pt=5,l=11,sg=1,ft=0,st=NACK:1407647670 mysgw: TSF:MSG:READ,183-139-129,s=37,c=6,t=155,pt=1,l=21,sg=0:48 mysgw: !TSF:MSG:PVER,0=2 mysgw: TSF:MSG:READ,139-214-233,s=61,c=3,t=193,pt=7,l=0,sg=1:0.00000000 mysgw: TSF:MSG:REL MSG mysgw: !TSF:RTE:233 UNKNOWN mysgw: !TSF:MSG:SEND,139-0-233-233,s=61,c=3,t=193,pt=7,l=0,sg=1,ft=0,st=NACK:0.00000000 mysgw: TSF:MSG:READ,83-33-7,s=179,c=2,t=27,pt=4,l=25,sg=1:-2057270722 mysgw: !TSF:MSG:PVER,3=2 mysgw: TSF:MSG:READ,110-148-67,s=113,c=0,t=158,pt=1,l=9,sg=1:251 mysgw: !TSF:MSG:PVER,1=2 mysgw: TSF:MSG:READ,75-209-102,s=204,c=7,t=25,pt=1,l=11,sg=1:52 mysgw: !TSF:MSG:PVER,0=2 mysgw: TSF:MSG:READ,184-209-235,s=58,c=1,t=140,pt=6,l=23,sg=1:1DC404A5401119FACF0000000000000000000000000000 mysgw: !TSF:MSG:PVER,3=2 mysgw: TSF:MSG:READ,172-203-51,s=140,c=2,t=173,pt=0,l=1,sg=1:? mysgw: TSF:MSG:REL MSG mysgw: !TSF:RTE:51 UNKNOWN mysgw: !TSF:MSG:SEND,172-0-51-51,s=140,c=2,t=173,pt=0,l=1,sg=1,ft=0,st=NACK:?Where is problem?
@macvictor
But how use itn on RFM69HW ? I dont see to be available #define MY_RFM69_ENABLE_ENCRYPTION... Only for #define MY_RF24_ENABLE_ENCRYPTION...
-
@pepson are you asking how to enable encryption on rfm69? (it is a bit unclear what you mean by "itn")
In that case, see https://www.mysensors.org/apidocs-beta/group__RFM69SettingGrpPub.html#ga17a7a919994e569f078e3787c2c4ecd2
-
-
@pepson yes I saw that. Thanks for checking. Have you reported the problem to the Domoticz team?
-
@mfalkvidd
Yes write on forum Domoticz in section BUG
-
@pepson great!
The report is at https://www.domoticz.com/forum/viewtopic.php?f=6&t=21125&sid=e414507bb1ca4596e93cf885047275a9 in case someone needs to find it in the future.
-
Hello!
I'm trying to "make" on Alpine Linux in a Docker (ok, maybe it's useless, but way interesting!).With a Debian image it's ok, but I'd like to use Alpine.
I get this error:
g++ -MT build/drivers/Linux/SPIDEV.o -MMD -MP -march=armv7-a -mtune=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_GATEWAY_LINUX -DMY_GATEWAY_MQTT_CLIENT -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DSPI_SPIDEV_DEVICE=\"/dev/spidev0.0\" -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/Linux/SPIDEV.cpp -o build/drivers/Linux/SPIDEV.o In file included from /usr/include/sys/ioctl.h:7:0, from drivers/Linux/SPIDEV.cpp:27: drivers/Linux/SPIDEV.cpp: In static member function 'static uint8_t SPIDEVClass::transfer(uint8_t)': drivers/Linux/SPIDEV.cpp:153:18: error: '_IOC_SIZEBITS' was not declared in this scope ret = ioctl(fd, SPI_IOC_MESSAGE(1), &tr); ^ drivers/Linux/SPIDEV.cpp: In static member function 'static void SPIDEVClass::transfernb(char*, char*, uint32_t)': drivers/Linux/SPIDEV.cpp:175:18: error: '_IOC_SIZEBITS' was not declared in this scope ret = ioctl(fd, SPI_IOC_MESSAGE(1), &tr); ^ make: *** [Makefile:99: build/drivers/Linux/SPIDEV.o] Error 1 root@local-mysgw-alpine:/opt/MySensors3$ make g++ -MT build/drivers/Linux/SPIDEV.o -MMD -MP -march=armv7-a -mtune=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_GATEWAY_LINUX -DMY_GATEWAY_MQTT_CLIENT -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DSPI_SPIDEV_DEVICE=\"/dev/spidev0.0\" -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/Linux/SPIDEV.cpp -o build/drivers/Linux/SPIDEV.o eIn file included from /usr/include/sys/ioctl.h:7:0, from drivers/Linux/SPIDEV.cpp:27: drivers/Linux/SPIDEV.cpp: In static member function 'static uint8_t SPIDEVClass::transfer(uint8_t)': drivers/Linux/SPIDEV.cpp:153:18: error: '_IOC_SIZEBITS' was not declared in this scope ret = ioctl(fd, SPI_IOC_MESSAGE(1), &tr); ^ drivers/Linux/SPIDEV.cpp: In static member function 'static void SPIDEVClass::transfernb(char*, char*, uint32_t)': drivers/Linux/SPIDEV.cpp:175:18: error: '_IOC_SIZEBITS' was not declared in this scope ret = ioctl(fd, SPI_IOC_MESSAGE(1), &tr); ^ make: *** [Makefile:99: build/drivers/Linux/SPIDEV.o] Error 1I'm surely missing a package... but can't state one. Any help?
@macvictor thanks for your post, it will help me a lot, I'm trying the same way.
-
@ghiglie https://lists.yoctoproject.org/pipermail/yocto/2016-January/028233.html seems to suggest that adding
#include <asm/ioctl.h>would solve the problem. Could you try that?
-
Was my fault!
**When copy and past command from word, for example, pay attention that software doesn't substitute the single "-" with a "-" longer.
I have a word with all commands, to replicate installation very fast. Was my fault (errr... Word fault.... but you understand). Have a nice day!
Hi,
I cannot go over the initialization of command.RPI3 + Amplified antenna by GertSander (https://www.openhardware.io/view/17/Raspberry-Pi2-GPIO-interface-for-NRF24L01). Power from 5v/3A and power for antenna taken from both 5V via the 3.3v stepper down.RPI3 is new, has about 12h (got yesterday).Yesterday it did work at first attempt. Today I would replicate so I did delete the uSD and restart over. No way to get the gateway on work.I did try 3 amplified antenna + 2 normal. No way.I did enable from raspi-config the SPI (and only it).It hangs on second line of output.These are the logs:sineverba@raspberrypi:~/MySensors $ ./configure --my-transport=nrf24 --my-gateway=serial --my-serial-is-pty --my-serial-pty=/dev/ttyUSB020 [SECTION] Detecting target machine. [OK] machine detected: SoC=BCM2837, Type=rpi3, CPU=armv7l. [SECTION] Detecting SPI driver. [OK] SPI driver detected:BCM. [SECTION] Detecting init system. [OK] init system detected: systemd. [SECTION] Saving configuration. [SECTION] Cleaning previous builds. [OK] Finished. sineverba@raspberrypi:~/MySensors $ make gcc -MT build/drivers/Linux/log.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_LINUX_IS_SERIAL_PTY -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/Linux/log.c -o build/drivers/Linux/log.o g++ -MT build/drivers/Linux/IPAddress.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_LINUX_IS_SERIAL_PTY -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/Linux/IPAddress.cpp -o build/drivers/Linux/IPAddress.o g++ -MT build/drivers/Linux/noniso.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_LINUX_IS_SERIAL_PTY -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/Linux/noniso.cpp -o build/drivers/Linux/noniso.o g++ -MT build/drivers/Linux/GPIO.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_LINUX_IS_SERIAL_PTY -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/Linux/GPIO.cpp -o build/drivers/Linux/GPIO.o g++ -MT build/drivers/Linux/SPIDEV.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_LINUX_IS_SERIAL_PTY -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/Linux/SPIDEV.cpp -o build/drivers/Linux/SPIDEV.o g++ -MT build/drivers/Linux/Print.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_LINUX_IS_SERIAL_PTY -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/Linux/Print.cpp -o build/drivers/Linux/Print.o g++ -MT build/drivers/Linux/EthernetClient.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_LINUX_IS_SERIAL_PTY -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/Linux/EthernetClient.cpp -o build/drivers/Linux/EthernetClient.o g++ -MT build/drivers/Linux/compatibility.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_LINUX_IS_SERIAL_PTY -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/Linux/compatibility.cpp -o build/drivers/Linux/compatibility.o g++ -MT build/drivers/Linux/SerialPort.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_LINUX_IS_SERIAL_PTY -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/Linux/SerialPort.cpp -o build/drivers/Linux/SerialPort.o g++ -MT build/drivers/Linux/Stream.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_LINUX_IS_SERIAL_PTY -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/Linux/Stream.cpp -o build/drivers/Linux/Stream.o g++ -MT build/drivers/Linux/interrupt.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_LINUX_IS_SERIAL_PTY -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/Linux/interrupt.cpp -o build/drivers/Linux/interrupt.o g++ -MT build/drivers/Linux/SerialSimulator.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_LINUX_IS_SERIAL_PTY -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/Linux/SerialSimulator.cpp -o build/drivers/Linux/SerialSimulator.o g++ -MT build/drivers/Linux/SoftEeprom.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_LINUX_IS_SERIAL_PTY -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/Linux/SoftEeprom.cpp -o build/drivers/Linux/SoftEeprom.o g++ -MT build/drivers/Linux/EthernetServer.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_LINUX_IS_SERIAL_PTY -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/Linux/EthernetServer.cpp -o build/drivers/Linux/EthernetServer.o g++ -MT build/examples_linux/mysgw.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_LINUX_IS_SERIAL_PTY -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c examples_linux/mysgw.cpp -o build/examples_linux/mysgw.o gcc -MT build/drivers/BCM/bcm2835.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_LINUX_IS_SERIAL_PTY -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/BCM/bcm2835.c -o build/drivers/BCM/bcm2835.o g++ -MT build/drivers/BCM/BCM.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_LINUX_IS_SERIAL_PTY -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/BCM/BCM.cpp -o build/drivers/BCM/BCM.o g++ -MT build/drivers/BCM/SPIBCM.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_LINUX_IS_SERIAL_PTY -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/BCM/SPIBCM.cpp -o build/drivers/BCM/SPIBCM.o g++ -MT build/drivers/BCM/Wire.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_LINUX_IS_SERIAL_PTY -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/BCM/Wire.cpp -o build/drivers/BCM/Wire.o g++ -MT build/drivers/BCM/RPi.o -MMD -MP -march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_SERIAL -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_LINUX_SERIAL_PTY=\"/dev/ttyUSB020\" -DMY_LINUX_IS_SERIAL_PTY -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/BCM -c drivers/BCM/RPi.cpp -o build/drivers/BCM/RPi.o g++ -pthread -o bin/mysgw build/drivers/Linux/log.o build/drivers/Linux/IPAddress.o build/drivers/Linux/noniso.o build/drivers/Linux/GPIO.o build/drivers/Linux/SPIDEV.o build/drivers/Linux/Print.o build/drivers/Linux/EthernetClient.o build/drivers/Linux/compatibility.o build/drivers/Linux/SerialPort.o build/drivers/Linux/Stream.o build/drivers/Linux/interrupt.o build/drivers/Linux/SerialSimulator.o build/drivers/Linux/SoftEeprom.o build/drivers/Linux/EthernetServer.o build/examples_linux/mysgw.o build/drivers/BCM/bcm2835.o build/drivers/BCM/BCM.o build/drivers/BCM/SPIBCM.o build/drivers/BCM/Wire.o build/drivers/BCM/RPi.o sineverba@raspberrypi:~/MySensors $ sudo ./bin/mysgw –d [sudo] password for sineverba: mysgw: Starting gateway... mysgw: Protocol version - 2.2.0-rc.2
-
Hi to all,
I'm testing an ethernet gateway on RPI3, with nrf24 + 1 node with a relay.I want introduce security and signing. On Arduino gateway / node no problem at all, but, how to do on the RPI3 as gateway?
I would get / create / set a software serial on PI itself and whitelisting it on the node, after I will introduce the AES Key and signing.
Cannot find in documentation how do it on PI3. Thank you very much!
-
@sineverba said in
Building a Raspberry Pi Gateway:Hi to all,
I'm testing an ethernet gateway on RPI3, with nrf24 + 1 node with a relay.I want introduce security and signing. On Arduino gateway / node no problem at all, but, how to do on the RPI3 as gateway?
I would get / create / set a software serial on PI itself and whitelisting it on the node, after I will introduce the AES Key and signing.
Cannot find in documentation how do it on PI3. Thank you very much!
Earlier in this forum... https://forum.mysensors.org/topic/4803/building-a-raspberry-pi-gateway/350
-
@mfalkvidd I'm trying today, but to compile correctly the Docker image I'll have to clone to my github account
or at least locally. My Dockerfile for the "Alpine edition" for Hass.io is simply:ARG BUILD_FROM ARG BUILD_ARCH ARG BUILD_DATE ARG BUILD_REF ARG BUILD_VERSION FROM ${BUILD_FROM} ENV CONFIG_PATH=/data/options.json ENV APPDIR=/opt/MySensors RUN apt-get update && apt-get install -y --force-yes \ make \ g++ \ git \ && rm -rf /var/lib/apt/lists/* /tmp/* /var/tmp/* ~/.cache \ && git clone https://github.com/mysensors/MySensors.git --branch development $APPDIR # Copy root filesystem COPY rootfs / #CMD [ "/run.sh" ]I deleted the LABELS 'cause... the data is still too rawly "buried" from others.
The Configure and Make is in run.sh.
BTW, I still need to figure out how to start mysgw as service... Mainlyt I'd like to redirect the log: how can I do this safely?
And... can I use the rx/tx/err led feature on Raspi too (aside being in a Docker) ?
EDIT: the code add works!
Another question: I'm not getting far from this... what is it trying to do?: Starting gateway... : Protocol version - 2.2.0-rc.2 : MCO:BGN:INIT GW,CP=RNNGL---,VER=2.2.0-rc.2 : TSF:LRT:OK : TSM:INIT : TSF:WUR:MS=0
-
@ghiglie Thank you, I did see that was for 2.1.1. Just playing with them!
-
Does the Pi Gateway support the MY_SIGNING_SIMPLE_PASSWD option? I couldn't find anything about that. I've been gearing up to use that feature in my network, but I've also been playing with moving my gateway onto my Pi Zero W.
-
@alowhum If you want to just encrypt data, just add the encryption key in the myconfig.h file and compile it
-
@gohan N00b question, but which steps from the step-by-step need to be redone to "compile it" after altering myconfig.h? Or can you just post the command lines?
-
As soon as you do the changes in myconfig.h before the MAKE, you are fine
-
Anyone tried using the new Pi Zero WH as a Raspberry Pi Gateway. Presumably by MQTT and using NRF24 radio?
@alowhum Have you been able to setup a gateway with your Raspberry Pi Zero?
-
@sentur That's what I'm doing now. Except mine is Zero W. Soldered the pins on myself.
-
@alowhum yes, to use MY_SIGNING_SIMPLE_PASSWD feature, add the following to your list of configure options:
... --my-signing=password --my-signing-password=<PASSWORD>
-
Is there anyway where i can see if i have IRQ configured ?
ive build it a long time ago, but now upgraded to a nrf24 PA/LNA and have more an more sensors.
-
look inside makefile.inc in mysensors folder, that should contain the parameters you set in ./configure
-
@gohanm, as it seems not ?, can i rebuild it easily? ```
SOC=BCM2837
CPPFLAGS=-march=armv8-a+crc -mtune=cortex-a53 -mfpu=neon-fp-armv8 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_LINUX -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -DMY_PORT=5003
LDFLAGS=-pthread
PREFIX=/usr/local
CC=gcc
CXX=g++
BUILDDIR=build
BINDIR=bin
GATEWAY_DIR=/usr/local/bin
INIT_SYSTEM=systemd
SPI_DRIVER=BCM```
-
make a copy of it and make a ./configure with the IRQ enabled and see what you get
-
@gohan make a copy of the makefile.inc and restart the ./configure command again you mean ?
ill try it tomorrow, too afraid to break things late in the evening
-
as far as you don't execute the MAKE command you are ok. Also make a copy of the mysgw executable just as backup if you never did it
-
but ill have to do it sometime , just ./configure with all the options, build , test and install ?
-
if you only want to check if irq is enabled, otherwise you could just build it fresh with irq enabled and you can go back by replacing the mysgw executable
-
@gohan ty
-
This post is deleted!
-
Moved to normal troubleshooting forum
-
This post is deleted!
-
@MasMat Yes I was able to build it on a Pi Zero. I did a fresh install on Dietpi. It worked fine when I didn't give any configuration options.
Now, however, I am still trying to run something on the PGIO pins in paralel to MySensors again, and this is not working. As I speak the Pi reboots every 5 minutes.. Not sure what to blame yet. Domoticz, PiGPIO, or MySensors.
Latest DietPi Stretch, latest Domoticz beta, latest MySensors beta.
-
