MH201 OpenWebNet – Status feedback not returned for lighting devices
Dear Legrand Support Team,
I am currently integrating a BTicino/Legrand MH201 gateway with an OpenWebNet client (Home Assistant / OpenHAB).
I have successfully established the OpenWebNet connection and authentication with the MH201. Commands sent to the lighting devices are working correctly. For example, I can switch on a light using the OpenWebNet command:
*1*1*15##
The light is switched on as expected.
However, I am not able to retrieve the status of the same device. When sending a status request, I do not receive any response from the MH201 indicating the current state of the light.
Could you please confirm the expected behavior of the MH201 regarding status feedback?
Specifically:
- Is the MH201 designed to return the current status of lighting devices (and other equipment such as roller shutters) through OpenWebNet status requests?
- Should a command such as
*#1*15##return the current state of the device? - If the MH201 supports this functionality, could the issue be related to a configuration setting, device compatibility, or a missing parameter in the MH201 setup?
- Is there any specific configuration required to enable status feedback or event notifications?
At this stage:
- OpenWebNet connection: OK
- Authentication: OK
- Lighting commands: OK
- Status feedback: Not received
Could you please clarify whether this behavior is expected (“as designed”) or if it indicates a configuration or product issue?
Thank you for your support.
Hello Baptiste,
I forwarded your questions to our internal support. I’ll tell you once I know more 🙂
Have a good day,
Leslie – Community Manager
<p>Hi Leslie,</p><p style=”text-align: left;”>Do you have any news ?</p><p>Thanks a lot for your help.</p><p>Have a nice day</p><p> </p>
Hi Jean-Baptiste,
I just came back from holidays with some feedback from our internal support :
From the description of the issue, it appears that only the command session has been estabilished, whereas both the command and the event sessions must be opened for a correct communication (the latter is specifically used to receive feedback on commands or status requests that have been sent).
Please note that it is good practice NOT to do polling (send status requests) on SCS objects, but to send status requests only at the start of communication and then monitor the spontaneous status updates via the event session.
Hoping it will help you resolve the problem,
Have a good day,
Leslie – Community Manager
You must be logged in to reply to this topic.
3 replies 
2 participants