rwblinn
-
Gesamte Inhalte
121 -
Benutzer seit
-
Letzter Besuch
Posts erstellt von rwblinn
-
-
Thanks a lot - works fine.
Further Question: Where to find the list of special chars and unicode to use (like the example you gave)?
Looking for Arror Up and Arrow Down to show trend on the LCD20x4 Bricklet display.
Again: The MQTT Proxy is fantastic.
-
Hi,
the Brick MQTT Proxy is a great extension - simplified a lot.
Question: How to display special chars on the LCD20x4?
Looking at the example below, how to display f.e. the special char ° which is HHHHHHHL according the special char table.
Example Publish Command:
mosquitto_pub -t tinkerforge/bricklet/lcd_20x4/rTS/write_line/set -m '{"line":0, "position":5, "text":"25 °C"}'
-
Hi,
I have been exploring openHAB as a starter, but experienced complex to use. Then searched for alternatives and ended up with Domoticz (open source, rather active community & developments, open api, devices easy to setup via browser, action triggers, graphs with export function ... ).
Unfortunate there are no TinkerForge bindings for Domoticz, but you can use the Domoticz api to define/read/write devices. This is done via http command (which I use via a B4J Server Application = read Bricklets)
Go here for www.domoticz.com/wiki/Domoticz_API/JSON_URL's.
PS: The WeatherCubeOne has been updated today - look www.rwblinn.de. The source code for the B4J Server Application is included.
-
Hi all,
find here http://www.rwblinn.de/144k1t2.htm the first Prototype of a simple Weatherstation which I have called WeatherCubeOne. The Cube is not fully ready yet as few tweaks required, but running fine.
Hardware
- Raspberry Pi 2 Model B.
- TinkerForge: Master Brick, Barometer Bricklet, Temperature Bricklet, Humidity Bricklet.
- MakerBeam aluminum profiles.
Software
- Domoticz Home Automation Server (http://www.domoticz.com).
- TinkerForge Brick Daemon.
- B4J App WeatherCubeOne (Developed by the author www.rwblinn.de).
- Raspberry Pi 2 Model B.
-
Hi,
setup I am using:
Raspberry Pi 2 Model B
TinkerForge: Master Brick, Bricklets:Temp, Hum, Baro, Illu, LCD, IO16
Software: Domoticz, B4J, Brick Deamon
Example simple Screenshot:
In the meantime, the solution has been developed further like adding TinkerForge LCD, trigger messages, adding switches, using IO16 - running all really well on the small Raspberry Pi.
//Really need to start documenting this further
-
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
I am working on the documentation and will share soon.
... in the meantime have a look at www.rwblinn.de under Home Automation Solution...
-
Thx = works like a charme - 30min all done.
In addition activities like reconfigure wlan, install xrdp, ...
but all GOOD.
Appreciate your help
-
Hi,
Please advice how to upgrade a RED Brick currently running v1.3 to v1.5?
Thank You
-
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
-
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
-
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?
-
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.
-
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.
More apps under Development.
Enjoy,
Rob
-
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
-
Hi Equinox,
thanks for your reply.
Will watch any developments regarding remote switches which are able to sent their switch state.
Regards,
Rob
-
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
-
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:
<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.
-
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?
-
Das wars. Vielen Dank für die schnelle Hilfe!.
Rob
-
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?
Brick MQTT Proxy - LCD20x4 Display Special Chars?
in General Discussion
Geschrieben
Thanks a lot for this very good explaination.
You might consider to include this in your documentation of the LCD displays.