Deomid Ryabkov
Deomid Ryabkov
there's plenty of interest, for sure. i think best start is to use the ubuntu port, it requires no additional hardware. after that we can consider adding tests on real...
`make ShellyU` will build a binary that can be run on a Ubuntu linux system and represents a fully functioning device, except of course there are no real outputs. but...
in fact, i do most of my developemnt on the ShellyU port: ``` $ make ShellyU && rsync -av --exclude=*.gz fs_ShellyU/ build_ShellyU/fs/ && ASAN_SYMBOLIZER_PATH=$(realpath /usr/bin/llvm-symbolizer-*) LLVM_PROFILE_FILE=${PWD}/llvm.prof build_ShellyU/objs/*.elf --insecure --chroot build_ShellyU/fs...
hm. i guess we could se accessory name = service name if service is the only one in within the accessory
no, it's our thing, will do
done, will be in alpha2
had to back this one out due to DNS name conflicts, see description in https://github.com/mongoose-os-apps/shelly-homekit/commit/acb57e02caef82438a2c82da5c67265a8c76fda0
requires https://github.com/mongoose-os-libs/dns-sd/issues/5
they will still fight for the same name if there is a clash, resulting in confusion. the spec outlines what the behavior should be, it just needs to be implemented.