💬 Building a Raspberry Pi Gateway
-
wow, it's was really fast! Thanks to answer. I'm use an ethernet interface. It's up but have no cable on their. I didn't install a controller yet, so, is there no problem yet, right?
Sorry that, I'm really a newbie using MySensors.[updating]
ysgw: 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 FAIL
mysgw: TSM:FAIL:CNT=1
mysgw: TSM:FAIL:PDT
mysgw: TSM:FAIL:RE-INIT
mysgw: TSM:INIT
mysgw: !TSM:INIT:TSP FAIL
mysgw: TSM:FAIL:CNT=2
mysgw: TSM:FAIL:PDT
-
@Djames-Suhanko said in
Building a Raspberry Pi Gateway:--my-controlle-ip-address
this also is not necessary. Also for now remove all these --my-gateway=mqtt --my-mqtt-publish-topic-prefix=mysensors-out
--my-mqtt-subscribe-topic-prefix=mysensors-in
--my-mqtt-client-id=mygateway1
and use it as ethernet gateway to keep it simple
-
Ok, I will try it right now!
-
Hello folks,
my past experience is using nrf24 library at https://github.com/Blavery/lib_nrf24, and i was able to send/receive "text" data (or "string" data) in between Raspi3 (master node) and Arduino (slave). And this is a big issue, because what i need is numerical data (float or integer), not text data, so Raspi 3 can process the numerical data (such as to do the plotting), and based on the processed data to make some decisions. My raspi 3 is controlling a moving robot. Can you advise appropriate nrf24 library for raspberry pi and Arduino, and sample codes for this kind of applicaitons? Thanks
-
Welcome to the MySensors community @erobot !
Not sure how you found us, but the library we use here is...MySensors. It certanly does what you describe. The best way to start is to read how MySensors works at https://www.mysensors.org/about and then go on to the many build examples and build your first node.
-
hi there, somehow my gateway seems to stop receiving data after a day or so from my sensors,
restarting the service seems to solve it for a time, how can i troubleshoot this issue ?
-
Same trouble for me. I use mySensors since 2 years and I have no problem with my Arduino Gateway. But from now 2 weeks, I try to use a pi gateway. It's working well but sometime, don't no why, my nrf24 stop to receive messages. Just restarting mygw service and re-work again. I don't see nothing anormal in my log, stop randomlly after 1 or 2 days.
Maybe a power issue to nrf24, I will try to add capacitor just for testing if can resolve this problem.
-
Same here too. With Rpi3 gateway. Would stop for hours, maybe start agian for a hour or two and then stop.
Have been running debug mode for last day, no idea what happened, but been stable so perhaps something in the update/upgrade made a problem and has now been fixed.
Will keep an eye on here and let you know if I find anything.
-
Looks as if it happened after updating Home Assistant, but that should be 2 different things right ?
-
@Richard-van-der-Plas what version are you using?
-
@gohan for me version dev (2.2)
-
dev 2.2.0 beta
-
Have you tried both ethernet or mqtt?
-
@gohan the latest stable version i guess. Where can i check?
-
@Richard-van-der-Plas try the 2.2 beta, it usually works better
-
@gohan just checked it's 2.1.1, is it easy to upgrade?
-
@Richard-van-der-Plas just clone the 2.2 dev instead of the stable, the rest is the same
-
@gohan fatal: destination path 'MySensors' already exists and is not an empty directory. It goes wrong with the first command, could you please give me some pointers ?
-
you need to either delete or rename the Mysensors folder
-
Hello,
I designed a PCB for rfm or nrf -> raspberry pi
https://www.openhardware.io/view/470/MySensors-Gateway-for-Raspberry-PI
-
I am trying to get the gateway to run the RFM69W radio but when I issue the "make" command I get this
In file included from ./MySensors.h:318:0, from examples_linux/mysgw.cpp:83: ./drivers/RFM69/new/RFM69_new.cpp:658:12: warning: ‘void RFM69_ATCmode(bool, int16_t)’ defined but not used [-Wunused-function] LOCAL void RFM69_ATCmode(const bool onOff, const int16_t targetRSSI) ^It is latest beta.
-
@gohan what configure command did you use? Knowing that would make it easier to reproduce the problem...
Does this warning cause any problem?
-
Just simple rfm69w 433 with default options. It compiles but I get no communication with nodes and 100% processor, but maybe I did a bad wiring
-
@gohan debug output could be useful
-
I would have posted it but it just shows as no nodes are trying to connect and nodes are unable to find a parent of course. I'm using the rfm2nrf pcb in order to have the pins to connect to the raspberry.
PS here is the log of the startup
__ __ ____ | \/ |_ _/ ___| ___ _ __ ___ ___ _ __ ___ | |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __| | | | | |_| |___| | __/ | | \__ \ _ | | \__ \ |_| |_|\__, |____/ \___|_| |_|___/\___/|_| |___/ |___/ 2.2.0-beta mysgw: MCO:BGN:INIT GW,CP=RPNG----,VER=2.2.0-beta 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: 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;PING mysgw: Client 0: 0;0;3;0;18;PING
-
On my test RPI3 it is working.... I have to double check the other one.
-
@gohan Hi there updated to the latest dev, but i still have to restart the service after a few days, this is the message in the log:
Sep 17 20:31:51 raspberrypi hass[17999]: #033[32m2017-09-17 20:31:51 INFO (Thread-13) [mysensors.gateway_tcp] Closing socket at ('192.168.1.115', 5003).#033[0m Sep 17 20:31:51 raspberrypi hass[17999]: #033[32m2017-09-17 20:31:51 INFO (Thread-13) [mysensors.gateway_tcp] Socket closed at ('192.168.1.115', 5003).#033[0m Sep 17 20:31:51 raspberrypi hass[17999]: #033[32m2017-09-17 20:31:51 INFO (Thread-13) [mysensors.gateway_tcp] No response. Disconnected.#033[0m Sep 17 20:31:51 raspberrypi hass[17999]: #033[32m2017-09-17 20:31:51 INFO (Thread-13) [mysensors.gateway_tcp] Trying to connect to ('192.168.1.115', 5003)#033[0mchecking with top, i see high CPU utilization:
20921 root 20 0 20036 872 784 R CPU ->99,5 0,1 682:53.59 mysgw
-
Hello, I'm also have issue with this question. My Raspberry Pi 2 type is a01041, but by the original "configure" file it is not recognized:
[SECTION] Detecting target machine. [OK] machine detected: SoC=unknown, Type=unknown, CPU=armv7l.Maybe someone could explain why it is not recognized?
"Configure" file lines:
function detect_machine { ... case $hardware in ... BCM2835) soc="BCM2835" if [[ $machine == "Raspberry"* ]]; then local rev=($(detect_rpi_revision)) if [[ $rev == "a02082" || $rev == "a22082" ]]; then tp="RPi3" else tp="Rpi2" fi fi ;; ... My Raspberry Pi 2 info: processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 38.40 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 1 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 38.40 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 2 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 38.40 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 3 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 38.40 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 Hardware : BCM2835 Revision : a01041 Serial : 0000000049a14619
-
Double radio or alternative pin for spi1:
https://forum.mysensors.org/topic/7702/double-spi-radio-raspberry-pi/2
-
I followed the instructions carefully. However I get an error. Can someone help?
git clone https://github.com/mysensors/MySensors.git --branch master cd MySensors ./configure --my-transport=nrf24 --my-gateway=ethernetThis results in a warning:
[SECTION] Detecting SPI driver. [WARNING] No supported SPI driver detected.When I run
makeI get the follwing error:In file included from examples_linux/mysgw.cpp:74:0: ./MySensors.h:254:2: error: #error No support for nRF24 radio on this platform #error No support for nRF24 radio on this platform ^ In file included from ./drivers/RF24/RF24.cpp:23:0, from ./MySensors.h:290, from examples_linux/mysgw.cpp:74: ./drivers/RF24/RF24.h:52:17: fatal error: SPI.h: No such file or directory #include <SPI.h> ^ compilation terminated. Makefile:114: recipe for target 'build/examples_linux/mysgw.o' failed make: *** [build/examples_linux/mysgw.o] Error 1Hope someone can help. Thanks.
-
Maybe you didn't enable SPI on the pi.
From command prompt type 'sudo raspi-config', then select option 5 from the menu. This takes you to where you can enable the SPI bus on the pi. Then try again.
S>
-
@skywatch Thank you! That solved my problem.
-
Hello friends,
Reading the instructions for building a RaspberryPi Gateway using RFM69, it states that one should use the development branch and not master, since the Pi is using a different version of the driver.
Anyone knows when this will be merged to master branch?
Also, since this forces all nodes to use development branch as well to be able to communicate with the gateway, assuming I use the development branch now and it is later on merged into master, is there an easy way to upgrade nodes remotely to the new code?
I am planning to use Wall Switch Insertable Node, and Mini Relay Mode - Both support OTA updates, am I correct to assume this will allow upgrading without taking the nodes out of where they are located?
Thanks!
Sefi
-
Like all nodes, you need to change the bootloader in order to enable ota.
-
hello, is there a inclusion mode planned for the raspberry pi gateway ?
-
Hi,
This seems a great job, but despite I had a look at many posts (yes, many out of the dozens of pages.. ), I still can't figure out some questions..- Beyond the obvious advantage of saving an arduino (and power supply, space..), is there an advantage for having the gateway hosted by the raspberry PI hosting my Domoticz ? (like more CPU available for handling communications or for signing ? or on the opposite more risks to overload the PI CPU -despite only a couple persons have complained about high CPU load))
- the default setup is Ethernet. What are the pros and cons of ethernet vs serial setup ? (speed? reliability ? possibility to move to other gateway?..)
- Is signing now implemented in this setup ? I didn't see it explicitely described, but some posts seem related to signing.
- if I want to use an external antenna and the high power NRF24, should I use an aother power source than raspberry PI ? (or maybe sharing the same USB charger, but diverting the power in parallel of the PI ?)
- is there a tutorial somewhere detailing how to uninstall and migrate to an external gateway ? During such migration, would I need to "touch" again my sensors and would I lose history logs of these sensors in Domoticz ?
Sorry for all these questions..
br,
Ricorico94
-
@ricorico94 said in
Building a Raspberry Pi Gateway:Hi,
This seems a great job, but despite I had a look at many posts (yes, many out of the dozens of pages.. ), I still can't figure out some questions..- Beyond the obvious advantage of saving an arduino (and power supply, space..), is there an advantage for having the gateway hosted by the raspberry PI hosting my Domoticz ? (like more CPU available for handling communications or for signing ? or on the opposite more risks to overload the PI CPU -despite only a couple persons have complained about high CPU load))
Not really. Cpu usage is normally 0-2% so it doesn't affect either way.
Switching between different gateway types (serial, ethernet, mqtt) can be easier since there is no need to re-wire anything, just reconfigure and recompile. But that could be done with a all-in-one Arduino setup as well.
Remote debug might be a benefit, since logging in to the raspberry pi to view log files can be done remotely. Remote debug for Arduino is possible, but usually requires additional hardware.
The raspberry pi has room for more logging, which can help troubleshooting.
The biggest downside is that a raspberry pi environment is infinitely more complex than an Arduino, which could affect reliability and make troubleshooting harder. On the other hand, there are more debugging tools available which might make troubleshooting easier.
- the default setup is Ethernet. What are the pros and cons of ethernet vs serial setup ? (speed? reliability ? possibility to move to other gateway?..)
No difference in speed. No difference in reliability.
Ethernet can easily be made accessible over the network. Doing that with serial can be done but is a bit tricky.
Some controllers don't have support for all gateway types. See https://www.mysensors.org/controller for details.
- Is signing now implemented in this setup ? I didn't see it explicitely described, but some posts seem related to signing.
Yes. See the help text produced by running ./configure --help
- if I want to use an external antenna and the high power NRF24, should I use an aother power source than raspberry PI ? (or maybe sharing the same USB charger, but diverting the power in parallel of the PI ?)
Yes. See the note on https://www.mysensors.org/build/raspberry#wiring
- is there a tutorial somewhere detailing how to uninstall and migrate to an external gateway ? During such migration, would I need to "touch" again my sensors and would I lose history logs of these sensors in Domoticz ?
See my answer in the question you posted yesterday.
Sorry for all these questions..
No worries. Except for posting one of the questions again (which wastes people's time and confuses people when they read only one of the places), you are very welcome to post as many questions as you like. Asking questions is usually the next best way to learn.
-
Thanks a lot for your clear explanations ! Very useful !
and.. bravo ! for all your work
-
Hi,
I'm trying to install the gateway on a Raspberry Pi 2 hosting Domoticz already (I had used the standard Domoticz image).
I receive an error message on the make step, but maybe I've not properly understood instructions (not very friendly with raspberry and linux environment).
First, I wired the NRF24 with PA (meaning I used an adapter and the 5V physical PIN#4) and the IRQ (wired on physical pin #15)
Then I logged into my raspberry and staid in initial directory (pi@raspberrypi )
I then typed:pi@raspberrypi ~ $ git clone https://github.com/mysensors/MySensors.git --branch master Cloning into 'MySensors'... remote: Counting objects: 14895, done. remote: Compressing objects: 100% (8/8), done. remote: Total 14895 (delta 0), reused 5 (delta 0), pack-reused 14887 Receiving objects: 100% (14895/14895), 12.17 MiB | 1.68 MiB/s, done. Resolving deltas: 100% (9022/9022), done. pi@raspberrypi ~ $ cd MySensors pi@raspberrypi ~/MySensors $ ./configure --helpHopefully I did it in adequate folder ? (now I see a Mysensors folder in my /home/pi folder).
Then I typed:pi@raspberrypi ~/MySensors $ --my-transport=nrf24 -bash: --my-transport=nrf24 : commande introuvable pi@raspberrypi ~/MySensors $ ./configure --my-transport=nrf24 [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: sysvinit. [SECTION] Saving configuration. [SECTION] Cleaning previous builds. [OK] Finished.So far, no error.. but should I have typed "./configure --my-transport=nrf24 --my-rf24-irq-pin=15" to implement the IRQ ? If yes, can I retype that command with new settings without issue ?
Then I understaood I had to run make command:
pi@raspberrypi ~/MySensors $ make gcc -MT build/drivers/Linux/log.o -MMD -MP -march=armv7-a -mtune=cortex-a7 -mfpu=neon-vfpv4 -mfloat-abi=hard -DMY_RADIO_NRF24 -DMY_GATEWAY_LINUX -DMY_DEBUG -DLINUX_SPI_BCM -DLINUX_ARCH_RASPBERRYPI -Ofast -g -Wall -Wextra -I. -I./core -I./drivers/Linux -I./drivers/RPi -I./drivers/BCM -c drivers/Linux/log.c -o build/drivers/Linux/log.o cc1: error: bad value (cortex-a7) for -mtune switch Makefile:118: recipe for target 'build/drivers/Linux/log.o' failed make: *** [build/drivers/Linux/log.o] Error 1But errors...
I tried to search on forum, and saw someone else meniotning a smilar error, but people were answering about OrangePI, whereas I use a Rasp PI 2.
I probably misunderstood some steps.. Could someone help me ?Note: in instructions, there's a statement I don't understand for ethernet gateway: "To set the gateway as a client that connects to a controller, use:--my-gateway=ethernet --my-controller-url-address=YOUR-CONTROLLER-ADDRES" . IN which case do we need that ? (as said, I plan to simply use this gateway on My dodmoticz rasp PI).
br,
Ricorico94
-
@ricorico94 said in
Building a Raspberry Pi Gateway:./configure --my-transport=nrf24 --my-rf24-irq-pin=15
That is fine, no need to add extra parameters as by defaults it will configure as ethernet gateway. Also try using the development branch as it has lots of bugs fixed.
-
@ricorico94 Yesterday I managed to make a working rpi gateway. I am on rpi3, use a socket adapter board for the radio and use domoticz. I posted all the details here: https://forum.mysensors.org/topic/7793/nrf24l01-problems-in-2-1-1-and-2-2-0-beta/24
-
Hi,
@arraWX : I looked at your post. Unfortunately, the error I face is before the start, as it's during the make, so it appears I follow the first steps you describe (config & make), but I still don't know how to solve the make errors.In case it can help understanding what's going on or what to do, I ran the command:
gcc -vwhich displayed: gcc version 4.6.3 (Debian 4.6.3-14+rpi1)
Could it be an issue this "+rpi1" whreas I've a PI 2 ?
-
Do not know if it is of any help, but mine says:
gcc version 4.9.2 (Raspbian 4.9.2-10)
-
Hi,
I tried to update gcc, just in case.. though I'm not sure of what I do.
I ran:pi@raspberrypi ~/MySensors $ sudo apt-get upgrade gccand after a little while, it ended without obvious mistake.
but if I do gcc -v again, I still get
gcc version 4.6.3 (Debian 4.6.3-14+rpi1)
(even after reboot)
Is there another step to be done, or am I using wrong command ?
-
try running first sudo apt-get update and then sudo apt-get upgrade , it should update all packages
-
@gohan : JUst tried it, but same result.. no change on version number.
is there something like apt-get install to be done also ?
-
I don't know really... I am using dietpi on a RPI3 and there is a convenient tool that you can check what to install and installs for you and among the others I have chosen the "Build-Essentials" that contains all the common packages for compile, so I don't know what packages are included.
-
@ricorico94 Do you see gcc-4.9 in the list returned by the command below?
sudo apt-cache search gccIf it's listed, try installing it by specifying the version:
sudo apt-get install gcc-4.9
-
Hi, wouldn't be proper to include in the guide also the command "--my-rfm69-irq-pin=22" during the configure procedure in order to improve the throughput for the rfm69 radios?
-
Hi,
Thanks to @marceloaqno and @Gohan and @arraWX , I could progress somewhow.. but still not working.When listing the versions as per Marceloagno advice, I could see gcc-4.6 and -4.7 and 4.8 but nothing else (no 4.9).
I then decided to take the risk of installing the 4.8.. The commands from Marcelagno did not work (well, I mean gcc - v was still showing 4.6).
Then I followed this tutorial on upgrade step by step to upgrade to gcc-4.8 and then the make command apparently succeeded (well, plenty messages, some warnings.. but no error apparently, as ar as I could see. I dd not find the folders desribed in website, but the commands were still ok.. weird, but I'm too rookie..)I then followed again the Mysensors tutorial with
sudo ./bin/mysgw -h
sudo ./bin/mysgw -d (and no error message. great!)
sudo make install
but then I ran
sudo systemctl enable mysgw.service
and I got error messagesudo: systemctl: command not foundAfter some search, I saw that it's a Jessie command whereas I discovered that my good old version of Rasp Pi, which was built from the standard Domoticz image in 2015 is still Wheezy
pi@raspberrypi ~/MySensors $ cat /etc/os-release PRETTY_NAME="Raspbian GNU/Linux 7 (wheezy)" NAME="Raspbian GNU/Linux" VERSION_ID="7" VERSION="7 (wheezy)" ID=raspbian ID_LIKE=debian ANSI_COLOR="1;31" HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"Any idea of what I should do now?..
another commande equivalent to the systemctl ?
an upgrade to Jessie (any risk ? and how to do it safely ?)br,
Ricorico94
-
I am new to Linux and hopefully have an easy question...
I have followed the build instructions and everything seems to be working well so far. One issue I'm having is getting node-red to see the usb port (/dev/ttyUSB020). I did some searching online and found that if I run the following command node-red will see the port and things start working.sudo chmod 666 /dev/ttyUSB020The problem is that each time I reboot the Pi the command needs to be run again. Does anyone have any ideas on how I can resolve this so I don't need to run the command each time the system is booted? Thanks in advance.
-
@petewill you can put the chmod command in /etc/rc.local
That will execute it on every boot.
https://www.raspberrypi.org/documentation/linux/usage/rc-local.md
-
@petewill or you can compile the gateway as ethernet or mqtt that are both supported by node-red, making life a little easier
-
@mfalkvidd Thanks. I thought about doing something like that but I wasn't sure that was the best process or if something should be modified during the install. I'll give it a shot this way though. Thanks again.
-
@gohan Sorry, I did not see your reply earlier. I tried an ethernet gateway in node-red a while ago and could never get it to work with Vera. There was some port conflicts or something. I have never played with mqtt. I need to learn it at some point but I am hoping to finish this project so I can move on to some others.
Do you think I will gain significant advantages by using that over a serial/usb gateway?
-
From a node-red perspective, IMHO, mqtt is easier to handle even without specific mysensors nodes, but it all depends what you need to do. I played with it some months ago but I got stuck when I had to start using javascript as I still don't know that language, but it was quite easy to link mysensors values to the dashboard without actually touching any code.
-
@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.```
