Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebSocket SourceRef is not handled correctly in source priorities #1747

Open
tkurki opened this issue May 30, 2024 · 0 comments
Open

WebSocket SourceRef is not handled correctly in source priorities #1747

tkurki opened this issue May 30, 2024 · 0 comments

Comments

@tkurki
Copy link
Member

tkurki commented May 30, 2024

SourcePriorities uses ws-victron.local:3000.XX as the source reference, but the incoming data actually has ws-victron.local:3000.192.168.1.127 as the value, so the source priorities mechanism never works correctly.

May 30 22:23:15 2024-05-30T20:23:15.000Z signalk-server:sourcepriorities Map(2) { 'ws-victron.local:3000.XX' => { precedence: 0, timeout: '' }, 'can00.c1321419e76cf955' => { precedence: 1, timeout: '5000' } }
May 30 22:23:15 2024-05-30T20:23:15.003Z signalk-server:sourcepriorities { precedence: 1, timeout: '5000' }
May 30 22:23:15 2024-05-30T20:23:15.005Z signalk-server:sourcepriorities { precedence: Infinity, timeout: 10000 }
May 30 22:23:15 2024-05-30T20:23:15.006Z signalk-server:sourcepriorities can00.c1321419e76cf955 true
May 30 22:23:15 2024-05-30T20:23:15.008Z signalk-server:sourcepriorities environment.water.temperature:ws-victron.local:3000.192.168.1.127:3000:false:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant