Lampe von Fa. Luke Roberts

[Gast]

Sieht relativ dick aus. Soviel Power braucht man eigentlich nicht. Zum Entwickeln hängt mein esp32 nur an einem PC USB Port

Mit dem 'Dimmersatz' hab ich allerdings eigene Zeit gekämpft

Ich wollte diese Teile verwenden
https://www.amazon.de/WayinTop-Encod...ref=mp_s_a_1_4 aber der Schaft ist zu lang also abgesägt und dann natürlich zu dick für den Gira Dimmerknopf. Also habe ich aus den schwarzen Knöpfen den Kunststoffeinsatz rausgefummel und irgendwie mit Heißkleber in die Giraabdeckung geklebt.
Nachdem sich meine handwerklichen Künste in Grenzen halten hat es einige Zeit gedauert 😂 ich war kurz davor doch den Homematic Drehgeber zu nehmen (https://www.homematic-ip.com/en/prod...ry-button.html) und damit http requests zu schicken.

[michael287]

Den Drehdinmer bräuchte ich gar nicht unbedingt, wäre eher nice to Have.
der Beetle (ohne) Fire hat ja nochmal einen etwas geschickteren Formfaktor, was UP Dosen angeht.
Da müsste man nur sehen, ob dein Projekt auf dem läuft.

[michael287]

Was mir immer noch nicht klar ist, ist wie ich den Rotary Encoder am Drehknopf befestigen könnte.
es muss ja eine feste Verbindung sein, da der Button des Rotary ja sonst nicht gedrückt werden kann?
Evtl könnte ich auch was im 3D Drucker dazu basteln..
bin mir nicht mal sicher, ob mein Drehknopf überhaupt drückest wäre, Jung AS 1450.
Wahrscheinlich einfach mal bestellen und testen. Der Homematic kommt bei mir nicht in Frage...


EDIT: Der von mir genannte Drehdimmerknopf kann auch gedrückt werden.

[nightfly2000]

Hi ich bekomme das Git nicht mal mit den Standard Einstellungen mit VSCode kompiliert...
Hat jemand eine Idee?

Anbei die fehler Meldung

Compiling .pio\build\default_env\src\BleGattClient.cpp.o
xtensa-esp32-elf-g++: error: unrecognized command line option '-R'
Compiling .pio\build\default_env\src\app_utils.cpp.o
xtensa-esp32-elf-g++: error: unrecognized command line option '-R'
Compiling .pio\build\default_env\src\main.cpp.o
*** [.pio\build\default_env\src\BleGattClient.cpp.o] Error 1
Compiling .pio\build\default_env\src\rotaryencoder.cpp.o
*** [.pio\build\default_env\src\app_utils.cpp.o] Error 1
xtensa-esp32-elf-g++: error: unrecognized command line option '-R'
*** [.pio\build\default_env\src\main.cpp.o] Error 1
xtensa-esp32-elf-g++: error: unrecognized command line option '-R'
*** [.pio\build\default_env\src\rotaryencoder.cpp.o] Error 1

[Gast]

Wenn du platformio_usersettings.ini.sample verwendest, musst du Zeile 43 ändern. da fehlt ein 'D', außerdem sollte die Zeile vermutlich auskommentiert sein.
Wenn du keine der über Widerstände codierten buttons verwendest, brauchst du das Feature eh nicht

            -RESISTOR_BUTTON_UP_CLICK_ACTION=kChangeBrightness

=>

        ;   -DRESISTOR_BUTTON_UP_CLICK_ACTION=kChangeBrightness

[nightfly2000]

Hi super Danke das war der Fehler.
Werde dann mal mit meinem Board und Settings probieren alles zu kompilieren.
Habe dafür das Atom lite Board geholt welches eigentlich damit funktionieren müsste. Mir gehts nur um die MQTT befehle zu senden. Den Rotary Switch brauche ich vorerst mal nicht! ;-)

[Gast]

Dann kannst du aus der ini im Prinzip alles nach dem Kommentar 'define Hardware settings' löschen das ist alles nur für Taster und Rotary

[nightfly2000]

Ok ja es funktioniert leider nicht trotz erfolgreichen kompilieren. Ich komme aufs Webinterface, dort sehe ich allerdings kein Bluetooth Device. Habe es mal mit der Mac Adresse von der Lampe aus der APP probiert. Bzw. auch mal die Zeile aus kommentiert zwecks Autoscan. Kann es an meinem Board liegen?
Laut meiner Recherche ist´s eigentlich egal welches ich nehme, weil alle irgendwie auf dem ESP32 basieren nur die GPIO´s unterscheiden sich halt.

https://docs.m5stack.com/en/core/atom_lite

Das ist das Board. Sofern ich alles so richtig Interpretiert habe müsste ich zwecks Testen die Zeile 39 den richtigen GPIO definieren. In meinem Fall den GPIO 39 das ist ein onboard Button. Damit müsste ich ja simple die Lampe ein/ausschalten können?
Bzw. gibts ein empfohlenes Flashtool?
Ich habe mal zwecks Windows https://github.com/Jason2866/ESP_Flasher/releases diesen genommen. Dort sieht man gleich auch die Logfiles recht gut beim Hochfahren!
LG.

[Gast]

Das Board sollte egal sein.
Schau mal in die platform.ini. Mit der Einstellung würde ein OTA update eines ESP32 mit der IP 192.168.66.43 versucht werden. Das klappt bei dir nicht

monitor_speed = 115200
upload_speed = 921600
monitor_port=COM13
;upload_port=COM13
upload_protocol = espota
upload_port = 192.168.66.43

Du solltest upload_port=COM Port des Atom, genauso monitor_port und upload_protocol auskommentieren
in platformio_usersettings.ini für den Button
-DSINGLE_BUTTON_PIN=GPIO_NUM_39


Damit sollte pio run auch unter Windows flashen.. Ohne die seriellem logs zur Laufzeit kann ich leider nicht viel sagen.

Ich mache das allerdings nicht von der command line sondern mit Visual Studio Code und der Platformio extension . Dann einfach F1 - plat tippen und entweder "PlatfromIO Upload oder Serial Monitor

[nightfly2000]

Hi ja werde ich gleich probieren. Ja kompilieren tue ich es eh auch mit VSCode. den Uploade mache ich allerdings nie mit dem Programm sondern immer mit diversen Tasmota Tools, weil ich da einige Geräte mit der Firmware betreibe. Werde das mit dem VSCode upload mal probieren und gebe bescheid ob die Settings so dann funktionieren!

[nightfly2000]

Anbei die Usersettings die ich jetzt nur von dem sample File abgeleitet habe.
Das MQTT habe ich mal fürs erste deaktiviert weil ich zwecks test mal das webinterface nutzen wollte.

[usersettings]
board =  m5stick-c  ## select your board
build_flags = -DWIFISID='"geheim"'
            -DWIFIPASSWORD='"geheim"'
;            -DMQTTUSER='nullptr'                        ## if you need mqtt user and password make sure to correctly quote them as in WIFIPASSWORD above
;            -DMQTTPASSWORD='nullptr'
            -DHOSTNAME='"lrcontroller"'
            -DDOMAINNAME='".local"'                     ## only used in setHostname
;           -DMQTTHOST='"192.168.0.140"'
;            -DMQTTPORT=1883
            -DNTP_SERVER='"europe.pool.ntp.org"'
            -DTIMEZONE='"CET-1CEST,M3.5.0,M10.5.0/3"'
;            -DUSE_ETHERNET                             ## use ethernet instead of Wifi
## Define network parameters
##   if not defined use DHCP
;            -DIP_ADDR='"192.168.1.69"'
            -DIP_SUBNET='"255.255.255.0"'               # these values are ignored if IP_ADDR is not defined
            -DIP_GATEWAY='"192.168.1.1"'                #
            -DDNS_SERVER='"192.168.1.9"'                #   dns is only required to contact the NTP Server
            -DDNS_SERVER2='"192.168.1.19"'              #   optional second DNS Server
            -DLR_BLEADDRESS='"e8:c5:06:04:66:ed"'      ## if you add the device address here we can skip scanning at startup
## Define hardware otpions
;            -DROTARY_PIN_A=GPIO_NUM_26                   ## pin A (CLK) of the rotary (Fire Beetle D3)
;            -DROTARY_PIN_B=GPIO_NUM_27                   ## pin B (DT) of the rotary (Fire Beetle D4)
;            -DROTARY_STEP_VALUE=5                       ## value change for every event. Default is 5
;            -DROTARY_DOUBLE_SPEED_INTERVAL=60           ## if less than 60 ms between 2 events double ROTARY_STEP_VALUE
;            -DROTARY_QUAD_SPEED_INTERVAL=30             ## if less than 30 ms between 2 events use 4 * ROTARY_STEP_VALUE
;            -DROTARY_BUTTON_PIN=GPIO_NUM_25              ## input pin of the rotary switch (SW) (Fire Beetle D2)
;            -DROTARY_BUTTON_PIN_CLICK_ACTION=kPowerToggle ## Modifiy the function attached to the action
;            -DROTARY_BUTTON_PIN_LONG_PRESS_ACTION=kNoop
;            -DRELAY_PIN=GPIO_NUM_23
;            -DSWITCH_PIN=GPIO_NUM_39                   ## Use a toggle switch (on/off switch not a button). triggers whenever the position is changed
## control from a single button
## click == toggle , long press tune up /mdown, double ckick change scene
            -DSINGLE_BUTTON_PIN=GPIO_NUM_39
;            -DSINGLE_BUTTON_DOUBLE_CLICK_ACTION=kNextScene
;            -DSINGLE_BUTTON_STEP_VALUE=20
;           -DRESISTOR_BUTTON_PIN=35                    ## Defines 3 buttons connected one GPIO using voltage dividers
;           -DRESISTOR_BUTTON_UP_CLICK_ACTION=kChangeBrightness
;            ## A virtual pin triggered if RESISTOR_BUTTON_UP and DRESISTOR_BUTTON_DOWN are pressed together
;            -DRESISTOR_BUTTON_D1=970                    ## 3.3k (both buttons pressed 5.1 and 10k parallel)
;            -DRESISTOR_BUTTON_UP=1450                   ## 5.1k
;            -DRESISTOR_BUTTON_DOWN=1840                 ## 10k
;            ## A virtual pin triggered if RESISTOR_BUTTON_SWITCH and DRESISTOR_BUTTON_SWITCH2 are pressed together
;            -DRESISTOR_BUTTON_D2=2250                 ## 15k (both buttons pressed 22k and 47k parallel) set to 0 if you want to disable it
;            -DRESISTOR_BUTTON_SWITCH=2620               ## 22k
;            -DRESISTOR_BUTTON_SWITCH2=3220               ## 47k

;            -DBUTTON_DOWN_PIN=GPIO_NUM_5                ## regular push buttons attached to GPIO
;            -DBUTTON_DOWN_PIN_LONG_PRESS_ACTION=kNoop  ## the the action to no operation
;            -DBUTTON_UP_PIN=GPIO_NUM_17                 ##
;            -DBUTTON_UP_PIN_STEP_VALUE=20              ## Change the step value for the button
            ### LONG PRESS Behavior: LONG PRESS on the rotary button is used to switch to the next scene. LONG_PRESS_DELAY defines how long the button must be pressed for the first event.
            ###                      LONG_PRESS_INTERVAL defines how long it takes to switch to the next scene
;            -DLONG_PRESS_DELAY=1500                     ## number of milliseconds to start a long press event. defaults to 1500ms if not defined
;            -DLONG_PRESS_INTERVAL=500                  ## number of milliseconds to fire the next long press event. defaults to 1500ms if not defined
;            -DDOUBLE_CLICK_INTERVAL=500                  ## max number of milliseconds to between 2 clicks to be a double click. defaults to 500ms if not defined

Und hier die platformio.ini

; PlatformIO Project Configuration File
;
;   Build options: build flags, source filter
;   Upload options: custom upload port, speed and extra flags
;   Library options: dependencies, extra library storages
;   Advanced options: extra scripting
;
; Please visit documentation for the other options and examples
; https://docs.platformio.org/page/projectconf.html
[platformio]
extra_configs = platformio_usersettings.ini

[build_envs]
default_envs = default_env
[env:default_env]
platform = espressif32
board =  ${usersettings.board} 
framework = arduino
board_build.partitions = partitions.csv
build_flags               =  ${usersettings.build_flags}
                             -DCORE_DEBUG_LEVEL=5
                             -DCONFIG_SW_COEXIST_ENABLE=1
# using the latest stable version
lib_deps =  h2zero/NimBLE-Arduino @ ^1.0.2
            bxparks/AceButton @ ^1.8
            AsyncTCP-esphome
            256dpi/MQTT @ ^2.5.0
            ottowinter/ESPAsyncWebServer-esphome @ ^1.2.7
monitor_filters = esp32_exception_decoder
monitor_speed = 115200
upload_speed = 921600
;monitor_port=COM4
;upload_port=COM04
;upload_protocol = espota
;upload_port = 192.168.66.43

Der Upload mit VSCode funktioniert bei mir nicht da bekomme ich immer eine Timeout Meldung.
Mit dem ESP Flasher von dem obigen Link klappt das flashen ohne Probleme
Dort kann man einen Log auch im Betrieb mit anschauen!
Anbei der Log:

Using 'COM4' as serial port.
Showing logs:
[18:49:38][D][lukeroberts.h:435] request_all_scenes(): Got 1 scenes
[18:49:38][D][lukeroberts.h:453] get_all_scenes(): Scene 0 name=OFF
[18:49:38]D NimBLERemoteService: ">> getCharacteristic: uuid: 44092844-0567-11e6-b862-0002a5d5c51b"
[18:49:38]D NimBLERemoteService: ">> retrieveCharacteristics() for service: 44092840-0567-11e6-b862-0002a5d5c51b"
[18:49:38]D NimBLERemoteService: "Characteristic Discovered >> status: 0 handle: 42"
[18:49:38]D NimBLERemoteCharacteristic: ">> NimBLERemoteCharacteristic()"
[18:49:38]D NimBLERemoteCharacteristic: "<< NimBLERemoteCharacteristic(): 44092844-0567-11e6-b862-0002a5d5c51b"
[18:49:38]D NimBLERemoteService: "Characteristic Discovered >> status: 14 handle: -1"
[18:49:38]D NimBLERemoteService: "<< Characteristic Discovered"
[18:49:38]D NimBLERemoteService: "<< retrieveCharacteristics()"
[18:49:38]D NimBLERemoteCharacteristic: ">> readValue(): uuid: 44092844-0567-11e6-b862-0002a5d5c51b, handle: 42 0x2a"
[18:49:38]I NimBLERemoteCharacteristic: "Read complete; status=0 conn_handle=0"
[18:49:38]D NimBLERemoteCharacteristic: "Got 1 bytes"
[18:49:39]I NimBLERemoteCharacteristic: "Read complete; status=14 conn_handle=0"
[18:49:39]D NimBLERemoteCharacteristic: "<< readValue length: 1 rc=0"
[18:49:39][I][lukeroberts.h:464] get_current_scene(): Current Scene: 0
[18:49:39]
[18:49:39][D][main.cpp:737] setup(): Inital State: Power = 0 scene 0
[18:49:39][I][app_utils.cpp:89] setupOta(): - Ready for OTA
[18:49:39][I][ArduinoOTA.cpp:141] begin(): OTA server at: lrcontroller.local.local:3232
[18:49:39][D][BleGattClient.cpp:213] loop(): trying to connect
[18:49:39][I][BleGattClient.cpp:215] loop(): Connected to the BLE Server.
[18:49:39][D][BleGattClient.h:37] send(): BLE GATT SEND
[18:49:39][I][BleGattClient.h:46] send(): Connected to the BLE Server.
[18:49:39]D NimBLERemoteCharacteristic: ">> writeValue(), length: 1"
[18:49:39]I NimBLERemoteCharacteristic: "Write complete; status=0 conn_handle=0"
[18:49:39]D NimBLEClient: "Got Client event "
[18:49:39]D NimBLEClient: "Notify Recieved for handle: 33"
[18:49:39]D NimBLERemoteCharacteristic: "<< writeValue, rc: 0"
[18:49:39][D][BleGattClient.cpD NimBLEClp:241] loop()ient: "che: Command sencking servt in 64 ms
[18:49:39]ice 44092840-0567-11e6-b862-0002a5d5c51b for handle: 33"
[18:49:39]D NimBLEClient: "Got Notification for characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
[18:49:39]Descriptor: uuid: 0x2902, handle: 34"
[18:49:39]D NimBLEClient: "Invoking callback for notification on characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
[18:49:39]Descriptor: uuid: 0x2902, handle: 34"
[18:49:39][I][BleGattClient.h:269] notifyCB(): Indication from e8:c5:06:04:66:ed : Service = 44092840-0567-11e6-b862-0002a5d5c51b, Characteristic = 44092842-0567-11e6-b862-0002a5d5c51b, len=1, Value=<> (252)
[18:49:39][V][BleGattClient.h:271] notifyCB(): Client data received len: 1
[18:49:39]
[18:49:39][V][BleGattClient.h:275] notifyCB(): Response byte[0]: 252 (0xFC)
[18:50:28][D][main.cpp:472] parse_command(): 61036 Start Parsing power on
[18:50:28][D][lukeroberts.h:152] set_dimmer(): Brightness: 1 0
[18:50:28][D][BleGattClient.cpp:213] loop(): trying to connect
[18:50:28][I][BleGattClient.cpp:215] loop(): Connected to the BLE Server.
[18:50:28][D][BleGattClient.h:37] send(): BLE GATT SEND
[18:50:28][I][BleGattClient.h:46] send(): Connected to the BLE Server.
[18:50:28]D NimBLERemoteCharacteristic: ">> writeValue(), length: 4"
[18:50:28]I NimBLERemoteCharacteristic: "Write complete; status=0 conn_handle=0"
[18:50:28]D NimBLEClient: "Got Client event "
[18:50:28]D NimBLEClient: "Notify Recieved for handle: 33"
[18:50:28]D NimBLERemoteCharacteristic: "<< writeValue, rc: 0"
[18:50:28][D][BleGattClientD NimBLECli.h:37] send(ent: "check): BLE GATT ing serviceSEND
[18:50:28][I][Bl 44092840-0eGattClient.567-11e6-b8h:46] send()62-0002a5d5: Connected c51b for hato the BLE Sendle:rver.
[18:50:28] 33"
[18:50:28]D NimBLERemoteCharacteristic: ">> writeValue(), length: 4"
[18:50:28]D NimBLEClient: "Got Notification for characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
[18:50:28]Descriptor: uuid: 0x2902, handle: 34"
[18:50:28]D NimBLEClient: "Invoking callback for notification on characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
[18:50:28]Descriptor: uuid: 0x2902, handle: 34"
[18:50:28][I][BleGattClient.h:269] notifyCB(): Indication from e8:c5:06:04:66:ed : Service = 44092840-0567-11e6-b862-0002a5d5c51b, Characteristic = 44092842-0567-11e6-b862-0002a5d5c51b, len=1, Value=<> (252)
[18:50:28][V][BleGattClient.h:271] notifyCB(): Client data received len: 1
[18:50:28]
[18:50:28][V][BleGattClient.h:275] notifyCB(): Response byte[0]: 252 (0xFC)
[18:50:28]I NimBLERemoteCharacteristic: "Write complete; status=0 conn_handle=0"
[18:50:28]D NimBLERemoteCharacteristic: "<< writeValue, rc: 0"
[18:50:28][D][BleGattClient.h:37] send(): BLE GATT SEND
[18:50:28][I][BleGattClient.h:46] send(): Connected to the BLE Server.
[18:50:28]D NimBLERemoteCharacteristic: ">> writeValue(), length: 1"
[18:50:28]I NimBLERemoteCharacteristic: "Write complete; status=0 conn_handle=0"
[18:50:28]D NimBLEClient: "Got Client event "
[18:50:28]D NimBLEClient: "Notify Recieved for handle: 33"
[18:50:28]D NimBLEClient: "checking service 44092840-0567-11e6-b862-0002a5d5c51b for handle: 33"
[18:50:28]D NimBLERemoteCharacteristic: "<< writeValue, rc: 0"
[18:50:28]D NimBLEClient: "Got Notification for characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
[18:50:28]Descriptor: uuid: 0x2902, handle: 34"
[18:50:28]D NimBLEClient: "Invoking callback for notification on characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
[18:50:28]Descriptor: uuid: 0x2902, handle: 34"
[18:50:28][I][BleGattClient.h:269] notifyCB(): Indication from e8:c5:06:04:66:ed : Service = 44092840-0567-11e6-b862-0002a5d5c51b, Characteristic = 44092842-0567-11e6-b862-0002a5d5c51b, len=1, Value=<> (252)
[18:50:28][V][BleGattClient.h:271] notifyCB(): Client data received len: 1
[18:50:28]
[18:50:28][V][BleGattC[D][BleGt.h:275] notafyCli): .csponse byte[p]:2452 loxFC)
[18:50:28]p(): Command sent in 313 ms
[18:50:30][D][main.cpp:472] parse_command(): 62669 Start Parsing power off
[18:50:30][D][BleGattClient.cpp:213] loop(): trying to connect
[18:50:30][I][BleGattClient.cpp:215] loop(): Connected to the BLE Server.
[18:50:30][D][BleGattClient.h:37] send(): BLE GATT SEND
[18:50:30][I][BleGattClient.h:46] send(): Connected to the BLE Server.
[18:50:30]D NimBLERemoteCharacteristic: ">> writeValue(), length: 4"
[18:50:30]I NimBLERemoteCharacteristic: "Write complete; status=0 conn_handle=0"
[18:50:30]D NimBLEClient: "Got Client event "
[18:50:30]D NimBLERemoteCharacteristic: "<< writeValue, rc: 0"
[18:50:30]D NimBLEClient: "Notify Recieved for handle: 33"
[18:50:30]D NimBLEClient: "checking service 44092840-0567-11e6-b862-0002a5d5c51b for handle: 33"
[18:50:30]D NimBLEClient: "Got Notification for characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
[18:50:30]Descriptor: uuid: 0x2902, handle: 34"
[18:50:30]D NimBLEClient: "Invoking callback for notification on characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
[18:50:30]Descriptor: uuid: 0x2902, handle: 34"
[18:50:30][I][BleGattClient.h:269] notifyCB(): Indication from e8:c5:06:04:66:ed : Service = 44092840-0567-11e6-b862-0002a5d5c51b, Characteristic = 44092842-0567-11e6-b862-0002a5d5c51b, len=1, Value=<> (252)
[18:50:30][V][BleGattClient.h:271] notifyCB(): Client data received len: 1
[18:50:30]
[18:50:30][V][BleGa[ttClleGaient.h:275]tnCtienCB(:3 Response b7t s0]:():2 (0xFC)
[18:50:30]LE GATT SEND
[18:50:30][I][BleGattClient.h:46] send(): Connected to the BLE Server.
[18:50:30]D NimBLERemoteCharacteristic: ">> writeValue(), length: 1"
[18:50:30]I NimBLERemoteCharacteristic: "Write complete; status=0 conn_handle=0"
[18:50:30]D NimBLEClient: "Got Client event "
[18:50:30]D NimBLEClient: "Notify Recieved for handle: 33"
[18:50:30]D NimBLERemoteCharacteristic: "<< writeValue, rc: 0"
[18:50:30]D NimBLEClient: "checking service 44092840-0567-11e6-b862-0002a5d5c51b for handle: 33"
[18:50:30]D NimBLEClient: "Got Notification for characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
[18:50:30]Descriptor: uuid: 0x2902, handle: 34"
[18:50:30]D NimBLEClient: "Invoking callback for notification on characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
[18:50:30]Descriptor: uuid: 0x2902, handle: 34"
[18:50:30][I][BleGattClient.h:269] notifyCB(): Indication from e8:c5:06:04:66:ed : Service = 44092840-0567-11e6-b862-0002a5d5c51b, Characteristic = 44092842-0567-11e6-b862-0002a5d5c51b, len=1, Value=<> (252)
[18:50:30][V][BleGattClient.h:271] notifyCB(): Client data received len: 1
[18:50:30]
[18:50:30][V][BleGattCl[D]t.heGa5] notifyCB():Cliesp.cpe byte[0]: 2p: 41xFCoop(): Command sent in 283 ms
[18:50:32][D][main.cpp:472] parse_command(): 64519 Start Parsing dimmer 35
[18:50:32][I][main.cpp:111] set_dimmer_value(): Set Dimmer Level to 35
[18:50:32][D][lukeroberts.h:152] set_dimmer(): Brightness: 1 35
[18:50:32][D][BleGattClient.cpp:213] loop(): trying to connect
[18:50:32][I][BleGattClient.cpp:215] loop(): Connected to the BLE Server.
[18:50:32][D][BleGattClient.h:37] send(): BLE GATT SEND
[18:50:32][I][BleGattClient.h:46] send(): Connected to the BLE Server.
[18:50:32]D NimBLERemoteCharacteristic: ">> writeValue(), length: 4"
[18:50:32]I NimBLERemoteCharacteristic: "Write complete; status=0 conn_handle=0"
[18:50:32]D NimBLEClient: "Got Client event "
[18:50:32]D NimBLEClient: "Notify Recieved for handle: 33"
[18:50:32]D NimBLEClient: "checking service 44092840-0567-11e6-b862-0002a5d5c51b for handle: 33"
[18:50:32]D NimBLERemoteCharacteristic: "<< writeValue, rc: 0"
[18:50:32]D NimBLEClient: "Got Notification for characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
[18:50:32]Descriptor: uuid: 0x2902, handle: 34"
[18:50:32]D NimBLEClient: "Invoking callback for notification on characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
[18:50:32]Descriptor: uuid: 0x2902, handle: 34"
[18:50:32][I][BleGattClient.h:269] notifyCB(): Indication from e8:c5:06:04:66:ed : Service = 44092840-0567-11e6-b862-0002a5d5c51b, Characteristic = 44092842-0567-11e6-b862-0002a5d5c51b, len=1, Value=<> (252)
[18:50:32][V][BleGattClient.h:271] notifyCB(): Client data received len: 1
[18:50:32]
[18:50:32][V][BleGattClient.[D]75] notifyC[():Gaespliee byte[0]: 252 ppxFC1] loop(): Command sent in 182 ms
[18:50:34][D][main.cpp:472] parse_command(): 66454 Start Parsing ct 333
[18:50:34][I][main.cpp:225] set_colortemperature_mired(): Set Color temperature to 333 mired
[18:50:34][I][lukeroberts.h:240] set_colortemperature_mired(): Color temperature to 333 from 0 (3003)
[18:50:34][D][BleGattClient.cpp:213] loop(): trying to connect
[18:50:34][I][BleGattClient.cpp:215] loop(): Connected to the BLE Server.
[18:50:34][D][BleGattClient.h:37] send(): BLE GATT SEND
[18:50:34][I][BleGattClient.h:46] send(): Connected to the BLE Server.
[18:50:34]D NimBLERemoteCharacteristic: ">> writeValue(), length: 5"
[18:50:34]I NimBLERemoteCharacteristic: "Write complete; status=0 conn_handle=0"
[18:50:34]D NimBLEClient: "Got Client event "
[18:50:34]D NimBLEClient: "Notify Recieved for handle: 33"
[18:50:34]D NimBLERemoteCharacteristic: "<< writeValue, rc: 0"
[18:50:34]D NimBLEClient: "checking service 44092840-0567-11e6-b862-0002a5d5c51b for handle: 33"
[18:50:34]D NimBLEClient: "Got Notification for characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
[18:50:34]Descriptor: uuid: 0x2902, handle: 34"
[18:50:34]D NimBLEClient: "Invoking callback for notification on characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
[18:50:34]Descriptor: uuid: 0x2902, handle: 34"
[18:50:34][I][BleGattClient.h:269] notifyCB(): Indication from e8:c5:06:04:66:ed : Service = 44092840-0567-11e6-b862-0002a5d5c51b, Characteristic = 44092842-0567-11e6-b862-0002a5d5c51b, len=1, Value=<> (252)
[18:50:34][V][BleGattClient.h:271] notifyCB(): Client data received len: 1
[18:50:34]
[18:50:34][V][BleGattC[Dent.h:275] notBlyCBttC Responsient.cpp:241] lo byte[0]: 252p(0xFCommand sent in 115 ms
[18:50:40]D NimBLEClient: "Got Client event "
[18:50:40]I NimBLEClient: "disconnect; reason=531, "
[18:50:40][I][BleGattClient.h:139] onDisconnect(): e8:c5:06:04:66:ed Disconnected
[18:50:40][D][BleGattClient.cpp:55] operator()(): BLE DISCONNECT

Der Log wird nur aktualisiert wenn ich am Webinterface die Schalflächen bediene.

Anbei der Log aus VSCode:

--- Available filters and text transformations: colorize, debug, default, direct, esp32_exception_decoder, hexlify, log2file, nocontrol, printable, send_on_enter, time
--- More details at http://bit.ly/pio-monitor-filters

Please build project in debug configuration to get more details about an exception.
See https://docs.platformio.org/page/projectconf/build_configurations.html


--- Miniterm on COM4 115200,8,N,1 ---
--- Quit: Ctrl+C | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
[D][lukeroberts.h:435] request_all_scenes(): Got 1 scenes
[D][lukeroberts.h:453] get_all_scenes(): Scene 0 name=OFF
D NimBLERemoteService: ">> getCharacteristic: uuid: 44092844-0567-11e6-b862-0002a5d5c51b"
D NimBLERemoteService: ">> retrieveCharacteristics() for service: 44092840-0567-11e6-b862-0002a5d5c51b"
D NimBLERemoteService: "Characteristic Discovered >> status: 0 handle: 42"
D NimBLERemoteCharacteristic: ">> NimBLERemoteCharacteristic()"
D NimBLERemoteCharacteristic: "<< NimBLERemoteCharacteristic(): 44092844-0567-11e6-b862-0002a5d5c51b"
D NimBLERemoteService: "Characteristic Discovered >> status: 14 handle: -1"
D NimBLERemoteService: "<< Characteristic Discovered"
D NimBLERemoteService: "<< retrieveCharacteristics()"
D NimBLERemoteCharacteristic: ">> readValue(): uuid: 44092844-0567-11e6-b862-0002a5d5c51b, handle: 42 0x2a"
I NimBLERemoteCharacteristic: "Read complete; status=0 conn_handle=0"
D NimBLERemoteCharacteristic: "Got 1 bytes"
I NimBLERemoteCharacteristic: "Read complete; status=14 conn_handle=0"
D NimBLERemoteCharacteristic: "<< readValue length: 1 rc=0"
[I][lukeroberts.h:464] get_current_scene(): Current Scene: 0

[D][main.cpp:737] setup(): Inital State: Power = 0 scene 0
[I][app_utils.cpp:89] setupOta(): - Ready for OTA
[I][ArduinoOTA.cpp:141] begin(): OTA server at: lrcontroller.local.local:3232
[D][BleGattClient.cpp:213] loop(): trying to connect
[I][BleGattClient.cpp:215] loop(): Connected to the BLE Server.
[D][BleGattClient.h:37] send(): BLE GATT SEND
[I][BleGattClient.h:46] send(): Connected to the BLE Server.
D NimBLERemoteCharacteristic: ">> writeValue(), length: 1"
I NimBLERemoteCharacteristic: "Write complete; status=0 conn_handle=0"
D NimBLEClient: "Got Client event "
D NimBLEClient: "Notify Recieved for handle: 33"
D NimBLERemoteCharacteristic: "<< writeValue, rc: 0"
D [D][BleGattCliNient.cpp:241] loop(): mBLEClient:Command sent "checking in 83 ms
service 44092840-0567-11e6-b862-0002a5d5c51b for handle: 33"
D NimBLEClient: "Got Notification for characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
Descriptor: uuid: 0x2902, handle: 34"
D NimBLEClient: "Invoking callback for notification on characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
Descriptor: uuid: 0x2902, handle: 34"
[I][BleGattClient.h:269] notifyCB(): Indication from e8:c5:06:04:66:ed : Service = 44092840-0567-11e6-b862-0002a5d5c51b, Characteristic = 44092842-0567-11e6-b862-0002a5d5c51b, len=1, Value=<�> (252)
[V][BleGattClient.h:271] notifyCB(): Client data received len: 1

[V][BleGattClient.h:275] notifyCB(): Response byte[0]: 252 (0xFC)
[D][main.cpp:472] parse_command(): 20442 Start Parsing power on
[D][lukeroberts.h:152] set_dimmer(): Brightness: 1 0
[D][BleGattClient.cpp:213] loop(): trying to connect
[I][BleGattClient.cpp:215] loop(): Connected to the BLE Server.
[D][BleGattClient.h:37] send(): BLE GATT SEND
[I][BleGattClient.h:46] send(): Connected to the BLE Server.
D NimBLERemoteCharacteristic: ">> writeValue(), length: 4"
I NimBLERemoteCharacteristic: "Write complete; status=0 conn_handle=0"
D NimBLEClient: "Got Client event "
D NimBLERemoteCharacteristic: "<< writeValue, rc: 0"
D Ni[D][BleGattCmBLEClientlient.h:37] s: "Notify end(): BLE GARecieved foTT SEND
[I]r handle: 3[BleGattClie3"
nt.h:46] send(): CoD NimBLEClinnected to tent: "checkhe BLE Serveing servicer.
44092840-0567-11e6-b862-0002a5d5c51b for handle: 33"
D NimBLEClient: "Got Notification for characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
Descriptor: uuid: 0x2902, handle: 34"
D NimBLERemoteCharacteristic: ">> writeValue(), length: 4"
D NimBLEClient: "Invoking callback for notification on characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
Descriptor: uuid: 0x2902, handle: 34"
[I][BleGattClient.h:269] notifyCB(): Indication from e8:c5:06:04:66:ed : Service = 44092840-0567-11e6-b862-0002a5d5c51b, Characteristic = 44092842-0567-11e6-b862-0002a5d5c51b, len=1, Value=<�> (252)
[V][BleGattClient.h:271] notifyCB(): Client data received len: 1

[V][BleGattClient.h:275] notifyCB(): Response byte[0]: 252 (0xFC)
I NimBLERemoteCharacteristic: "Write complete; status=0 conn_handle=0"
D NimBLERemoteCharacteristic: "<< writeValue, rc: 0"
[D][BleGattClient.h:37] send(): BLE GATT SEND
[I][BleGattClient.h:46] send(): Connected to the BLE Server.
D NimBLERemoteCharacteristic: ">> writeValue(), length: 1"
I NimBLERemoteCharacteristic: "Write complete; status=0 conn_handle=0"
D NimBLEClient: "Got Client event "
D NimBLEClient: "Notify Recieved for handle: 33"
D NimBLEClient: "checking service 44092840-0567-11e6-b862-0002a5d5c51b for handle: 33"
D NimBLERemoteCharacteristic: "<< writeValue, rc: 0"
D NimBLEClient: "Got Notification for characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
Descriptor: uuid: 0x2902, handle: 34"
D NimBLEClient: "Invoking callback for notification on characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
Descriptor: uuid: 0x2902, handle: 34"
[I][BleGattClient.h:269] notifyCB(): Indication from e8:c5:06:04:66:ed : Service = 44092840-0567-11e6-b862-0002a5d5c51b, Characteristic = 44092842-0567-11e6-b862-0002a5d5c51b, len=1, Value=<�> (252)
[V][BleGattClient.h:271] notifyCB(): Client data received len: 1

[V][Ble[D][BGettCtCent.h:275] nltint.B():2Response byt4[]0lo 25):(0xFC)
Command sent in 333 ms
[D][main.cpp:472] parse_command(): 24820 Start Parsing dimmer 61
[I][main.cpp:111] set_dimmer_value(): Set Dimmer Level to 61
[D][lukeroberts.h:152] set_dimmer(): Brightness: 1 61
[D][BleGattClient.cpp:213] loop(): trying to connect
[I][BleGattClient.cpp:215] loop(): Connected to the BLE Server.
[D][BleGattClient.h:37] send(): BLE GATT SEND
[I][BleGattClient.h:46] send(): Connected to the BLE Server.
D NimBLERemoteCharacteristic: ">> writeValue(), length: 4"
I NimBLERemoteCharacteristic: "Write complete; status=0 conn_handle=0"
D NimBLERemoteCharacteristic: "<< writeValue, rc: 0"
D NimBLEClient: "Got Client event "
D NimBLEClient: "Notify Recieved for handle: 33"
D NimBLEClient: "checking service 44092840-0567-11e6-b862-0002a5d5c51b for handle: 33"
D NimBLEClient: "Got Notification for characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
Descriptor: uuid: 0x2902, handle: 34"
D NimBLEClient: "Invoking callback for notification on characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
Descriptor: uuid: 0x2902, handle: 34"
[I][BleGattClient.h:269] notifyCB(): Indication from e8:c5:06:04:66:ed : Service = 44092840-0567-11e6-b862-0002a5d5c51b, Characteristic = 44092842-0567-11e6-b862-0002a5d5c51b, len=1, Value=<�> (252)
[V][BleGattClient.h:271] notifyCB(): Client data received len: 1

[V][BleGattCl[Dnt.h:275] not[ByeG():Clesponse byte[0]:.252:24xFC)
1] loop(): Command sent in 143 ms
[D][main.cpp:472] parse_command(): 27154 Start Parsing ct 297
[I][main.cpp:225] set_colortemperature_mired(): Set Color temperature to 297 mired
[I][lukeroberts.h:240] set_colortemperature_mired(): Color temperature to 297 from 0 (3367)
[D][BleGattClient.cpp:213] loop(): trying to connect
[I][BleGattClient.cpp:215] loop(): Connected to the BLE Server.
[D][BleGattClient.h:37] send(): BLE GATT SEND
[I][BleGattClient.h:46] send(): Connected to the BLE Server.
D NimBLERemoteCharacteristic: ">> writeValue(), length: 5"
I NimBLERemoteCharacteristic: "Write complete; status=0 conn_handle=0"
D NimBLEClient: "Got Client event "
D NimBLEClient: "Notify Recieved for handle: 33"
D NimBLEClient: "checking service 44092840-0567-11e6-b862-0002a5d5c51b for handle: 33"
D NimBLERemoteCharacteristic: "<< writeValue, rc: 0"
D NimBLEClient: "Got Notification for characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
Descriptor: uuid: 0x2902, handle: 34"
D NimBLEClient: "Invoking callback for notification on characteristic Characteristic: uuid: 44092842-0567-11e6-b862-0002a5d5c51b, handle: 33 0x0021, props: 0x28
Descriptor: uuid: 0x2902, handle: 34"
[I][BleGattClient.h:269] notifyCB(): Indication from e8:c5:06:04:66:ed : Service = 44092840-0567-11e6-b862-0002a5d5c51b, Characteristic = 44092842-0567-11e6-b862-0002a5d5c51b, len=1, Value=<�> (252)
[V][BleGattClient.h:271] notifyCB(): Client data received len: 1

[V][BleGattCl[D][Bleient.h:275] nttiliCB(.c Response bpte[41] 25op(0xFC)
(): Command sent in 129 ms
D NimBLEClient: "Got Client event "
I NimBLEClient: "disconnect; reason=531, "
[I][BleGattClient.h:139] onDisconnect(): e8:c5:06:04:66:ed Disconnected
[D][BleGattClient.cpp:55] operator()(): BLE DISCONNECT

Der GPIO 39 wird im Log nicht dedektiert wenn ich den Button drücke!

[Gast]

Die BLE Verbindung steht schon mal und dimmen scheint auch zu funktionieren - richtig?
Den SINGLE_BUTTON Teil musss ich morgen mal testen . Deine Config sieht ok aus

[nightfly2000]

Ja das ist ja das Problem, das sich per Webinterface die Lampe nicht steuern lässt. Also egal welchen Regler ich bediene nichts passiert!
Sollte unter dem Dropdownmenu etwas angezeigt werden?
LG.

[Gast]

ok dann vergessen wir mal den Button - könnte sein das PIN 39 nicht funktioniert.
Im Code setze ich das flag INPUT_PULLUP und das geht nur bei den PINs < 34

Zu BLE selbst:
Die logs sind seltsam - es wird zwar einen Verbindung aufgebaut und es findet anscheinend eine Kommunikation statt aber wohl nur teilweise.
Security hast du für die Lampe nicht gesetzt, oder?

Nimm doch bitte die BLE Addresse noch mal raus und lass einen scan machen

Im Log solltest du dann soetwas sehen

I NimBLEScan: "New advertiser: 00:a0:50:a4:35:8c"
I NimBLEScan: "New advertiser: 08:46:af:d8:1d:fd"
D NimBLEUUID: "Comparing UUIDs; type 128 to 16; UUID 44092840-0567-11e6-b862-0002a5d5c51b to 0xfd6f"
I NimBLEScan: "Updated advertiser: 00:a0:50:a4:35:8c"
D NimBLEUUID: "Comparing UUIDs; type 128 to 128; UUID 44092840-0567-11e6-b862-0002a5d5c51b to 00035b03-58e6-07dd-021a-08123a000300"
I NimBLEScan: "New advertiser: 1d:8f:7d:19:61:e5"
I NimBLEScan: "New advertiser: 6c:98:e2:9a:28:6b"
I NimBLEScan: "Updated advertiser: 6c:98:e2:9a:28:6b"
D NimBLEUUID: "Comparing UUIDs; type 128 to 16; UUID 44092840-0567-11e6-b862-0002a5d5c51b to 0xfe9f"
I NimBLEScan: "New advertiser: 28:8b:04:1e:d4:04"
I NimBLEScan: "New advertiser: f8:77:b8:97:3c:15"
I NimBLEScan: "New advertiser: d4:c2:5a:79:49:c4"
I NimBLEScan: "New advertiser: c4:b9:69:fe:14:b6"
I NimBLEScan: "Updated advertiser: c4:b9:69:fe:14:b6"
D NimBLEUUID: "Comparing UUIDs; type 128 to 128; UUID 44092840-0567-11e6-b862-0002a5d5c51b to 44092840-0567-11e6-b862-0002a5d5c51b"
[I][BleGattClient.cpp:296] onResult(): Advertised Device found:
[B][I][BleGattClient.cpp:298] onResult(): Found Our Service
[I][BleGattClient.cpp:301] onResult(): Device found Name: , Address: c4:b9:69:fe:14:b6, serviceUUID: 44092840-0567-11e6-b862-0002a5d5c51b[/B]
D NimBLEScan: "<< stop([I][BleGattClient.cpp:331] scan(): Scan complete
[I][main.cpp:713] setup(): DEVICE : c4:b9:69:fe:14:b6
..
[I][BleGattClient.cpp:92] connect_to_server(): Connected to: c4:b9:69:fe:14:b6
[B][I][BleGattClient.cpp:93] connect_to_server(): RSSI: -88[/B]
D NimBLEScan: ">> stop()"

[nightfly2000]

Ok Fehler war, das in der App die Security eingeschaltet war!!! Jetzt lässt sie sich per Webinterface steuern und im Dropdown sind auch die Szenen ersichtlich!
Danke nochmal für die Hilfe!!!! LG.

[Gast]

Super
Wenn du willst kannst du noch den Code aus dem Dev Tree ausprobieren - https://github.com/martgras/LukeRobertsControl/tree/dev bzw https://github.com/martgras/LukeRobe.../heads/dev.zip.

Vielleicht geht damit GPIO 39 für den Button - ich habe gerade eine kleine Änderung hochgeladen.

[loxforum]

Gast Danke für das Projekt, funktioniert auf dem ESP32 von AZDelivery ganz gut, einzig scheint sich irgendwann die BLE Verbindung zu verabschieden, muss aber dazusagen das ich den uC mit HTTP Requests bombardiere (habe 10s Repeat für mehrere Befehle eingestellt).

Daher meine Frage: Wie bindet ihr die LR Lampe in die Loxone Config ein? Per Szenen oder per Dimmer und Lichtfarbe? Power nur über BLE oder per Relais? Die Kombination aus mehreren Virtuellen Ausgängen scheint nicht zuverlässig zu funktionieren.

[Gast]

Moin zusammen, ich bin leider nicht aus der Knx Welt, Altbau, vielleicht wird das ja irgendwann mal was

Ich arbeite im Moment mit Home Assistant, habe ebenfalls eine Luke Roberts, nun da gibt es einzig für die Homey von Athom eine App die auch funktioniert, ich will aber die Homey in Rente schicken, für Home Assistant gibt es keine Integration, ich frage mich wie ich den Code idealerweise auf Esphome bekomme.

Ich würde den Esp dann als Bridge einsetzen, ich will nur per Hue Bewegungsmelder die Lampe auf Scene X setzen wollen. Da würde dann home Assistant ins Spiel kommen um die Verbindung mit den Bewegungsmelder zu bekommen. Hätte da jemand eine Idee wie ich das anstellen kann?

Danke im Voraus.

[loxforum]

Dafür ist der ESP sicher nicht schlecht. Damit kannst du per HTTP Request oder MQTT die Szenen einstellen.