Hello fellow smart home enthusiasts! I wanted to share my recent experience with resolving an issue related to my Modbus dimmer setup. It was a bit of a rollercoaster, but I’m thrilled to say I figured it out and learned a lot along the way. 
The Problem: I had a NodeMCU acting as a Modbus dimmer, controlling my lights. While it worked perfectly in Paper UI and Basic UI, switching to a Dimmer item type for Google Home tagging caused unexpected behavior. The lights would either flash to the requested brightness and turn off or jump to 1% and stay there. It was perplexing! 
The Investigation: I suspected a scaling issue—perhaps the system was dividing the value by 100 somewhere. I checked my transformation rules, verified the address range, and even tried adjusting the PWM output range. Nothing seemed to fix it. I scoured forums and documentation, but the solution wasn’t immediately clear. 
The Breakthrough: After hours of trial and error, I realized the issue was indeed with scaling. The Modbus value needed to be correctly interpreted as a percentage without any unintended transformations. By adjusting the transformation script to ensure the value wasn’t being altered post-receipt, the dimmer started behaving as expected. 
The Solution: Here’s what worked for me:1. Transformation Adjustment: Ensure your transformation script correctly scales the input without introducing unintended divisions or multiplications.2. Channel Configuration: Double-check that the channel suffixes match your item types to avoid unexpected behavior.3. Testing: Gradually test different brightness levels to ensure consistent performance.Lessons Learned: This experience taught me the importance of meticulous transformation rule setup and the value of persistent troubleshooting. It also highlighted how crucial it is to thoroughly understand how each component interacts within your smart home ecosystem. 
If anyone else is struggling with similar issues, I hope this helps! Happy tinkering! 