Shelly1 actions DDD - having issues getting started

  • Hi All, I am not sure if there is a welcome area but hi, just new to the forum and fairly new to Shelly receiving my first Shelly1 & Shelly1PM early in January.

    Really pleased with the devices, software seems great and I have worked out and tested most of the features and functions but I have drawn a blank!

    I am trying to do something quite specific and I am struggling. I have a Shelly1 and 1PM and I am trying to get one to control the other, I want the switch inputs on one device to control the relay output on the other quickly.

    As I have it linked and setup just now using a scene and rules, if I close the switch contacts on "Device 1" within about 1 second "Device 2" relay will come on, if I open the switch contacts on "Device 1", then "Device 2" will follow within about 1 second - but I need to be able to use the relay to go closed circuit for perhaps a single 250ms button pulse say within a 150ms tolerance.

    At the moment if I close the switch contacts on "Device 1" for say 250-500ms then it doesn't even register on "Device 2" so too slow and they are side by side!

    According to this page (https://shelly.cloud/support/direct…munication-ddd/) if you use DDD (Direct Device to Device) then the "speech" is extremely fast - just a few milliseconds. Sounds good to me.

    But I cannot get these actions to work.

    As I see if if I take the "Button Switched on URL" and put the IP address of the device I want to control I would make that: http://192.168.0.13/Red/0?turn=on - now assuming that syntax is correct then my thinking is that my device which is online and was at 192.168.0.13 would have come on - not a chirp.

    OK - so thinking about it all, first these 2 devices must be on the same network obviously, so they were both on the home wi-fi - both therefore I know could see each other as they were talking to each other. So I can only assume that the code is wrong.

    Then this got me thinking, that means this setup needs to sit on a WiFi network - routers changes, wifi drops out etc. so I was aiming to run them on their own little network - so I set one up as a wifi access point, I can then connect my iPad to its own wifi network and navigate to its little web-server and take command of it via 192.168.33.1 - I could then connect my iPad to the the wifi network of the second device and I could have then linked it to the wifi network of the first device - see where I am going? However, I had a sudden through before I hit yes - how would I then ever connect to that device again? My thinking was that if I then connected to the network formed of the first device, I would be able to see the second device also connected to it and presumably issued with it's own IP address from device 1 - but I wouldn't know what that IP address was and I am not sure how I would locate it as the discover app might not see it - that would then potentially give me a bricked Shelly!

    Now, I have looked into MQTT stuff and I understand that I could ping MQTT commands about from home automation software and that is something I am interested in for my own house (can anyone recommend good free software for this - Home Assistant? But otherwise how do I create and broadcast MQTT commands?

    Also, I want to make this 2 device setup as standalone as possible - so I like the idea of pre-configuring them on their own little wifi network then as soon as they power up they should just work.

    Any help would be much appreciated - once I get my head around linking them up standalone and work out DDD and MQTT then I think I will quickly work out how to make things happen and be less of a burden on the forum but I just cannot find enough help or guides etc. to get me over the hump. I have spent probably around 12hrs over the last week researching and trying and trying and it's so simple yet I can't get them going.

  • Welcome @Carrerahill to our forum,

    I had a very close situation a few weeks ago.

    lets say your Shelly set up with the Wifi-AP is Shelly A and your Shelly you want to connect to that AP is Shelly B then it is not that much effort to find out the IP of Shelly B as the DHCP Server of Shelly A would assign IPs in a simple counting way.

    The first device connected to that AP would get the IP ending up with 33.2 the second device gets 33.3 and so on. So if you connect your iPad you should be able to find the Shelly B in the second or third try.

    If you verified that Shelly B is succefully connected to the AP Shelly you can set it up with a static IP ( well I prefer high ones because there could be a situation where I want to connect a few more Clientsa to the AP and using IPs above 200 would get me out of struggling with double used IPs from DHCP and static setup)

    From now on I was able to define Actions which work fine since about a few weeks. Also my App found the new devices as soon as I connected my mobile to the Shelly A Wifi.

    Hope that was usefull to you - and if it works we can handle the MQTT stuff if you still need

    greetings

    Hannes

  • hi!

    using IPs above 200 would get me out

    think that's to high! i started in november with shelly and today im over 50 pices! so i changed my system and have only 9 slots for dhcp. all other are reserved ip's, or fixed in shelly devices.;)

  • Dieses Thema enthält 3 weitere Beiträge, die nur für registrierte Benutzer sichtbar sind, bitte registrieren Sie sich oder melden Sie sich an um diese lesen zu können.