Bug Fix Shelly Dimmer MQTT Transition Time Not Writable In IoBroker

by Pedro Alvarez 68 views

Hey everyone,

We've got a critical bug report to address concerning the Shelly Dimmer series, specifically the Dimmer1, Dimmer2, Dimmer Gen3, and RGBW models. It appears there's an issue with setting the transition time via MQTT within the ioBroker adapter. This is a crucial feature for many users, including myself, who rely on smooth lighting transitions for various scenarios throughout the day. Let's dive into the details and see what's going on.

The Problem: Transition Time Not Writable via MQTT

The core issue is that the transition time setting, which allows you to control how smoothly your lights dim or brighten, is no longer writeable through MQTT in the ioBroker adapter. Some users have reported that after switching their Shelly devices to MQTT, they can no longer adjust the transition time from the adapter. This is a major problem because it impacts the ability to create dynamic lighting scenes and automations. The transition time functionality is essential for creating smooth and visually appealing lighting effects, especially in scenarios where you want to avoid abrupt changes in brightness. For example, you might want a quick 1-second fade during the day but a gentler 5-second transition at night for a more soothing ambiance.

For those unfamiliar, the transition time dictates how long it takes for a light to fade from one brightness level to another. A short transition time results in a quick, almost instantaneous change, while a longer transition time creates a gradual and smooth fade. This is particularly useful for creating a comfortable and natural lighting environment. Imagine waking up in the morning to a gentle sunrise simulation, or winding down in the evening with a gradual dimming of the lights. These are the kinds of experiences that become difficult, if not impossible, to achieve when the transition time setting is not functioning correctly. Transition time is very useful in the lighting.

Furthermore, some users have pointed out that the Dimmer Gen3 models seem to be missing the transition data point altogether, making it impossible to adjust the transition time even if the write functionality were working. This inconsistency across different Shelly models adds another layer of complexity to the problem. We need to figure out why this data point is missing in some models and ensure that the transition time setting is consistently available and functional across the entire Shelly Dimmer series. This involves not only fixing the writeability issue but also ensuring that the necessary data points are present in the first place. MQTT functionality is very important for home automation.

Impact on Lighting Automation

This issue significantly impacts lighting automation setups. Many users, including the reporter, rely on different transition times for various scenarios. For example:

  • Daytime: A fast 1-second fade for quick adjustments.
  • Nighttime: A smooth 5-second transition for a gentler ambiance.
  • Alerts: Using flickering lights to signal events like a doorbell ring.
  • RGBW Control: Creating dynamic lighting effects with color transitions.

Without a working transition time setting, these kinds of automations become difficult or impossible to implement. The ability to control the transition time adds a layer of sophistication to lighting setups, allowing for nuanced and personalized lighting experiences. For instance, you could set up a routine where the lights gradually dim over a period of 30 minutes before bedtime, helping you to relax and prepare for sleep. Or you could create a scene where the lights slowly brighten in the morning, mimicking the sunrise and gently waking you up. These are just a few examples of how the transition time setting can enhance your home lighting experience.

Specific Observations

  • The reporter notes that this functionality used to work, but it's unclear which adapter version introduced the bug.
  • The Dimmer Gen3 models appear to be missing the transition data point entirely.

User Environment

To better understand the scope of this issue, here are the details of the user's environment:

  • Shelly Devices: Dimmer1, Dimmer2, Dimmer Gen3, RGBW
  • Shelly Firmware Version: Latest
  • Protocol: MQTT
  • Node.js Version: 20
  • ioBroker js-controller Version: 7
  • Adapter Version: 10.1.0

This information is crucial for developers to reproduce the issue and identify the root cause. By knowing the specific versions of the software and firmware involved, they can narrow down the potential sources of the bug. For example, a recent update to the Shelly firmware might have introduced a change that is not being correctly handled by the ioBroker adapter. Or, a bug in the adapter itself might be preventing it from correctly communicating with the Shelly devices over MQTT. The more information we can provide to the developers, the better equipped they will be to diagnose and fix the problem. User environment is always very useful for debugging.

Debugging Information

Unfortunately, the user didn't provide any logs in debug mode. Debug logs are essential for troubleshooting, as they provide a detailed record of the adapter's activity and can help pinpoint where the issue is occurring. When reporting bugs, it's always a good idea to include debug logs, as they can save developers a significant amount of time in diagnosing the problem. In this case, debug logs could reveal whether the adapter is sending the correct MQTT messages to the Shelly devices, or if there's an error occurring within the adapter itself.

Potential Causes and Solutions

Let's brainstorm some potential causes and solutions for this issue:

  1. MQTT Payload Format: There might be a change in the expected MQTT payload format for setting the transition time. The adapter might be sending the data in an incorrect format, causing the Shelly devices to ignore the command. This could be due to a change in the Shelly firmware or a bug in the adapter's MQTT implementation.

    • Solution: Investigate the MQTT payload format expected by the Shelly devices and ensure the adapter is sending data in the correct format. This might involve examining the Shelly documentation or using an MQTT client to monitor the messages being sent and received.

  2. Data Point Mapping: The data point mapping between the adapter and the Shelly devices might be incorrect. The adapter might be trying to write to the wrong MQTT topic or using an incorrect data type. This could be due to a misconfiguration in the adapter or a bug in the data point mapping logic.

    • Solution: Verify the data point mapping between the adapter and the Shelly devices. Ensure that the adapter is writing to the correct MQTT topic and using the correct data type for the transition time setting. This might involve examining the adapter's configuration settings or the Shelly device's MQTT documentation.

  3. Adapter Bug: There might be a bug in the adapter's code that is preventing the transition time from being written correctly. This could be due to an error in the logic that handles MQTT communication or a problem with the data processing. Adapter bugs happen sometimes, no worries guys.

    • Solution: Review the adapter's code for any potential bugs that could be causing the issue. This might involve using a debugger to step through the code and identify where the problem is occurring. It could also involve examining the adapter's change log to see if any recent changes might have introduced the bug.

  4. Firmware Incompatibility: A recent firmware update on the Shelly devices might have introduced a change that is incompatible with the current version of the adapter. This could be due to a change in the MQTT API or a bug in the firmware itself.

    • Solution: Check for any known compatibility issues between the Shelly firmware and the adapter. If there is a known issue, consider downgrading the firmware or waiting for an adapter update that addresses the compatibility problem. It might also be helpful to contact Shelly support to report the issue and see if they have any recommendations.

  5. Missing Data Point (Dimmer Gen3): The transition data point might be genuinely missing in the Dimmer Gen3 models. This could be a bug in the Shelly firmware or a configuration issue.

    • Solution: Investigate why the transition data point is missing in the Dimmer Gen3 models. This might involve examining the Shelly device's MQTT documentation or contacting Shelly support. If it's a bug in the firmware, a future update might address the issue. If it's a configuration issue, there might be a setting that needs to be adjusted to enable the data point.

Next Steps

To further investigate this issue, we need to:

  1. Gather More Information: Ask other users if they are experiencing the same problem. The more data points we have, the better we can understand the scope of the issue.
  2. Request Debug Logs: Encourage users to provide debug logs when reporting issues. This is crucial for developers to diagnose problems efficiently.
  3. Test Different Adapter Versions: Try rolling back to previous adapter versions to see if the issue persists. This can help determine if a recent update introduced the bug.
  4. Examine MQTT Traffic: Use an MQTT client to monitor the messages being sent and received between the adapter and the Shelly devices. This can help identify if the adapter is sending the correct commands and if the devices are responding appropriately.
  5. Contact Shelly Support: Reach out to Shelly support to report the issue and see if they have any insights or recommendations.

Conclusion

The inability to set the transition time via MQTT in the Shelly Dimmer series is a significant bug that impacts lighting automation setups. By gathering more information, analyzing debug logs, and collaborating with the community and Shelly support, we can hopefully identify the root cause and find a solution. Let's work together to get this issue resolved and restore this essential functionality. If you're experiencing this issue, please share your experiences and any relevant information in the comments below. Your input can help us get closer to a fix. Community work is always the best for open-source projects!

Thanks for reading, and let's get this bug squashed!

Repair Input Keyword

  • Is the issue present in the current beta version of the adapter? (Yes)
  • Is there another open issue with the same topic? (No)
  • Is the issue described in the adapter documentation/FAQ? (No)
  • Which Shelly devices are affected? (Dimmer1, Dimmer2, Dimmer Gen3, RGBW)
  • What is the Shelly firmware version? (Latest)
  • What protocol is being used? (MQTT)
  • What is the problem? (Transition time cannot be written, Dimmer Gen3 missing transition data point)
  • Are there iobroker.current.log files in debug mode? (No response)
  • What is the Node.js version? (20)
  • What is the ioBroker js-controller version? (7)
  • What is the adapter version? (10.1.0)

SEO Title

Bug Fix Shelly Dimmer MQTT Transition Time Not Writable in ioBroker