Where is zp config

Usually this will be a restored S2 player, but there's no guarantee, especially after clearing the cached accessories. This could cause HomeKit to drop accessories, treating them as new accessories when re-exposed, losing any association to HomeKit rooms, groups, scenes, and automations.

To prevent this, set forceS2 in config. If you run into Homebridge startup issues, please double-check what versions of Node. Other versions might or might not work - I simply don't have the bandwidth to test these. This way, you can determine whether the issue is related to Homebridge ZP itself, or to the interaction of multiple Homebridge plugins in your setup.

You can start this separate instance of Homebridge on a different system, as a different user, or from a different user directory specified by the -U flag. Make sure to use a different Homebridge name , username , and if running on the same system port in the config. Homebridge ZP outputs an info message for each HomeKit characteristic value it sets and for each HomeKit characteristic value change notification it receives.

When Homebridge is started with -D , Homebridge ZP outputs a debug message for each request it makes to a Sonos zone player and for each zone player notification event it receives. Like the Sonos app, Homebridge ZP subscribes to the zone player events to be notified in real-time of changes.

It creates a web server to receive these notifications. The IP address and port number for this listener are logged in a debug message, e. To check whether the listener is reachable from the network, open this URL in your web browser.

You should see an overview of the active subscriptions per zone player. If you have a question, please post a message to the zp channel of the Homebridge community on Discord. If you encounter a problem, please open an issue on GitHub.

Please attach a copy of homebridge. Homebridge ZP is a hobby project of mine, provided as-is, with no warranty whatsoever. I've been running it successfully at my home for years, but your mileage might vary. The HomeKit terminology needs some getting used to.

An accessory more or less corresponds to a physical device, accessible from your iOS device over WiFi or Bluetooth. A bridge like Homebridge is an accessory that provides access to other, bridged, accessories. An accessory might provide multiple services. Each service corresponds to a virtual device like a lightbulb, switch, motion sensor, Siri interacts with services, not with accessories. A service contains one or more characteristics. A characteristic is like a service attribute, which might be read or written by HomeKit apps.

You might want to checkout Apple's HomeKit Accessory Simulator , which is distributed as an additional tool for Xcode. The Sonos terminology needs some getting used to. A zone corresponds to a physical room. It consists of a single zone player, two zone players configured as a stereo pair, or a home theatre setup e.

Typically, zone setup is static; you would only change it when physically re-arranging your zone players between rooms. A zone group is a collection of one or more zones, playing the same music in sync.

A zone group is controlled by its coordinator zone. Controls for volume and mute act on a zone group or on a single zone. Controls for bass, treble, and loudness act on a single zone. Note that Sonos uses the term room ambiguously: on the Sonos app main screen it corresponds to a zone group, but in the Room Settings it corresponds to a zone.

Git github. All rights reserved. Note that Sonos doesn't support events for these, so Homebridge ZP cannot provide real-time monitoring for this; Includes command-line tools, for controlling Sonos zone players and for troubleshooting. GinaW Member. November in General support. I placed this file in the root directory so it wasnt accessible from the web.

I then changed the code in the zp-config. I know you can do this easily with Worpress by simply dumping the wp-config. Any advice? November That file must be within the zp-data folder. Just why do you want to move this file anyway? Moving it will not make it safer. Only proper security measures such as only allowing owner access to the zp-core folder will do that.

Anyway, if you are refering to the threads on this forum about that file being compromised, that was most likely caused by the site administrators not removing the setup files, not by someone actually accessing your server and the folder directly.

Unless, of course, you have no folder security. In which case it does not matter where you move it, it will still be vulnerable. September Old post I know but I've been having problems with the config file getting corrupted as well. Quite often in fact. Luckily, I simply replace the file with a known good one and all is well - but it's annoying because my clients hate seeing the error. I have to constantly monitor my sites which is time consuming.

What should the permissions be for zp-data folder?? Also what other steps can be taken so this stops happening? Thanks, Mike. I am sorry for these issues. I fear I cannot really help as I have never encountered this on several sites with several shared hosts. Normally the file is not even touched unless you change things.

As Setup suggests the files in zp-data should be You need a server to run Homebridge. This can be anything running Node. See the Homebridge Wiki for details. As Sonos uses UPnP to discover the zone players, the server running Homebridge must be on the same subnet as your Sonos zone players. Homebridge ZP creates an accessory per Sonos zone, named after the zone, e. Living Room Sonos for the Living Room zone. By default, this accessory contains a single Switch service, with the same name as the accessory.

Additional characteristics control volume, select input, change track, etc. However, neither Apple's Home app nor Siri support these. Note that speaker support in Apple's Home app is based on the AirPlay2 protocol.

Despite the "HomeKit" branding, technically, this has nothing to do with HomeKit. No Homebridge plugin can expose speakers that look like AirPlay2 speakers in the Home app. Also note that these Airplay2 speakers cannot be accessed by other HomeKit apps.

When "tv": true is set in config. Note that Apple has imposed some technical restrictions on Television accessories:. When multiple Sonos zones, e. Living Room and Kitchen , are grouped into one Sonos group, the Sonos app shows them as a single room, e. When this group is broken, each zone forms a separate standalone group, containing only that zone. If Homebridge ZP would mimic this behaviour, dynamically creating and deleting accessories for groups, HomeKit would lose the assignment to HomeKit rooms, groups, scenes, and automations, every time an accessory is deleted.

Consequently, you would have to reconfigure HomeKit each time you group or ungroup Sonos zones. To overcome this, Homebridge ZP creates an accessory and corresponding service for each Sonos zone. This service actually controls the Sonos group the zone is in rather than the zone. When separated, the Living Room Sonos service controls the standalone Living Room group, consisting of only the Living Room zone; and the Kitchen Sonos service controls the standalone Kitchen group, consisting of only the Kitchen zone.

The Sonos Group characteristic shows which group the zone belongs to, or rather: the name of the group coordinator zone, in this example: Living Room. So does changing the Kitchen Sonos Volume. When ungrouped, changing the Living Room Sonos Volume only changes the volume of the Living Room zone; and changing the Kitchen Sonos Volume only changes the volume of the Kitchen zone. To change the volume of an individual zone in a multi-zone group, an additional Volume characteristic is needed for the zone, next to the Volume characteristic for the group.

As HomeKit doesn't support multiple characteristics of the same type per service, it actually requires an additional service. By specifying "speakers": true in config. This service is named after the zone as well, in our example: Living Room Speakers. The Speakers service On characteristic is used to join, or leave a Sonos group. On is set, when the zone is a member of other zone's group. It is clear, when the zone is the coordinator of it's own group either standalone or with other zones as member.

By setting On , the zone will join groups with the target coordinator. The target coordinator is set using the Sonos Coordinator characteristic in the Sonos service. By clearing On , the zone will leave the group and become coordinator of a standalone group. Additional characteristics for Volume , Mute , Bass , Treble , and Loudness control the corresponding zone attributes.

Note that Bass , Treble , and Loudness are custom characteristics. They might not be supported by all HomeKit apps, see Caveats below. Like the Sonos service, the type of the Speakers service can be changed in config.

Homebridge ZP includes a command-line tool, zp , to interact with your Sonos Zone Players from the command line. It takes a -h or --help argument to provide a brief overview of its functionality and command-line arguments. In Homebridge's config. Below is an example config. If you have a split Sonos system, Homebridge ZP will expose either the S2 or the S1 zone players, depending on which player is quickest to respond during discovery. Usually this will be a restored S2 player, but there's no guarantee, especially after clearing the cached accessories.

This could cause HomeKit to drop accessories, treating them as new accessories when re-exposed, losing any association to HomeKit rooms, groups, scenes, and automations.

To prevent this, set forceS2 in config.