-
Notifications
You must be signed in to change notification settings - Fork 0
/
config.yml.example
142 lines (135 loc) · 6.58 KB
/
config.yml.example
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
# =========================================================
# Actuator Configuration
# =========================================================
# The configurations in this section descrbie the IoT Service Blockchain addresses of actuators the
# AI component connects to
# You may remove or add additional actuators
# The key is the `location` slot in the speech-to-intent model, e.g., `kitchen`, `living room`, and
# `bedroom`
# You can obtain `organization_id`, `device_id`, and `service_name` of each actuator from previous
# step
actuators:
kitchen:
organization_id: Org2MSP
device_id: eDUwOTo6Q049dXNlcjEsQz1VUyxTVD1Ob3J0aCBDYXJvbGluYSxPPUh5cGVybGVkZ2VyLE9VPWNsaWVudDo6Q049Y2Eub3JnMi5leGFtcGxlLmNvbSxDPVVLLEw9SHVyc2xleSxTVD1IYW1wc2hpcmUsTz1vcmcyLmV4YW1wbGUuY29t
service_name: kitchen_light_switch
# =========================================================
# Picovoice Settings
# =========================================================
# The configurations in this section descrbie the Picovoice API settings
picovoice:
# Path to the directory where wake word detection model files (.ppn) and speech-to-intent model
# files (.rhn) are placed
asset_dir: ../assets/picovoice
# Your Picovoice API access key
access_key: your_picovoice_access_key
# =========================================================
# InterPlanetary File System (IPFS) Settings
# =========================================================
# The configurations in this section descrbie the IPFS settings
ipfs:
# The path to your IPFS repository directory
# Do not use the same repository for the AI component and the assistant component if they are
# running on the same host
repo_path: /home/pi/.ipfs_ai/
# The swarm key of IPFS if you would like to connect to a private IPFS network
# Leave this field empty to connect to a public IPFS network
# This ID is generated using https://github.com/Kubuxu/go-ipfs-swarm-key-gen
swarm_key: |
/key/swarm/psk/1.0.0/
/base16/
a1eb10eea29fc978cbf7f9fd936a554cf08c53edb603ecb9d1885b2df8ba663f
# The listening multiaddrs of the current peer
swarm_addresses:
- /ip4/0.0.0.0/tcp/14001
- /ip6/::/tcp/14001
- /ip4/0.0.0.0/udp/14001/quic
- /ip6/::/udp/14001/quic
# The multiaddrs of the bootstrap peers
# Leave this empty if this peer is the bootstrap peer
bootstrap_peers: []
# =========================================================
# IoT Device Information
# =========================================================
# The configurations in this section descrbie the device on the IoT Service Blockchain
device:
device_name: voice_ai_01
device_description: IoT Voice AI
# =========================================================
# IoT Service Information
# =========================================================
# The configurations in this section descrbie the service provided by the above IoT device
service:
service_name: voice_command
service_version: 1
service_description: An AI service that translate user voice commands to intents
# =========================================================
# Hyperledger Fabric User Identity
# =========================================================
# The configurations in this section descrbie the blockchain user credentials used to connect
# to the blockchain
client:
# The exact name of your organization's membership service provider (MSP)
organization_id: Org2MSP
# Your user's certificate in PEM format
certificate: |
-----BEGIN CERTIFICATE-----
MIICqTCCAlCgAwIBAgIUOVBvmT+48dmMU8tDorKT2w5iXqAwCgYIKoZIzj0EAwIw
bDELMAkGA1UEBhMCVUsxEjAQBgNVBAgTCUhhbXBzaGlyZTEQMA4GA1UEBxMHSHVy
c2xleTEZMBcGA1UEChMQb3JnMi5leGFtcGxlLmNvbTEcMBoGA1UEAxMTY2Eub3Jn
Mi5leGFtcGxlLmNvbTAeFw0yMjAyMjQyMjU1MDBaFw0yMzAyMjQyMzAwMDBaMF0x
CzAJBgNVBAYTAlVTMRcwFQYDVQQIEw5Ob3J0aCBDYXJvbGluYTEUMBIGA1UEChML
SHlwZXJsZWRnZXIxDzANBgNVBAsTBmNsaWVudDEOMAwGA1UEAxMFdXNlcjEwWTAT
BgcqhkjOPQIBBggqhkjOPQMBBwNCAAQiudNGrkeDrwCzh1HPyKCP1vJvES63w08+
v/ixW70r3PbdMLVGxWV+CpB5i6EYfI8vaQRj4eMg/g3lD69hY86Uo4HeMIHbMA4G
A1UdDwEB/wQEAwIHgDAMBgNVHRMBAf8EAjAAMB0GA1UdDgQWBBRe0LbcLsn8Pk1d
Q7r4hs0C2TxmQjAfBgNVHSMEGDAWgBQHDyl1BrUzNWbJmnePSuKhu4o1tzAhBgNV
HREEGjAYghZpb3Qtc2VydmljZS1ibG9ja2NoYWluMFgGCCoDBAUGBwgBBEx7ImF0
dHJzIjp7ImhmLkFmZmlsaWF0aW9uIjoiIiwiaGYuRW5yb2xsbWVudElEIjoidXNl
cjEiLCJoZi5UeXBlIjoiY2xpZW50In19MAoGCCqGSM49BAMCA0cAMEQCIAD95A6M
QomoPT7VpaLCDBtjjoH50ZuzgL6pV+WT1Z1KAiBOBq3CdWdGY9/gPX+f51xDSSNl
dgf4MbjCztZVvi/dog==
-----END CERTIFICATE-----
# Your user's private signing key in PEM format
private_key: |
-----BEGIN PRIVATE KEY-----
MIGHAgEAMBMGByqGSM49AgEGCCqGSM49AwEHBG0wawIBAQQg1SQL5D+rag7hkI44
LaZAIa6D6SdmLQm8wGaLBC8DZa+hRANCAAQiudNGrkeDrwCzh1HPyKCP1vJvES63
w08+v/ixW70r3PbdMLVGxWV+CpB5i6EYfI8vaQRj4eMg/g3lD69hY86U
-----END PRIVATE KEY-----
# =========================================================
# Hyperledger Fabric Gateway Settings
# =========================================================
# The configurations in this section descrbie the connection parameters of a Hyperledger Fabric
# Gateway you connect to
gateway:
# Gateway peer's endpoint
endpoint: localhost:9051
# Gateway peer's overridden TLS server name
server_name: peer0.org2.example.com
# Gateway peer's TLS certificate in PEM format
tls_certificate: |
-----BEGIN CERTIFICATE-----
MIICHjCCAcWgAwIBAgIUerQNkSpfpb2zU04qKk2IxewztUIwCgYIKoZIzj0EAwIw
bDELMAkGA1UEBhMCVUsxEjAQBgNVBAgTCUhhbXBzaGlyZTEQMA4GA1UEBxMHSHVy
c2xleTEZMBcGA1UEChMQb3JnMi5leGFtcGxlLmNvbTEcMBoGA1UEAxMTY2Eub3Jn
Mi5leGFtcGxlLmNvbTAeFw0yMjAyMjQyMjU1MDBaFw0zNzAyMjAyMjU1MDBaMGwx
CzAJBgNVBAYTAlVLMRIwEAYDVQQIEwlIYW1wc2hpcmUxEDAOBgNVBAcTB0h1cnNs
ZXkxGTAXBgNVBAoTEG9yZzIuZXhhbXBsZS5jb20xHDAaBgNVBAMTE2NhLm9yZzIu
ZXhhbXBsZS5jb20wWTATBgcqhkjOPQIBBggqhkjOPQMBBwNCAARrbpU3+KO6EWeR
OJeIXgGlTwOYs17I0tqeddsd6keK/FfQvcrUnwG2cv0JXotQ9CZidBc+d2ecA0/Y
SOkUJp5oo0UwQzAOBgNVHQ8BAf8EBAMCAQYwEgYDVR0TAQH/BAgwBgEB/wIBATAd
BgNVHQ4EFgQUBw8pdQa1MzVmyZp3j0riobuKNbcwCgYIKoZIzj0EAwIDRwAwRAIg
RpoKAGfgo33mokiVMALoAHFNjXtpxDXDcDPb2c9oeEYCIDeEC4l219Y7JcPEzppp
yGdkh4TIcJPvsfA+0vatlNTH
-----END CERTIFICATE-----
# =========================================================
# Hyperledger Fabric Chaincode Information
# =========================================================
# The configurations in this section descrbie where to find the IoT Service Blockchain chaincode
# and smart contracts
network:
# Name of the blockchain network/channel
name: mychannel
# Name of the chaincode package
chaincode: iotservice