You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently I code at my labtop and test at respberry pi. I pre-defined some contacts as triggers( only reply when A send me messages). I am using talker id from message.payload. But in most case there is no reply due to the talker id has been changed.
First, I login and use another account to send test message, then I logout and try again. The talker id's are different.
Is this normal that talker id keeps changing or how can i target a contact if not using talker id?
here are logs of messages:
First time:
WechatifiedMessageImpl {
_events: [Object: null prototype] {},
_eventsCount: 0,
_maxListeners: undefined,
id: '1965***',
payload: {
id: '1965***',
talkerId: '@E69C***',
text: 'test',
timestamp: 1697***,
type: 7,
listenerId: '@0c56***'
},
[Symbol(kCapture)]: false
}
Recently I code at my labtop and test at respberry pi. I pre-defined some contacts as triggers( only reply when A send me messages). I am using talker id from message.payload. But in most case there is no reply due to the talker id has been changed.
First, I login and use another account to send test message, then I logout and try again. The talker id's are different.
Is this normal that talker id keeps changing or how can i target a contact if not using talker id?
here are logs of messages:
First time:
WechatifiedMessageImpl {
_events: [Object: null prototype] {},
_eventsCount: 0,
_maxListeners: undefined,
id: '1965***',
payload: {
id: '1965***',
talkerId: '@E69C***',
text: 'test',
timestamp: 1697***,
type: 7,
listenerId: '@0c56***'
},
[Symbol(kCapture)]: false
}
Second Time:
WechatifiedMessageImpl {
_events: [Object: null prototype] {},
_eventsCount: 0,
_maxListeners: undefined,
id: '5645***',
payload: {
id: '5645***',
talkerId: '@d5e7***',
text: 'lk',
timestamp: 1697***,
type: 7,
listenerId: '@CDC1***'
},
[Symbol(kCapture)]: false
}
The text was updated successfully, but these errors were encountered: