Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / hklages/node-red-contrib-sonos-events issues and pull requests

#16 - Sonos port is regularly no longer recognized and displayed as disconnected in „events“ node

Issue - State: closed - Opened by Tonitom 7 months ago - 17 comments
Labels: documentation, solved

#15 - Issue with RenderingControl mutestate function always returning "off" even when Sonos speaker is muted

Issue - State: closed - Opened by dobdib 7 months ago - 10 comments
Labels: bug, solved

#14 - update dependencies

Pull Request - State: closed - Opened by hklages 8 months ago

#13 - No callbacks after switch off and on of a player at the event node

Issue - State: closed - Opened by bwatconbee 11 months ago - 2 comments

#12 - node-red and sonos-events

Issue - State: closed - Opened by jackc94 over 1 year ago - 2 comments

#11 - discover fix

Pull Request - State: closed - Opened by hklages almost 2 years ago

#10 - 1.2.0 discovery

Pull Request - State: closed - Opened by hklages almost 2 years ago

#9 - 1.1.0 before testing including DNS

Pull Request - State: closed - Opened by hklages over 2 years ago

#8 - Possible to add changing power source / battery level of Sonos Move/Roam as an event?

Issue - State: closed - Opened by mac89muc almost 3 years ago - 2 comments

#7 - Events can't be selected

Issue - State: closed - Opened by Blomus almost 3 years ago - 6 comments
Labels: awaiting feedback

#6 - Cannot get feedback from SONOS player / group / household

Issue - State: closed - Opened by JoeWiseman over 3 years ago - 5 comments
Labels: documentation, solved

#5 - Http admin and Prefix for player and listener ip discovery

Pull Request - State: closed - Opened by hklages over 3 years ago

#4 - How to listen on alarm clock event?

Issue - State: closed - Opened by dprokscha over 3 years ago - 10 comments
Labels: solved

#3 - Incorrect IP for listener

Issue - State: closed - Opened by patrickharris over 3 years ago - 26 comments
Labels: solved

#2 - No output via AVTransport content on track changes

Issue - State: closed - Opened by j-p-l almost 4 years ago - 4 comments

#1 - No Player / No Listener hostname found in Docker environment

Issue - State: closed - Opened by xX-Nexus-Xx almost 4 years ago - 3 comments
Labels: documentation, solved