Beiträge von Dimitri Troncquo

    Hi,

    We are developing a solution based on a setup involving 3 shellies. Since introducing a few scripts, the 4pm has become instable, crashing often and for no obvious reason. I'm looking for some guidance.

    The setup is as follows:

    1 Shelly 4pm, which communicates to with the outside world through our own MQTT broker, using TLS.

    1 Shelly RGBW2 and 1 Shelly 1PM both connected to output 0 of the Shelly 4pm, pulling 24V.

    The other 3 outputs are used for 240V appliances.

    Because the the Gen 1 shellies don't support MQTT with TLS, we decided to route all communication over the 4PM. This includes reporting consolidated status updates to a MQTT topic.

    There are 3 scripts running on the 4PM.

    1. RGBW2 command relay

    2. Shelly 1 command relay

    3. Status reporting

    The first two scripts work along the same lines. They listen to a MQTT topic and relay the posted commands to the device in question using HTTP GET requests.

    The third script has 4 steps.

    1. call get status on 4pm.

    2. call get status on RGBW over HTTP

    3. call get status on Shelly 1 over HTTP

    4. consolidate statuses and post to MQTT topic

    These 4 steps are run in a timer loop (every 3 seconds).

    All these scripts seems to work, but as I mentioned, the 4PM seems to crash every now an then. Usually it does recover, but still, service is interrupted, so we would like to solve the issue.

    We have tried the same configuration on two different device setups, so I'm pretty sure it's not a faulty device which causes the issue.

    Is what we are trying to do just too heavy for the 4pm? Maybe I'm looking in the wrong place?

    Is there any way to access device logs which might help me out? Are there any other steps I can do to debug?

    Best regards,

    Dimitri