Starting a new thread as this was getting lost in the Hints, Tips & Troubleshooting thread.
Post details of your integration with Home Assistant etc.
was actually just looking at that so will be putting in that request alright
You'll find my discussion on the topic there if you look back - around Jan of this year.
Hi Folks. Shelly Em came and I'm wiring it up currently. Putting it in the attic with the solar installation. I have a socket up there. I am better off wiring the EM to a 3 pin plug and plugging it into the socket for its power? I'll then put the clamps on the AC from the inverters.
Does that sound like the best way of doing things?
Yes, that's the most compliant method, and pop it into a small electrical box. Shelly just needs one 3A fuse in the plug.
Great stuff. So it just needs the live and neutral from the 3 core cable. Not the earth.
Correct, no earth required.
You're a gent.
Found a cool little card that can be highly customizable for PV metrics:
Installed via HACS —> https://slipx06.github.io/sunsynk-power-flow-card/index.html#
I use the same one.
Great visualisation with this card - its just a matter of getting the right entitiy to display!
Sure hope your LV battery voltage is not 237v 🤣
I have a Solax system, and their battery packs run at ~120 v, and I have two packs wired in series. Hence the 240v
I'm having trouble getting HomeAssistant to talk to OpenDTU. Have mosquito installed, setup user account etc.
Has anyone got that going (openDTU with HA? via mosquito).
Have a look at mqtt explorer and connect to your mqtt broker (mosquito) and see if it's posting the data correctly
Yes.
I presume you hostname, port, username are correct?
Enable MQTT and HA Auto Discovery.
I have my base topic as Hoymiles or whatever suits you.
Have Prefix Topic as Homeassistant with all else enabled.
Once that was done the Hoymiles appeared in Home Assistant.
Did you restart Home Assistant?
Does the OpenDTU appear on the MQTT Server under the MQTT finder?
Thanks for coming back ALM. My suspicion is that it's a routing problem. OpenDTU is on 192.168.0.191 but my HA is on 172.25.163.148/20. I presume I'll have to move HA to a 192.168.0.x address?
I'm actually quite clued in on networks (CCNA level), but I'm a windows head. Unix etc is certainly not my "happy place", so simple things that I take for granted I have to scratch my head and search how to do them. I'll have a look at it later, but from what I was looking at last night with some of the charting which people have going, it looks the business to be fair.
I'm also a complete novice on HA too, so there is that. Lots of new things that I'm looking at.
Welcome to the club. Between us all we'll get you up and running. 🙂
I'm assuming that 172.25.163.0/20 is indeed a proper network, and not a local address space that has been allocated by docker etc?
People generally put HA on their trusted VLAN (LAN), and then have any IoT devices in the untrusted VLANs with fw rules to allow access from HA out to them.
If you're going to leave HA on 172.25.163.0/20 you'll need to add a route to the 192.168.0.191 gateway, or add a NAT address for the HA machine in the 192.168.0.0/24 network.
Most likely.
Once an MQTT server is set up it should be fairly straight forward to get OpenDTU talking to it by just entering the details.
It should then appear as a 'device' under MQTT in HA.
You can then set up a fancy dashboard and away you go into the HA rabbit hole…
Thanks for this, now have it setup with solis and hoymiles
Not the easiest to work the entities out but I like that it can do the estimate time to charge/discharge
Here's the code to make it easier for folk:
type: custom:sunsynk-power-flow-card cardstyle: lite show_solar: true battery: energy: 31230 shutdown_soc: 10 show_daily: true invert_power: true dynamic_colour: true linear_gradient: true show_remaining_energy: true show_absolute: false auto_scale: false hide_soc: false colour: - 171 - 13 - 13 charge_colour: - 0 - 153 - 0 solar: show_daily: true mppts: 2 load: show_daily: true show_aux: false load1_name: EV load2_icon: '' load1_icon: mdi:car-electric additional_loads: 1 grid: show_daily_buy: true show_daily_sell: true show_nonessential: true entities: use_timer_248: switch.sunsynk_toggle_system_timer priority_load_243: switch.sunsynk_toggle_priority_load inverter_power_175: sensor.sunsynk_inverter_power grid_connected_status_194: binary_sensor.sunsynk_grid_connected_status inverter_status_59: sensor.sunsynk_overall_state grid_power_169: sensor.sunsynk_grid_power battery_power_190: sensor.battery_power battery_current_191: sensor.battery_current battery_temp_182: sensor.battery_temperature battery_voltage_183: sensor.battery_voltage battery_soc_184: sensor.battery_state_of_charge day_battery_discharge_71: sensor.solar_battery_discharged_today day_battery_charge_70: sensor.solar_battery_charged_today day_pv_energy_108: sensor.inverter_solar_generation_peak pv1_power_186: sensor.pv_power_1 pv2_power_187: sensor.pv_power_2 pv1_current_110: sensor.pv_current_1 pv1_voltage_109: sensor.pv_voltage_1 pv2_voltage_111: sensor.pv_voltage_2 pv2_current_112: sensor.pv_current_2 day_load_energy_84: sensor.inverter_daily_energy_peak day_grid_import_76: sensor.inverter_daily_energy_import_peak day_grid_export_77: sensor.inverter_daily_energy_export_peak grid_ct_power_172: sensor.deye_sunsynk_sol_ark_grid_power_ct essential_power: sensor.load_power essential_load1_extra: sensor.shellyem_5e26f6_channel_2_power pv_total: sensor.pv_power inverter: autarky: 'no' modern: false show_battery: true large_font: true show_grid: true dynamic_line_width: true
I just picked up an orange Pi and solar assistant. Solar assistant is working well but I'm having difficulty connecting it to HA.
I have Mqtt integration but when I put in the ip address of solar assistant it comes back with "failed to connect"
Any ideas?
Did you follow this to the letter? https://solar-assistant.io/help/home-assistant/setup and https://solar-assistant.io/help/home-assistant/broker-setup
That's how I got mine to work
Of course I didn't, I only tried the first link🤣
It's nearly always the monkey at the wheel at fault.😁
That how I got it going as well. I believe it should work without doing the broker setup but I couldn't get it going.
If docker is specifying "network_mode: host" for the HA container then the port should be available on the docker host IP. Is that IP set as 172.25.163.x/20 ? Very odd network to set a host up on, so I think (and am hoping) Johnathan might be right that it's a docker internal network.
You'd be best off moving the docker host to a 192.168.0.x/24 (or /25, whatever) then do a docker-compose to redeploy. If you're planning on doing an isolated/segregated IOT network then good luck with that. It's driving me mad as I keep having to move the Shelly devices off that IOT network just to do FW updates and such. 🤣
Still can't get this to work, would anyone understand the mqtt broker log if I upload it?
Download https://mqtt-explorer.com/ and see if you can connect to SA and read those values.
When working you should also be able to connect to the HA mqtt broker and see the SA values here
Downloaded that but I've no idea what I'm doing with it.
Put your SA IP in there and hit connect (no user/password)
You should see all the sensors there if SA is configured correctly:
I assume you have this addon installed?
Thanks, that worked, I can see the sensors now in mqtt explorer.
I have mosquitto broker installed yes.
![Photo of [Deleted User]](https://wd.vanillicon.com/v2/d38dadd4e9049f636f3a15f844846484.svg)
![Photo of [Deleted User]](https://wd.vanillicon.com/v2/da062963b749703a88f3d03ba7706479.svg)
