Ra72xx
Ra72xx
@Nerivec As the new 1.37 release finally offers the possibility to get herdsman logs easily, I captured a few minutes debug log during which I switched random lights on and...
I noticed that when starting with the ember driver, the Z2M container often fails with the following error at the first attempt, however works after the second (automatic) restart: ```...
> I think something is not going right during startup sequence. The send queue is way too high (117 in your first debug line, 211 by the end). Seems something...
I just did one more try with the new driver and rtscts disabled: ``` serial: port: /dev/ttyACM0 adapter: ember rtscts: false ``` Doesn't seem to help, first launch of Z2M...
As I want to switch from Zigbee2MQTT, I'll post a comment to keep this issue alive...
> device_automation_triggers = { > (SHORT_PRESS, BUTTON_1): {COMMAND: COMMAND_OFF, CLUSTER_ID: 6, ENDPOINT_ID: 10, ARGS: []}, > (SHORT_PRESS, BUTTON_2): {COMMAND: COMMAND_ON, CLUSTER_ID: 6, ENDPOINT_ID: 10, ARGS: []}, > (SHORT_PRESS, BUTTON_3): {COMMAND:...
For my better understanding (as I said, I don't use ZHA yet, but Zigbee2MQTT, but I got lots of this Busch Jäger Switches in my flat and the missing support...
Will you release a new version with the `persist=full` mode enabled? I tried out the current build and grabbing the devices, even if present when starting, results in `failed to...
Replying to myself: The failure to grab the input device was because "persistent-evdev" which I used previously to emulate the input devices not yet present when starting "evsieve" was still...