amazonechocontrol all-fixes test-14 (5.3, runs on 5.2.x)

Test build for openHAB 5.3, built from main 560a922, and it runs on openHAB 5.2.x as well. It supersedes amazonechocontrol-all-fixes-test-13 and adds three smart home changes for openhab#21660 (Tile x/y updating very delayed) that have no pull request yet.

Everything merged into main is included, among it every pull request of the earlier test builds: openhab#21439, openhab#21442, openhab#21492, openhab#21514, openhab#21515, openhab#21557, openhab#21446, openhab#21516, openhab#21561, openhab#21575, openhab#21573, openhab#21583, openhab#21601, openhab#21609, openhab#21592, openhab#21608, openhab#21614 and openhab#21628 (see the test-9 and test-13 notes for what each one does). New since test-13 is openhab#21665: a command Amazon rejects names the device family in its WARN line.

New in this build, no pull request yet:

• The smart home polling intervals are a minimum again. pollingIntervalSmartHomeAlexa and pollingIntervalSmartSkills were capped at 10 and 60 seconds instead of starting there. Both now apply as configured, so with the defaults devices connected to Alexa directly are polled every 30 seconds instead of 10, and skill devices such as Tile every 120 seconds instead of 60. Set pollingIntervalSmartSkills to 60 on the account thing to keep the old pace for Tile.
• A smart home device with an empty merge list is polled. Such a device was never asked for its state, and nothing logged it.
• The smart home poll is visible at DEBUG. With org.openhab.binding.amazonechocontrol.internal.handler.SmartHomeDeviceHandler at DEBUG, each poll logs one line per device with the states Amazon returned, including timeOfSample, the time Amazon took the reading. With org.openhab.binding.amazonechocontrol.internal.connection.Connection at DEBUG, each poll names the devices it asks for, every error Amazon reports for them, and any device that came back without a state.

Please use DEBUG on these two loggers, not TRACE on the whole binding: at TRACE the binding polls some skill devices more often, which changes what is being measured.

Before you test the login: copy userdata/jsondb/amazonechocontrol%3Aaccount%3A<your account>.json aside. With openHAB stopped, putting it back restores the old session should anything go wrong.

SHA-256 f57065f114c556088d3446c9f56928dac8218ef54b9330a6ec55b6f572daf214.

To test: uninstall the store amazonechocontrol binding and remove the test-13 jar, drop this jar into the addons folder (velocity-engine-core-2.3.jar must be present there as well, it is a feature dependency not contained in the jar).

samsungtv: legacyCipherSuites test build 1 (5.3)

Test build of the samsungtv binding for openHAB 5.3, from fix/samsungtv-tls-noise on top of main (e1607fe833).

It adds the thing parameter legacyCipherSuites, default true. At the default nothing changes: the websocket client keeps trusting any certificate and keeps every cipher suite the runtime offers, exactly as today.

Turn it off to use the client openHAB configures itself. Core then selects the binding's trust manager by the common name SmartViewSDK in the TV's certificate. That trust manager validates nothing beyond the name. Jetty's default cipher exclusions apply, which also removes the ten warnings each connection logs today.

Turning it off needs a TV whose certificate carries that common name. Without it the TLS handshake fails and you have to turn the setting back on. Either result is worth reporting.

SHA-256 of the jar:

7ad7f862dbe30c86ec19ca8cfb8de8bdf2b3200680780303d238dacd8d006a59

amazonechocontrol all-fixes test-12 (5.2.x)

Superseded by amazonechocontrol-all-fixes-test-13 (adds openhab#21628, the hardcoded conversation id).

Combined test build for openHAB 5.2.x, superseding amazonechocontrol-all-fixes-test-11: everything merged into main since 5.2.0 plus the changes still in review.

Merged since 5.2.0, all included: openhab#21439, openhab#21442, openhab#21492, openhab#21514, openhab#21515, openhab#21557, openhab#21446, openhab#21516, openhab#21561, openhab#21575, openhab#21573, openhab#21583 (see the test-9 notes for what each one does), and since test-11 also openhab#21601 (announcement delay check fixed, volume restore documented) and openhab#21609 (comms host fixed, sendMessage works again, aborted requests name their URI and cause).

In review, included:

• openhab#21592 - Keep third-party media devices online (Sonos media twin, issue openhab#21591)
• openhab#21608 - Read the security panel arm state as a string (issue openhab#20091)
• openhab#21614 - Stop fetching unused list data: a change to an Alexa shopping or to-do list no longer makes a request whose answer nobody read, and the getting items from list ... failed ... 503 stack trace at INFO is gone. New in this build.

Before you test the login: copy userdata/jsondb/amazonechocontrol%3Aaccount%3A<your account>.json aside. With openHAB stopped, putting it back restores the old session should anything go wrong.

SHA-256 a40e89281795249e05eb60695fcc2c803c73c78d9caf682bd4b60fc470b57d6f.

To test: uninstall the store amazonechocontrol binding, drop the jar into the addons folder (velocity-engine-core-2.3.jar must be present there as well, it is a feature dependency not contained in the jar).

amazonechocontrol all-fixes test-11 (5.2.x)

Superseded by amazonechocontrol-all-fixes-test-12 (adds openhab#21614, the unused list fetch).

Combined test build for openHAB 5.2.x, superseding amazonechocontrol-all-fixes-test-10: everything merged into main since 5.2.0 plus the changes still in review.

Merged since 5.2.0, all included: openhab#21439, openhab#21442, openhab#21492, openhab#21514, openhab#21515, openhab#21557, openhab#21446, openhab#21516, openhab#21561, openhab#21575, openhab#21573, openhab#21583 (see the test-9 notes for what each one does).

In review, included:

• openhab#21592 - Keep third-party media devices online (Sonos media twin, issue openhab#21591)
• openhab#21601 - Announcement delay check fixed, volume restore documented
• openhab#21608 - Read the security panel arm state as a string (issue openhab#20091)
• openhab#21609 - Fix the comms host and name aborted requests (issue openhab#19783): the sendMessage channel of the account thing works again, the stored retail domain repairs itself on the first login check. New in this build. For amazon.com accounts the push connection moves from the EU to the NA dispatcher, which is where it belongs, so if push events were dead for you, this build is worth a try.

Before you test the login: copy userdata/jsondb/amazonechocontrol%3Aaccount%3A<your account>.json aside. With openHAB stopped, putting it back restores the old session should anything go wrong.

SHA-256 80f4b1d646637ab7a8334c8a6f8fd7c6356b01841077fba2291dd64b95a3d0cd.

To test: uninstall the store amazonechocontrol binding, drop the jar into the addons folder (velocity-engine-core-2.3.jar must be present there as well, it is a feature dependency not contained in the jar).

amazonechocontrol all-fixes test-10 (5.2.x)

Combined test build for openHAB 5.2.x, superseding amazonechocontrol-all-fixes-test-9: everything merged into main since 5.2.0 plus the changes still in review.

Merged since 5.2.0, all included: openhab#21439, openhab#21442, openhab#21492, openhab#21514, openhab#21515, openhab#21557, openhab#21446, openhab#21516, openhab#21561, openhab#21575, openhab#21573, openhab#21583 (see the test-9 notes for what each one does).

In review, included:

• openhab#21592 - Keep third-party media devices online (Sonos media twin, issue openhab#21591)
• openhab#21601 - Announcement delay check fixed, volume restore documented
• openhab#21608 - Read the security panel arm state as a string (issue openhab#20091): the SecurityPanelController channels fill again when Amazon sends armState as a plain string. New in this build, untested on a real security panel, the reporter of openhab#20091 is asked to try it.

Before you test the login: copy userdata/jsondb/amazonechocontrol%3Aaccount%3A<your account>.json aside. With openHAB stopped, putting it back restores the old session should anything go wrong.

SHA-256 7a89a8a128da0ca2cadc274c2d53c63a3b058b04f0be56a4fab7a8b558139a5a.

To test: uninstall the store amazonechocontrol binding, drop the jar into the addons folder (velocity-engine-core-2.3.jar must be present there as well, it is a feature dependency not contained in the jar).

amazonechocontrol: combined test build 9 (main state plus experimental Sonos media-twin support)

Combined test build for openHAB 5.2.x, superseding amazonechocontrol-all-fixes-test-8: everything merged into main since 5.2.0 plus one experimental change that has no pull request yet.

Merged since 5.2.0, all included:

• openhab#21439 - Improve handling of throttled notification polls (ML19821)
• openhab#21442 - Poll notifications only while a channel is linked (ML19821)
• openhab#21492 - Use one logger for requests and responses (ML19821)
• openhab#21514 - Reach the voice history without push events (ML19821)
• openhab#21515 - Send a browser user agent on the notification poll (ML19821)
• openhab#21557 - Add MAC address to discovery, including the limit-MAC-lookups update (ballle98)
• openhab#21446 - Buffer push stream data until a message is complete (ML19821, merged 2026-09-02)
• openhab#21516 - Handle PUSH_DND_STATE_CHANGE push messages (ML19821, merged 2026-09-01)
• openhab#21561 - Restart dispatcher on login (ML19821, merged 2026-09-02)
• openhab#21575 - Browser agent on all notification calls (ML19821, merged 2026-09-03)
• openhab#21573 - Fix the servlet login after a logout (ML19821, merged 2026-09-03, complete)
• openhab#21583 - Keep rejected-request traces at DEBUG (ML19821, merged 2026-09-04): a request Amazon rejects logs one line, with the stack trace when the logger is at DEBUG, otherwise the same message at WARN

Experimental, open pull request openhab#21592 (issue openhab#21591, one line of logic):

• Keep third-party media devices online. Amazon lists Sonos speakers as family THIRD_PARTY_AVS_MEDIA_DISPLAY and reports them offline permanently, so a thing on such a serial never left OFFLINE. With this build it goes ONLINE and its media channels fill: player, title, subtitle, provider, image, progress, volume, and PAUSE/PLAY work through the player channel. Field-tested on one Sonos Move. To try it: create an echo thing by hand with the serial number of a MEDIA_DISPLAY entry from the binding's servlet page (http://:8080/amazonechocontrol), link player and title, play something through Alexa or the Sonos app. Shuffle on a radio station still answers 400, that is Amazon saying the content has no shuffle control.

Before you test the login: copy userdata/jsondb/amazonechocontrol%3Aaccount%3A<your account>.json aside. With openHAB stopped, putting it back restores the old session should anything go wrong.

SHA-256 98957abaf097d214260419b36a6e4483189feb918ea5b3dfd795e675178a4e1e.

To test: uninstall the store amazonechocontrol binding, drop the jar into the addons folder (velocity-engine-core-2.3.jar must be present there as well, it is a feature dependency not contained in the jar).

amazonechocontrol: combined test build 8 (all fixes since 5.2.0, rejected-request traces at DEBUG after review)

Superseded by test-9, which adds experimental support for Sonos media-twin devices. No known defect in this build, it equals main.

Combined test build for openHAB 5.2.x, superseding amazonechocontrol-all-fixes-test-7: everything merged into main since 5.2.0, no open pull request left.

Merged since 5.2.0, all included:

• openhab#21439 - Improve handling of throttled notification polls (ML19821)
• openhab#21442 - Poll notifications only while a channel is linked (ML19821)
• openhab#21492 - Use one logger for requests and responses (ML19821)
• openhab#21514 - Reach the voice history without push events (ML19821)
• openhab#21515 - Send a browser user agent on the notification poll (ML19821)
• openhab#21557 - Add MAC address to discovery, including the limit-MAC-lookups update (ballle98)
• openhab#21446 - Buffer push stream data until a message is complete (ML19821, merged 2026-09-02)
• openhab#21516 - Handle PUSH_DND_STATE_CHANGE push messages (ML19821, merged 2026-09-01)
• openhab#21561 - Restart dispatcher on login (ML19821, merged 2026-09-02)
• openhab#21575 - Browser agent on all notification calls (ML19821, merged 2026-09-03)
• openhab#21573 - Fix the servlet login after a logout (ML19821, merged 2026-09-03, complete)
• openhab#21583 - Keep rejected-request traces at DEBUG (ML19821, merged 2026-09-04): a request Amazon rejects logs one line, with the stack trace when the logger is at DEBUG, otherwise the same message at WARN

Open: none. This build equals the amazonechocontrol state of main on 2026-09-04, built for 5.2.x.

Before you test the login: copy userdata/jsondb/amazonechocontrol%3Aaccount%3A<your account>.json aside. With openHAB stopped, putting it back restores the old session should anything go wrong.

SHA-256 f386630d60f453b21d46d61e3cab78914a544c15ae8d93cc44b26e8b81c9d81d.

To test: uninstall the store amazonechocontrol binding, drop the jar into the addons folder (velocity-engine-core-2.3.jar must be present there as well, it is a feature dependency not contained in the jar).

amazonechocontrol: combined test build 7 (all fixes since 5.2.0, servlet login fix, rejected-request traces at DEBUG)

Superseded by test-8, which logs a rejected request once at one level after the review on openhab#21583. No known defect in this build.

Combined test build for openHAB 5.2.x, superseding amazonechocontrol-all-fixes-test-6: everything merged into main since 5.2.0 plus the one open pull request.

Merged since 5.2.0, all included:

• openhab#21439 - Improve handling of throttled notification polls (ML19821)
• openhab#21442 - Poll notifications only while a channel is linked (ML19821)
• openhab#21492 - Use one logger for requests and responses (ML19821)
• openhab#21514 - Reach the voice history without push events (ML19821)
• openhab#21515 - Send a browser user agent on the notification poll (ML19821)
• openhab#21557 - Add MAC address to discovery, including the limit-MAC-lookups update (ballle98)
• openhab#21446 - Buffer push stream data until a message is complete (ML19821, merged 2026-09-02)
• openhab#21516 - Handle PUSH_DND_STATE_CHANGE push messages (ML19821, merged 2026-09-01)
• openhab#21561 - Restart dispatcher on login (ML19821, merged 2026-09-02)
• openhab#21575 - Browser agent on all notification calls (ML19821, merged 2026-09-03)
• openhab#21573 - Fix the servlet login after a logout (ML19821, merged 2026-09-03; this build carries it at 2df578e, without the follow-up commit that only changes a log line)

Open, at their current state:

• openhab#21583 - Keep rejected-request traces at DEBUG (ML19821, fixes openhab#21577): a request Amazon rejects logs one WARN line with the cause, the stack trace moves to DEBUG. Field-tested with shuffle to a device with nothing playing.

Before you test the login: copy userdata/jsondb/amazonechocontrol%3Aaccount%3A<your account>.json aside. With openHAB stopped, putting it back restores the old session should anything go wrong.

SHA-256 f88b217abdc734f2f97be3ea1c7aace64e743cf21a95f945654b3bd9f1011f07.

To test: uninstall the store amazonechocontrol binding, drop the jar into the addons folder (velocity-engine-core-2.3.jar must be present there as well, it is a feature dependency not contained in the jar).

amazonechocontrol: combined test build 6 (all fixes since 5.2.0, dispatcher fix, servlet login fix, reminder fix)

Superseded by test-7, which keeps the stack traces of rejected Amazon requests at DEBUG. No known defect in this build.

Combined test build for openHAB 5.2.x, superseding amazonechocontrol-all-fixes-test-5: everything merged into main since 5.2.0 plus the two open pull requests.

Merged since 5.2.0, all included:

• openhab#21439 - Improve handling of throttled notification polls (ML19821)
• openhab#21442 - Poll notifications only while a channel is linked (ML19821)
• openhab#21492 - Use one logger for requests and responses (ML19821)
• openhab#21514 - Reach the voice history without push events (ML19821)
• openhab#21515 - Send a browser user agent on the notification poll (ML19821)
• openhab#21557 - Add MAC address to discovery, including the limit-MAC-lookups update (ballle98)
• openhab#21446 - Buffer push stream data until a message is complete (ML19821, merged 2026-09-02)
• openhab#21516 - Handle PUSH_DND_STATE_CHANGE push messages (ML19821, merged 2026-09-01)
• openhab#21561 - Restart dispatcher on login (ML19821, merged 2026-09-02)

Open, at their current state:

• openhab#21573 - Fix the servlet login after a logout (ML19821): the login dialog stays on its own host, echoed links are translated back, the browser's identity is passed on, redirect(false) really stops. Field-tested: Logout on the servlet page, then sign in again with e-mail and password, account back ONLINE.
• openhab#21575 - Browser agent on all notification calls (ML19821): creating a reminder through the remind channel works again instead of failing with 400 ThrottlingException. Field-tested on a production system.

Before you test the login: copy userdata/jsondb/amazonechocontrol%3Aaccount%3A<your account>.json aside. With openHAB stopped, putting it back restores the old session should anything go wrong.

SHA-256 8df773a90c11dc41a306eae7d7af5a2ebbd97b024f78af1278212725fdb395c1.

To test: uninstall the store amazonechocontrol binding, drop the jar into the addons folder (velocity-engine-core-2.3.jar must be present there as well, it is a feature dependency not contained in the jar).

amazonechocontrol: combined test build 5 (all fixes since 5.2.0, dispatcher fix, servlet login fix)

Superseded by test-6, which adds the reminder fix (browser agent on all notification calls). No known defect in this build.

Combined test build for openHAB 5.2.x, superseding amazonechocontrol-all-fixes-test-4: everything merged into main since 5.2.0 plus the two open pull requests.

Merged since 5.2.0, all included:

• openhab#21439 - Improve handling of throttled notification polls (ML19821)
• openhab#21442 - Poll notifications only while a channel is linked (ML19821)
• openhab#21492 - Use one logger for requests and responses (ML19821)
• openhab#21514 - Reach the voice history without push events (ML19821)
• openhab#21515 - Send a browser user agent on the notification poll (ML19821)
• openhab#21557 - Add MAC address to discovery, including the limit-MAC-lookups update (ballle98)
• openhab#21446 - Buffer push stream data until a message is complete (ML19821, merged 2026-09-02)
• openhab#21516 - Handle PUSH_DND_STATE_CHANGE push messages (ML19821, merged 2026-09-01)

Open, at their current state:

• openhab#21561 - Restart dispatcher on login (ML19821)
• openhab#21573 - Fix the servlet login after a logout (ML19821): the login dialog stays on its own host, echoed links are translated back, the browser's identity is passed on, redirect(false) really stops. Field-tested on a production system: Logout on the servlet page, then sign in again with e-mail and password, account back ONLINE.

Before you test the login: copy userdata/jsondb/amazonechocontrol%3Aaccount%3A<your account>.json aside. With openHAB stopped, putting it back restores the old session should anything go wrong.

SHA-256 74ee41d64d28af77f802be43099b86b735f7b72d3bc5413788a567973341d584.

To test: uninstall the store amazonechocontrol binding, drop the jar into the addons folder (velocity-engine-core-2.3.jar must be present there as well, it is a feature dependency not contained in the jar).