Paulus Schoutsen
Paulus Schoutsen
Yes. https://github.com/zwave-js/zwave-js-server/blob/1595c0d76c1be6a5d73c747f2d99e078514d91bf/src/lib/forward.ts#L116-L126
A good start would be to expand our integration test to connect with different schema versions and compare output. We first would need to a add a mock node to...
The reason you see all your devices twice is because the sensor setup code adds data for all config entries instead of just the requested entry https://github.com/HandyHat/ha-hildebrandglow-dcc/blob/9d8bae14c718f5d2dd7f61e3f8c03d11206f393a/custom_components/hildebrandglow_dcc/sensor.py#L41
Above issues have been addressed. It now correctly raises if an unsupported chip is passed in (`chip == null`) and with #33 the latest UI issues has been fixed. Give...
Maybe the C3 stub is incorrect and so gets stuck once written to RAM https://github.com/espressif/esptool-js/blob/main/targets/esp32c3.js
As a workaround, you can close the port before passing it to ESPLoader. That's how we do it in ESP Web Tools: https://github.com/esphome/esp-web-tools/blob/9fee26fbab6b2a53ff82010c4e6b36dd74fee754/src/install-dialog.ts#L828-L830
Device pictures is on the road map for HA.
So the trick for migration is going to be evolving around entity registry. It does require that given a unique ID of a Z-Wave entity, we can generate the unique...
We can't, as not everyone wants to upgrade and we can't migrate by just adding an mqtt broker and setting up the ozwdaemon.
The old one hasn't received upgrades in a while and I don't see anyone picking it up. We will promote this one and hide the other one.