Hi,
I’ve updated the system to 3.70~45 to test the Shelly integration with my Shelly EM gen1 which is measuring the current from my PV inverter connected to Multiplus II Ac out.
The device is not detected, probably because it is not sending the expected mDNS name under _shelly._tcp.local. that the dbus-shelly service is expecting.
Capturing some traffic with tcpdump on the Cerbo GX shows what this Shelly is sending:
15:44:55.203771 IP 192.168.40.21.mdns > mdns.mcast.net.mdns: 0* [0q] 6/0/0 PTR _http._tcp.local., PTR shellyem-BCF(redacted)F4B._http._tcp.local., (Cache flush) SRV shellyem-BCF(redacted)F4B.local.:80 0 0, (Cache flush) TXT "id=shellyem-BCF(redacted)F4B" "arch=esp8266" "app=shellyem" "fw_version=1.0" "fw_id=20230913-114150/v1.14.0-gcb84623" "discoverable=false" "discoverable=false", (Cache flush) A 192.168.40.21, (Cache flush) NSEC (530)
Therefore I modified Fabian Lauer’s dbus-shelly-3em-smartmeter to adapt it to the EM. It is working great but there is a minor glitch in the new Cerbo remote console.
On VRM and the old console, the PV inverter is correctly shown on the output of the multiplus:
While on the new console the pvinverter is shown on the input:
But the information about the device is correctly indicating AC Out:
Best regards,
Raúl.