Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - rwblinn

Pages: 1 ... 4 5 [6]
76
Hi,

build a Raspberry Pi solution using www.Domoticz.com server interfacing with TinkerForge Bricklets via an own developed B4J Webserver (www.b4x.com).
Think Domoticz is a good alternative to openHAB. Easy to add devices, data stored in SQLite database, Various trending with export functionality. There are no TinkerForge bindings for Domoticz, therefor build B4J Webserver using Inline Java with the TinkerForge.jar library to get the Bricklet Data and update the Domoticz sensors. Not complex to develop btw 8)
I am working on the documentation and will share soon.
... in the meantime have a look at www.rwblinn.de under Home Automation Solution...

77
General Discussion / Re: How to upgrade the RED Brick to version 1.5
« on: February 05, 2015, 17:39:19 »
Thx = works like a charme - 30min all done.
In addition activities like reconfigure wlan, install xrdp, ...

but all GOOD.

Appreciate your help

78
General Discussion / How to upgrade the RED Brick to version 1.5
« on: February 05, 2015, 16:36:18 »
Hi,
Please advice how to upgrade a RED Brick currently running v1.3 to v1.5?

Thank You

79
General Discussion / Re: Red Brick not booting [SOLVED]
« on: January 04, 2015, 18:01:11 »
Hi,

deleted the files and rebooted. Logs below. Seems an issue with server socket.

SOLVED: Actions taken: started brickd > started brickv > in settings brick daemon found the listen address 192.168.0.24 > changed to 0.0.0.0 > saved > rebooted the red brick > brickd running.

Thanks for your help

BRICKD
2015-01-04 17:53:52.471385 <I> <main_linux.c:275> Brick Daemon 2.2.0+redbrick started (daemonized)
2015-01-04 17:53:52.484484 <E> <network.c:202> Could not bind IPv4 server socket to '192.168.0.24' on port 4223: EADDRNOTAVAIL (99)
2015-01-04 17:53:52.484689 <E> <network.c:322> Could not open any socket to listen to
2015-01-04 17:53:52.485051 <I> <main_linux.c:392> Brick Daemon 2.2.0+redbrick stopped

REDAPI
2015-01-04 17:53:52.151358 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image

80
General Discussion / Re: Red Brick not booting
« on: January 03, 2015, 17:59:32 »
Hi,

pls find the logs.
In the mean time:
* connected a master brick with several bricklets, a monitor with keyboard and mouse.
* Checked using lxterminal if brickd was running > is not.
* Started the brickd using sudo brickd.
* Brickv now shows the Red Brick but not the extensions.
* Did also a sudo apt-get update and upgrade plus reboot > but after reboot brickd is not running.
* Rebooted again > brickd not running > opened lxterminal > started brickd using sudo brickd > started brickv > connected via ipaddress > the masterbrick and connected UIDs are found (red_stack.c:506 SPI stack slave discovery done. found 1 slave with 4 UIDs)
* So, the question is why brickd stops and can not find the slaves during boot.

brickd.log
2014-12-29 17:30:26.604795 <I> <main_linux.c:275> Brick Daemon 2.2.0+redbrick started (daemonized)
2014-12-29 17:30:28.222705 <I> <red_extension.c:482> Could not find Extension at position 0
2014-12-29 17:30:28.223231 <I> <red_extension.c:482> Could not find Extension at position 1
2014-12-29 17:30:28.227047 <I> <redapid.c:306> Connected to RED Brick API Daemon
2014-12-29 17:30:28.734749 <I> <red_stack.c:506> SPI stack slave discovery done. Found 0 slave(s) with 0 UID(s) in total
2014-12-29 17:35:01.536539 <I> <red_stack.c:526> Starting reinitialization of SPI slaves
2014-12-29 17:35:03.586592 <I> <red_stack.c:506> SPI stack slave discovery done. Found 0 slave(s) with 0 UID(s) in total


redapid.log
2014-12-29 17:30:26.418443 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image
2014-12-29 17:30:28.226844 <I> <network.c:97> Brick Daemon connected
2014-12-29 17:42:15.375909 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image
2014-12-29 17:42:17.184630 <I> <network.c:97> Brick Daemon connected
2014-12-29 17:56:14.922549 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image
2014-12-29 17:56:16.734145 <I> <network.c:97> Brick Daemon connected
2014-12-29 17:57:15.531784 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image
2014-12-29 17:57:17.344387 <I> <network.c:97> Brick Daemon connected
2014-12-29 17:58:15.805319 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image
2014-12-29 17:58:18.382527 <I> <network.c:97> Brick Daemon connected
2015-01-03 15:16:23.068630 <I> <brickd.c:45> Brick Daemon disconnected by peer
2015-01-03 15:16:24.705548 <I> <signal.c:53> Received SIGTERM
2015-01-03 15:16:24.705875 <W> <session.c:165> Destroying session (id: 1) while it is still tracking 3 external reference(s) to the following objects (logged on debug level):
2015-01-03 15:16:24.706265 <I> <main.c:383> RED Brick API Daemon 2.0.0 stopped
2015-01-03 15:16:35.929036 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image
2015-01-03 15:16:37.740076 <I> <network.c:97> Brick Daemon connected
2015-01-03 16:04:03.548469 <W> <api.c:957> Unknown function ID 250
2015-01-03 16:06:16.246472 <I> <brickd.c:45> Brick Daemon disconnected by peer
2015-01-03 16:06:18.928020 <I> <network.c:97> Brick Daemon connected
2015-01-03 16:06:19.650473 <W> <api.c:957> Unknown function ID 250
2015-01-03 16:07:21.713381 <I> <brickd.c:45> Brick Daemon disconnected by peer
2015-01-03 16:07:24.408626 <I> <network.c:97> Brick Daemon connected
2015-01-03 16:07:25.588723 <W> <api.c:957> Unknown function ID 250
2015-01-03 16:07:56.620711 <W> <api.c:957> Unknown function ID 250
2015-01-03 16:10:14.047589 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image
2015-01-03 16:12:14.093732 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image
2015-01-03 16:21:15.155989 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image
2015-01-03 16:21:14.097470 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image
2015-01-03 16:30:15.359022 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image
2015-01-03 16:30:15.524451 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image
2015-01-03 17:02:14.505632 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image
2015-01-03 17:08:14.474640 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image
2015-01-03 17:08:14.849923 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image
2015-01-03 17:17:15.552346 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image
2015-01-03 17:26:57.576512 <I> <signal.c:53> Received SIGTERM
2015-01-03 17:26:57.577033 <I> <main.c:383> RED Brick API Daemon 2.0.0 stopped
2015-01-03 17:27:11.858495 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image
2015-01-03 17:30:47.040953 <I> <network.c:97> Brick Daemon connected
2015-01-03 17:33:32.567326 <I> <brickd.c:45> Brick Daemon disconnected by peer
2015-01-03 17:33:35.270745 <I> <network.c:97> Brick Daemon connected
2015-01-03 17:35:27.202084 <I> <brickd.c:45> Brick Daemon disconnected by peer
2015-01-03 17:35:28.597477 <I> <signal.c:53> Received SIGTERM
2015-01-03 17:35:28.597813 <W> <session.c:165> Destroying session (id: 3) while it is still tracking 16 external reference(s) to the following objects (logged on debug level):
2015-01-03 17:35:28.598384 <I> <main.c:383> RED Brick API Daemon 2.0.0 stopped
2015-01-03 17:35:41.576397 <I> <main.c:309> RED Brick API Daemon 2.0.0 started (daemonized) on 1.3 (full) image
2015-01-03 17:39:25.524075 <I> <network.c:97> Brick Daemon connected

81
General Discussion / Red Brick not booting
« on: January 03, 2015, 16:53:05 »
Hi,

after connecting my (new) red brick via USB to a windows PC and configuring using the Brick Viewer. I rebooted the brick BUT ...the Green Light is ON (Linux bootmodus) but not blinking (Linux ready). Can also not connect via the Brick Viewer. The Brick has a wlan adapter and is reachable using ping.

Any hints?

82
Hi borg,

Yes that is correct.
Anywhere Software offers Rapid Application Development tools for native Android (tool B4A), iOS (tool B4i) and Desktop plus server (tool B4J). I have developed first B4A and B4J apps to talk to a TinkerForge MasterBrick and several connected Bricklets (RemoteSwitch, Temperature, Humidity, Barometer) using the tinkerforge.jar Library. The Basic dialect developed by Anywhere Software offers a JavaObject library to make that happen.

83
Hi All,

want to share example apps to control the Master Brick and Bricklets using B4x (see http://www.b4x.com - Rapid Application Development (RAD) tools for native Android (B4A), iOS (B4i) and desktop / webserver apps (B4J)). So far, have not seen any TinkerForge examples using B4x. With B4x it is rather simple to control Bricks using the Java Library. It is also possible to use the JavaScript Library.

Additional information & examples
Control Bricklets RemoteSwitch, Temperature, Humidity
B4A & B4J App using TinkerForge Java API Binding.
http://www.b4x.com/android/forum/threads/tinkerforge-control-example.48625/#post-302383

Raspberry Pi Webserver to control Bricklet RemoteSwitch
B4J Webserver using JQuery Mobile & TinkerForge JavaScript API Binding.
http://www.b4x.com/android/forum/threads/home-automation-with-b4a-b4j-using-tinkerforge.41474/#post-252946

More apps under Development.
Enjoy,
Rob

84
Hi,

what is the best way, in JavaScript, to fast (=immediate) check if a) the HOST is reachable and b) the bricklet is connencted.
There should no delay in response after trying to connect.
If an error, then the result to be messaged to the user.

Appreciated,
Rob

85
Hi Equinox,

thanks for your reply.

Will watch any developments regarding remote switches which are able to sent their switch state.

Regards,
Rob

86
Hi All,

have build an app (based on the JavaScript API) using the remote switch bricklet to switch devices ON/OFF.
When starting the App, would like to determine the state of a remote switch to be able to set the initial state of the switches in the app.

Question: Is there a (JavaScript) function available? like getRemoteSwitchState resulting in on or off?

Appreciated,
Rob

87
Hallo,

bin diese Woche neu eingestiegen und habe das JavaScript Beispiel "Temperatur Bricket ExampleCallback", wie folgt installiert:
\temperature\Tinkerforge\Tinkerforge.js
\temperature\ExampleCallback.html

In ExampleCallback.html folgende Anpassungen:
Code: [Select]
<script src="./Tinkerforge/Tinkerforge.js" type='text/javascript'></script>

und den HOST, PORT, UID entsprechend definieren.

Info: habe den Master Brick an einem Raspberry, der als Homeserver aufgesetzt ist, angeschlossen. Zugriff erfolgt Remote via duckdns und Home Router Port forwarding.

88
Hallo,

versuche beispiel ExampleAuthenticate.pas auszuführen, aber erhalte timeout fehler bei sender.Authenticate.

Habe die gleichen angaben für HOST, PORT und SECRET verwendet, wie für den Brick Viewer (funktioniert einwandfrei). Auch mittels iot-remote.com funktioniert es.

Zugriff erfolgt via internet auf ein raspi server.

Was könnte das problem sein?

89
Anfängerfragen und FAQ / Re: IOT Remote keine Verbindung
« on: May 28, 2014, 18:23:08 »
Das wars. Vielen Dank für die schnelle Hilfe!.

Rob

90
Anfängerfragen und FAQ / IOT Remote keine Verbindung
« on: May 28, 2014, 14:38:22 »
Hallo,

bin neueinstiger. das remote starter kit installiert und remote schalter können via brick viewer geschaltet werden, aber via IOT-REMOTE.COM nicht?
Brick Viewer Setup: Host: localhost, Port=4223; Keine Auth.

Angaben im iot-remote.com (localhost, 4223, auth leer) ergibt fehlermeldung nr 13 (=could not connect to localhost).

Wer hat einen tipp?

Pages: 1 ... 4 5 [6]