Don’t get connect to Shelly plus 1pm

[testpaul999]

Have try this with gen2 device Shelly plus 1pm and have no success.
Did yon have any hints?
If I start the script 0.6 the last statement are 0.0.0.0:8000 already in use.but this is not the ip of the Shelly!
Regards

[mkrasselt1]

No you are wrong, the script starts(is beeing started by venus os) automaticly on reboot, and binds a websocket server onto the venus device. you need to add the "outbound websocket server" to the shellys settings using the scheme ws://ip.of.venus.device:8000 and restart the shelly to transmit data to the venus os :)

[jjdejong]

My Shelly PM 1 is recognized by the console, but no readings are provided.

[mkrasselt1]

My Shelly PM 1 is recognized by the console, but no readings are provided.

could you please show the device information of the shelly and the settings for outgoing websocket ?

[jjdejong]

[jjdejong]

Is it not because the PM1 API uses RPC methods like PM1.GetStatus, whereas the EM API uses methods like EM.GetStatus?

[jjdejong]

Yeah, the meter.py file uses things such as:

                        try:
				d = data['params']['em:0']
			except KeyError:
				pass
			else:
				with self.service as s:
					s['/Ac/L1/Voltage'] = d["a_voltage"]
					s['/Ac/L2/Voltage'] = d["b_voltage"]
					s['/Ac/L3/Voltage'] = d["c_voltage"]
					s['/Ac/L1/Current'] = d["a_current"]
					s['/Ac/L2/Current'] = d["b_current"]
					s['/Ac/L3/Current'] = d["c_current"]
					s['/Ac/L1/Power'] = d["a_act_power"]
					s['/Ac/L2/Power'] = d["b_act_power"]
					s['/Ac/L3/Power'] = d["c_act_power"]
					s['/Ac/Power'] = d["a_act_power"] + d["b_act_power"] + d["c_act_power"]

Whereas the PM1 has just one channel switch:0 providing apower, voltage, current, aenergy, so the whole file needs to be adapted to PM1 devices.

[mkrasselt1]

can you do that yourself, now you know how?

[jjdejong]

OK, I came up with something. The issue is that the Shelly Plus 1PM (at least mine) does not send all sensor data (voltage, current, apower, aenergy) at each WS notification, which is something the Victron seems to expect. Not sure this is a defect of my device or a flaw in the 1PM's firmware.

[matt1309]

I think a few of us have tried the same.
I'm working on adding all switches ie if you swap devicetype to PM it'll create three more devices for each switch on 1pm Pro

Still needs debugging but here's the first draft
https://github.com/matt1309/dbus-shelly-1pmSupport/tree/master

[kurtinge100]

@matt1309 Did you got your PM to work? Will this work for the Shelly Pro 1 PM, as well ?

[matt1309]

@matt1309 Did you got your PM to work? Will this work for the Shelly Pro 1 PM, as well ?

I gave up making a generalised version but happy to help make a static version for pm if you need it.

[jjdejong]

@matt1309 Did you got your PM to work? Will this work for the Shelly Pro 1 PM, as well ?

I've worked on generalized version here:
https://github.com/jjdejong/dbus-shelly/tree/master
However, the PM and 1PM devices are only "sometimes" recognized on the console, and they don't show any updates beyond the first values. Note that the PM and 1PM devices don't send all sensor data at every notification like the EM Pro. Not sure if this is the issue.

[kurtinge100]

@matt1309 and @jjdejong:
If it is not too much trouble, please make a static version for Pro 1PM as I have this connected to my charger which I am remotely controlling. Would be nice to have the values showed up in the AC IN buble

[jjdejong]

@matt1309 and @jjdejong: If it is not too much trouble, please make a static version for Pro 1PM as I have this connected to my charger which I am remotely controlling. Would be nice to have the values showed up in the AC IN buble

It is some trouble, since we've gone through the effort of genericising!

[kurtinge100]

@matt1309 and @jjdejong: If it is not too much trouble, please make a static version for Pro 1PM as I have this connected to my charger which I am remotely controlling. Would be nice to have the values showed up in the AC IN buble

It is some trouble, since we've gone through the effort of genericising!

Well......don't bother, then. It is not that important :)