My Deye Station (inverter S/N 2410096799, single-phase hybrid, 4.32 kWp) reports solar production, battery SoC, charge power, consumption and grid power correctly in Homey. However, measure_ac_temperature and measure_battery_temperature always show as null.
I’ve verified in DeyeCloud (deyecloud.com) that the inverter reports these values normally: AC Temperature 32.3°C, DC Temperature 39.8°C, Battery Temperature 22.0°C.
This suggests the Homey app isn’t reading/mapping the correct registers for this inverter model, rather than a hardware or connection issue.
Is this a known limitation, or could the register mapping be fixed?
Thanks for the detailed report — that’s genuinely useful.
Quick check first: AC Temperature maps to an “advanced” capability that’s hidden by default at pairing (you need to check “Advanced” during the pairing wizard to get it). If you didn’t check that box, it simply wasn’t added as a capability — not a bug, just opt-in. You can confirm this by re-pairing with Advanced checked.
Battery Temperature is different — it’s not gated behind Advanced, and it lives on the same Battery device as SoC and charge power (which you say work fine), so I can’t explain it from the code alone. It’s possible your specific hybrid model (single-phase, 4.32 kWp) uses a different register for battery temperature than the one we’ve validated so far.
Could you run a diagnostic scan against your logger and paste the output here (or send it privately)? It reads all registers directly and shows raw + decoded values, which will tell me exactly what’s being received at the register we’re using for Battery Temperature (and confirm whether AC Temperature is really just the advanced-setting issue):
Ran the diagnostic scan against my logger (192.168.3.230). Auto-detect correctly identified the model as deye_hybrid (score=61).
Both temperatures are present and read correctly at the register level: AC Temperature 31C at register 91, DC Temperature 38C at register 90, and Battery Temperature 22C at register 182. These match what I see in DeyeCloud, so it looks like both are just the Advanced-capability opt-in issue at pairing rather than a register mismatch for my model.
One question on that: when I try “Repair device” on the existing Deye Station in Homey, it only re-authenticates against DeyeCloud and doesn’t show an Advanced-capability option anywhere in that flow. Is Advanced only available during a fresh “Add device” pairing, or is there a settings toggle on the device itself I should look for instead?
You might want to remove the serial number from your post. Depending on how well Deye Cloud is secured, it might allow others to access your device remotely.
Confirmed the cause: “Advanced” is currently only offered during the initial “Add device” pairing — there’s no way to turn it on afterwards for an already-paired device. Since you didn’t check it the first time, AC Temperature (and the other advanced sensors) were never added.
Two options:
Remove and re-pair now, checking “Advanced” this time. Everything else (production, SoC, etc.) comes back the same way — quick round-trip, works today.
Try the test build: Deye Inverter (Local) | Homey — I’ve added an “Add advanced sensors” checkbox to the Repair flow, so you shouldn’t have to remove the device at all: install the test version, open Repair on the existing device, check it, save. Note: my own test inverter is a string model, not hybrid like yours, so I haven’t been able to verify this end-to-end on a hybrid + Grid Meter setup. If it doesn’t pick up the new sensors, fall back to option 1 (remove and re-pair) — that path is unaffected either way.
On Battery Temperature specifically: that one isn’t gated behind Advanced at all, so if it’s still missing after either option above (on the separate Battery device, not Inverter), let me know and we’ll dig further — but I suspect it’ll just show up correctly once Advanced is on, alongside the rest.
Update: I removed the old device and re-paired from scratch, but I never saw an “Advanced” checkbox anywhere in the Add Device wizard. Instead the pairing created three separate devices automatically - inverter, battery, and solar panel - each with its own capabilities.
Good news either way: AC Temperature and Battery Temperature are both present and reading correctly now on the new inverter device, so whatever changed in the pairing flow, it resolved the issue on my end. Just flagging the missing checkbox in case it’s a UI regression worth a look.
The inverter is not found by scanning. With IP adress and serial number it is found.
However, the inverter type is not selectable. When 10k-sg04 is selected and choose ‘add’ it tells me that the devices is not found and can not be added. Unfortunately.
Thanks for the report! The SUN-15K-SG05LP3-EU-SM2 isn’t one of our currently defined models, so auto-detect correctly found nothing and — since it had to try every known model with no match — likely ran long enough to time out the pairing session, which is probably why “Add” failed right after you picked a model manually.
Could you help me confirm whether the SG05LP3 register layout is close enough to our existing “SG04LP3 Hybrid 3-phase” profile to reuse it? I don’t have this hardware to test against myself. There’s a small diagnostic script (no Homey app needed) that connects directly to your logger and dumps what each of our current models reads from it:
Enter your logger’s IP and serial number when prompted
It’ll save a .txt report to your Desktop — if you could paste that here (or attach the file), that tells me exactly which registers respond and with what values, so I can confirm compatibility (or build a dedicated profile) with actual data instead of guessing.
