Version 5.24.5.4 has been released via the HS Updater. It is an incremental release that captures changes since the last update. New feature added and issues addressed per mcsMQTT Change Log (HS4 & HS3) - HomeSeer Message Board and the release notes.
Backward compatibility has been an objective so an update should be transparent to users. This post is make users aware of a change in the UI for selecting a JSON key to be a unique identifier. i.e. elevate. In prior release the elevate function was done by associating the JSON key that is to be elevated and then using the Edit tab to mark this key as being elevate either singularly or as a wildcard.
With the 5.24.5.x the UI has changed so that elevate capability is performed on the main topic by entering on the Edit tab text box of the parent topic the elevate key (e.g., Id or for wildcard as *: Id.) vs. the prior approach of selecting a radio button of the JSON key that is to be elevated. There is no longer a need to associate the elevated key to create a HS device.
The more significant impact is that mcsMQTT.db that contains the elevate information in the field ElevateKeys has changed so that the elevate key is now just the key as one would enter in a textbox rather than the full path of parent JSON objects that include the key. mcsMQTT, at startup, tries to recognize the change and formats the ElevateKeys field to the new convention. This means the change should be transparent to the user if all goes as intended. For the user of the wildcard radio option for elevate there should be no impact since the ElevateKeys field in the database did not change in this case.
Bottom line is:
1. The user interface has changed on how JSON keys are elevated so their value becomes part of the unique identification. It is now a textbox on the parent topic rather than a radio on the JSON key.
2. A backup should be done before updating to 5.26.5.4 via Updater so that it is possible to go back it all does not go as intended.
Backward compatibility has been an objective so an update should be transparent to users. This post is make users aware of a change in the UI for selecting a JSON key to be a unique identifier. i.e. elevate. In prior release the elevate function was done by associating the JSON key that is to be elevated and then using the Edit tab to mark this key as being elevate either singularly or as a wildcard.
With the 5.24.5.x the UI has changed so that elevate capability is performed on the main topic by entering on the Edit tab text box of the parent topic the elevate key (e.g., Id or for wildcard as *: Id.) vs. the prior approach of selecting a radio button of the JSON key that is to be elevated. There is no longer a need to associate the elevated key to create a HS device.
The more significant impact is that mcsMQTT.db that contains the elevate information in the field ElevateKeys has changed so that the elevate key is now just the key as one would enter in a textbox rather than the full path of parent JSON objects that include the key. mcsMQTT, at startup, tries to recognize the change and formats the ElevateKeys field to the new convention. This means the change should be transparent to the user if all goes as intended. For the user of the wildcard radio option for elevate there should be no impact since the ElevateKeys field in the database did not change in this case.
Bottom line is:
1. The user interface has changed on how JSON keys are elevated so their value becomes part of the unique identification. It is now a textbox on the parent topic rather than a radio on the JSON key.
2. A backup should be done before updating to 5.26.5.4 via Updater so that it is possible to go back it all does not go as intended.
Comment