The Zoney device almost certainly isn’t any replacement for the Bridge. It does show the Bridge setup, but that’s because it’s copied from the Bridge. I can clearly see in the code that it loads the same animations as the Bridge setup normally does.
And there’s a reason why they did that. All of the ESP32-based devices (Bridge and Energy Dongle) use the same OTA server (ota.homeybridge.net) and the same broker.homeybridge.net server for communicating with Homey Cloud and checking if it’s a genuine device (see this post). These are parts of the strings in the Homey Energy Dongle firmware file obtained from usb.homey.app:
0123456789abcdef E (%lu) %s: Failed to get peer name: %d (%d)
X-Homey-Bridge-Host Broker E (%lu) %s: Incoming host name is too long: %s
X-Homey-Bridge-Port X-Homey-Bridge-TLS X-Homey-ID E (%lu) %s: Incoming homey id is too long: %s
I (%lu) %s: HTTP_EVENT_ERROR
I (%lu) %s: HTTP_EVENT_ON_CONNECTED
I (%lu) %s: HTTP_EVENT_HEADER_SENT
I (%lu) %s: HTTP_EVENT_ON_DATA, len=%d
I (%lu) %s: HTTP_EVENT_ON_FINISH
I (%lu) %s: HTTP_EVENT_DISCONNECTED
https://broker.homeybridge.net/v1/info I (%lu) %s: Request to %s
E (%lu) %s: Failed to initialise HTTP client
GetInfo E (%lu) %s: %s(%d): Failed to set header X-Homey-Bridge-Build: 0x%04x
E (%lu) %s: %s(%d): Failed to set header X-Homey-Bridge-Serial: 0x%04x
E (%lu) %s: %s(%d): esp_http_client_open failed: 0x%04x
I (%lu) %s: HTTP GET Status = %d
InitInput GPIO E (%lu) %s: %s(%d): gpio_config failed: 0x%04x
E (%lu) %s: %s(%d): gpio_isr_handler_add failed: 0x%04x
Internal error %02x:%02x:%02x:%02x:%02x:%02x commands restart get_mac get_serial_hash get_version minimum_free largest_free_block Batch fusing not enabled Failed to disable JTAG Failed to disable ROM printing Failed to commit fuses I (%lu) %s: Assigning MAC: %s
%2hhx:%2hhx:%2hhx:%2hhx:%2hhx:%2hhx Invalid or missing MAC address Invalid MAC address E (%lu) %s: Failed to generate serial: 0x%04x
random_part E (%lu) %s: Failed to begin batch: 0x%04x
Missing hex or color Invalid hex Invalid hex length %02hhx%02hhx%02hhx Invalid hex format enabled Invalid or missing 'enabled' field get_serial dump_ram_log logging fuse_begin_batch generate_serial assign_mac commit_fuses_and_lock set_led erase_homey_cache get_free_memory HyEnergyDongle E (%lu) %s: %s(%d): Failed to initialize DSMR
E (%lu) %s: %s(%d): Failed to register EnergyDongle commands
E (%lu) %s: %s(%d): Failed to register EnergyDongle factory commands
E (%lu) %s: %s(%d): Failed to initialize EnergyDongle WS
I (%lu) %s: Got Homey information from cache:
I (%lu) %s: - Host: %s
I (%lu) %s: - Port: %d
I (%lu) %s: - Homey id: %s
I (%lu) %s: - TLS: %d
I (%lu) %s: Broker failed to get Homey information: 0x%04x
E (%lu) %s: Invalid serial!
W (%lu) %s: Not linked to a Homey
I (%lu) %s: Got Homey information from broker:
I (%lu) %s: - Host: %s (old: %s)
I (%lu) %s: - Port: %d (old: %d)
I (%lu) %s: - Homey id: %s (old: %s)
I (%lu) %s: - TLS: %d (old: %d)
W (%lu) %s: Failed to cache Homey information: 0x%04x
I (%lu) %s: Retrying state %s in %lu seconds
I (%lu) %s: Connect backoff: %lus
I (%lu) %s: Connected to Homey after %lu attempts
I (%lu) %s: Failed to connect to Homey (attempt: %lu)
E (%lu) %s: Failed to connect to WiFi: 0x%04x
E (%lu) %s: Transport failed: 0x%04x
E (%lu) %s: Ping watchdog triggered
W (%lu) %s: Failed to close transport: 0x%04x
E (%lu) %s: In stopped state
I (%lu) %s: Boot ID: %08lx
E (%lu) %s: Unexpected event bits: %lu
I (%lu) %s: State change: %s -> %s
E (%lu) %s: State failed: %s, error: 0x%04x
X-Homey-Bridge-Build sOnHttpClientInit E (%lu) %s: %s(%d): Failed to set header X-Homey-Build: 0x%04x
X-Homey-Bridge-Version E (%lu) %s: %s(%d): Failed to set header X-Homey-Bridge-Version: 0x%04x
X-Homey-Bridge-Serial E (%lu) %s: %s(%d): Failed to set header X-Homey-Serial: 0x%04x
I (%lu) %s: HTTP_EVENT_ON_HEADER, key=%s, value=%s
X-Homey-Bridge-Force-Update X-Homey-Bridge-Update-Available E (%lu) %s: Failed to start OTA Task
E (%lu) %s: Failed to get OTA state: 0x%04x
E (%lu) %s: Failed to boot after OTA: 0x%04x
I (%lu) %s: Boot success after OTA
E (%lu) %s: Failed to abort OTA process: 0x%04x
Begin https://ota.homeybridge.net/v2 I (%lu) %s: Request: %s
I (%lu) %s: No new firmware found
You see it uses homeybridge.net, which the Bridge also uses. The Zoney likely also works the same way, so that’s why they copied the Homey Bridge setup (for testing). I couldn’t find anything else about the Zoney in the mobile app except for the Bluetooth advertisement it expeects (which is how I got the mobile app to show the setup wizard, by cloning and advertising it from another device) and the setup process. I think it was some kind of internal test by Athom that was accidentally left in the production builds of the app.
