-
Notifications
You must be signed in to change notification settings - Fork 9
Latest build results #14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I guess the sqlite database file permission is missing. Could you try running with sudo, or change the file permission of the database file. |
BTW, I'm working on the warnings. Once that is fixed, we should be able to clearly see the error messages. |
running "sudo cargo run" is not possible ("sudo: cargo: command not found") I also tried "cargo build --release" today. It compiled (slowly), but after that I couldn't find the executable. There was no "target" folder. |
Trying to get things to work. I added two devices, one on port 8888 and one on port 8000, since that's the port I keep seeing in the logs, even though the about file mentions port 8888. Oct 23 21:46:30 gateway run-app.sh[562]: 2018-10-23 21:46:30.209 thing-url: Failed to parse description at http://localhost:8000: SyntaxError: Unexpected token A in JSON at position 0 |
Here's a random bit of log from the console: pi@gateway:~/MySController-rs $ sudo ./target/debug/myscontroller-rs |
If I use the 5003 port on both places in the conf.ini file, I get an error. So: ` [Gateway] [Controller] [Server] Which leads to an error: pi@gateway:~/MySController-rs/target/debug $ sudo ./myscontroller-rs |
It even seems to lead to an undervoltage situation, although it could just be a coincidence. Oct 23 22:02:55 gateway run-app.sh[562]: 2018-10-23 22:02:55.058 Loading add-on: thing-url-adapter |
I just discovered that I can go to the IP address of the Raspberry Pi That shows a tiny API details page. If I try and visit:
..that gives an empty json:
|
It seems the 'generic adapter' dies when trying to poll the devices. This is from journalCTL: Oct 23 22:48:07 gateway run-app.sh[592]: Package not enabled: zigbee-adapter Maybe slight overlap with: Oct 23 22:48:33 gateway run-app.sh[592]: 2018-10-23 22:48:33.949 generic-sensors: at processImmediate [as _immediateCallback] (timers.js:745:5) |
And a final bit of console reporting: pi@gateway:~ $ sudo service myscontroller-rs stop |
Could you also post your conf.ini file here. |
I think conf.ini got changed when you pulled the latest code. |
I now have this Address in the Mozilla Gateway: conf.ini: encoding=utf-8 [Gateway] [Controller] [Server] The journalctl results: pi@gateway:~ $ sudo ./MySController-rs/target/debug/myscontroller-rs The two sensors it found earlier are not being updated. Add devices Oct 24 12:40:02 gateway run-app.sh[539]: 2018-10-24 12:40:02.986 About to call startPairing on GenericSensorsAdapter |
If I use this conf where both ports are set to 5003 (as in the example on github) encoding=utf-8 [Gateway] [Controller] [Server] I the console I get this "Address already in use" error, but data does still come through: pi@gateway:~ $ sudo ./MySController-rs/target/debug/myscontroller-rs I see this in LSOF: I see this in JournalCTL: Oct 24 12:45:35 gateway run-app.sh[539]: 2018-10-24 12:45:35.866 getValue for property level for: Ambient Light Sensor returning 0 These correspond to the values in my Mozilla Gateway interface. It's as if it's reading those values. |
This config is correct. Don't use the same port for controller (I'll correct the example). I don't see the log of WoT server starting up, something like
This error message is also pointing to that fact. Could you change the port number in file |
And regarding the |
This is me plugging in another device (plant moisture sensor with 6 sensors and 6 'dimmers' to set the minimum moisture level per plant where it should be irrigated) INFO 2018-10-24T11:11:52Z: myscontroller_rs::core::connection: 0.0.0.0:5003 >> "1;7;2;0;3;\n" |
This is an interesing error that occurs when I change the value of a sensor in the Mozilla Gateway manually. Oct 24 13:10:08 gateway run-app.sh[539]: 2018-10-24 13:10:08.733 generic-sensors: at AmbientLight.onerror (/home/pi/.mozilla-iot/addons/generic-sensors-adapter/node_modules/generic-sensors-lite/ambientlight/index.js:33:11) |
Yes, that was what I expected. But that folder didn't exist after running that command. |
That's really strange :/ Regarding the errors, it reiterates the same thing, the WoT server is not running. Please try with a new port and see if that works. |
I'll try this url: or should it be https? |
This should work. http only |
I still don't see the server starting in the console output. pi@gateway:~/MySController-rs/target/debug $ sudo ./myscontroller-rs |
Perhaps a quick call? I have emailed you. |
Pulled the latest version (the one which where the WoT server reboots when a new device appears). Maybe I should start with a fresh Mozilla Gateway image again. pi@gateway:~/MySController-rs/target/debug $ ./myscontroller-rs |
It seems an error is generated if it hasn't seen a device before. pi@gateway:~/MySController-rs/target/debug $ sudo ./myscontroller-rs |
Restarting the node should fix the issue. |
I found a new issue. At first I started the target/debug version, and noticed that port 8888 was set as LISTEN. So it seemed the WoT server was started: myscontro 9412 pi 16u IPv4 92285339 0t0 TCP *:8000 (LISTEN) However, the Mozilla Gateway didn't seem to connect to it. So I thought "perhaps it should be a service, then it might start earlier, and then it might work. However, the result as a service is a different error: A larger part of the journalctl log: Oct 28 17:50:55 gateway dhcpcd[321]: wlan0: starting wpa_supplicant |
Interesting: if I manually try to add a webthing at the 'add things' page, I get: http://127.0.0.1:8888 -> Web things must be added individually So that implies it can connect to the WoT server. JournalCTL also does NOT give an error, but says "Opened a new things socket". So that looks good. The console logs still starts without mentioning that the WoT server started: pi@gateway:~/MySController-rs/target/debug $ ./myscontroller-rs The error (which we saw in the earlier comments I posted too) seems to point to the MySensors gateway itself (node 0). If I started the MySensors Gateway deamon I get this: ERROR 2018-10-28T18:13:11Z: myscontroller_rs::core::connection: Error while reading -- reached EOF So the MySConroller-rs does neatly reconnect to the MySensors gateway software (nice!), but just has the same error again. |
From the logs, I can see that the node with id 0 is not created in
myscontroller database. If you could restart the node (with myscontroller
running), then it should create the node.
After that it should work fine.
…On Sun, Oct 28, 2018 at 11:44 PM flatsiedatsie ***@***.***> wrote:
Interesting:
if I manually try to add a webthing at the 'add things' page, I get:
http://127.0.0.1:8888 -> Web things must be added individually
https://127.0.0.1:8888 -> Web thing not found
So that implies it can connect to the WoT server.
JournalCTL also does NOT give an error, but says "Opened a new things
socket". So that looks good.
The console logs still starts without mentioning that the WoT server
started:
***@***.***:~/MySController-rs/target/debug $ ./myscontroller-rs
INFO 2018-10-28T17:56:14Z: actix_web::server::srv: Starting 4 http workers
INFO 2018-10-28T17:56:14Z: actix_web::server::srv: Starting server on
http://0.0.0.0:8000
INFO 2018-10-28T17:56:14Z: myscontroller_rs: Starting proxy server
INFO 2018-10-28T17:56:14Z: myscontroller_rs::core::connection: Server
listening on -- 0.0.0.0:8090
INFO 2018-10-28T17:56:14Z: myscontroller_rs::core::connection: Waiting for
server connection -- 0.0.0.0:5003 ...
INFO 2018-10-28T17:56:14Z: myscontroller_rs::core::connection: Connected
to -- 0.0.0.0:5003
INFO 2018-10-28T17:56:14Z: myscontroller_rs::core::connection:
0.0.0.0:5003 >> "0;255;3;0;14;Gateway startup complete.\n"
INFO 2018-10-28T17:56:14Z: myscontroller_rs::core::connection:
0.0.0.0:5003 >> "0;255;0;0;18;2.3.0\n"
*ERROR 2018-10-28T17:56:14Z:
myscontroller_rs::core::message_handler::presentation: Error while checking
for existing node of Sensor { node_id: 0, child_sensor_id: 255,
sensor_type: ArduinoRepeaterNode, description: "2.3.0" } NotFound*
INFO 2018-10-28T17:56:14Z: actix_web::server::srv: Starting 4 http workers
INFO 2018-10-28T17:56:14Z: actix_web::server::srv: Starting server on
http://0.0.0.0:8888
INFO 2018-10-28T17:56:14Z: actix_web::middleware::logger:
192.168.2.1:59842 [28/Oct/2018:18:56:14 +0100] "GET / HTTP/1.1" 200 2 "-"
"node-fetch/1.0 (+https://github.com/bitinn/node-fetch)" 0.001903
INFO 2018-10-28T17:58:31Z: actix_web::middleware::logger: 127.0.0.1:49744
[28/Oct/2018:18:58:31 +0100] "GET / HTTP/1.1" 200 2 "-" "node-fetch/1.0 (+
https://github.com/bitinn/node-fetch)" 0.001459
INFO 2018-10-28T17:58:51Z: actix_web::middleware::logger: 127.0.0.1:49746
[28/Oct/2018:18:58:51 +0100] "GET / HTTP/1.1" 200 2 "-" "node-fetch/1.0 (+
https://github.com/bitinn/node-fetch)" 0.001568
INFO 2018-10-28T18:03:41Z: actix_web::middleware::logger: 127.0.0.1:49748
[28/Oct/2018:19:03:41 +0100] "GET / HTTP/1.1" 200 2 "-" "node-fetch/1.0 (+
https://github.com/bitinn/node-fetch)" 0.001364
INFO 2018-10-28T18:03:54Z: actix_web::middleware::logger: 127.0.0.1:49752
[28/Oct/2018:19:03:54 +0100] "GET / HTTP/1.1" 200 2 "-" "node-fetch/1.0 (+
https://github.com/bitinn/node-fetch)" 0.001216
INFO 2018-10-28T18:04:03Z: actix_web::middleware::logger: 127.0.0.1:49754
[28/Oct/2018:19:04:03 +0100] "GET /2 HTTP/1.1" 404 0 "-" "node-fetch/1.0 (+
https://github.com/bitinn/node-fetch)" 0.001198
INFO 2018-10-28T18:04:07Z: actix_web::middleware::logger: 127.0.0.1:49756
[28/Oct/2018:19:04:07 +0100] "GET /1 HTTP/1.1" 404 0 "-" "node-fetch/1.0 (+
https://github.com/bitinn/node-fetch)" 0.001177
INFO 2018-10-28T18:04:10Z: actix_web::middleware::logger: 127.0.0.1:49758
[28/Oct/2018:19:04:10 +0100] "GET / HTTP/1.1" 200 2 "-" "node-fetch/1.0 (+
https://github.com/bitinn/node-fetch)" 0.001191
The error (which we saw in the earlier comments I posted too) seems to
point to the *MySensors gateway* itself (node 0).
If I started the MySensors Gateway deamon I get this:
ERROR 2018-10-28T18:13:11Z: myscontroller_rs::core::connection: Error
while reading -- *reached EOF*
INFO 2018-10-28T18:13:11Z: myscontroller_rs::core::connection: Waiting for
server connection -- 0.0.0.0:5003 ...
INFO 2018-10-28T18:13:11Z: myscontroller_rs::core::connection: Connected
to -- 0.0.0.0:5003
INFO 2018-10-28T18:13:11Z: myscontroller_rs::core::connection:
0.0.0.0:5003 >> "0;255;3;0;14;Gateway startup complete.\n"
INFO 2018-10-28T18:13:11Z: myscontroller_rs::core::connection:
0.0.0.0:5003 >> "0;255;0;0;18;2.3.0\n"
*ERROR 2018-10-28T18:13:11Z:
myscontroller_rs::core::message_handler::presentation: Error while checking
for existing node of Sensor { node_id: 0, child_sensor_id: 255,
sensor_type: ArduinoRepeaterNode, description: "2.3.0" } NotFound*
So the MySConroller-rs does neatly reconnect to the MySensors gateway
software (nice!), but just has the same error again.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABaM5F_62pesaxatYfjWDjE0tRJ2rJ7_ks5upfQSgaJpZM4X1hCn>
.
|
Node 0 is the MySensors gateway. I tried restarting it, but that didn't change anything. The Mozilla gateway always shows just two sensors: a temperature and a light sensor. Even though I have no device that contains those sensors. When I added those devices in the past they never got updated. I think it might also be related to the generic-sensors-adapter add-on? Can the Mozilla Gateway only support certain specific types of devices? What MySensors devices do you connect to it? I think I will wait with further testing and trying until you've tried it on a Raspberry Pi :-) |
For gateway this error message fine.
|
Yes, I have multiple nodes present. This is what I get when I try to access it: [] |
The two devices that the Mozilla Gateway did find, it turns out those are from the GPIO add-on. So I now realise I've never had a successful connection. Have you had a chance to test it on a Raspberry Pi yourself? |
I was able to test it in a Raspberry Pi. It works fine. I would suggest you to do things step by step to understand if there is a problem.
Let me know if you stuck on any of these steps. We can get into a call and figure out the issue. |
That's great news! I'll try right away! Did you try it based on the Mozilla Gateway image? |
Here's the latest build details: pi@gateway: warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type warning: cannot find type
thread 'main' panicked at 'Failed to create pool.: Error(Some("Unable to open the database file"))', libcore/result.rs:1009:5 I had deleted the database file for a 'clean start', and had to start MySController-rs from output/debug with sudo to re-create it. pi@gateway: |
I still can't get it to work. Hardware:
sudo curl https://sh.rustup.rs -sSf | sh I always get the same errors. pi@gateway:~/MySController-rs/target/debug $ sudo ./myscontroller-rs |
I created a put request in Postman, as suggested. http://192.168.2.110:8000/nodes?{&"node_name"= "NewSensor",&"node_id"= 1,&"firmware_type"= This results in the response: [] After that, trying "http://192.168.2.110:8000/nodes" or "http://192.168.2.110:8888/" both still result in: [] |
You need to create a node with id 14.
…On Mon, Nov 19, 2018, 9:45 PM flatsiedatsie ***@***.*** wrote:
I still can't get it to work.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABaM5LqdW54iHGGmMexGCCHFseg7Ht97ks5uwtkMgaJpZM4X1hCn>
.
|
It should be post request.
…On Mon, Nov 19, 2018, 9:56 PM flatsiedatsie ***@***.*** wrote:
I created a put request in Postman, as suggested.
http://192.168.2.110:8000/nodes?{&"node_name"= "NewSensor",&"node_id"=
1,&"firmware_type"=
This results in the response:
[]
After that, trying "http://192.168.2.110:8000/nodes" or "
http://192.168.2.110:8888/" both still result in:
[]
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABaM5Dc9Wj54oJByFfBEok6wPqwbCfBhks5uwtuwgaJpZM4X1hCn>
.
|
Got the Post to work. http://192.168.2.110:8000/nodes now gives data. [{"node_id":1,"node_name":"NewSensor","firmware_type":0,"firmware_version":0,"desired_firmware_type":1,"desired_firmware_version":1,"auto_update":false,"scheduled":false,"parent_node_id":0},{"node_id":14,"node_name":"CO2 sensor","firmware_type":0,"firmware_version":0,"desired_firmware_type":1,"desired_firmware_version":1,"auto_update":true,"scheduled":false,"parent_node_id":0}] http://192.168.2.110:8888 still results in [] |
I restarted from scratch today with a fresh Mozilla Gateway image (0.6.1), and a fresh creation of MySController-rs. But I got to the same place.
|
I think the problem is in the way you post data. The json should go in body
and not as query param.
…On Mon, Nov 19, 2018, 10:26 PM flatsiedatsie ***@***.*** wrote:
I restarted from scratch today with a fresh Mozilla Gateway image (0.6.1),
and a fresh creation of MySController-rs. But I got to the same place.
- Are you also using a radio connected to the GPIO? With the MySensors
gateway software running as the Ethernet version?
- What kind of MySensors devices are you running? Perhaps they are
very different?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABaM5BWQm3lE9IRLtXAE4C_o96y6yNGhks5uwuK7gaJpZM4X1hCn>
.
|
yes, I fixed that. I updated my post above. |
http://192.168.2.110:8000/sensors now gives: [{"node_id":14,"child_sensor_id":255,"sensor_type":"ArduinoRepeaterNode","description":"2.3.0"},{"node_id":14,"child_sensor_id":0,"sensor_type":"AirQuality","description":""}] 8888 is still empty. |
Did you restart the myscontroller after sensors got added? |
My sensors bootloader would help in
It is not mandatory. But will make your life easier. |
Thanks for the answers.
Yes I did. I restarted everything I could restart multiple times :-) |
I just noticed: pi@gateway:~/MySController-rs/target/debug $ sudo ./myscontroller-rs |
Ah, that makes sense. Airquality sensor has to be handled. I'll work on
that.
…On Tue, Nov 20, 2018, 1:34 PM flatsiedatsie ***@***.*** wrote:
I just noticed:
***@***.***:~/MySController-rs/target/debug $ sudo ./myscontroller-rs
INFO 2018-11-20T08:03:55Z: actix_web::server::srv: Starting 4 http workers
INFO 2018-11-20T08:03:55Z: actix_web::server::srv: Starting server on
http://0.0.0.0:8000
INFO 2018-11-20T08:03:55Z: myscontroller_rs: Starting proxy server
INFO 2018-11-20T08:03:55Z: myscontroller_rs::core::connection: Waiting for
server connection -- 0.0.0.0:5003 ...
*WARN 2018-11-20T08:03:55Z: myscontroller_rs::wot::adapter:
PresentationType ArduinoRepeaterNode is not handled yet! WARN
2018-11-20T08:03:55Z: myscontroller_rs::wot::adapter: PresentationType
AirQuality is not handled yet!*
INFO 2018-11-20T08:03:55Z: myscontroller_rs::core::connection: Connected
to -- 0.0.0.0:5003
INFO 2018-11-20T08:03:55Z: myscontroller_rs::core::connection: Server
listening on -- 0.0.0.0:9095
INFO 2018-11-20T08:03:55Z: myscontroller_rs::core::connection:
0.0.0.0:5003 >> "0;255;3;0;14;Gateway startup complete.\n"
INFO 2018-11-20T08:03:55Z: myscontroller_rs::core::connection:
0.0.0.0:5003 >> "0;255;0;0;18;2.3.0\n"
ERROR 2018-11-20T08:03:55Z:
myscontroller_rs::core::message_handler::presentation: Error while checking
for existing node of Sensor { node_id: 0, child_sensor_id: 255,
sensor_type: ArduinoRepeaterNode, description: "2.3.0" } NotFound
INFO 2018-11-20T08:03:55Z: actix_web::server::srv: Starting 4 http workers
INFO 2018-11-20T08:03:55Z: actix_web::server::srv: Starting server on
http://0.0.0.0:8888
INFO 2018-11-20T08:03:55Z: actix_web::middleware::logger:
192.168.2.110:38282 [20/Nov/2018:09:03:55 +0100] "GET / HTTP/1.1" 200 2
"-" "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)" 0.039264
INFO 2018-11-20T08:03:57Z: myscontroller_rs::core::connection:
0.0.0.0:5003 >> "14;0;1;0;37;301\n"
WARN 2018-11-20T08:03:57Z: myscontroller_rs::wot: No thing found matching
SetMessage { node_id: 14, child_sensor_id: 0, ack: 0, value: Value {
set_type: Level, value: "301" } }
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABaM5B8jXbz0ZQqN594rYUFhQhgfLOJxks5uw7epgaJpZM4X1hCn>
.
|
It's alive! This time really. I added another test device with three relays. And after adding that device manually the :8888 shows devices! And they show up in Mozilla Gateway! It's a start! So I guess now the only question is:
|
This is because - in our setup we create the nodes by sending firmwares over the air (and the node_id gets assigned automatically by the controller). But in your case the node ids are already set, but the controller doesn't know about the node_id. I have a solution in mind. If there is a presentation message from node, we can auto create it with no firmware.
Definitely. I need help in understanding about the sensor outputs. What kind of values will be coming from the sensor, so that I can map it correctly to the Mozilla WoT thing. To start with, what is the output of AirQuality Sensor, quick look at the mysensors API tells that V_LEVEL and V_UNIT_PREFIX are applicable for S_AIR_QUALITY. Is that all? |
And it would be better to use some other medium or another issue. Because this issue is filled with long logs and Github is struggling to load this page :D |
Perhaps it's useful, so here are the latest results from "cargo run":
pi@gateway:~ $ cd MySController-rs/
pi@gateway:
/MySController-rs $ git pull/MySController-rs $ cargo runremote: Enumerating objects: 83, done.
remote: Counting objects: 100% (83/83), done.
remote: Compressing objects: 100% (36/36), done.
remote: Total 63 (delta 44), reused 44 (delta 26), pack-reused 0
Unpacking objects: 100% (63/63), done.
From https://github.com/tsathishkumar/MySController-rs
85a1ef9..d8f4b0e master -> origin/master
Updating 85a1ef9..d8f4b0e
Fast-forward
.bintray.json | 6 +-
.travis.yml | 1 +
Cargo.lock | 2 +-
Cargo.toml | 16 ++---
README.md | 16 ++++-
build.sh | 24 ++-----
.../down.sql | 1 +
.../up.sql | 1 +
src/core/interceptor.rs | 33 ++++-----
src/core/message/internal.rs | 83 ++++++++++++++++++++++
src/core/message/mod.rs | 13 +++-
src/core/message_handler/internal.rs | 64 ++++++++++++-----
src/core/server.rs | 3 +-
src/handler/node.rs | 1 +
src/model/node.rs | 2 +
15 files changed, 195 insertions(+), 71 deletions(-)
create mode 100644 migrations/2018-10-12-103949_add_parent_node_id_in_nodes/down.sql
create mode 100644 migrations/2018-10-12-103949_add_parent_node_id_in_nodes/up.sql
create mode 100644 src/core/message/internal.rs
pi@gateway:
Compiling myscontroller-rs v0.6.1 (/home/pi/MySController-rs)
warning: unused import:
hex
--> src/core/message/internal.rs:2:5
|
2 | use hex;
| ^^^
|
= note: #[warn(unused_imports)] on by default
warning: unused import:
std::mem
--> src/core/message/internal.rs:5:5
|
5 | use std::mem;
| ^^^^^^^^
warning: unnecessary parentheses around method argument
--> src/core/message_handler/internal.rs:82:14
|
82 | .set((parent_node_id.eq(_parent_node_id)))
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: remove these parentheses
|
= note: #[warn(unused_parens)] on by default
warning: cannot find type
table
in this scope--> <::diesel::macros::table_body macros>:165:33
|
165 | derive ( Debug , Clone , Copy , QueryId ) ] /// The actual table struct
| ^^^^^^^ names from parent modules are not accessible without an explicit import
|
= note: #[warn(proc_macro_derive_resolution_fallback)] on by default
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
table
in this scope--> <::diesel::macros::table_body macros>:165:33
|
165 | derive ( Debug , Clone , Copy , QueryId ) ] /// The actual table struct
| ^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
firmware_type
in this scope--> <::diesel::macros::__diesel_column macros>:5:33
|
5 | derive ( Debug , Clone , Copy , QueryId , Default ) ] pub struct $ column_name
| ^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
firmware_version
in this scope--> <::diesel::macros::__diesel_column macros>:5:33
|
5 | derive ( Debug , Clone , Copy , QueryId , Default ) ] pub struct $ column_name
| ^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
name
in this scope--> <::diesel::macros::__diesel_column macros>:5:33
|
5 | derive ( Debug , Clone , Copy , QueryId , Default ) ] pub struct $ column_name
| ^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
blocks
in this scope--> <::diesel::macros::__diesel_column macros>:5:33
|
5 | derive ( Debug , Clone , Copy , QueryId , Default ) ] pub struct $ column_name
| ^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
crc
in this scope--> <::diesel::macros::__diesel_column macros>:5:33
|
5 | derive ( Debug , Clone , Copy , QueryId , Default ) ] pub struct $ column_name
| ^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
data
in this scope--> <::diesel::macros::__diesel_column macros>:5:33
|
5 | derive ( Debug , Clone , Copy , QueryId , Default ) ] pub struct $ column_name
| ^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
Firmware
in this scope--> src/model/firmware.rs:23:10
|
23 | #[derive(Queryable, Serialize, Deserialize, Insertable, Clone)]
| ^^^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
firmwares
in this scope--> src/model/firmware.rs:23:45
|
23 | #[derive(Queryable, Serialize, Deserialize, Insertable, Clone)]
| ^^^^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
Firmware
in this scope--> src/model/firmware.rs:23:45
|
23 | #[derive(Queryable, Serialize, Deserialize, Insertable, Clone)]
| ^^^^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
node_id
in this scope--> <::diesel::macros::__diesel_column macros>:5:33
|
5 | derive ( Debug , Clone , Copy , QueryId , Default ) ] pub struct $ column_name
| ^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
node_name
in this scope--> <::diesel::macros::__diesel_column macros>:5:33
|
5 | derive ( Debug , Clone , Copy , QueryId , Default ) ] pub struct $ column_name
| ^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
desired_firmware_type
in this scope--> <::diesel::macros::__diesel_column macros>:5:33
|
5 | derive ( Debug , Clone , Copy , QueryId , Default ) ] pub struct $ column_name
| ^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
desired_firmware_version
in this scope--> <::diesel::macros::__diesel_column macros>:5:33
|
5 | derive ( Debug , Clone , Copy , QueryId , Default ) ] pub struct $ column_name
| ^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
auto_update
in this scope--> <::diesel::macros::__diesel_column macros>:5:33
|
5 | derive ( Debug , Clone , Copy , QueryId , Default ) ] pub struct $ column_name
| ^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
scheduled
in this scope--> <::diesel::macros::__diesel_column macros>:5:33
|
5 | derive ( Debug , Clone , Copy , QueryId , Default ) ] pub struct $ column_name
| ^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
parent_node_id
in this scope--> <::diesel::macros::__diesel_column macros>:5:33
|
5 | derive ( Debug , Clone , Copy , QueryId , Default ) ] pub struct $ column_name
| ^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
Node
in this scope--> src/model/node.rs:15:10
|
15 | #[derive(Queryable, Serialize, Deserialize, Insertable, Debug)]
| ^^^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
nodes
in this scope--> src/model/node.rs:15:45
|
15 | #[derive(Queryable, Serialize, Deserialize, Insertable, Debug)]
| ^^^^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
Node
in this scope--> src/model/node.rs:15:45
|
15 | #[derive(Queryable, Serialize, Deserialize, Insertable, Debug)]
| ^^^^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
child_sensor_id
in this scope--> <::diesel::macros::__diesel_column macros>:5:33
|
5 | derive ( Debug , Clone , Copy , QueryId , Default ) ] pub struct $ column_name
| ^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
sensor_type
in this scope--> <::diesel::macros::__diesel_column macros>:5:33
|
5 | derive ( Debug , Clone , Copy , QueryId , Default ) ] pub struct $ column_name
| ^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
description
in this scope--> <::diesel::macros::__diesel_column macros>:5:33
|
5 | derive ( Debug , Clone , Copy , QueryId , Default ) ] pub struct $ column_name
| ^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
PresentationType
in this scope--> src/model/sensor.rs:16:10
|
16 | #[derive(Queryable, Serialize, Deserialize, Insertable, Debug, PartialEq, Clone)]
| ^^^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
Sensor
in this scope--> src/model/sensor.rs:16:10
|
16 | #[derive(Queryable, Serialize, Deserialize, Insertable, Debug, PartialEq, Clone)]
| ^^^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
sensors
in this scope--> src/model/sensor.rs:16:45
|
16 | #[derive(Queryable, Serialize, Deserialize, Insertable, Debug, PartialEq, Clone)]
| ^^^^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
Sensor
in this scope--> src/model/sensor.rs:16:45
|
16 | #[derive(Queryable, Serialize, Deserialize, Insertable, Debug, PartialEq, Clone)]
| ^^^^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: cannot find type
PresentationType
in this scope--> src/model/sensor.rs:16:45
|
16 | #[derive(Queryable, Serialize, Deserialize, Insertable, Debug, PartialEq, Clone)]
| ^^^^^^^^^^ names from parent modules are not accessible without an explicit import
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #50504 rust-lang/rust#50504
warning: unused variable:
ack
--> src/core/message_handler/internal.rs:38:65
|
38 | InternalMessage {node_id, child_sensor_id: 255, ack, sub_type: InternalType::DiscoverResponse, ref payload } => {
| ^^^ help: try ignoring the field:
ack: _
|
= note: #[warn(unused_variables)] on by default
warning: constant item is never used:
MAX_MESSAGE_LENGTH
--> src/core/message/internal.rs:7:1
|
7 | const MAX_MESSAGE_LENGTH: usize = 32;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: #[warn(dead_code)] on by default
INFO 2018-10-23T12:51:35Z: actix_web::server::srv: Starting 4 http workers
INFO 2018-10-23T12:51:35Z: actix_web::server::srv: Starting server on http://0.0.0.0:8000
Running migration 20181012103949
thread 'main' panicked at 'called
Result::unwrap()
on anErr
value: QueryError(DatabaseError(__Unknown, "attempt to write a readonly database"))', libcore/result.rs:1009:5stack backtrace:
0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
1: std::sys_common::backtrace::print
at libstd/sys_common/backtrace.rs:71
at libstd/sys_common/backtrace.rs:59
2: std::panicking::default_hook::{{closure}}
at libstd/panicking.rs:211
3: std::panicking::default_hook
at libstd/panicking.rs:227
4: std::panicking::rust_panic_with_hook
at libstd/panicking.rs:476
5: std::panicking::continue_panic_fmt
at libstd/panicking.rs:390
6: rust_begin_unwind
at libstd/panicking.rs:325
7: core::panicking::panic_fmt
at libcore/panicking.rs:77
8: core::result::unwrap_failed
at libcore/macros.rs:26
9: <core::result::Result<T, E>>::unwrap
at libcore/result.rs:808
10: myscontroller_rs::main
at src/main.rs:105
11: std::rt::lang_start::{{closure}}
at libstd/rt.rs:74
12: std::panicking::try::do_call
at libstd/rt.rs:59
at libstd/panicking.rs:310
13: __rust_maybe_catch_panic
at libpanic_unwind/lib.rs:102
14: std::panicking::try
at libstd/panicking.rs:289
15: std::rt::lang_start_internal
at libstd/panic.rs:392
at libstd/rt.rs:58
16: std::rt::lang_start
at libstd/rt.rs:74
17: main
18: __libc_start_main
pi@gateway:~/MySController-rs $
The text was updated successfully, but these errors were encountered: