I tried this out yesterday with an Eve Energy plug and everything worked as described and I can control the power state of the plug in HA. For some reason, the power monitoring is not being detected in HA though this might be a device problem because the Eve app shows zero watts usage even though there is a load on the plug.
This can take quite a while until the Eve Energy shows the real values in HA, for me it was two days!
1 Like
I read that the current Matter standards do NOT include energy monitoring features: If you read the description of the Eve Energy plugs carefully, it is only the Eve app that allows you to read energy monitoring data. Consequently, HA is currently not able to receive consumption data, if I’m right.
Can some expert confirm?
1 Like
Thats the way I read it - and as far as corroboration: Do Matter devices support smart energy management? - Stacey on IoT | Internet of Things news and analysis
1 Like
I re-flashed the SkyConnect firmware before, using https://skyconnect.home-assistant.io/firmware-update/.
Today I installed OpenThread border router, and it flashed my SC dongle.
After that, my zha won’t load, b/c of custom quirks. So I disabled quirks, rebooted and all, but it won’ t load.
So I flash the SC again using the FW update tool, but whatever I do, it ends after a few minutes with these errors.
Euh , help? I’ ve no spare dongle here…
2023-04-03 01:50:11 emscripten universal_silabs_flasher.flasher[42] INFO Probing ApplicationType.GECKO_BOOTLOADER
2023-04-03 01:50:11 emscripten universal_silabs_flasher.common[42] DEBUG Connection made: <webserial_transport.WebSerialTransport object at 0x1674c00>
2023-04-03 01:50:11 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'3'
2023-04-03 01:50:13 emscripten universal_silabs_flasher.flasher[42] INFO Probing ApplicationType.CPC
2023-04-03 01:50:13 emscripten universal_silabs_flasher.common[42] DEBUG Connection made: <webserial_transport.WebSerialTransport object at 0x1679e30>
2023-04-03 01:50:13 emscripten universal_silabs_flasher.cpc[42] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2023-04-03 01:50:13 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2023-04-03 01:50:14 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 1 of 4)
2023-04-03 01:50:14 emscripten universal_silabs_flasher.cpc[42] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2023-04-03 01:50:14 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2023-04-03 01:50:15 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 2 of 4)
2023-04-03 01:50:15 emscripten universal_silabs_flasher.cpc[42] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2023-04-03 01:50:15 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2023-04-03 01:50:16 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 3 of 4)
2023-04-03 01:50:16 emscripten universal_silabs_flasher.cpc[42] DEBUG Sending frame CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b'')))
2023-04-03 01:50:16 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'\x14\x00\n\x00\xc4U\xd3\x02\x00\x04\x00\x03\x00\x00\x00\xdb\x12'
2023-04-03 01:50:17 emscripten universal_silabs_flasher.cpc[42] DEBUG Failed to send CPCTransportFrame(endpoint=<EndpointId.SYSTEM: 0>, control=196, payload=UnnumberedFrame(command_id=<UnnumberedFrameCommandId.PROP_VALUE_GET: 2>, command_seq=0, payload=PropertyCommand(property_id=<PropertyId.SECONDARY_CPC_VERSION: 3>, value=b''))), trying again in 0.10s (attempt 4 of 4)
2023-04-03 01:50:17 emscripten universal_silabs_flasher.flasher[42] INFO Probing ApplicationType.EZSP
2023-04-03 01:50:17 emscripten bellows.ezsp[42] DEBUG Resetting EZSP
2023-04-03 01:50:17 emscripten bellows.uart[42] DEBUG Resetting ASH
2023-04-03 01:50:17 emscripten bellows.uart[42] DEBUG Sending: b'1ac038bc7e'
2023-04-03 01:50:22 emscripten bellows.uart[42] DEBUG Connection lost: None
2023-04-03 01:50:22 emscripten bellows.uart[42] DEBUG Closed serial connection
2 Likes
hello,
I have exactly the same problem, any developments?
Is the HA team working on getting USB/ip working properly in HAOS so we can use the sky connect from a separate device from the one the VM runs on?
I tried everything I found online… I took my loss, learned my lesson about experimental and beta stuff, and I ordered a €23,- Sonoff-zigbee-3.0-usb-dongle-plus-e.
Advantage: it works great with Zigbee2MQTT.
Oh, everything has to be paired as new devices again, there’s no migration from ZHA to Z2M (yet).
It’s really annoying, and expensive, about there is/seems to be no way to flash the stock firmware to the SkyConnect.
I bought it for the “Matter preparedness”, but I’ll now stick to zigbee.
What a bummer.
Were you able to get the Sonoff Dongle Plus E working with multiprotocol as well?
I can’t get the SkyConnect working with multiprotocol through a VM and it’s absolutely frustrating, and no one else seems to have the same requirements/issues. So looking for alternatives.
Really a bummer!
I don’t understand how they claim to have a working tool to reset the firmware (Home Assistant SkyConnect) but it doesn’t work!
We can only hope that some update will come out soon.
No I’m not gonna flash my Sonoff until I’m really sure it works.
Btw, just in case anyone needs to flash the SkyConnect back to EZSP.
Web flasher can be found here.
Ezsp firmware can be found here. I’m using 7.2.1, working fine with Z2M.
You’ll need to have CP210x drivers installed to flash the firmware.
Yes, I know. I tested everything in every way but could not restore the original firmware. Right now my SkyConnect is useless.
First of all - most people here are not native English speakers. Allow us some slack, and be glad you’re not asked to write another language flawlessly. I’d like to see you try Dutch. Second of all: even native English speakers are in agreement on this, so maybe you should take your argument here:
6 Likes
Is it possible to use the Sonoff Dongle as a Thread Router?
Not sure, also trying to find out.
I’m only aware that the newer ezsp chips by silicon labs are designed to support multiprotocol with a hardware packet router.
Not very sure about the technical details nor what is required to make it works besides the Multiprotocol add-on.
I would be fine with Thread only because I’m trying to switch everything smart home device for Thread and I need more coverage
It’s possible if you have the E variant of the sonoff zigbee 3.0 dongle which uses a silicon labs chip, very similar to the one in the skyconnect/yellow. But this is all still quite experimental so try this at your own risk. I’ve successfully used the firmware from there GitHub - ksjh/silabs-firmware-builder: Silicon Labs firmware builder with the multiprotocol addon to connect a handful of Zigbee and (homekit over) thread devices.
1 Like
Tasmota v12.5.0 now has Matter support for lights, relays and temperature sensors.
Tried it all again tonight on a Windows machine, I installed the driver(s), but unfortunately, same result;
SkyConnect looks good, with the driver installed. The flash tool sees it on Com8. But the flashing process ends into an error.
I used the stable firmware though, but I’m getting the feeling it is not firmware file related.
NabuCasa_SkyConnect_EZSP_v7.1.1.0_ncp-uart-hw_115200.gbl
flash log:
2023-04-18 22:27:19 emscripten universal_silabs_flasher.flasher[42] INFO Probing ApplicationType.GECKO_BOOTLOADER at 115200 baud
2023-04-18 22:27:19 emscripten universal_silabs_flasher.common[42] DEBUG Connection made: <webserial_transport.WebSerialTransport object at 0x13e5d28>
2023-04-18 22:27:19 emscripten universal_silabs_flasher.common[42] DEBUG Sending data b'3'
Yes this is the complete log.