Important notes for the Shelly couplings on Homematic

Here are some hints and tips that should be read and used especially when problems occur.

Content:according to my instructions

# 1 delays in the homematic process

# 2 fixed IP
# 3 Common mistakes

# 4 Create a new topic with questions about problems

Delays in the homematic process

Coupling many Shelly to Homematic according to my instructions and updating them at very short intervals may result in delays depending on the size of the overall homematic installation.

To eliminate this problem as far as possible, I recommend:

1. Do not set the CUxD timer or homematic timing intervals for all status updates (switch status, online status ...) too short / small.
2. Always use the original "Monitor Online Status option".

Explanation to 2:

By checking the online status and integrating into the respective update program, you can save valuable computing time (especially when used on the CCU2). The test will then be performed only if the corresponding Shelly device is also online.

Here for clarification a program screenshot:

Onlinestatus in Aktualisierung.png

In the 2nd AND-condition it is checked wether the Shelly is online. If it is offline, there is no query and thus no valuable query time and waiting for an answer.

This query should be included in all relevant Shelly update programs.

And if you install it right away, you do not need to rework it as your installation grows.

Fixed IP:

All the device and script settings for pairing always access the IP address of the Shelly, I recommend setting the IP addresses fixed in the Shelly devices. DHCP should be avoided.

If e.g. after a firmware update of the router, the IP addresses reassigned, so react possibly the wrong devices due to the newly assigned IP.

Of course, make sure that the fixed IP addresses are not in the range of the DHCP pool.

Common mistakes

If problems occur with a pairing, here is a small list of common sources of error:

1. wrong IP address or CUxD device address or CUxD channel entered in the device settings and / or the scripts
2. wrong CUxD device created
   (please pay attention to the screenshots in the instructions, if the pictures differ from yours, you have created a wrong device.
3. Script no longer executable due to accidental changes. In this case delete script, copy in new and adjust.
4. The CUxD-Exec device only serves to send the HTTP commands in the scripts and receive the response from the Shelly.
   
   It is not to be used as a switch or button for the individual switching actions such as ON / OFF, set colors ...
   
   The 16-channel universal control or the multi-DIM device is there!
5. No settings are made in the CUxD-Exec device or channel! If entries are made here, misconduct is very likely.
6. Errors in the status feedback may be the responsibility of the recently introduced homematic internal firewall. Therefore, the firewall should be disabled as a test!
7. The http requests and scripts are programmed on Shelly, which are not protected with username and password. But who wants to have username and password in the couplings, finds here the necessary steps.

Note on my part to 6th and 7th:

I consider the configuration and use of the internal homematic firewall superfluous. If someone has managed to get into my own network unauthorized and unwanted, then I have other worries than needing to rebuild the Homematic with a backup if necessary. As a result, all my Shelly are also not login-protected.

Create a new topic with questions about problems

If you can not find the mistake on yourself ...

• Please create a new topic, in which you describe the problem as accurately as possible

• please post screenshots of the device settings in Homematic

• please post your custom script in a code-tag Code-Tag.png

Thank you very much