As it turns out, the fields presented in the solarbank info for the set load and the fields presented in get_device_load may have a different mapping.
When 2 solarbanks are used in a system, the set home load per System will be 50% of the site home load that is being defined in the schedule. Each solarbank reports both pre-set values, but the individual setting (parallel_home_load) appears to be set only when 2 solarbanks are used. However, the solarbank info details from the scene query as used for the sites update will show the active pre-set per device.
Furthermore the schedule is currently a common property for the site. Solarbank devices share the same schedule, but it cannot be modified independently at this point in time.
To maintain flexibility for the future, the schedule will continue to be reported along the device details, although it cannot be set independently yet. The home load pre-sets for Site details and device details will be adjusted and properly mapped.
This will also support future set home load helper function that can act for a specific device. The site_id, device_sn and schedule is available in the device details and can be used by the helper to have all details for changing / updating the corresponding schedule with the new home load settings.
As it turns out, the fields presented in the solarbank info for the set load and the fields presented in get_device_load may have a different mapping. When 2 solarbanks are used in a system, the set home load per System will be 50% of the site home load that is being defined in the schedule. Each solarbank reports both pre-set values, but the individual setting (parallel_home_load) appears to be set only when 2 solarbanks are used. However, the solarbank info details from the scene query as used for the sites update will show the active pre-set per device. Furthermore the schedule is currently a common property for the site. Solarbank devices share the same schedule, but it cannot be modified independently at this point in time. To maintain flexibility for the future, the schedule will continue to be reported along the device details, although it cannot be set independently yet. The home load pre-sets for Site details and device details will be adjusted and properly mapped.
This will also support future set home load helper function that can act for a specific device. The site_id, device_sn and schedule is available in the device details and can be used by the helper to have all details for changing / updating the corresponding schedule with the new home load settings.