@ 66er Yes I get the feeling of confidence with this you mean direct ip local access yes?

After I set two actions 1 to turn relay off on high temp and the other to turn relay on on low temp woks ok and I can see the two actions in the list. Then I go to to edit one action some hours later and the settings have dissapeared then they com back again some hours later? Seem like a bug when the settings don't show the actions still work - any one else seen this?

Here are two different screenshots one from mobile app and one from shelly cloud.

Depending who you access settings you see different things between apps? Just try it one app says MQTT connected the clouds says disconnectd?

Only the new control. cloud app shows the MQTT decice is field name?

@ Seven of Nine
Android old/current app

As a comparison new cloud control web app abb you can see the extra device id field but it shows diconnected even thought it connected to my broker and shown in MQTT Explorer

One common system Ok Lets say

Sitename is the common prefix ?

Then I have 3 devices at the sitename

deives ids

1

2

3

Ok thanks for the tips. But lets look at the first problem

3 identical setups with Shelly 1Plus and Add On module

lets start here.

Only 1 device is captured by MQTT Explorer App? I removed the lines forsys, swicth:0 and wifi from screenshot. All three devices are under subtopic 'nursery' with different device ids

Years ago I learnt some basic MQTT..
Some of these solutions are still working today some commercial application based on Shelly 1 (Gen 1?) yes they work perfectly really great THEN

Recently I try and deploy 3 x Shelly Plus 1 relays using Add On with 1 wire temp sensor. The 1 wire temp sensors work perfect but MQTT is dead in the water

Yes im upgraded to latest firmware....

With my MQTT Explorer on PC I see nothing I understand?

As mentioned I have 3 x Shelly 1 Plus relays BUT only one is picked up by MQTT Explorer on PC? Why only 1 not the other 2? but even with the one that connects -how to I read it it? What am I missing? they have a common MQTT topic but diff devices Ids whats going on

When I try and connect in Node-Red just never it reports connected then Not connected repeating and this is all on the local network???

I have tried using old app and new control app and direct device http access in all sorts of ways but no luck but I do see some issues with software GUI between mobile app Shelly my cloud and direct http access are different -is anything tested these days?

RPC or not RPC no documentations? All these new options buy no direction from Shelly what to use as default/std?

Thanks for help by anyone

Hey thanks, this looks like the answer, i'll let you know...

Hello

I am integrating a Shelly 1L with Node-Red using the HTTP API. The Shelly is controlled via the SW input using a PIR, everything works fine. Is there a way I can disable the Shelly SW input, i.e. Can I disable the SW Input from Node-Red to stop the Shelly switching? I have studied the Shelly APi docs but can't see such a feature?

Thanks

C

ok

Hi

ATTN: Technical Director Shelly products Las Vagas USA.

I am posting this as this is an ongoing issue reported by many other users.

2 x Shelly1 (v3 up to date firmware) same problem after 2-3hrs device disappears from network, nmap finds nothing, ping nothing, API does not connect. I have to cycle the power supply to bring the wifi side back to life again!?

As other users have indicated its only reproducible when the device is connecting via the rest api (in my case node-red) when the API is NOT used the devices remain online for ever zero disconnects.

Its highly concerning that this issue has not been formally addressed and even worse that other threads have been marked resolved when there is no clear communication from company on how to fix it?

Thanks

C

More of the same

2 x Shelly1 same problem after 2-3hrs device disappears from network, nmap finds nothing, ping nothing, API does not connect.

THE ISSUE as other have indicated above is only reproducible when the device is connecting via the rest api (in my case node-red) when the API is NOT used the devices remain online for ever zero disconnects.

Am I missing something -why is the thread maked resolved, there is no answer? So I will now make another