Closed phalox closed 1 year ago
@phalox Hi,
Great, that seems to have solved it!
What would be your recommended development process? When playing around with different settings, adding & removing sensors etc, this seems a little tedious. I also found it challenging to debug zigbee issues. Often it's a matter of reflashing/repowering, but I'd love some more visibility.
Unfortunately, Z2M is not friendly for DIY :). I use the same procedure while testing/
Referring to a closed issue #178
I seem to be experiencing the same issue:
I've deleted the device in Z2M, and restarted Z2M. None of it seems to fix the problem. When I make changes to the firmware (e.g. add an input), they do show up in Z2M.
I've also let it validate that the hex file is correct, and that seems to be the case:
I bumped into one more thing.... When exporting the converter and opening the file, I still see the old name (ptvo.switch).
Could it be that this is part of the issue?
Also, using the custom converter in Z2M, I think it's still not triggered because of the lack of another modelID
Originally posted by @phalox in https://github.com/ptvoinfo/zigbee-configurable-firmware/issues/178#issuecomment-1703841926