mcsMQTT has been placed in Updater for HS4. It is functionally nearly the same as the HS3 plugin of the same version number. The intent is that migration from the HS3 plugin is seamless with no special actions needed by user. While I have been testing various aspects of the plugin for months and have kept it current with the HS3 plugin there are likely users that have a setup I have not considered. It is good to have a backup so if something is not working for you then you can restore from backup.
The biggest difference for mcsMQTT between HS3 and HS4 is the Feature vs. Device concept in HS4. In HS3 mcsMQTT in the past few months I have tried to honor the HS4 expectations so the transition to HS4 would be a natural progression. For those that are using older mcsMQTT versions then this transition could result in some unexpected behaviors.
I have elected to not carry forward the BLE location identification wit ESP32 and RPi into HS4. I do not think anybody was using it.
The event trigger and event actions between HS3 and HS4 are the same, but the UI is different and the supporting code is largely new. Existing HS3 events should import without any additional user activity.
HS4 does not yet support scripting provided by a plugin. If you are using these features of mcsMQTT with the HS3 plugin then don’t expect them to work with the HS4 plugin at this time. Eventually HS4 will have this area supported.
There really is no urgency to move from the HS3 to HS4 plugin, but it would be nice if you tip toe’d into the HS4 plugin to identify issues so they can be addressed before everybody needs to move to the HS4 plugin. I will continue to make updates to both HS3 and HS4 but as HS4 matures the HS4 plugin may be the only one that new features.
The biggest difference for mcsMQTT between HS3 and HS4 is the Feature vs. Device concept in HS4. In HS3 mcsMQTT in the past few months I have tried to honor the HS4 expectations so the transition to HS4 would be a natural progression. For those that are using older mcsMQTT versions then this transition could result in some unexpected behaviors.
I have elected to not carry forward the BLE location identification wit ESP32 and RPi into HS4. I do not think anybody was using it.
The event trigger and event actions between HS3 and HS4 are the same, but the UI is different and the supporting code is largely new. Existing HS3 events should import without any additional user activity.
HS4 does not yet support scripting provided by a plugin. If you are using these features of mcsMQTT with the HS3 plugin then don’t expect them to work with the HS4 plugin at this time. Eventually HS4 will have this area supported.
There really is no urgency to move from the HS3 to HS4 plugin, but it would be nice if you tip toe’d into the HS4 plugin to identify issues so they can be addressed before everybody needs to move to the HS4 plugin. I will continue to make updates to both HS3 and HS4 but as HS4 matures the HS4 plugin may be the only one that new features.
Comment