# NSPanel Pro v4.1.0 Release: New Features & Enhancements **URL:** \ **Category:** NSPanel Pro\ **Created:** [November 6, 2025, 5:36pm UTC](https://forum.ewelink.cc/t/nspanel-pro-v4-1-0-release-new-features-enhancements/206443 "2025-11-06T17:36:51Z")\ **Posts on this page:** 1\ **Showing post:** 16
**Author:** ![jam3](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.ewelink.cc/jam3/32/7918_2.png) [@jam3](https://forum.ewelink.cc/u/jam3)\ **Post date:** [November 7, 2025, 4:04pm UTC](https://forum.ewelink.cc/t/nspanel-pro-v4-1-0-release-new-features-enhancements/206443/16 "2025-11-07T16:04:54Z")
> [@MichaelLearnsToCode](#): > > download eWeLink Android App `v5.21.0` Thank you. Looks like NSPanel Pro is now acting like a ZBBridge-U with Matter sync — nice move! Let me take a quick look at how it plays with MQTT. I’ll let you know soon how it goes. @MichaelLearnsToCode @JoJo **Update:** I started MQTT using the new version of the app. I have a number of observations. I’ve noticed that NSPanel Pro publishes the Zigbee device state to MQTT only when a parameter changes, for example, `state`, `temperature`, etc. As a result, after restarting Home Assistant or the MQTT broker, entities remain without values until the device sends a new update. MQTT publications use `retain: false`, so the broker does not store the last known state. To fix this, it would be helpful if NSPanel Pro (or Zigbee2CUBE) published device states with `retain: true`. This way, Home Assistant could automatically retrieve the last known state after a restart, without needing to manually query each device. Alternatively, could NSPanel Pro respond to `homeassistant/status` or `broker/status` and publish device states upon reconnect? In its current form, the MQTT integration between NSPanel Pro and Home Assistant is unreliable and of limited practical use. --- _[View the full topic](https://forum.ewelink.cc/t/nspanel-pro-v4-1-0-release-new-features-enhancements/206443)._