NEWS
Test Adapter rpi2 2.x
-
ähm.. ja.. die github Version hab ich auch noch nicht getestet. Kann sein, dass da noch fehler drin sind. Die Tests laufen ja auch nicht durch. ;-)
Bin am Freitag nur dazu gekommen neuen Code zu produzieren, ausprobieren und Fehler glatt bügeln, dafür hat die Zeit nicht mehr gereicht. Insofern, was @Thomas-Braun sagt: Bitte erstmal bei der Version aus dem repository bleiben. Ich bitte um tests, wenns soweit ist.Und ja, eigentlich wollte ich das Freitag noch schaffen, aber ging halt nicht. Aber im Forum wollte ich halt auch noch kurz antworten. ;-)
-
Dieser Hinweis ist wichtig an der Stelle, daher hatte ich die Version und aus Github geschrieben. Aber korrekt und wichtig für alle da zu unterscheiden.
Ich such jetzt im Programm mal nach dem Fehler der mir beim Neustart des Adapters meinen Eingang auf false setzt, obwohl dieser definitiv true ist.
@Garfonso
Problem gefunden und hätte hier eine Lösung. Die Initialisierung geht nicht schnell genug.
Habe eine Delay Funktion nach dem GPIO watch Befehl integriert - jetzt wird der Eingang korrekt auf True gesetzt.function delay(ms) { return new Promise(resolve => setTimeout(resolve, ms)); } // Füge eine kurze Verzögerung hinzu, um sicherzustellen, dass der Pin initialisiert ist 121 this.gpioInputPorts.push(gpioSetting.gpio); // neu await delay(100); // Verzögerung von 100 Millisekunden 122 await this.readValue(gpioSetting.gpio);im DEBUG Log zeigt er mir damit aber eine lange liste true. Das "false" am Anfang kommt leider immer noch durch. Er korrigiert es jetzt aber. Kannst du beim 1. lesen des Eingangs den Inhalt verwerfen? Das liegt sicher an der Debounce Abfrage - richtig?
2025-02-23 17:43:25.161 - debug: rpi2.0 (34903) GPIO chip undefined initialized 2025-02-23 17:43:25.161 - debug: rpi2.0 (34903) Port 17 direction: in 2025-02-23 17:43:25.164 - debug: rpi2.0 (34903) Setting state for port 17 to false 2025-02-23 17:43:25.221 - silly: rpi2.0 (34903) States user redis pmessage rpi2.0.*/rpi2.0.gpio.17.state:{"val":false,"ack":true,"ts":1740329005219,"q":0,"from":"system.adapter.rpi2.0","user":"system.user.admin","lc":1740329005219} 2025-02-23 17:43:25.225 - debug: rpi2.0 (34903) Port 22 direction: outhigh 2025-02-23 17:43:25.227 - debug: rpi2.0 (34903) Adding event listener for port 17 2025-02-23 17:43:26.792 - debug: rpi2.0 (34903) GPIO change on port 17: true 2025-02-23 17:43:26.793 - debug: rpi2.0 (34903) Setting state for port 17 to true 2025-02-23 17:43:26.795 - debug: rpi2.0 (34903) GPIO change on port 17: true 2025-02-23 17:43:26.797 - debug: rpi2.0 (34903) Setting state for port 17 to true 2025-02-23 17:43:26.800 - debug: rpi2.0 (34903) GPIO change on port 17: true 2025-02-23 17:43:26.801 - debug: rpi2.0 (34903) Setting state for port 17 to true 2025-02-23 17:43:26.803 - debug: rpi2.0 (34903) GPIO change on port 17: true 2025-02-23 17:43:26.804 - debug: rpi2.0 (34903) Setting state for port 17 to true 2025-02-23 17:43:26.806 - debug: rpi2.0 (34903) GPIO change on port 17: true@smallfeuer said in Test Adapter rpi2 2.x:
im DEBUG Log zeigt er mir damit aber eine lange liste true. Das "false" am Anfang kommt leider immer noch durch. Er korrigiert es jetzt aber. Kannst du beim 1. lesen des Eingangs den Inhalt verwerfen? Das liegt sicher an der Debounce Abfrage - richtig?
Hä? Welches Problem hat das denn jetzt gelöst?
In deinem log sehe ich, dass der Port initialisiert wurde, dann wurdefalseeingelesen, nach dem timeout, den du dort hinzugefügt hast und danach meldet die library von "außen" mehrere Veränderungen zu true. Wenn da nur einmal true rauskommen soll, könntest du das mit debounce timer lösen.Was genau hat der delay jetzt bei dir behoben, wenn es nicht das initiale lesen war?
-
@garfonso Kein Stress. Sag bescheid wenn du soweit bist.
@smallfeuer said in Test Adapter rpi2 2.x:
@garfonso Kein Stress. Sag bescheid wenn du soweit bist.
Jetzt kannst du von github mal ausprobieren und gucken, ob es einen Unterschied macht. Der initiale Zustand der Eingäge wird jetzt erst gelesen, nachdem der Eventlistener hinzugefügt wurde.
Wenn da immer noch das falsche bei rum kommt, weiß ich nicht mehr so richtig weiter.
In dem Fall, könntest du mir deine Konfiguration mal zukommen lassen? Weiß zwar nicht, ob ich da ohne Hardware hier weiter komme, aber vielleicht fällt mir was ein. ;-)Ultimativer Lovelace Leitfaden: https://forum.iobroker.net/topic/35937/der-ultimative-iobroker-lovelace-leitfaden-dokumentation
Lovelace UI Beispiele: https://forum.iobroker.net/topic/35950/zeigt-her-eure-lovelace-visualisierung
-
@smallfeuer said in Test Adapter rpi2 2.x:
@garfonso Kein Stress. Sag bescheid wenn du soweit bist.
Jetzt kannst du von github mal ausprobieren und gucken, ob es einen Unterschied macht. Der initiale Zustand der Eingäge wird jetzt erst gelesen, nachdem der Eventlistener hinzugefügt wurde.
Wenn da immer noch das falsche bei rum kommt, weiß ich nicht mehr so richtig weiter.
In dem Fall, könntest du mir deine Konfiguration mal zukommen lassen? Weiß zwar nicht, ob ich da ohne Hardware hier weiter komme, aber vielleicht fällt mir was ein. ;-)@garfonso
Ich hab ja auf Raspi 4 Bookworm die rpi2 v 2.3.2 und wenn du da Hilfe bei Tests brauchst sag Bescheid.
Habe 8 Ausgänge am Raspie mit High aktiv und 6 Eingänge (Pull down) die ich kurzfristig auch für Tests mit 3,3V beschalten könnte. Derzeit verwende ich GPIO 23 mit einem Taster.Was mir im Thread auffällt ist, dass viele von Ihren Relaiszustand schreiben. Dieser kann aber je nach verwendeter Relaiskarte auch invertiert sein. Es wäre hier sinnvoll sich immer auf high oder low an den Pins am Raspie zu beziehen. Weiter sollte auch immer in der ersten Zeile benannt werden ob es schon die 2.3.2 ist.
Zum Thema GPIO mit Raspie 5 hab ich grad was im Netz gesehen. Ev. hilft euch das!
https://kofler.info/gpio-aerger-auf-dem-raspberry-pi-5/
https://kofler.info/gpio-reloaded-ii-bash/#more-7796Dort ist auch eine Abfrage der GPIOs mit z.B. pinctrl get 23 für GPIO 23 beschrieben die bei mir prima funktioniert.
pinctrl get [gpionr] ermittelt den aktuellen Status aller GPIOs bzw. des angegebenen GPIOs. pinctrl funcs [gpionr] ermittelt, welche alternativen Funktionen der angegebene GPIO bzw. alle GPIOs erfüllen können. pinctrl set gpionr options verändert den Status des angegeben GPIOs. Mögliche Optionen sind: ip = Input op = Output dl = Zustand Low (Drive Low) dh = Zustand High (Drive High) pu = Pull-up-Widerstand aktiv pd = Pull-down-Widerstand aktiv pn = keine Pull-up/down-Funktion a0 bis a7 = alternative Funktion n aktivieren no = Deaktivieren (no function) Soweit sich sinnvolle Kombinationen ergeben, dürfen mehrere der obigen Optionen auf einmal übergeben werden, jeweils getrennt durch Leerzeichen. Welche alternative Funktionen ein GPIO unterstützt und wie sie nummeriert sind, geht aus pinctrl funcs hervor.code_text -
@smallfeuer said in Test Adapter rpi2 2.x:
im DEBUG Log zeigt er mir damit aber eine lange liste true. Das "false" am Anfang kommt leider immer noch durch. Er korrigiert es jetzt aber. Kannst du beim 1. lesen des Eingangs den Inhalt verwerfen? Das liegt sicher an der Debounce Abfrage - richtig?
Hä? Welches Problem hat das denn jetzt gelöst?
In deinem log sehe ich, dass der Port initialisiert wurde, dann wurdefalseeingelesen, nach dem timeout, den du dort hinzugefügt hast und danach meldet die library von "außen" mehrere Veränderungen zu true. Wenn da nur einmal true rauskommen soll, könntest du das mit debounce timer lösen.Was genau hat der delay jetzt bei dir behoben, wenn es nicht das initiale lesen war?
@garfonso
Naja, ich dachte es hätte was geändert. Deshalb hatte ich ja drunter geschrieben gestern Abend - ich verstehe es nicht mehr :)Vorher war es so, dass beim Rebooten "false" stehen geblieben ist und der Eingang gar nicht auf true ging. Nun hatte ich ja die Github Version installiert die nicht lief, dann meine komplette Instanz + Adapter gelöscht und neu auf 2.3.1 gespielt.
Danach blieb von meinem Problem nur noch über, das der 1. Befehl false war und es dann auf true wechselte obwohl ein Signal anliegt. Kurz gesagt - vergiss mein Delay - ich teste jetzt mal die Github Version.
-
@smallfeuer said in Test Adapter rpi2 2.x:
@garfonso Kein Stress. Sag bescheid wenn du soweit bist.
Jetzt kannst du von github mal ausprobieren und gucken, ob es einen Unterschied macht. Der initiale Zustand der Eingäge wird jetzt erst gelesen, nachdem der Eventlistener hinzugefügt wurde.
Wenn da immer noch das falsche bei rum kommt, weiß ich nicht mehr so richtig weiter.
In dem Fall, könntest du mir deine Konfiguration mal zukommen lassen? Weiß zwar nicht, ob ich da ohne Hardware hier weiter komme, aber vielleicht fällt mir was ein. ;-)@garfonso Getestet - läuft, Fehler mit falschen "False" Befehl ist aber identisch. Hast du ne Idee wie wir den 1. Befehl der vom Ausgang gelesen wird verwerfen können?
-
@garfonso Getestet - läuft, Fehler mit falschen "False" Befehl ist aber identisch. Hast du ne Idee wie wir den 1. Befehl der vom Ausgang gelesen wird verwerfen können?
sogar die debounce funktion funktioniert im nachhinein. Was meintest du mit meiner Konfiguration? Ist ja einfach nur ein Eingang der spannung high hat und dauerhaft als true durchgereicht werden sollte.
@Hasont Kannst du das mal nachstellen? Einfach mal einen Eingang auf True bringen über die Pi Spannung und schauen was beim reboot passiert?
DeBUG auf alles - > Dann sollte es sich identisch verhalten.rpi2.0 2025-02-24 20:12:27.178 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.177 debug Ignoring change event due to debounce: 15ms < 500. rpi2.0 2025-02-24 20:12:27.176 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.175 debug Ignoring change event due to debounce: 13ms < 500. rpi2.0 2025-02-24 20:12:27.174 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.174 debug Ignoring change event due to debounce: 12ms < 500. rpi2.0 2025-02-24 20:12:27.173 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.173 debug Ignoring change event due to debounce: 11ms < 500. rpi2.0 2025-02-24 20:12:27.172 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.172 debug Ignoring change event due to debounce: 10ms < 500. rpi2.0 2025-02-24 20:12:27.171 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.171 debug Ignoring change event due to debounce: 9ms < 500. rpi2.0 2025-02-24 20:12:27.171 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.170 debug Ignoring change event due to debounce: 8ms < 500. rpi2.0 2025-02-24 20:12:27.170 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.169 debug Ignoring change event due to debounce: 7ms < 500. rpi2.0 2025-02-24 20:12:27.169 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.168 debug Ignoring change event due to debounce: 6ms < 500. rpi2.0 2025-02-24 20:12:27.168 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.167 debug Ignoring change event due to debounce: 5ms < 500. rpi2.0 2025-02-24 20:12:27.167 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.166 debug Ignoring change event due to debounce: 4ms < 500. rpi2.0 2025-02-24 20:12:27.166 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.165 debug Ignoring change event due to debounce: 3ms < 500. rpi2.0 2025-02-24 20:12:27.164 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.162 debug Setting state for port 17 to true rpi2.0 2025-02-24 20:12:27.162 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:25.826 silly States user redis pmessage rpi2.0.*/rpi2.0.gpio.27.state:{"val":true,"ack":true,"ts":1740424345823,"q":0,"from":"system.adapter.rpi2.0","user":"system.user.admin","lc":1740424345823} rpi2.0 2025-02-24 20:12:25.770 debug Written true into port 27 rpi2.0 2025-02-24 20:12:25.769 debug Setting initial value for port 27 to true rpi2.0 2025-02-24 20:12:25.767 silly States user redis pmessage rpi2.0.*/rpi2.0.gpio.24.state:{"val":true,"ack":true,"ts":1740424345764,"q":0,"from":"system.adapter.rpi2.0","user":"system.user.admin","lc":1740424345764} rpi2.0 2025-02-24 20:12:25.711 debug Written true into port 24 rpi2.0 2025-02-24 20:12:25.710 debug Setting initial value for port 24 to true rpi2.0 2025-02-24 20:12:25.706 silly States user redis pmessage rpi2.0.*/rpi2.0.gpio.23.state:{"val":true,"ack":true,"ts":1740424345703,"q":0,"from":"system.adapter.rpi2.0","user":"system.user.admin","lc":1740424345703} rpi2.0 2025-02-24 20:12:25.650 debug Written true into port 23 rpi2.0 2025-02-24 20:12:25.650 debug Setting initial value for port 23 to true rpi2.0 2025-02-24 20:12:25.646 silly States user redis pmessage rpi2.0.*/rpi2.0.gpio.22.state:{"val":true,"ack":true,"ts":1740424345643,"q":0,"from":"system.adapter.rpi2.0","user":"system.user.admin","lc":1740424345643} rpi2.0 2025-02-24 20:12:25.591 debug Written true into port 22 rpi2.0 2025-02-24 20:12:25.590 debug Setting initial value for port 22 to true rpi2.0 2025-02-24 20:12:25.586 silly States user redis pmessage rpi2.0.*/rpi2.0.gpio.17.state:{"val":false,"ack":true,"ts":1740424345583,"q":0,"from":"system.adapter.rpi2.0","user":"system.user.admin","lc":1740424345583} rpi2.0 2025-02-24 20:12:25.528 debug Setting state for port 17 to false rpi2.0 2025-02-24 20:12:25.528 debug Read false from port 17. -
sogar die debounce funktion funktioniert im nachhinein. Was meintest du mit meiner Konfiguration? Ist ja einfach nur ein Eingang der spannung high hat und dauerhaft als true durchgereicht werden sollte.
@Hasont Kannst du das mal nachstellen? Einfach mal einen Eingang auf True bringen über die Pi Spannung und schauen was beim reboot passiert?
DeBUG auf alles - > Dann sollte es sich identisch verhalten.rpi2.0 2025-02-24 20:12:27.178 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.177 debug Ignoring change event due to debounce: 15ms < 500. rpi2.0 2025-02-24 20:12:27.176 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.175 debug Ignoring change event due to debounce: 13ms < 500. rpi2.0 2025-02-24 20:12:27.174 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.174 debug Ignoring change event due to debounce: 12ms < 500. rpi2.0 2025-02-24 20:12:27.173 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.173 debug Ignoring change event due to debounce: 11ms < 500. rpi2.0 2025-02-24 20:12:27.172 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.172 debug Ignoring change event due to debounce: 10ms < 500. rpi2.0 2025-02-24 20:12:27.171 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.171 debug Ignoring change event due to debounce: 9ms < 500. rpi2.0 2025-02-24 20:12:27.171 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.170 debug Ignoring change event due to debounce: 8ms < 500. rpi2.0 2025-02-24 20:12:27.170 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.169 debug Ignoring change event due to debounce: 7ms < 500. rpi2.0 2025-02-24 20:12:27.169 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.168 debug Ignoring change event due to debounce: 6ms < 500. rpi2.0 2025-02-24 20:12:27.168 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.167 debug Ignoring change event due to debounce: 5ms < 500. rpi2.0 2025-02-24 20:12:27.167 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.166 debug Ignoring change event due to debounce: 4ms < 500. rpi2.0 2025-02-24 20:12:27.166 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.165 debug Ignoring change event due to debounce: 3ms < 500. rpi2.0 2025-02-24 20:12:27.164 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.162 debug Setting state for port 17 to true rpi2.0 2025-02-24 20:12:27.162 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:25.826 silly States user redis pmessage rpi2.0.*/rpi2.0.gpio.27.state:{"val":true,"ack":true,"ts":1740424345823,"q":0,"from":"system.adapter.rpi2.0","user":"system.user.admin","lc":1740424345823} rpi2.0 2025-02-24 20:12:25.770 debug Written true into port 27 rpi2.0 2025-02-24 20:12:25.769 debug Setting initial value for port 27 to true rpi2.0 2025-02-24 20:12:25.767 silly States user redis pmessage rpi2.0.*/rpi2.0.gpio.24.state:{"val":true,"ack":true,"ts":1740424345764,"q":0,"from":"system.adapter.rpi2.0","user":"system.user.admin","lc":1740424345764} rpi2.0 2025-02-24 20:12:25.711 debug Written true into port 24 rpi2.0 2025-02-24 20:12:25.710 debug Setting initial value for port 24 to true rpi2.0 2025-02-24 20:12:25.706 silly States user redis pmessage rpi2.0.*/rpi2.0.gpio.23.state:{"val":true,"ack":true,"ts":1740424345703,"q":0,"from":"system.adapter.rpi2.0","user":"system.user.admin","lc":1740424345703} rpi2.0 2025-02-24 20:12:25.650 debug Written true into port 23 rpi2.0 2025-02-24 20:12:25.650 debug Setting initial value for port 23 to true rpi2.0 2025-02-24 20:12:25.646 silly States user redis pmessage rpi2.0.*/rpi2.0.gpio.22.state:{"val":true,"ack":true,"ts":1740424345643,"q":0,"from":"system.adapter.rpi2.0","user":"system.user.admin","lc":1740424345643} rpi2.0 2025-02-24 20:12:25.591 debug Written true into port 22 rpi2.0 2025-02-24 20:12:25.590 debug Setting initial value for port 22 to true rpi2.0 2025-02-24 20:12:25.586 silly States user redis pmessage rpi2.0.*/rpi2.0.gpio.17.state:{"val":false,"ack":true,"ts":1740424345583,"q":0,"from":"system.adapter.rpi2.0","user":"system.user.admin","lc":1740424345583} rpi2.0 2025-02-24 20:12:25.528 debug Setting state for port 17 to false rpi2.0 2025-02-24 20:12:25.528 debug Read false from port 17.if (value === undefined) { value = this.gpioPorts[port].value; this.log.debug(`Read ${value} from port ${port}.`);Also ich habe es jetzt soweit analysiert, hier wird der Wert beim 1. Durchlauf false gesetzt, ein delay ändert das Ergebnis aber hier nicht.
Liest der Befehl
value = this.gpioPorts[port].value;den Wert direkt aus? Dann muss der Fehler weiter vorn in dieser Funktion verankert liegen :(
-
if (value === undefined) { value = this.gpioPorts[port].value; this.log.debug(`Read ${value} from port ${port}.`);Also ich habe es jetzt soweit analysiert, hier wird der Wert beim 1. Durchlauf false gesetzt, ein delay ändert das Ergebnis aber hier nicht.
Liest der Befehl
value = this.gpioPorts[port].value;den Wert direkt aus? Dann muss der Fehler weiter vorn in dieser Funktion verankert liegen :(
@smallfeuer
Ja, genau, das .value liest den Wert aus. Daher hab ich dort das debug log ergänzt, was man bei dir auch sieht:
2025-02-24 20:12:25.528 debug Read false from port 17.
Die restlichen Änderungen kommen über den onChange listener beim "watch", also da wird der Adapter über Änderungen am Pin informiert, sieht dann leicht anders aus:
2025-02-24 20:12:27.162 debug GPIO change on port 17: trueEs könnte sein, dass da noch eine Initialisierung läuft, und daher das false am Anfang kommt. Dazu hab ich aber in der Bibliothek bisher nichts finden können. :-/
Bei meinem Test-System kommen am Anfang auch keine Change-Events. -
@smallfeuer
Ja, genau, das .value liest den Wert aus. Daher hab ich dort das debug log ergänzt, was man bei dir auch sieht:
2025-02-24 20:12:25.528 debug Read false from port 17.
Die restlichen Änderungen kommen über den onChange listener beim "watch", also da wird der Adapter über Änderungen am Pin informiert, sieht dann leicht anders aus:
2025-02-24 20:12:27.162 debug GPIO change on port 17: trueEs könnte sein, dass da noch eine Initialisierung läuft, und daher das false am Anfang kommt. Dazu hab ich aber in der Bibliothek bisher nichts finden können. :-/
Bei meinem Test-System kommen am Anfang auch keine Change-Events.@garfonso Kannst du mir sagen wo ich die aktuell genutzte GPIO - Bibliothek vom Bookworm finde? Kann mich gern mal durch den Code suchen - etwas C- Verständnis hab ich mittlerweile.
Alternativ würde ich jetzt folgendes Tun. Ich werde den GPIO INPUT einfach als Trigger nutzen und prüfen wie lange die Instanz "True" ist -> dementsprechend dann das Script starten über einen eigenen Datenpunkt. Ist zwar ein wenig aufwand, aber so werde ich die Falschmeldung bei Updates/Stromausfall los.
-
@garfonso Kannst du mir sagen wo ich die aktuell genutzte GPIO - Bibliothek vom Bookworm finde? Kann mich gern mal durch den Code suchen - etwas C- Verständnis hab ich mittlerweile.
Alternativ würde ich jetzt folgendes Tun. Ich werde den GPIO INPUT einfach als Trigger nutzen und prüfen wie lange die Instanz "True" ist -> dementsprechend dann das Script starten über einen eigenen Datenpunkt. Ist zwar ein wenig aufwand, aber so werde ich die Falschmeldung bei Updates/Stromausfall los.
-
sogar die debounce funktion funktioniert im nachhinein. Was meintest du mit meiner Konfiguration? Ist ja einfach nur ein Eingang der spannung high hat und dauerhaft als true durchgereicht werden sollte.
@Hasont Kannst du das mal nachstellen? Einfach mal einen Eingang auf True bringen über die Pi Spannung und schauen was beim reboot passiert?
DeBUG auf alles - > Dann sollte es sich identisch verhalten.rpi2.0 2025-02-24 20:12:27.178 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.177 debug Ignoring change event due to debounce: 15ms < 500. rpi2.0 2025-02-24 20:12:27.176 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.175 debug Ignoring change event due to debounce: 13ms < 500. rpi2.0 2025-02-24 20:12:27.174 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.174 debug Ignoring change event due to debounce: 12ms < 500. rpi2.0 2025-02-24 20:12:27.173 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.173 debug Ignoring change event due to debounce: 11ms < 500. rpi2.0 2025-02-24 20:12:27.172 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.172 debug Ignoring change event due to debounce: 10ms < 500. rpi2.0 2025-02-24 20:12:27.171 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.171 debug Ignoring change event due to debounce: 9ms < 500. rpi2.0 2025-02-24 20:12:27.171 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.170 debug Ignoring change event due to debounce: 8ms < 500. rpi2.0 2025-02-24 20:12:27.170 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.169 debug Ignoring change event due to debounce: 7ms < 500. rpi2.0 2025-02-24 20:12:27.169 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.168 debug Ignoring change event due to debounce: 6ms < 500. rpi2.0 2025-02-24 20:12:27.168 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.167 debug Ignoring change event due to debounce: 5ms < 500. rpi2.0 2025-02-24 20:12:27.167 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.166 debug Ignoring change event due to debounce: 4ms < 500. rpi2.0 2025-02-24 20:12:27.166 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.165 debug Ignoring change event due to debounce: 3ms < 500. rpi2.0 2025-02-24 20:12:27.164 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:27.162 debug Setting state for port 17 to true rpi2.0 2025-02-24 20:12:27.162 debug GPIO change on port 17: true rpi2.0 2025-02-24 20:12:25.826 silly States user redis pmessage rpi2.0.*/rpi2.0.gpio.27.state:{"val":true,"ack":true,"ts":1740424345823,"q":0,"from":"system.adapter.rpi2.0","user":"system.user.admin","lc":1740424345823} rpi2.0 2025-02-24 20:12:25.770 debug Written true into port 27 rpi2.0 2025-02-24 20:12:25.769 debug Setting initial value for port 27 to true rpi2.0 2025-02-24 20:12:25.767 silly States user redis pmessage rpi2.0.*/rpi2.0.gpio.24.state:{"val":true,"ack":true,"ts":1740424345764,"q":0,"from":"system.adapter.rpi2.0","user":"system.user.admin","lc":1740424345764} rpi2.0 2025-02-24 20:12:25.711 debug Written true into port 24 rpi2.0 2025-02-24 20:12:25.710 debug Setting initial value for port 24 to true rpi2.0 2025-02-24 20:12:25.706 silly States user redis pmessage rpi2.0.*/rpi2.0.gpio.23.state:{"val":true,"ack":true,"ts":1740424345703,"q":0,"from":"system.adapter.rpi2.0","user":"system.user.admin","lc":1740424345703} rpi2.0 2025-02-24 20:12:25.650 debug Written true into port 23 rpi2.0 2025-02-24 20:12:25.650 debug Setting initial value for port 23 to true rpi2.0 2025-02-24 20:12:25.646 silly States user redis pmessage rpi2.0.*/rpi2.0.gpio.22.state:{"val":true,"ack":true,"ts":1740424345643,"q":0,"from":"system.adapter.rpi2.0","user":"system.user.admin","lc":1740424345643} rpi2.0 2025-02-24 20:12:25.591 debug Written true into port 22 rpi2.0 2025-02-24 20:12:25.590 debug Setting initial value for port 22 to true rpi2.0 2025-02-24 20:12:25.586 silly States user redis pmessage rpi2.0.*/rpi2.0.gpio.17.state:{"val":false,"ack":true,"ts":1740424345583,"q":0,"from":"system.adapter.rpi2.0","user":"system.user.admin","lc":1740424345583} rpi2.0 2025-02-24 20:12:25.528 debug Setting state for port 17 to false rpi2.0 2025-02-24 20:12:25.528 debug Read false from port 17.Hallo, ich hab den Raspie auf GPIO 17 fest auf 3,3V gesetzt.
Wurde sofort mit True angezeigt.
Dann hab ich neu gebootet und GPIO 17 war false.rpi2.0 2025-02-26 18:45:42.625 debug GPIO change on port 23: false rpi2.0 2025-02-26 18:45:42.625 debug Ignoring change event due to debounce: 4ms < 200. rpi2.0 2025-02-26 18:45:42.624 debug GPIO change on port 23: false rpi2.0 2025-02-26 18:45:42.624 debug Ignoring change event due to debounce: 3ms < 200. rpi2.0 2025-02-26 18:45:42.624 debug GPIO change on port 23: false rpi2.0 2025-02-26 18:45:42.623 debug Ignoring change event due to debounce: 2ms < 200. rpi2.0 2025-02-26 18:45:42.623 debug GPIO change on port 23: false rpi2.0 2025-02-26 18:45:42.622 debug Ignoring change event due to debounce: 1ms < 200. rpi2.0 2025-02-26 18:45:42.622 debug GPIO change on port 23: false rpi2.0 2025-02-26 18:45:42.621 debug Setting state for port 23 to false rpi2.0 2025-02-26 18:45:42.620 debug GPIO change on port 23: false rpi2.0 2025-02-26 18:42:45.609 debug Port 23 direction: in rpi2.0 2025-02-26 18:42:45.601 debug Setting state for port 22 to false rpi2.0 2025-02-26 18:42:45.599 debug Port 22 direction: in rpi2.0 2025-02-26 18:42:45.598 debug Port 21 direction: outlow rpi2.0 2025-02-26 18:42:45.597 debug Port 20 direction: outlow rpi2.0 2025-02-26 18:42:45.595 debug Port 19 direction: outlow rpi2.0 2025-02-26 18:42:45.587 debug Setting state for port 18 to false rpi2.0 2025-02-26 18:42:45.586 debug Port 18 direction: in rpi2.0 2025-02-26 18:42:45.564 debug Setting state for port 17 to false rpi2.0 2025-02-26 18:42:45.557 debug Port 17 direction: in rpi2.0 2025-02-26 18:42:45.556 debug Port 16 direction: outlow rpi2.0 2025-02-26 18:42:45.554 debug Port 13 direction: outlow rpi2.0 2025-02-26 18:42:45.550 debug Port 12 direction: outlow rpi2.0 2025-02-26 18:42:45.550 debug Got chip: class Default extends classes_1.Device {} rpi2.0 2025-02-26 18:42:45.549 debug Got 4 from Raspberry Pi 4 Model B Rev 1.2code_textBin dann mal in den Keller und hab meine Frau gebeten in den Objekten GPIO17 zu beachten und True mitzuteilen. Ich hab dann alle 5 sec ein/aus geschaltet. Vom zugerufenen her war das eher ein Flip/Flop als ein Schalter.
Hab dann Protokoll gemacht. Soll eigentlich alle ca. 5sec True/False wechseln. Komm damit nicht klar.
Habs mal angehängt!rpi2.0 2025-02-26 20:09:52.044 debug Ignoring change event due to debounce: 5ms < 200. rpi2.0 2025-02-26 20:09:52.044 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:52.043 debug Ignoring change event due to debounce: 4ms < 200. rpi2.0 2025-02-26 20:09:52.043 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:52.043 debug Ignoring change event due to debounce: 4ms < 200. rpi2.0 2025-02-26 20:09:52.042 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:52.042 debug Ignoring change event due to debounce: 3ms < 200. rpi2.0 2025-02-26 20:09:52.041 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:52.041 debug Ignoring change event due to debounce: 2ms < 200. rpi2.0 2025-02-26 20:09:52.040 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:52.039 debug Setting state for port 17 to true rpi2.0 2025-02-26 20:09:52.038 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:47.685 debug Ignoring change event due to debounce: 36ms < 200. rpi2.0 2025-02-26 20:09:47.685 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:47.677 debug Ignoring change event due to debounce: 28ms < 200. rpi2.0 2025-02-26 20:09:47.676 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:47.676 debug Ignoring change event due to debounce: 27ms < 200. rpi2.0 2025-02-26 20:09:47.676 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:47.649 debug Setting state for port 17 to false rpi2.0 2025-02-26 20:09:47.649 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:43.757 debug Setting state for port 17 to true rpi2.0 2025-02-26 20:09:43.757 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:43.705 debug Ignoring change event due to debounce: 151ms < 200. rpi2.0 2025-02-26 20:09:43.704 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:43.704 debug Ignoring change event due to debounce: 150ms < 200. rpi2.0 2025-02-26 20:09:43.704 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:43.704 debug Ignoring change event due to debounce: 150ms < 200. rpi2.0 2025-02-26 20:09:43.703 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:43.555 debug Setting state for port 23 to false rpi2.0 2025-02-26 20:09:43.555 debug GPIO change on port 23: false rpi2.0 2025-02-26 20:09:43.554 debug Ignoring change event due to debounce: 0ms < 200. rpi2.0 2025-02-26 20:09:43.554 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:43.554 debug Setting state for port 17 to true rpi2.0 2025-02-26 20:09:43.553 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:38.391 debug Setting state for port 17 to false rpi2.0 2025-02-26 20:09:38.391 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:33.705 debug Setting state for port 17 to true rpi2.0 2025-02-26 20:09:33.705 debug GPIO change on port 17: true -
Hallo, ich hab den Raspie auf GPIO 17 fest auf 3,3V gesetzt.
Wurde sofort mit True angezeigt.
Dann hab ich neu gebootet und GPIO 17 war false.rpi2.0 2025-02-26 18:45:42.625 debug GPIO change on port 23: false rpi2.0 2025-02-26 18:45:42.625 debug Ignoring change event due to debounce: 4ms < 200. rpi2.0 2025-02-26 18:45:42.624 debug GPIO change on port 23: false rpi2.0 2025-02-26 18:45:42.624 debug Ignoring change event due to debounce: 3ms < 200. rpi2.0 2025-02-26 18:45:42.624 debug GPIO change on port 23: false rpi2.0 2025-02-26 18:45:42.623 debug Ignoring change event due to debounce: 2ms < 200. rpi2.0 2025-02-26 18:45:42.623 debug GPIO change on port 23: false rpi2.0 2025-02-26 18:45:42.622 debug Ignoring change event due to debounce: 1ms < 200. rpi2.0 2025-02-26 18:45:42.622 debug GPIO change on port 23: false rpi2.0 2025-02-26 18:45:42.621 debug Setting state for port 23 to false rpi2.0 2025-02-26 18:45:42.620 debug GPIO change on port 23: false rpi2.0 2025-02-26 18:42:45.609 debug Port 23 direction: in rpi2.0 2025-02-26 18:42:45.601 debug Setting state for port 22 to false rpi2.0 2025-02-26 18:42:45.599 debug Port 22 direction: in rpi2.0 2025-02-26 18:42:45.598 debug Port 21 direction: outlow rpi2.0 2025-02-26 18:42:45.597 debug Port 20 direction: outlow rpi2.0 2025-02-26 18:42:45.595 debug Port 19 direction: outlow rpi2.0 2025-02-26 18:42:45.587 debug Setting state for port 18 to false rpi2.0 2025-02-26 18:42:45.586 debug Port 18 direction: in rpi2.0 2025-02-26 18:42:45.564 debug Setting state for port 17 to false rpi2.0 2025-02-26 18:42:45.557 debug Port 17 direction: in rpi2.0 2025-02-26 18:42:45.556 debug Port 16 direction: outlow rpi2.0 2025-02-26 18:42:45.554 debug Port 13 direction: outlow rpi2.0 2025-02-26 18:42:45.550 debug Port 12 direction: outlow rpi2.0 2025-02-26 18:42:45.550 debug Got chip: class Default extends classes_1.Device {} rpi2.0 2025-02-26 18:42:45.549 debug Got 4 from Raspberry Pi 4 Model B Rev 1.2code_textBin dann mal in den Keller und hab meine Frau gebeten in den Objekten GPIO17 zu beachten und True mitzuteilen. Ich hab dann alle 5 sec ein/aus geschaltet. Vom zugerufenen her war das eher ein Flip/Flop als ein Schalter.
Hab dann Protokoll gemacht. Soll eigentlich alle ca. 5sec True/False wechseln. Komm damit nicht klar.
Habs mal angehängt!rpi2.0 2025-02-26 20:09:52.044 debug Ignoring change event due to debounce: 5ms < 200. rpi2.0 2025-02-26 20:09:52.044 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:52.043 debug Ignoring change event due to debounce: 4ms < 200. rpi2.0 2025-02-26 20:09:52.043 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:52.043 debug Ignoring change event due to debounce: 4ms < 200. rpi2.0 2025-02-26 20:09:52.042 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:52.042 debug Ignoring change event due to debounce: 3ms < 200. rpi2.0 2025-02-26 20:09:52.041 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:52.041 debug Ignoring change event due to debounce: 2ms < 200. rpi2.0 2025-02-26 20:09:52.040 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:52.039 debug Setting state for port 17 to true rpi2.0 2025-02-26 20:09:52.038 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:47.685 debug Ignoring change event due to debounce: 36ms < 200. rpi2.0 2025-02-26 20:09:47.685 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:47.677 debug Ignoring change event due to debounce: 28ms < 200. rpi2.0 2025-02-26 20:09:47.676 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:47.676 debug Ignoring change event due to debounce: 27ms < 200. rpi2.0 2025-02-26 20:09:47.676 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:47.649 debug Setting state for port 17 to false rpi2.0 2025-02-26 20:09:47.649 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:43.757 debug Setting state for port 17 to true rpi2.0 2025-02-26 20:09:43.757 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:43.705 debug Ignoring change event due to debounce: 151ms < 200. rpi2.0 2025-02-26 20:09:43.704 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:43.704 debug Ignoring change event due to debounce: 150ms < 200. rpi2.0 2025-02-26 20:09:43.704 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:43.704 debug Ignoring change event due to debounce: 150ms < 200. rpi2.0 2025-02-26 20:09:43.703 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:43.555 debug Setting state for port 23 to false rpi2.0 2025-02-26 20:09:43.555 debug GPIO change on port 23: false rpi2.0 2025-02-26 20:09:43.554 debug Ignoring change event due to debounce: 0ms < 200. rpi2.0 2025-02-26 20:09:43.554 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:43.554 debug Setting state for port 17 to true rpi2.0 2025-02-26 20:09:43.553 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:38.391 debug Setting state for port 17 to false rpi2.0 2025-02-26 20:09:38.391 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:33.705 debug Setting state for port 17 to true rpi2.0 2025-02-26 20:09:33.705 debug GPIO change on port 17: true@hasont Also das hin und her ist verständlich, du hast kein Pull down Widerstand eingebaut nehme ich an - wenn du also die 3,3V am Ausgang ausschaltest ist das Signal undefiniert. Siehe auch einen meiner letzten Kommentare zum Thema PullUP/Pulldown.
oder hier: https://www.electronics-tutorials.ws/de/logische/pullup-widerstaende.htmlWas meinst du mit neu gebootet? Den Adapter, oder den Pi?
Beim Pi Neustart könnte es natürlich sein, das wirklich keine 3,3V ankommen. Insbesondere wenn du die 3,3V vom Ausgang holst.Interessant ist also im wesentlichen nur ob beim Start oder Neustart des Adapters der Wert mal auf False geht.
bitte als Ausgang aber die 3,3V Spannungsversorgung nehmen, und keinen Ausgang der auf True sitzt. Sicherheitshalber sollte man hier glaube ich einen kleinen Widerstand zwischen packen, falls vorhanden. Für einen kurzen Test sollte es aber auch ohne gehen. -
Hallo, ich hab den Raspie auf GPIO 17 fest auf 3,3V gesetzt.
Wurde sofort mit True angezeigt.
Dann hab ich neu gebootet und GPIO 17 war false.rpi2.0 2025-02-26 18:45:42.625 debug GPIO change on port 23: false rpi2.0 2025-02-26 18:45:42.625 debug Ignoring change event due to debounce: 4ms < 200. rpi2.0 2025-02-26 18:45:42.624 debug GPIO change on port 23: false rpi2.0 2025-02-26 18:45:42.624 debug Ignoring change event due to debounce: 3ms < 200. rpi2.0 2025-02-26 18:45:42.624 debug GPIO change on port 23: false rpi2.0 2025-02-26 18:45:42.623 debug Ignoring change event due to debounce: 2ms < 200. rpi2.0 2025-02-26 18:45:42.623 debug GPIO change on port 23: false rpi2.0 2025-02-26 18:45:42.622 debug Ignoring change event due to debounce: 1ms < 200. rpi2.0 2025-02-26 18:45:42.622 debug GPIO change on port 23: false rpi2.0 2025-02-26 18:45:42.621 debug Setting state for port 23 to false rpi2.0 2025-02-26 18:45:42.620 debug GPIO change on port 23: false rpi2.0 2025-02-26 18:42:45.609 debug Port 23 direction: in rpi2.0 2025-02-26 18:42:45.601 debug Setting state for port 22 to false rpi2.0 2025-02-26 18:42:45.599 debug Port 22 direction: in rpi2.0 2025-02-26 18:42:45.598 debug Port 21 direction: outlow rpi2.0 2025-02-26 18:42:45.597 debug Port 20 direction: outlow rpi2.0 2025-02-26 18:42:45.595 debug Port 19 direction: outlow rpi2.0 2025-02-26 18:42:45.587 debug Setting state for port 18 to false rpi2.0 2025-02-26 18:42:45.586 debug Port 18 direction: in rpi2.0 2025-02-26 18:42:45.564 debug Setting state for port 17 to false rpi2.0 2025-02-26 18:42:45.557 debug Port 17 direction: in rpi2.0 2025-02-26 18:42:45.556 debug Port 16 direction: outlow rpi2.0 2025-02-26 18:42:45.554 debug Port 13 direction: outlow rpi2.0 2025-02-26 18:42:45.550 debug Port 12 direction: outlow rpi2.0 2025-02-26 18:42:45.550 debug Got chip: class Default extends classes_1.Device {} rpi2.0 2025-02-26 18:42:45.549 debug Got 4 from Raspberry Pi 4 Model B Rev 1.2code_textBin dann mal in den Keller und hab meine Frau gebeten in den Objekten GPIO17 zu beachten und True mitzuteilen. Ich hab dann alle 5 sec ein/aus geschaltet. Vom zugerufenen her war das eher ein Flip/Flop als ein Schalter.
Hab dann Protokoll gemacht. Soll eigentlich alle ca. 5sec True/False wechseln. Komm damit nicht klar.
Habs mal angehängt!rpi2.0 2025-02-26 20:09:52.044 debug Ignoring change event due to debounce: 5ms < 200. rpi2.0 2025-02-26 20:09:52.044 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:52.043 debug Ignoring change event due to debounce: 4ms < 200. rpi2.0 2025-02-26 20:09:52.043 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:52.043 debug Ignoring change event due to debounce: 4ms < 200. rpi2.0 2025-02-26 20:09:52.042 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:52.042 debug Ignoring change event due to debounce: 3ms < 200. rpi2.0 2025-02-26 20:09:52.041 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:52.041 debug Ignoring change event due to debounce: 2ms < 200. rpi2.0 2025-02-26 20:09:52.040 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:52.039 debug Setting state for port 17 to true rpi2.0 2025-02-26 20:09:52.038 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:47.685 debug Ignoring change event due to debounce: 36ms < 200. rpi2.0 2025-02-26 20:09:47.685 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:47.677 debug Ignoring change event due to debounce: 28ms < 200. rpi2.0 2025-02-26 20:09:47.676 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:47.676 debug Ignoring change event due to debounce: 27ms < 200. rpi2.0 2025-02-26 20:09:47.676 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:47.649 debug Setting state for port 17 to false rpi2.0 2025-02-26 20:09:47.649 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:43.757 debug Setting state for port 17 to true rpi2.0 2025-02-26 20:09:43.757 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:43.705 debug Ignoring change event due to debounce: 151ms < 200. rpi2.0 2025-02-26 20:09:43.704 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:43.704 debug Ignoring change event due to debounce: 150ms < 200. rpi2.0 2025-02-26 20:09:43.704 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:43.704 debug Ignoring change event due to debounce: 150ms < 200. rpi2.0 2025-02-26 20:09:43.703 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:43.555 debug Setting state for port 23 to false rpi2.0 2025-02-26 20:09:43.555 debug GPIO change on port 23: false rpi2.0 2025-02-26 20:09:43.554 debug Ignoring change event due to debounce: 0ms < 200. rpi2.0 2025-02-26 20:09:43.554 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:43.554 debug Setting state for port 17 to true rpi2.0 2025-02-26 20:09:43.553 debug GPIO change on port 17: true rpi2.0 2025-02-26 20:09:38.391 debug Setting state for port 17 to false rpi2.0 2025-02-26 20:09:38.391 debug GPIO change on port 17: false rpi2.0 2025-02-26 20:09:33.705 debug Setting state for port 17 to true rpi2.0 2025-02-26 20:09:33.705 debug GPIO change on port 17: true@hasont said in Test Adapter rpi2 2.x:
Hab dann Protokoll gemacht. Soll eigentlich alle ca. 5sec True/False wechseln. Komm damit nicht klar.
Habs mal angehängt!Also laut log hat es doch funktioniert? Alle 5 Sekunden ist ein Wechsel durchgekommen. Zwischendurch
sind ein paar andere Dinge vom debounce timer abgefangen worden...?- 20:09:33 true
- 20:09:38 false
- 20:09:43 true (kam instgesammt 6 mal, 4 davon per debounce timer abgerufen, der letzte kam durch, also tatsächlich doppelt -> debounce timer erhöhen, falls das nicht gewünscht ist, oder weniger rumprellen ;-) )
- 20:09:47 false (da kamen dann tatsächlich ein paar true, aber alle vom timer abgefangen)
- 20:09:52 true (wieder mit einigen, die im debounce timer hängen bleiben)
Was ist da jetzt genau falsch?
-
@hasont Also das hin und her ist verständlich, du hast kein Pull down Widerstand eingebaut nehme ich an - wenn du also die 3,3V am Ausgang ausschaltest ist das Signal undefiniert. Siehe auch einen meiner letzten Kommentare zum Thema PullUP/Pulldown.
oder hier: https://www.electronics-tutorials.ws/de/logische/pullup-widerstaende.htmlWas meinst du mit neu gebootet? Den Adapter, oder den Pi?
Beim Pi Neustart könnte es natürlich sein, das wirklich keine 3,3V ankommen. Insbesondere wenn du die 3,3V vom Ausgang holst.Interessant ist also im wesentlichen nur ob beim Start oder Neustart des Adapters der Wert mal auf False geht.
bitte als Ausgang aber die 3,3V Spannungsversorgung nehmen, und keinen Ausgang der auf True sitzt. Sicherheitshalber sollte man hier glaube ich einen kleinen Widerstand zwischen packen, falls vorhanden. Für einen kurzen Test sollte es aber auch ohne gehen.@smallfeuer sagte in Test Adapter rpi2 2.x:
@hasont Also das hin und her ist verständlich, du hast kein Pull down Widerstand eingebaut nehme ich an - wenn du also die 3,3V am Ausgang ausschaltest ist das Signal undefiniert. Siehe auch einen meiner letzten Kommentare zum Thema PullUP/Pulldown.
oder hier: https://www.electronics-tutorials.ws/de/logische/pullup-widerstaende.htmlPulldown ist an jedem Input mit 10k gegen Masse. Hab es mit ner Kroko Klemme gemacht.
Was meinst du mit neu gebootet? Den Adapter, oder den Pi?
Beim Pi Neustart könnte es natürlich sein, das wirklich keine 3,3V ankommen. Insbesondere wenn du die 3,3V vom Ausgang holst.Sorry, hab dich da mit schauen was bei einem reboot passiert falsch verstanden. Dachte du meinst den Raspie. Die 3,3 V kommen aber aus einem kurzschlussfestem Regler und stehen auch beim Reboot des Raspie an.
Interessant ist also im wesentlichen nur ob beim Start oder Neustart des Adapters der Wert mal auf False geht.
bitte als Ausgang aber die 3,3V Spannungsversorgung nehmen, und keinen Ausgang der auf True sitzt. Sicherheitshalber sollte man hier glaube ich einen kleinen Widerstand zwischen packen, falls vorhanden. Für einen kurzen Test sollte es aber auch ohne gehen.Hier ein log nach ein/aus der rpi2 2.3.2 Instanz im Objekt bleibt es True. Habs noch ein paarmal probiert. Immer TRUE
Am GPIO 23 hängt ein Taster und der wird über ein Script abgefragt. Alle Inputs stehen auf 200ms und im Script ist noch ein zusätzliches Entprellen für GPIO23 eingebaut. Muss ich ev. ändern. Welche Zeiten zum Entprellen sind denn Sinnvoll in der rpi2 2.3.2 Instanz und was macht die genau? Muss ein Signal dann mindestens z.B. 200ms anstehen bis es im Objekt erkannt wird? Hab ja noch immer das Problem, dass mein Taster am GPIO durch Leuchtstoffröhre trotz 10k an GND gerne mal das Gartenwasser einschaltet.rpi2.0 2025-02-27 15:31:08.197 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.197 debug Ignoring change event due to debounce: 166ms < 200. rpi2.0 2025-02-27 15:31:08.197 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.196 debug Ignoring change event due to debounce: 165ms < 200. rpi2.0 2025-02-27 15:31:08.196 debug GPIO change on port 23: true rpi2.0 2025-02-27 15:31:08.195 debug Ignoring change event due to debounce: 164ms < 200. rpi2.0 2025-02-27 15:31:08.195 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.195 debug Ignoring change event due to debounce: 163ms < 200. rpi2.0 2025-02-27 15:31:08.194 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.193 debug Ignoring change event due to debounce: 162ms < 200. rpi2.0 2025-02-27 15:31:08.193 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.192 debug Ignoring change event due to debounce: 161ms < 200. rpi2.0 2025-02-27 15:31:08.191 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.184 debug Written false into port 25 rpi2.0 2025-02-27 15:31:08.184 debug Setting initial value for port 25 to false rpi2.0 2025-02-27 15:31:08.083 debug Setting state for port 22 to false rpi2.0 2025-02-27 15:31:08.083 debug GPIO change on port 22: false rpi2.0 2025-02-27 15:31:08.082 debug Setting state for port 18 to false rpi2.0 2025-02-27 15:31:08.081 debug GPIO change on port 18: false rpi2.0 2025-02-27 15:31:08.081 debug Ignoring change event due to debounce: 13ms < 200. rpi2.0 2025-02-27 15:31:08.080 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.080 debug Ignoring change event due to debounce: 12ms < 200. rpi2.0 2025-02-27 15:31:08.079 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.078 debug Ignoring change event due to debounce: 10ms < 200. rpi2.0 2025-02-27 15:31:08.078 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.077 debug Ignoring change event due to debounce: 9ms < 200. rpi2.0 2025-02-27 15:31:08.077 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.076 debug Ignoring change event due to debounce: 8ms < 200. rpi2.0 2025-02-27 15:31:08.076 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.075 debug Ignoring change event due to debounce: 7ms < 200. rpi2.0 2025-02-27 15:31:08.075 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.074 debug Ignoring change event due to debounce: 6ms < 200. rpi2.0 2025-02-27 15:31:08.074 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.073 debug Ignoring change event due to debounce: 5ms < 200. rpi2.0 2025-02-27 15:31:08.073 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.072 debug Ignoring change event due to debounce: 4ms < 200. rpi2.0 2025-02-27 15:31:08.072 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.071 debug Ignoring change event due to debounce: 3ms < 200. rpi2.0 2025-02-27 15:31:08.071 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.070 debug Ignoring change event due to debounce: 2ms < 200. rpi2.0 2025-02-27 15:31:08.070 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.069 debug Ignoring change event due to debounce: 1ms < 200. rpi2.0 2025-02-27 15:31:08.069 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.068 debug Setting state for port 17 to true rpi2.0 2025-02-27 15:31:08.068 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.039 debug Ignoring change event due to debounce: 8ms < 200. rpi2.0 2025-02-27 15:31:08.038 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.038 debug Ignoring change event due to debounce: 7ms < 200. rpi2.0 2025-02-27 15:31:08.038 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.038 debug Ignoring change event due to debounce: 7ms < 200. rpi2.0 2025-02-27 15:31:08.038 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.037 debug Ignoring change event due to debounce: 6ms < 200. rpi2.0 2025-02-27 15:31:08.037 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.037 debug Ignoring change event due to debounce: 6ms < 200. rpi2.0 2025-02-27 15:31:08.037 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.037 debug Ignoring change event due to debounce: 6ms < 200. rpi2.0 2025-02-27 15:31:08.036 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.036 debug Ignoring change event due to debounce: 5ms < 200. rpi2.0 2025-02-27 15:31:08.036 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.036 debug Ignoring change event due to debounce: 5ms < 200. rpi2.0 2025-02-27 15:31:08.036 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.035 debug Ignoring change event due to debounce: 4ms < 200. rpi2.0 2025-02-27 15:31:08.035 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.035 debug Ignoring change event due to debounce: 4ms < 200. rpi2.0 2025-02-27 15:31:08.035 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.034 debug Ignoring change event due to debounce: 3ms < 200. rpi2.0 2025-02-27 15:31:08.034 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.034 debug Ignoring change event due to debounce: 3ms < 200. rpi2.0 2025-02-27 15:31:08.034 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.033 debug Ignoring change event due to debounce: 2ms < 200. rpi2.0 2025-02-27 15:31:08.033 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.033 debug Ignoring change event due to debounce: 2ms < 200. rpi2.0 2025-02-27 15:31:08.032 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.032 debug Ignoring change event due to debounce: 1ms < 200. rpi2.0 2025-02-27 15:31:08.032 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.032 debug Ignoring change event due to debounce: 1ms < 200. rpi2.0 2025-02-27 15:31:08.031 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.031 debug Ignoring change event due to debounce: 0ms < 200. rpi2.0 2025-02-27 15:31:08.031 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.031 debug Setting state for port 23 to false rpi2.0 2025-02-27 15:31:08.030 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.030 debug Ignoring change event due to debounce: 199ms < 200. rpi2.0 2025-02-27 15:31:08.030 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.030 debug Ignoring change event due to debounce: 199ms < 200. rpi2.0 2025-02-27 15:31:08.030 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.029 debug Ignoring change event due to debounce: 198ms < 200. rpi2.0 2025-02-27 15:31:08.029 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.029 debug Ignoring change event due to debounce: 198ms < 200. rpi2.0 2025-02-27 15:31:08.029 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.029 debug Ignoring change event due to debounce: 198ms < 200. rpi2.0 2025-02-27 15:31:08.028 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.028 debug Ignoring change event due to debounce: 197ms < 200. rpi2.0 2025-02-27 15:31:08.028 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.028 debug Ignoring change event due to debounce: 197ms < 200. rpi2.0 2025-02-27 15:31:08.028 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.027 debug Ignoring change event due to debounce: 196ms < 200. rpi2.0 2025-02-27 15:31:08.027 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.027 debug Ignoring change event due to debounce: 196ms < 200. rpi2.0 2025-02-27 15:31:08.027 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.027 debug Ignoring change event due to debounce: 196ms < 200. rpi2.0 2025-02-27 15:31:08.026 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.026 debug Ignoring change event due to debounce: 195ms < 200. rpi2.0 2025-02-27 15:31:08.026 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.026 debug Ignoring change event due to debounce: 195ms < 200. rpi2.0 2025-02-27 15:31:08.026 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.025 debug Ignoring change event due to debounce: 194ms < 200. rpi2.0 2025-02-27 15:31:08.025 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.025 debug Ignoring change event due to debounce: 194ms < 200. rpi2.0 2025-02-27 15:31:08.025 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.025 debug Ignoring change event due to debounce: 194ms < 200. rpi2.0 2025-02-27 15:31:08.024 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.024 debug Ignoring change event due to debounce: 193ms < 200. rpi2.0 2025-02-27 15:31:08.024 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.024 debug Ignoring change event due to debounce: 193ms < 200. rpi2.0 2025-02-27 15:31:08.024 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.023 debug Ignoring change event due to debounce: 192ms < 200. rpi2.0 2025-02-27 15:31:08.023 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.023 debug Ignoring change event due to debounce: 192ms < 200. rpi2.0 2025-02-27 15:31:08.022 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.022 debug Ignoring change event due to debounce: 191ms < 200. rpi2.0 2025-02-27 15:31:08.022 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.021 debug Ignoring change event due to debounce: 190ms < 200. rpi2.0 2025-02-27 15:31:08.021 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.020 debug Ignoring change event due to debounce: 189ms < 200. rpi2.0 2025-02-27 15:31:08.020 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.019 debug Ignoring change event due to debounce: 188ms < 200. rpi2.0 2025-02-27 15:31:08.019 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.018 debug Ignoring change event due to debounce: 187ms < 200. rpi2.0 2025-02-27 15:31:08.017 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.017 debug Ignoring change event due to debounce: 186ms < 200. rpi2.0 2025-02-27 15:31:08.016 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.016 debug Ignoring change event due to debounce: 185ms < 200. rpi2.0 2025-02-27 15:31:08.015 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.014 debug Ignoring change event due to debounce: 183ms < 200. rpi2.0 2025-02-27 15:31:08.014 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.013 debug Ignoring change event due to debounce: 182ms < 200. rpi2.0 2025-02-27 15:31:08.012 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.012 debug Ignoring change event due to debounce: 181ms < 200. rpi2.0 2025-02-27 15:31:08.011 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.010 debug Ignoring change event due to debounce: 179ms < 200. rpi2.0 2025-02-27 15:31:08.009 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.009 debug Ignoring change event due to debounce: 178ms < 200. rpi2.0 2025-02-27 15:31:08.008 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.007 debug Ignoring change event due to debounce: 176ms < 200. rpi2.0 2025-02-27 15:31:08.007 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.006 debug Ignoring change event due to debounce: 175ms < 200. rpi2.0 2025-02-27 15:31:08.005 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.004 debug Ignoring change event due to debounce: 173ms < 200. rpi2.0 2025-02-27 15:31:08.004 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.003 debug Ignoring change event due to debounce: 172ms < 200. rpi2.0 2025-02-27 15:31:08.002 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.002 debug Ignoring change event due to debounce: 171ms < 200. rpi2.0 2025-02-27 15:31:08.001 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.001 debug Ignoring change event due to debounce: 170ms < 200. rpi2.0 2025-02-27 15:31:08.000 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.999 debug Ignoring change event due to debounce: 168ms < 200. rpi2.0 2025-02-27 15:31:07.999 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.999 debug Ignoring change event due to debounce: 168ms < 200. rpi2.0 2025-02-27 15:31:07.998 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.998 debug Ignoring change event due to debounce: 167ms < 200. rpi2.0 2025-02-27 15:31:07.997 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.997 debug Ignoring change event due to debounce: 166ms < 200. rpi2.0 2025-02-27 15:31:07.997 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.996 debug Ignoring change event due to debounce: 165ms < 200. rpi2.0 2025-02-27 15:31:07.996 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.995 debug Ignoring change event due to debounce: 164ms < 200. rpi2.0 2025-02-27 15:31:07.995 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.994 debug Ignoring change event due to debounce: 163ms < 200. rpi2.0 2025-02-27 15:31:07.994 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.994 debug Ignoring change event due to debounce: 163ms < 200. rpi2.0 2025-02-27 15:31:07.993 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.992 debug Ignoring change event due to debounce: 161ms < 200. rpi2.0 2025-02-27 15:31:07.992 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.992 debug Ignoring change event due to debounce: 161ms < 200. rpi2.0 2025-02-27 15:31:07.991 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.991 debug Ignoring change event due to debounce: 160ms < 200. rpi2.0 2025-02-27 15:31:07.991 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.990 debug Ignoring change event due to debounce: 159ms < 200. rpi2.0 2025-02-27 15:31:07.990 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.990 debug Ignoring change event due to debounce: 159ms < 200. rpi2.0 2025-02-27 15:31:07.990 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.989 debug Ignoring change event due to debounce: 158ms < 200. rpi2.0 2025-02-27 15:31:07.989 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.989 debug Ignoring change event due to debounce: 158ms < 200. rpi2.0 2025-02-27 15:31:07.989 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.988 debug Ignoring change event due to debounce: 157ms < 200. rpi2.0 2025-02-27 15:31:07.988 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.988 debug Ignoring change event due to debounce: 157ms < 200. rpi2.0 2025-02-27 15:31:07.987 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.987 debug Ignoring change event due to debounce: 156ms < 200. rpi2.0 2025-02-27 15:31:07.987 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.987 debug Ignoring change event due to debounce: 156ms < 200. rpi2.0 2025-02-27 15:31:07.986 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.986 debug Ignoring change event due to debounce: 155ms < 200. rpi2.0 2025-02-27 15:31:07.986 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.986 debug Ignoring change event due to debounce: 155ms < 200. rpi2.0 2025-02-27 15:31:07.985 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.985 debug Ignoring change event due to debounce: 154ms < 200. rpi2.0 2025-02-27 15:31:07.985 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.985 debug Ignoring change event due to debounce: 154ms < 200. rpi2.0 2025-02-27 15:31:07.984 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.984 debug Ignoring change event due to debounce: 153ms < 200. rpi2.0 2025-02-27 15:31:07.984 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.983 debug Ignoring change event due to debounce: 152ms < 200. rpi2.0 2025-02-27 15:31:07.983 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.983 debug Ignoring change event due to debounce: 152ms < 200. rpi2.0 2025-02-27 15:31:07.983 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.982 debug Ignoring change event due to debounce: 151ms < 200. rpi2.0 2025-02-27 15:31:07.982 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.982 debug Ignoring change event due to debounce: 151ms < 200. rpi2.0 2025-02-27 15:31:07.982 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.981 debug Ignoring change event due to debounce: 150ms < 200. rpi2.0 2025-02-27 15:31:07.981 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.980 debug Ignoring change event due to debounce: 149ms < 200. rpi2.0 2025-02-27 15:31:07.980 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.980 debug Ignoring change event due to debounce: 149ms < 200. rpi2.0 2025-02-27 15:31:07.979 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.979 debug Ignoring change event due to debounce: 148ms < 200. rpi2.0 2025-02-27 15:31:07.979 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.978 debug Ignoring change event due to debounce: 147ms < 200. rpi2.0 2025-02-27 15:31:07.978 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.978 debug Ignoring change event due to debounce: 147ms < 200. rpi2.0 2025-02-27 15:31:07.977 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.977 debug Ignoring change event due to debounce: 146ms < 200. rpi2.0 2025-02-27 15:31:07.977 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.976 debug Ignoring change event due to debounce: 145ms < 200. rpi2.0 2025-02-27 15:31:07.976 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.976 debug Ignoring change event due to debounce: 145ms < 200. rpi2.0 2025-02-27 15:31:07.975 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.975 debug Ignoring change event due to debounce: 144ms < 200. rpi2.0 2025-02-27 15:31:07.974 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.974 debug Ignoring change event due to debounce: 143ms < 200. rpi2.0 2025-02-27 15:31:07.974 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.973 debug Ignoring change event due to debounce: 142ms < 200. rpi2.0 2025-02-27 15:31:07.973 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.973 debug Ignoring change event due to debounce: 141ms < 200. rpi2.0 2025-02-27 15:31:07.972 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.971 debug Ignoring change event due to debounce: 140ms < 200. rpi2.0 2025-02-27 15:31:07.971 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.970 debug Ignoring change event due to debounce: 139ms < 200. rpi2.0 2025-02-27 15:31:07.970 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.969 debug Ignoring change event due to debounce: 138ms < 200. rpi2.0 2025-02-27 15:31:07.969 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.969 debug Ignoring change event due to debounce: 138ms < 200. rpi2.0 2025-02-27 15:31:07.969 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.968 debug Ignoring change event due to debounce: 137ms < 200. rpi2.0 2025-02-27 15:31:07.968 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.968 debug Ignoring change event due to debounce: 137ms < 200. rpi2.0 2025-02-27 15:31:07.968 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.967 debug Ignoring change event due to debounce: 136ms < 200. rpi2.0 2025-02-27 15:31:07.967 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.967 debug Ignoring change event due to debounce: 136ms < 200. rpi2.0 2025-02-27 15:31:07.967 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.966 debug Ignoring change event due to debounce: 135ms < 200. rpi2.0 2025-02-27 15:31:07.966 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.966 debug Ignoring change event due to debounce: 135ms < 200. rpi2.0 2025-02-27 15:31:07.966 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.965 debug Ignoring change event due to debounce: 134ms < 200. rpi2.0 2025-02-27 15:31:07.965 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.965 debug Ignoring change event due to debounce: 134ms < 200. rpi2.0 2025-02-27 15:31:07.964 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.964 debug Ignoring change event due to debounce: 133ms < 200. rpi2.0 2025-02-27 15:31:07.964 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.964 debug Ignoring change event due to debounce: 133ms < 200. rpi2.0 2025-02-27 15:31:07.963 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.963 debug Ignoring change event due to debounce: 132ms < 200. rpi2.0 2025-02-27 15:31:07.963 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.962 debug Ignoring change event due to debounce: 131ms < 200. rpi2.0 2025-02-27 15:31:07.962 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.961 debug Ignoring change event due to debounce: 130ms < 200. rpi2.0 2025-02-27 15:31:07.961 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.961 debug Ignoring change event due to debounce: 130ms < 200. rpi2.0 2025-02-27 15:31:07.961 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.960 debug Ignoring change event due to debounce: 129ms < 200. rpi2.0 2025-02-27 15:31:07.960 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.960 debug Ignoring change event due to debounce: 129ms < 200. rpi2.0 2025-02-27 15:31:07.959 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.959 debug Ignoring change event due to debounce: 128ms < 200. rpi2.0 2025-02-27 15:31:07.959 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.958 debug Ignoring change event due to debounce: 127ms < 200. rpi2.0 2025-02-27 15:31:07.958 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.957 debug Ignoring change event due to debounce: 126ms < 200. rpi2.0 2025-02-27 15:31:07.956 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.956 debug Ignoring change event due to debounce: 125ms < 200. rpi2.0 2025-02-27 15:31:07.955 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.955 debug Ignoring change event due to debounce: 124ms < 200. rpi2.0 2025-02-27 15:31:07.954 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.954 debug Ignoring change event due to debounce: 123ms < 200. rpi2.0 2025-02-27 15:31:07.953 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.943 debug Written false into port 21 rpi2.0 2025-02-27 15:31:07.943 debug Setting initial value for port 21 to false rpi2.0 2025-02-27 15:31:07.895 debug Written false into port 20 rpi2.0 2025-02-27 15:31:07.895 debug Setting initial value for port 20 to false rpi2.0 2025-02-27 15:31:07.847 debug Ignoring change event due to debounce: 16ms < 200. rpi2.0 2025-02-27 15:31:07.846 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.842 debug Written false into port 19 rpi2.0 2025-02-27 15:31:07.842 debug Setting initial value for port 19 to false rpi2.0 2025-02-27 15:31:07.833 debug Ignoring change event due to debounce: 2ms < 200. rpi2.0 2025-02-27 15:31:07.832 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.832 debug Ignoring change event due to debounce: 1ms < 200. rpi2.0 2025-02-27 15:31:07.832 debug GPIO change on port 23: true rpi2.0 2025-02-27 15:31:07.832 debug Ignoring change event due to debounce: 0ms < 200. rpi2.0 2025-02-27 15:31:07.831 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.831 debug Setting state for port 23 to false rpi2.0 2025-02-27 15:31:07.830 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.825 debug Written false into port 16 rpi2.0 2025-02-27 15:31:07.825 debug Setting initial value for port 16 to false rpi2.0 2025-02-27 15:31:07.778 debug Ignoring change event due to debounce: 186ms < 200. rpi2.0 2025-02-27 15:31:07.778 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.773 debug Written false into port 13 rpi2.0 2025-02-27 15:31:07.772 debug Setting initial value for port 13 to false rpi2.0 2025-02-27 15:31:07.764 debug Ignoring change event due to debounce: 172ms < 200. rpi2.0 2025-02-27 15:31:07.764 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.763 debug Setting state for port 17 to true rpi2.0 2025-02-27 15:31:07.763 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:07.754 debug Written false into port 12 rpi2.0 2025-02-27 15:31:07.753 debug Setting initial value for port 12 to false rpi2.0 2025-02-27 15:31:07.753 debug Adding event listener for port 27 rpi2.0 2025-02-27 15:31:07.752 debug Adding event listener for port 24 rpi2.0 2025-02-27 15:31:07.752 debug Adding event listener for port 23 rpi2.0 2025-02-27 15:31:07.752 debug Adding event listener for port 22 rpi2.0 2025-02-27 15:31:07.752 debug Adding event listener for port 18 rpi2.0 2025-02-27 15:31:07.751 debug Adding event listener for port 17 rpi2.0 2025-02-27 15:31:07.699 debug Setting state for port 27 to false rpi2.0 2025-02-27 15:31:07.698 debug Port 27 direction: in rpi2.0 2025-02-27 15:31:07.696 debug Port 26 direction: outlow rpi2.0 2025-02-27 15:31:07.695 debug Port 25 direction: outlow rpi2.0 2025-02-27 15:31:07.646 debug Setting state for port 24 to false rpi2.0 2025-02-27 15:31:07.644 debug Port 24 direction: in rpi2.0 2025-02-27 15:31:07.593 debug Setting state for port 23 to false rpi2.0 2025-02-27 15:31:07.591 debug Port 23 direction: in rpi2.0 2025-02-27 15:31:07.540 debug Setting state for port 22 to false rpi2.0 2025-02-27 15:31:07.539 debug Port 22 direction: in rpi2.0 2025-02-27 15:31:07.537 debug Port 21 direction: outlow rpi2.0 2025-02-27 15:31:07.536 debug Port 20 direction: outlow rpi2.0 2025-02-27 15:31:07.535 debug Port 19 direction: outlow rpi2.0 2025-02-27 15:31:07.485 debug Setting state for port 18 to false rpi2.0 2025-02-27 15:31:07.483 debug Port 18 direction: in rpi2.0 2025-02-27 15:31:07.430 debug Setting state for port 17 to false rpi2.0 2025-02-27 15:31:07.427 debug Port 17 direction: in rpi2.0 2025-02-27 15:31:07.426 debug Port 16 direction: outlow rpi2.0 2025-02-27 15:31:07.424 debug Port 13 direction: outlow rpi2.0 2025-02-27 15:31:07.423 debug Port 12 direction: outlow rpi2.0 2025-02-27 15:31:07.422 debug Got chip: class Default extends classes_1.Device { } rpi2.0 2025-02-27 15:31:07.422 debug Got 4 from Raspberry Pi 4 Model B Rev 1.2 code_textWenn ich den Adapter nicht beende und nur was darin ändere kommt immer diese Warnung. Ev. könnt Ihr ja was damit anfangen.
admin.0 2025-02-27 15:56:54.758 warn rpi2 has an invalid jsonConfig: [{"instancePath":"/items/_gpios/items/_pullUpWarning/hidden","schemaPath":"#/patternProperties/%5E.%2B/properties/hidden/type","keyword":"type","params":{"type":"string"},"message":"must be string"},{"instancePath":"/items/_gpios","schemaPath":"#/properties/items/patternProperties/%5E.%2B/allOf/9/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"},{"instancePath":"","schemaPath":"#/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"}]code_text -
@hasont said in Test Adapter rpi2 2.x:
Hab dann Protokoll gemacht. Soll eigentlich alle ca. 5sec True/False wechseln. Komm damit nicht klar.
Habs mal angehängt!Also laut log hat es doch funktioniert? Alle 5 Sekunden ist ein Wechsel durchgekommen. Zwischendurch
sind ein paar andere Dinge vom debounce timer abgefangen worden...?- 20:09:33 true
- 20:09:38 false
- 20:09:43 true (kam instgesammt 6 mal, 4 davon per debounce timer abgerufen, der letzte kam durch, also tatsächlich doppelt -> debounce timer erhöhen, falls das nicht gewünscht ist, oder weniger rumprellen ;-) )
- 20:09:47 false (da kamen dann tatsächlich ein paar true, aber alle vom timer abgefangen)
- 20:09:52 true (wieder mit einigen, die im debounce timer hängen bleiben)
Was ist da jetzt genau falsch?
@garfonso sagte in Test Adapter rpi2 2.x:
@hasont said in Test Adapter rpi2 2.x:
Hab dann Protokoll gemacht. Soll eigentlich alle ca. 5sec True/False wechseln. Komm damit nicht klar.
Habs mal angehängt!Also laut log hat es doch funktioniert? Alle 5 Sekunden ist ein Wechsel durchgekommen. Zwischendurch
sind ein paar andere Dinge vom debounce timer abgefangen worden...?- 20:09:33 true
- 20:09:38 false
- 20:09:43 true (kam instgesammt 6 mal, 4 davon per debounce timer abgerufen, der letzte kam durch, also tatsächlich doppelt -> debounce timer erhöhen, falls das nicht gewünscht ist, oder weniger rumprellen ;-) )
- 20:09:47 false (da kamen dann tatsächlich ein paar true, aber alle vom timer abgefangen)
- 20:09:52 true (wieder mit einigen, die im debounce timer hängen bleiben)
Was ist da jetzt genau falsch?
Du hast recht, wahrscheinlich hab ich mir einen abgezittert mit meiner Kroko Klemme.
Wenn ich 1000ms eingeben müsste ich 1sec den Taster drücken um ein True zu bekommen, oder? -
@smallfeuer sagte in Test Adapter rpi2 2.x:
@hasont Also das hin und her ist verständlich, du hast kein Pull down Widerstand eingebaut nehme ich an - wenn du also die 3,3V am Ausgang ausschaltest ist das Signal undefiniert. Siehe auch einen meiner letzten Kommentare zum Thema PullUP/Pulldown.
oder hier: https://www.electronics-tutorials.ws/de/logische/pullup-widerstaende.htmlPulldown ist an jedem Input mit 10k gegen Masse. Hab es mit ner Kroko Klemme gemacht.
Was meinst du mit neu gebootet? Den Adapter, oder den Pi?
Beim Pi Neustart könnte es natürlich sein, das wirklich keine 3,3V ankommen. Insbesondere wenn du die 3,3V vom Ausgang holst.Sorry, hab dich da mit schauen was bei einem reboot passiert falsch verstanden. Dachte du meinst den Raspie. Die 3,3 V kommen aber aus einem kurzschlussfestem Regler und stehen auch beim Reboot des Raspie an.
Interessant ist also im wesentlichen nur ob beim Start oder Neustart des Adapters der Wert mal auf False geht.
bitte als Ausgang aber die 3,3V Spannungsversorgung nehmen, und keinen Ausgang der auf True sitzt. Sicherheitshalber sollte man hier glaube ich einen kleinen Widerstand zwischen packen, falls vorhanden. Für einen kurzen Test sollte es aber auch ohne gehen.Hier ein log nach ein/aus der rpi2 2.3.2 Instanz im Objekt bleibt es True. Habs noch ein paarmal probiert. Immer TRUE
Am GPIO 23 hängt ein Taster und der wird über ein Script abgefragt. Alle Inputs stehen auf 200ms und im Script ist noch ein zusätzliches Entprellen für GPIO23 eingebaut. Muss ich ev. ändern. Welche Zeiten zum Entprellen sind denn Sinnvoll in der rpi2 2.3.2 Instanz und was macht die genau? Muss ein Signal dann mindestens z.B. 200ms anstehen bis es im Objekt erkannt wird? Hab ja noch immer das Problem, dass mein Taster am GPIO durch Leuchtstoffröhre trotz 10k an GND gerne mal das Gartenwasser einschaltet.rpi2.0 2025-02-27 15:31:08.197 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.197 debug Ignoring change event due to debounce: 166ms < 200. rpi2.0 2025-02-27 15:31:08.197 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.196 debug Ignoring change event due to debounce: 165ms < 200. rpi2.0 2025-02-27 15:31:08.196 debug GPIO change on port 23: true rpi2.0 2025-02-27 15:31:08.195 debug Ignoring change event due to debounce: 164ms < 200. rpi2.0 2025-02-27 15:31:08.195 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.195 debug Ignoring change event due to debounce: 163ms < 200. rpi2.0 2025-02-27 15:31:08.194 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.193 debug Ignoring change event due to debounce: 162ms < 200. rpi2.0 2025-02-27 15:31:08.193 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.192 debug Ignoring change event due to debounce: 161ms < 200. rpi2.0 2025-02-27 15:31:08.191 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.184 debug Written false into port 25 rpi2.0 2025-02-27 15:31:08.184 debug Setting initial value for port 25 to false rpi2.0 2025-02-27 15:31:08.083 debug Setting state for port 22 to false rpi2.0 2025-02-27 15:31:08.083 debug GPIO change on port 22: false rpi2.0 2025-02-27 15:31:08.082 debug Setting state for port 18 to false rpi2.0 2025-02-27 15:31:08.081 debug GPIO change on port 18: false rpi2.0 2025-02-27 15:31:08.081 debug Ignoring change event due to debounce: 13ms < 200. rpi2.0 2025-02-27 15:31:08.080 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.080 debug Ignoring change event due to debounce: 12ms < 200. rpi2.0 2025-02-27 15:31:08.079 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.078 debug Ignoring change event due to debounce: 10ms < 200. rpi2.0 2025-02-27 15:31:08.078 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.077 debug Ignoring change event due to debounce: 9ms < 200. rpi2.0 2025-02-27 15:31:08.077 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.076 debug Ignoring change event due to debounce: 8ms < 200. rpi2.0 2025-02-27 15:31:08.076 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.075 debug Ignoring change event due to debounce: 7ms < 200. rpi2.0 2025-02-27 15:31:08.075 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.074 debug Ignoring change event due to debounce: 6ms < 200. rpi2.0 2025-02-27 15:31:08.074 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.073 debug Ignoring change event due to debounce: 5ms < 200. rpi2.0 2025-02-27 15:31:08.073 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.072 debug Ignoring change event due to debounce: 4ms < 200. rpi2.0 2025-02-27 15:31:08.072 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.071 debug Ignoring change event due to debounce: 3ms < 200. rpi2.0 2025-02-27 15:31:08.071 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.070 debug Ignoring change event due to debounce: 2ms < 200. rpi2.0 2025-02-27 15:31:08.070 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.069 debug Ignoring change event due to debounce: 1ms < 200. rpi2.0 2025-02-27 15:31:08.069 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.068 debug Setting state for port 17 to true rpi2.0 2025-02-27 15:31:08.068 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:08.039 debug Ignoring change event due to debounce: 8ms < 200. rpi2.0 2025-02-27 15:31:08.038 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.038 debug Ignoring change event due to debounce: 7ms < 200. rpi2.0 2025-02-27 15:31:08.038 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.038 debug Ignoring change event due to debounce: 7ms < 200. rpi2.0 2025-02-27 15:31:08.038 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.037 debug Ignoring change event due to debounce: 6ms < 200. rpi2.0 2025-02-27 15:31:08.037 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.037 debug Ignoring change event due to debounce: 6ms < 200. rpi2.0 2025-02-27 15:31:08.037 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.037 debug Ignoring change event due to debounce: 6ms < 200. rpi2.0 2025-02-27 15:31:08.036 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.036 debug Ignoring change event due to debounce: 5ms < 200. rpi2.0 2025-02-27 15:31:08.036 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.036 debug Ignoring change event due to debounce: 5ms < 200. rpi2.0 2025-02-27 15:31:08.036 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.035 debug Ignoring change event due to debounce: 4ms < 200. rpi2.0 2025-02-27 15:31:08.035 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.035 debug Ignoring change event due to debounce: 4ms < 200. rpi2.0 2025-02-27 15:31:08.035 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.034 debug Ignoring change event due to debounce: 3ms < 200. rpi2.0 2025-02-27 15:31:08.034 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.034 debug Ignoring change event due to debounce: 3ms < 200. rpi2.0 2025-02-27 15:31:08.034 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.033 debug Ignoring change event due to debounce: 2ms < 200. rpi2.0 2025-02-27 15:31:08.033 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.033 debug Ignoring change event due to debounce: 2ms < 200. rpi2.0 2025-02-27 15:31:08.032 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.032 debug Ignoring change event due to debounce: 1ms < 200. rpi2.0 2025-02-27 15:31:08.032 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.032 debug Ignoring change event due to debounce: 1ms < 200. rpi2.0 2025-02-27 15:31:08.031 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.031 debug Ignoring change event due to debounce: 0ms < 200. rpi2.0 2025-02-27 15:31:08.031 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.031 debug Setting state for port 23 to false rpi2.0 2025-02-27 15:31:08.030 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.030 debug Ignoring change event due to debounce: 199ms < 200. rpi2.0 2025-02-27 15:31:08.030 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.030 debug Ignoring change event due to debounce: 199ms < 200. rpi2.0 2025-02-27 15:31:08.030 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.029 debug Ignoring change event due to debounce: 198ms < 200. rpi2.0 2025-02-27 15:31:08.029 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.029 debug Ignoring change event due to debounce: 198ms < 200. rpi2.0 2025-02-27 15:31:08.029 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.029 debug Ignoring change event due to debounce: 198ms < 200. rpi2.0 2025-02-27 15:31:08.028 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.028 debug Ignoring change event due to debounce: 197ms < 200. rpi2.0 2025-02-27 15:31:08.028 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.028 debug Ignoring change event due to debounce: 197ms < 200. rpi2.0 2025-02-27 15:31:08.028 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.027 debug Ignoring change event due to debounce: 196ms < 200. rpi2.0 2025-02-27 15:31:08.027 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.027 debug Ignoring change event due to debounce: 196ms < 200. rpi2.0 2025-02-27 15:31:08.027 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.027 debug Ignoring change event due to debounce: 196ms < 200. rpi2.0 2025-02-27 15:31:08.026 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.026 debug Ignoring change event due to debounce: 195ms < 200. rpi2.0 2025-02-27 15:31:08.026 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.026 debug Ignoring change event due to debounce: 195ms < 200. rpi2.0 2025-02-27 15:31:08.026 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.025 debug Ignoring change event due to debounce: 194ms < 200. rpi2.0 2025-02-27 15:31:08.025 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.025 debug Ignoring change event due to debounce: 194ms < 200. rpi2.0 2025-02-27 15:31:08.025 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.025 debug Ignoring change event due to debounce: 194ms < 200. rpi2.0 2025-02-27 15:31:08.024 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.024 debug Ignoring change event due to debounce: 193ms < 200. rpi2.0 2025-02-27 15:31:08.024 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.024 debug Ignoring change event due to debounce: 193ms < 200. rpi2.0 2025-02-27 15:31:08.024 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.023 debug Ignoring change event due to debounce: 192ms < 200. rpi2.0 2025-02-27 15:31:08.023 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.023 debug Ignoring change event due to debounce: 192ms < 200. rpi2.0 2025-02-27 15:31:08.022 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.022 debug Ignoring change event due to debounce: 191ms < 200. rpi2.0 2025-02-27 15:31:08.022 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.021 debug Ignoring change event due to debounce: 190ms < 200. rpi2.0 2025-02-27 15:31:08.021 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.020 debug Ignoring change event due to debounce: 189ms < 200. rpi2.0 2025-02-27 15:31:08.020 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.019 debug Ignoring change event due to debounce: 188ms < 200. rpi2.0 2025-02-27 15:31:08.019 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.018 debug Ignoring change event due to debounce: 187ms < 200. rpi2.0 2025-02-27 15:31:08.017 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.017 debug Ignoring change event due to debounce: 186ms < 200. rpi2.0 2025-02-27 15:31:08.016 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.016 debug Ignoring change event due to debounce: 185ms < 200. rpi2.0 2025-02-27 15:31:08.015 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.014 debug Ignoring change event due to debounce: 183ms < 200. rpi2.0 2025-02-27 15:31:08.014 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.013 debug Ignoring change event due to debounce: 182ms < 200. rpi2.0 2025-02-27 15:31:08.012 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.012 debug Ignoring change event due to debounce: 181ms < 200. rpi2.0 2025-02-27 15:31:08.011 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.010 debug Ignoring change event due to debounce: 179ms < 200. rpi2.0 2025-02-27 15:31:08.009 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.009 debug Ignoring change event due to debounce: 178ms < 200. rpi2.0 2025-02-27 15:31:08.008 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.007 debug Ignoring change event due to debounce: 176ms < 200. rpi2.0 2025-02-27 15:31:08.007 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.006 debug Ignoring change event due to debounce: 175ms < 200. rpi2.0 2025-02-27 15:31:08.005 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.004 debug Ignoring change event due to debounce: 173ms < 200. rpi2.0 2025-02-27 15:31:08.004 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.003 debug Ignoring change event due to debounce: 172ms < 200. rpi2.0 2025-02-27 15:31:08.002 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.002 debug Ignoring change event due to debounce: 171ms < 200. rpi2.0 2025-02-27 15:31:08.001 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:08.001 debug Ignoring change event due to debounce: 170ms < 200. rpi2.0 2025-02-27 15:31:08.000 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.999 debug Ignoring change event due to debounce: 168ms < 200. rpi2.0 2025-02-27 15:31:07.999 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.999 debug Ignoring change event due to debounce: 168ms < 200. rpi2.0 2025-02-27 15:31:07.998 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.998 debug Ignoring change event due to debounce: 167ms < 200. rpi2.0 2025-02-27 15:31:07.997 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.997 debug Ignoring change event due to debounce: 166ms < 200. rpi2.0 2025-02-27 15:31:07.997 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.996 debug Ignoring change event due to debounce: 165ms < 200. rpi2.0 2025-02-27 15:31:07.996 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.995 debug Ignoring change event due to debounce: 164ms < 200. rpi2.0 2025-02-27 15:31:07.995 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.994 debug Ignoring change event due to debounce: 163ms < 200. rpi2.0 2025-02-27 15:31:07.994 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.994 debug Ignoring change event due to debounce: 163ms < 200. rpi2.0 2025-02-27 15:31:07.993 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.992 debug Ignoring change event due to debounce: 161ms < 200. rpi2.0 2025-02-27 15:31:07.992 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.992 debug Ignoring change event due to debounce: 161ms < 200. rpi2.0 2025-02-27 15:31:07.991 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.991 debug Ignoring change event due to debounce: 160ms < 200. rpi2.0 2025-02-27 15:31:07.991 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.990 debug Ignoring change event due to debounce: 159ms < 200. rpi2.0 2025-02-27 15:31:07.990 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.990 debug Ignoring change event due to debounce: 159ms < 200. rpi2.0 2025-02-27 15:31:07.990 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.989 debug Ignoring change event due to debounce: 158ms < 200. rpi2.0 2025-02-27 15:31:07.989 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.989 debug Ignoring change event due to debounce: 158ms < 200. rpi2.0 2025-02-27 15:31:07.989 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.988 debug Ignoring change event due to debounce: 157ms < 200. rpi2.0 2025-02-27 15:31:07.988 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.988 debug Ignoring change event due to debounce: 157ms < 200. rpi2.0 2025-02-27 15:31:07.987 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.987 debug Ignoring change event due to debounce: 156ms < 200. rpi2.0 2025-02-27 15:31:07.987 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.987 debug Ignoring change event due to debounce: 156ms < 200. rpi2.0 2025-02-27 15:31:07.986 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.986 debug Ignoring change event due to debounce: 155ms < 200. rpi2.0 2025-02-27 15:31:07.986 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.986 debug Ignoring change event due to debounce: 155ms < 200. rpi2.0 2025-02-27 15:31:07.985 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.985 debug Ignoring change event due to debounce: 154ms < 200. rpi2.0 2025-02-27 15:31:07.985 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.985 debug Ignoring change event due to debounce: 154ms < 200. rpi2.0 2025-02-27 15:31:07.984 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.984 debug Ignoring change event due to debounce: 153ms < 200. rpi2.0 2025-02-27 15:31:07.984 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.983 debug Ignoring change event due to debounce: 152ms < 200. rpi2.0 2025-02-27 15:31:07.983 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.983 debug Ignoring change event due to debounce: 152ms < 200. rpi2.0 2025-02-27 15:31:07.983 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.982 debug Ignoring change event due to debounce: 151ms < 200. rpi2.0 2025-02-27 15:31:07.982 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.982 debug Ignoring change event due to debounce: 151ms < 200. rpi2.0 2025-02-27 15:31:07.982 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.981 debug Ignoring change event due to debounce: 150ms < 200. rpi2.0 2025-02-27 15:31:07.981 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.980 debug Ignoring change event due to debounce: 149ms < 200. rpi2.0 2025-02-27 15:31:07.980 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.980 debug Ignoring change event due to debounce: 149ms < 200. rpi2.0 2025-02-27 15:31:07.979 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.979 debug Ignoring change event due to debounce: 148ms < 200. rpi2.0 2025-02-27 15:31:07.979 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.978 debug Ignoring change event due to debounce: 147ms < 200. rpi2.0 2025-02-27 15:31:07.978 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.978 debug Ignoring change event due to debounce: 147ms < 200. rpi2.0 2025-02-27 15:31:07.977 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.977 debug Ignoring change event due to debounce: 146ms < 200. rpi2.0 2025-02-27 15:31:07.977 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.976 debug Ignoring change event due to debounce: 145ms < 200. rpi2.0 2025-02-27 15:31:07.976 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.976 debug Ignoring change event due to debounce: 145ms < 200. rpi2.0 2025-02-27 15:31:07.975 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.975 debug Ignoring change event due to debounce: 144ms < 200. rpi2.0 2025-02-27 15:31:07.974 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.974 debug Ignoring change event due to debounce: 143ms < 200. rpi2.0 2025-02-27 15:31:07.974 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.973 debug Ignoring change event due to debounce: 142ms < 200. rpi2.0 2025-02-27 15:31:07.973 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.973 debug Ignoring change event due to debounce: 141ms < 200. rpi2.0 2025-02-27 15:31:07.972 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.971 debug Ignoring change event due to debounce: 140ms < 200. rpi2.0 2025-02-27 15:31:07.971 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.970 debug Ignoring change event due to debounce: 139ms < 200. rpi2.0 2025-02-27 15:31:07.970 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.969 debug Ignoring change event due to debounce: 138ms < 200. rpi2.0 2025-02-27 15:31:07.969 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.969 debug Ignoring change event due to debounce: 138ms < 200. rpi2.0 2025-02-27 15:31:07.969 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.968 debug Ignoring change event due to debounce: 137ms < 200. rpi2.0 2025-02-27 15:31:07.968 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.968 debug Ignoring change event due to debounce: 137ms < 200. rpi2.0 2025-02-27 15:31:07.968 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.967 debug Ignoring change event due to debounce: 136ms < 200. rpi2.0 2025-02-27 15:31:07.967 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.967 debug Ignoring change event due to debounce: 136ms < 200. rpi2.0 2025-02-27 15:31:07.967 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.966 debug Ignoring change event due to debounce: 135ms < 200. rpi2.0 2025-02-27 15:31:07.966 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.966 debug Ignoring change event due to debounce: 135ms < 200. rpi2.0 2025-02-27 15:31:07.966 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.965 debug Ignoring change event due to debounce: 134ms < 200. rpi2.0 2025-02-27 15:31:07.965 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.965 debug Ignoring change event due to debounce: 134ms < 200. rpi2.0 2025-02-27 15:31:07.964 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.964 debug Ignoring change event due to debounce: 133ms < 200. rpi2.0 2025-02-27 15:31:07.964 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.964 debug Ignoring change event due to debounce: 133ms < 200. rpi2.0 2025-02-27 15:31:07.963 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.963 debug Ignoring change event due to debounce: 132ms < 200. rpi2.0 2025-02-27 15:31:07.963 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.962 debug Ignoring change event due to debounce: 131ms < 200. rpi2.0 2025-02-27 15:31:07.962 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.961 debug Ignoring change event due to debounce: 130ms < 200. rpi2.0 2025-02-27 15:31:07.961 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.961 debug Ignoring change event due to debounce: 130ms < 200. rpi2.0 2025-02-27 15:31:07.961 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.960 debug Ignoring change event due to debounce: 129ms < 200. rpi2.0 2025-02-27 15:31:07.960 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.960 debug Ignoring change event due to debounce: 129ms < 200. rpi2.0 2025-02-27 15:31:07.959 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.959 debug Ignoring change event due to debounce: 128ms < 200. rpi2.0 2025-02-27 15:31:07.959 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.958 debug Ignoring change event due to debounce: 127ms < 200. rpi2.0 2025-02-27 15:31:07.958 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.957 debug Ignoring change event due to debounce: 126ms < 200. rpi2.0 2025-02-27 15:31:07.956 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.956 debug Ignoring change event due to debounce: 125ms < 200. rpi2.0 2025-02-27 15:31:07.955 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.955 debug Ignoring change event due to debounce: 124ms < 200. rpi2.0 2025-02-27 15:31:07.954 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.954 debug Ignoring change event due to debounce: 123ms < 200. rpi2.0 2025-02-27 15:31:07.953 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.943 debug Written false into port 21 rpi2.0 2025-02-27 15:31:07.943 debug Setting initial value for port 21 to false rpi2.0 2025-02-27 15:31:07.895 debug Written false into port 20 rpi2.0 2025-02-27 15:31:07.895 debug Setting initial value for port 20 to false rpi2.0 2025-02-27 15:31:07.847 debug Ignoring change event due to debounce: 16ms < 200. rpi2.0 2025-02-27 15:31:07.846 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.842 debug Written false into port 19 rpi2.0 2025-02-27 15:31:07.842 debug Setting initial value for port 19 to false rpi2.0 2025-02-27 15:31:07.833 debug Ignoring change event due to debounce: 2ms < 200. rpi2.0 2025-02-27 15:31:07.832 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.832 debug Ignoring change event due to debounce: 1ms < 200. rpi2.0 2025-02-27 15:31:07.832 debug GPIO change on port 23: true rpi2.0 2025-02-27 15:31:07.832 debug Ignoring change event due to debounce: 0ms < 200. rpi2.0 2025-02-27 15:31:07.831 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.831 debug Setting state for port 23 to false rpi2.0 2025-02-27 15:31:07.830 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.825 debug Written false into port 16 rpi2.0 2025-02-27 15:31:07.825 debug Setting initial value for port 16 to false rpi2.0 2025-02-27 15:31:07.778 debug Ignoring change event due to debounce: 186ms < 200. rpi2.0 2025-02-27 15:31:07.778 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.773 debug Written false into port 13 rpi2.0 2025-02-27 15:31:07.772 debug Setting initial value for port 13 to false rpi2.0 2025-02-27 15:31:07.764 debug Ignoring change event due to debounce: 172ms < 200. rpi2.0 2025-02-27 15:31:07.764 debug GPIO change on port 23: false rpi2.0 2025-02-27 15:31:07.763 debug Setting state for port 17 to true rpi2.0 2025-02-27 15:31:07.763 debug GPIO change on port 17: true rpi2.0 2025-02-27 15:31:07.754 debug Written false into port 12 rpi2.0 2025-02-27 15:31:07.753 debug Setting initial value for port 12 to false rpi2.0 2025-02-27 15:31:07.753 debug Adding event listener for port 27 rpi2.0 2025-02-27 15:31:07.752 debug Adding event listener for port 24 rpi2.0 2025-02-27 15:31:07.752 debug Adding event listener for port 23 rpi2.0 2025-02-27 15:31:07.752 debug Adding event listener for port 22 rpi2.0 2025-02-27 15:31:07.752 debug Adding event listener for port 18 rpi2.0 2025-02-27 15:31:07.751 debug Adding event listener for port 17 rpi2.0 2025-02-27 15:31:07.699 debug Setting state for port 27 to false rpi2.0 2025-02-27 15:31:07.698 debug Port 27 direction: in rpi2.0 2025-02-27 15:31:07.696 debug Port 26 direction: outlow rpi2.0 2025-02-27 15:31:07.695 debug Port 25 direction: outlow rpi2.0 2025-02-27 15:31:07.646 debug Setting state for port 24 to false rpi2.0 2025-02-27 15:31:07.644 debug Port 24 direction: in rpi2.0 2025-02-27 15:31:07.593 debug Setting state for port 23 to false rpi2.0 2025-02-27 15:31:07.591 debug Port 23 direction: in rpi2.0 2025-02-27 15:31:07.540 debug Setting state for port 22 to false rpi2.0 2025-02-27 15:31:07.539 debug Port 22 direction: in rpi2.0 2025-02-27 15:31:07.537 debug Port 21 direction: outlow rpi2.0 2025-02-27 15:31:07.536 debug Port 20 direction: outlow rpi2.0 2025-02-27 15:31:07.535 debug Port 19 direction: outlow rpi2.0 2025-02-27 15:31:07.485 debug Setting state for port 18 to false rpi2.0 2025-02-27 15:31:07.483 debug Port 18 direction: in rpi2.0 2025-02-27 15:31:07.430 debug Setting state for port 17 to false rpi2.0 2025-02-27 15:31:07.427 debug Port 17 direction: in rpi2.0 2025-02-27 15:31:07.426 debug Port 16 direction: outlow rpi2.0 2025-02-27 15:31:07.424 debug Port 13 direction: outlow rpi2.0 2025-02-27 15:31:07.423 debug Port 12 direction: outlow rpi2.0 2025-02-27 15:31:07.422 debug Got chip: class Default extends classes_1.Device { } rpi2.0 2025-02-27 15:31:07.422 debug Got 4 from Raspberry Pi 4 Model B Rev 1.2 code_textWenn ich den Adapter nicht beende und nur was darin ändere kommt immer diese Warnung. Ev. könnt Ihr ja was damit anfangen.
admin.0 2025-02-27 15:56:54.758 warn rpi2 has an invalid jsonConfig: [{"instancePath":"/items/_gpios/items/_pullUpWarning/hidden","schemaPath":"#/patternProperties/%5E.%2B/properties/hidden/type","keyword":"type","params":{"type":"string"},"message":"must be string"},{"instancePath":"/items/_gpios","schemaPath":"#/properties/items/patternProperties/%5E.%2B/allOf/9/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"},{"instancePath":"","schemaPath":"#/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must match \"then\" schema"}]code_text@hasont sagte in Test Adapter rpi2 2.x:
pullUpWarning/hiddenHast du Pullup / Pulldown ein Haken gesetzt? Oder nur von True mal auf false geändert ? wenn ja, dann mit Bestätigung?
Ich fasse kurz zusammen - heißt bei dir bleibt der Eingang die ganze Zeit auf True! Ich werde mal meinen Magnetschalter überbrücken um die Verbindung zu optimieren. Mal schauen ob der vielleicht zu viel Widerstand hat. Auch wenn ich mir das nicht vorstellen kann- da er ja sonst dauerhaft stabil ein True bringt.
-
@garfonso sagte in Test Adapter rpi2 2.x:
@hasont said in Test Adapter rpi2 2.x:
Hab dann Protokoll gemacht. Soll eigentlich alle ca. 5sec True/False wechseln. Komm damit nicht klar.
Habs mal angehängt!Also laut log hat es doch funktioniert? Alle 5 Sekunden ist ein Wechsel durchgekommen. Zwischendurch
sind ein paar andere Dinge vom debounce timer abgefangen worden...?- 20:09:33 true
- 20:09:38 false
- 20:09:43 true (kam instgesammt 6 mal, 4 davon per debounce timer abgerufen, der letzte kam durch, also tatsächlich doppelt -> debounce timer erhöhen, falls das nicht gewünscht ist, oder weniger rumprellen ;-) )
- 20:09:47 false (da kamen dann tatsächlich ein paar true, aber alle vom timer abgefangen)
- 20:09:52 true (wieder mit einigen, die im debounce timer hängen bleiben)
Was ist da jetzt genau falsch?
Du hast recht, wahrscheinlich hab ich mir einen abgezittert mit meiner Kroko Klemme.
Wenn ich 1000ms eingeben müsste ich 1sec den Taster drücken um ein True zu bekommen, oder?@hasont sagte in Test Adapter rpi2 2.x:
en müsste ich 1sec den Taster drücken um ein True zu bekommen, oder?
Korrekt.
-
@hasont sagte in Test Adapter rpi2 2.x:
pullUpWarning/hiddenHast du Pullup / Pulldown ein Haken gesetzt? Oder nur von True mal auf false geändert ? wenn ja, dann mit Bestätigung?
Ich fasse kurz zusammen - heißt bei dir bleibt der Eingang die ganze Zeit auf True! Ich werde mal meinen Magnetschalter überbrücken um die Verbindung zu optimieren. Mal schauen ob der vielleicht zu viel Widerstand hat. Auch wenn ich mir das nicht vorstellen kann- da er ja sonst dauerhaft stabil ein True bringt.
pi2.0 2025-02-27 15:31:07.430 debug Setting state for port 17 to falseObowhl, hier ist doch mein false. Die anderen True kommen alle vom watch Befehl.
Hast du die Änderung der Datenpunkte in der Datenbank oder History geblockt? Da war garantiert das eine "false" bei - wenn der DEBUG es scho sagt. -
@hasont sagte in Test Adapter rpi2 2.x:
pullUpWarning/hiddenHast du Pullup / Pulldown ein Haken gesetzt? Oder nur von True mal auf false geändert ? wenn ja, dann mit Bestätigung?
Ich fasse kurz zusammen - heißt bei dir bleibt der Eingang die ganze Zeit auf True! Ich werde mal meinen Magnetschalter überbrücken um die Verbindung zu optimieren. Mal schauen ob der vielleicht zu viel Widerstand hat. Auch wenn ich mir das nicht vorstellen kann- da er ja sonst dauerhaft stabil ein True bringt.
@smallfeuer sagte in Test Adapter rpi2 2.x:
@hasont sagte in Test Adapter rpi2 2.x:
pullUpWarning/hiddenHast du Pullup / Pulldown ein Haken gesetzt? Nein, alle ohne
Oder nur von True mal auf false geändert ? wenn ja, dann mit Bestätigung? NeinIch fasse kurz zusammen - heißt bei dir bleibt der Eingang die ganze Zeit auf True! Ich werde mal meinen Magnetschalter überbrücken um die Verbindung zu optimieren. Mal schauen ob der vielleicht zu viel Widerstand hat. Auch wenn ich mir das nicht vorstellen kann- da er ja sonst dauerhaft stabil ein True bringt.
Hab grad im Objekt nachgesehen und mein GPIO 17 war False. Bin in den Keller um zu sehen ob ich ev. die Krokoklemme schon abgeklemmt habe >> Nein war noch geschaltet.
Dann schau ich in den PC und der GPIO 17 ist wieder True (hab nur Licht eingeschaltet)
Ich bleib da mal für dich dran!Edit 27.02 21:00: Grad mal alle Eingänge auf 1000ms gesetzt um zu sehen ob der Eingang GPIO 23 beim Licht einschalten (Neon) noch kommen.
In Instanz rsp2 abgespeichert und jetzt ist GPIO 17 FALSE, Eingang noch an 3,3V Leider kein log!!
Edit:28.02 10:38 Gerade nachgesehen und GPIO ist wieder True > Log eingeschaltet und Instanz neu gestartet.
GPIO 17 war wieder False 2025-02-28 10:21:11.461 und ist dann 2025-02-28 10:28:55.677 auf True
Der GPIO 17 ist dauerhaft an 3,3VHier das Logfile von 10:21 - 10:36
02 Log-Größe: 25.2 MB Zeit rpi2.0 2025-02-28 10:36:57.654 debug Ignoring change event due to debounce: 7ms < 1000. rpi2.0 2025-02-28 10:36:57.653 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:36:57.647 debug Setting state for port 23 to false rpi2.0 2025-02-28 10:36:57.646 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:35:57.650 debug Ignoring change event due to debounce: 5ms < 1000. rpi2.0 2025-02-28 10:35:57.649 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:35:57.646 debug Setting state for port 23 to false rpi2.0 2025-02-28 10:35:57.645 debug GPIO change on port 23: false ebus.0 2025-02-28 10:35:06.748 info all history done ebus.0 2025-02-28 10:35:06.717 info all http done ebus.0 2025-02-28 10:35:06.661 info installed ebusd version is 24.1 rpi2.0 2025-02-28 10:34:57.652 debug Ignoring change event due to debounce: 5ms < 1000. rpi2.0 2025-02-28 10:34:57.651 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:34:57.649 debug Ignoring change event due to debounce: 2ms < 1000. rpi2.0 2025-02-28 10:34:57.648 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:34:57.647 debug Setting state for port 23 to false rpi2.0 2025-02-28 10:34:57.646 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:33:57.652 debug Setting state for port 23 to false rpi2.0 2025-02-28 10:33:57.651 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:32:57.652 debug Ignoring change event due to debounce: 11ms < 1000. rpi2.0 2025-02-28 10:32:57.651 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:32:57.651 debug Ignoring change event due to debounce: 10ms < 1000. rpi2.0 2025-02-28 10:32:57.650 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:32:57.649 debug Ignoring change event due to debounce: 8ms < 1000. rpi2.0 2025-02-28 10:32:57.648 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:32:57.641 debug Setting state for port 23 to false rpi2.0 2025-02-28 10:32:57.640 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:31:57.651 debug Setting state for port 23 to false rpi2.0 2025-02-28 10:31:57.651 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:30:57.653 debug Ignoring change event due to debounce: 7ms < 1000. rpi2.0 2025-02-28 10:30:57.652 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:30:57.646 debug Setting state for port 23 to false rpi2.0 2025-02-28 10:30:57.645 debug GPIO change on port 23: false ebus.0 2025-02-28 10:30:06.758 info all history done ebus.0 2025-02-28 10:30:06.725 info all http done ebus.0 2025-02-28 10:30:06.666 info installed ebusd version is 24.1 host.raspberrypi 2025-02-28 10:30:00.027 warn instance system.adapter.ebus.0 already running with pid 1127 rpi2.0 2025-02-28 10:29:57.653 debug Ignoring change event due to debounce: 11ms < 1000. rpi2.0 2025-02-28 10:29:57.652 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:29:57.645 debug Ignoring change event due to debounce: 3ms < 1000. rpi2.0 2025-02-28 10:29:57.644 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:29:57.642 debug Setting state for port 23 to false rpi2.0 2025-02-28 10:29:57.641 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:28:55.679 debug Setting state for port 23 to false rpi2.0 2025-02-28 10:28:55.679 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:28:55.678 debug Setting state for port 17 to true rpi2.0 2025-02-28 10:28:55.677 debug GPIO change on port 17: true rpi2.0 2025-02-28 10:27:57.653 debug Ignoring change event due to debounce: 9ms < 1000. rpi2.0 2025-02-28 10:27:57.652 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:27:57.644 debug Setting state for port 23 to false rpi2.0 2025-02-28 10:27:57.643 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:26:57.652 debug Ignoring change event due to debounce: 6ms < 1000. rpi2.0 2025-02-28 10:26:57.651 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:26:57.649 debug Ignoring change event due to debounce: 3ms < 1000. rpi2.0 2025-02-28 10:26:57.648 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:26:57.646 debug Setting state for port 23 to false rpi2.0 2025-02-28 10:26:57.645 debug GPIO change on port 23: false ebus.0 2025-02-28 10:25:06.851 info all history done ebus.0 2025-02-28 10:25:06.819 info all http done ebus.0 2025-02-28 10:25:06.751 info installed ebusd version is 24.1 rpi2.0 2025-02-28 10:24:57.639 debug Setting state for port 23 to false rpi2.0 2025-02-28 10:24:57.639 debug GPIO change on port 23: false rpi2.0 2025-02-28 10:21:11.627 debug Port 23 direction: in rpi2.0 2025-02-28 10:21:11.576 debug Setting state for port 22 to false rpi2.0 2025-02-28 10:21:11.575 debug Port 22 direction: in rpi2.0 2025-02-28 10:21:11.574 debug Port 21 direction: outlow rpi2.0 2025-02-28 10:21:11.573 debug Port 20 direction: outlow rpi2.0 2025-02-28 10:21:11.571 debug Port 19 direction: outlow rpi2.0 2025-02-28 10:21:11.521 debug Setting state for port 18 to false rpi2.0 2025-02-28 10:21:11.519 debug Port 18 direction: in rpi2.0 2025-02-28 10:21:11.461 debug Setting state for port 17 to false rpi2.0 2025-02-28 10:21:11.458 debug Port 17 direction: in rpi2.0 2025-02-28 10:21:11.457 debug Port 16 direction: outlow rpi2.0 2025-02-28 10:21:11.455 debug Port 13 direction: outlow rpi2.0 2025-02-28 10:21:11.454 debug Port 12 direction: outlow rpi2.0 2025-02-28 10:21:11.453 debug Got chip: class Default extends classes_1.Device {} rpi2.0 2025-02-28 10:21:11.453 debug Got 4 from Raspberry Pi 4 Model B Rev 1.2code_text host.raspberrypi 2025-02-28 10:21:04.831 info stopInstance timeout system.adapter.rpi2.0 killing pid 3483Edit 2.03 16:43 Musste IOB gestern und heute mehrfach starten. Mein GPIO 17 war danach immer False und ging nach unbestimmter Zeit dann auf True. Irgendwie scheint es so als würde er auf einen Trigger warten. Grad war es direkt nach einem VIS-Login.
rpi2.0 2025-03-02 16:40:18.648 debug Setting state for port 23 to false rpi2.0 2025-03-02 16:40:18.648 debug GPIO change on port 23: false rpi2.0 2025-03-02 16:40:18.648 debug Ignoring change event due to debounce: 0ms < 1000. rpi2.0 2025-03-02 16:40:18.648 debug GPIO change on port 17: true rpi2.0 2025-03-02 16:40:18.648 debug Setting state for port 17 to true rpi2.0 2025-03-02 16:40:18.647 debug GPIO change on port 17: true web.0 2025-03-02 16:40:16.242 info ==> Connected system.user.admin from ::ffff:192.168.1.104 web.0 2025-03-02 16:40:15.951 info <== Disconnect system.user.admin from ::ffff:192.168.1.104 vis.0 rpi2.0 2025-03-02 16:40:10.254 debug Ignoring change event due to debounce: 36ms < 1000. rpi2.0 2025-03-02 16:40:10.254 debug GPIO change on port 23: falseHab dann den Prozess neu gestartet GPIO 17 wieder False. Im VIS GPIO 25 geändert und sofort kam auch beim GPIO 17 ohne debounce ein True.
rpi2.0 2025-03-02 16:56:46.083 debug Setting state for port 23 to false rpi2.0 2025-03-02 16:56:46.082 debug GPIO change on port 23: false rpi2.0 2025-03-02 16:56:46.081 debug Setting state for port 17 to true rpi2.0 2025-03-02 16:56:46.081 debug GPIO change on port 17: true rpi2.0 2025-03-02 16:56:46.077 debug Written true into port 25 rpi2.0 2025-03-02 16:56:46.077 debug stateChange for rpi2.0.gpio.25.state found state = {"val":true,"ack":false,"ts":1740931006072,"q":0,"from":"system.adapter.web.0","user":"system.user.admin","lc":1740931006072}
Support us
394
Online32.4k
Users81.5k
Topics1.3m
Posts