You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update the Service Area cluster's XML, and any necessary SDK code, to match the latest spec changes since 0.7. These spec changes address multiple spec issues and are addressed in a couple of spec PRs. Below is a summary of the spec issues and changes that this issue needs addressing.
Remove the LISTORDER feature as discussed in this issue and implemented in this PR.
Add the SkippedArea argument to the SkipArea command as discussed in this issue and implemented in this PR.
Add the LandmarkInfoStruct type and update the AreaInfoStruct as discussed in this issue and implemented in this PR.
Change the MapId type to uint32 as discussed in this issue and implemented in this PR.
Add the PROG feature as discussed in this issue and implemented in this PR.
Add the MAPS feature as discussed in this issue and implemented in this PR.
Removed the SurfaceTag as discussed in this issue and implemented in this PR.
Ensure that the final XML matches the latest spec.
The text was updated successfully, but these errors were encountered:
Update the Service Area cluster's XML, and any necessary SDK code, to match the latest spec changes since 0.7. These spec changes address multiple spec issues and are addressed in a couple of spec PRs. Below is a summary of the spec issues and changes that this issue needs addressing.
LISTORDER
feature as discussed in this issue and implemented in this PR.SkippedArea
argument to theSkipArea
command as discussed in this issue and implemented in this PR.LandmarkInfoStruct
type and update theAreaInfoStruct
as discussed in this issue and implemented in this PR.MapId
type touint32
as discussed in this issue and implemented in this PR.PROG
feature as discussed in this issue and implemented in this PR.MAPS
feature as discussed in this issue and implemented in this PR.SurfaceTag
as discussed in this issue and implemented in this PR.The text was updated successfully, but these errors were encountered: