question

Hi @mr-23

Can you share the commands you're using to send the request in node red?

If you search Send Command in this page it shows you how to send it using mosquitto_pub

Switch | Shelly Technical Documentation

Hello Matt,

this is the test that I have set up.

Hi @mr-23

Do you have shelly 1pm or shelly1pm plus. The api documentation differs depending on that?

Shelly 1pm uses this:

Shelly1/PM: Overview – API Reference

Shelly 1pm plus: (Guessing it's this one based on name)

MQTT | Shelly Technical Documentation

Documentation has the topic in this form:

<topic_prefix>/command/switch:<id>

where <topic_prefix> is a custom prefix if set or defaults to <device_id>

I would read that as shellyplus1-<SERIAL>/command/switch:0

Thanks for your helb.

I have found it:

This is the right string.

topic_prefix/command/switch:0

@mr-23, have you had success controlling the shelly switch using Node Red over MQTT? could you post your commands that worked? I am sure that I am missing a small but critical command structure.

Hi @matt1309

shelly plus1pm. It is a single contact, 110-240 vac, 24-30 vdc.

It shows up on MQTT Explorer as

"shellies/shellyplus1pm-90380c36f9e4"

I found the following page:

Shelly1/1PM: MQTT

Shelly1 and Shelly1PM uses the following topics, where <model> is either shelly1 or shelly1pm:

• shellies/<model>-<deviceid>/relay/0 to report status: on, off or overpower (the latter only for Shelly1PM)
• shellies/<model>-<deviceid>/relay/0/command accepts on, off or toggle and applies accordingly
• shellies/<model>-<deviceid>/input/0 reports the state of the SW terminal
• shellies/<model>-<deviceid>/longpush/0 reports longpush state as 0 (shortpush) or 1 (longpush)
• shellies/<model>-<deviceid>/input_event/0 reports input event and event counter, e.g.: {"event":"S","event_cnt":2} see /status for details

Shelly1PM adds:

• shellies/shelly1pm-<deviceid>/relay/0/power reports instantaneous power in Watts
• shellies/shelly1pm-<deviceid>/relay/0/energy reports an incrementing energy counter in Watt-minute
• shellies/shelly1pm-<deviceid>/temperature reports internal device temperature in °C
• shellies/shelly1pm-<deviceid>/temperature_f reports internal device temperature in °F
• shellies/shelly1pm-<deviceid>/overtemperature reports 1 when device has overheated, normally 0
• shellies/shelly1pm-<deviceid>/temperature_status reports Normal, High, Very High
• shellies/shelly1pm-<deviceid>/relay/0/overpower_value reports the value in Watts, on which an overpower condition is detected.

Thanks for the information, @matt1309. I will investigate this path. I am not a programmer by trade, so let me ask another question.

Would I create a json file/script for the device, changing the command as necessary for the desired change, and send that json over the MQTT node?

Hi @matt1309 matt1309,

Thanks for the suggestion to use http. I was able to use a http request node using the Get method and with the following in the URL line: <local ip of switch>/rpc/Switch.Set?id=0&on=false <to turn off>,

<local ip of switch>/rpc/Switch.Set?id=0&on=true ,to turn on> and <local ip of switch>/rpc/Switch.Toggle?id=0 <to toggle between off and on and off etc.>.

These nodes took me a very long time to trouble shoot and I am not sure why. I entered the command directly into the address bar of my browser and it worked. I copied the command and placed it into the Node and it would not work. Finally, I did something that made a change, and I do not know what I did, and then the node began working.

Anyway, this small problem solved. I do wish that there were some working examples of the Shelly Plus 1PM being controlled by other methods, but atleast now I can continue with my original project.

Thanks again for your help.