Jump to content
View in the app

A better way to browse. Learn more.

Tinkerunity

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

muekno

Members
  • Benutzer seit

  • Letzter Besuch

  1. Habe jetzt testhalber Leere Zeile 34 gelöscht und der Check geht durch, unverständlich Gruß RAiner
  2. root@CAN:~# sudo brickd --check-config Unexpected error ERANGE (34) occurred Error(s) occurred while reading config file '/etc/brickd.conf' Das heisst für mich Zeile 34 hat einen Fehler, Ausschnitt der brickd.conf 28 # The default values are 0.0.0.0, 4223, 0 (disabled), 4240 and off. 29 listen.address = 0.0.0.0 30 listen.plain_port = 4223 31 listen.websocket_port = 4280 # 32 listen.mesh_gateway_port = 4240 33 listen.dual_stack = off 34 35 # Network Authentication 36 # Zeilenummern habe ich händisch eingefügt, was soll an einer Leerzeile die original vorhanden ist falsch sein. Geändert habe ich an der Datei nur den Port für den websocket_port Gruß Rainer
  3. Ich habe ein PI mit dem aktuelle RASBIAN BUSTER TINY aktuelle Patches, d.h. ohne Tastatur und Bildschirm. verbinde über SSH. Habe nach dieser https://www.tinkerforge.com/de/doc/Embedded/Raspberry_Pi.html anleitung alles fehlerfrei installiert, bekomme aber beim start von brickd -- Support: https://www.debian.org/support -- -- The unit brickd.service has entered the 'failed' state with result 'exit-code'. Feb 05 13:25:18 CAN systemd[1]: Failed to start Brick Daemon. -- Subject: A start job for unit brickd.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit brickd.service has finished with a failure. -- -- The job identifier is 682 and the job result is failed. Feb 05 13:26:57 CAN systemd[1]: Starting Brick Daemon... -- Subject: A start job for unit brickd.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit brickd.service has begun execution. -- -- The job identifier is 739. Feb 05 13:26:57 CAN brickd[3213]: Error(s) occurred while reading config file '/etc/brickd.conf' Feb 05 13:26:57 CAN systemd[1]: brickd.service: Control process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecStart= process belonging to unit brickd.service has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Feb 05 13:26:57 CAN systemd[1]: brickd.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit brickd.service has entered the 'failed' state with result 'exit-code'. Feb 05 13:26:57 CAN systemd[1]: Failed to start Brick Daemon. -- Subject: A start job for unit brickd.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit brickd.service has finished with a failure. benötige Hilfe, Danke Rainer

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.