notifications.notifications
Hi signalk users. Moving into using alarms and alerts. I have modified some paths and added zones in the metadata using the browser. Now i have duplicate notifications.notifications paths for some of these paths. What controls the creation of these? How can this be controlled? How do I cleanup what has been created? Point me to any documentation Please.
12 Replies
Can you provide more details? Show your zones config and exatly what the "notifications.notifications" look like in the browser.
Do you have zones defined by the older @signalk/zones plugin? I think it can cause this issue. (check AppStore installed / source under Data Browser)
To migrate zone configuration from @signalk/zones plugin to use SK server directly, under SK Data Browser, click edit and then save for each path with a zone shown . Then disable then @signalk/zones plugin.
Cleanup: after removing @signalk/zones plugin try restarting SK ... that may help but you might have to edit baseDeltas.json
Cleanup: after removing @signalk/zones plugin try restarting SK ... that may help but you might have to edit baseDeltas.json
Thanks for replys. @David Sanner i dont have zones plugin. @Scott Bender This is the Data browser
You might start by making a copy of baseDeltas.json and then removing the issues - though you have to keep the json format regular (remove all between and including {}, if last remove the trailing comma).
I've seen this pop up when I had @signalk/zones but I think what is likely happening in your case is that if you edit the meta data of a notifications.xxx.xxx entry under "Data Browser" and save it, the notification entry gets stored in baseDeltas.js which then can have the duplicate notification.notification issue after sk restarts.
I've seen this pop up when I had @signalk/zones but I think what is likely happening in your case is that if you edit the meta data of a notifications.xxx.xxx entry under "Data Browser" and save it, the notification entry gets stored in baseDeltas.js which then can have the duplicate notification.notification issue after sk restarts.
@David Sanner manually removing the invalid entries from the json has resolved the issue. Still unsure why it happen, maybe i edited the notification. metadata accidently and this cause the issue. In fact on testing if you edit the automatically created notification metadata object this is the effect.
For clarity editing the circled red item.
That's what I'm thinking & my testing yesterday showed the same. Glad you could edit manually.
Not sure the fix for others, maybe a delete button or special case that removes the edit feature for paths that start with notification? Perhaps open an issue w/ SK server on github just to make sure the issue is known.
Not sure the fix for others, maybe a delete button or special case that removes the edit feature for paths that start with notification? Perhaps open an issue w/ SK server on github just to make sure the issue is known.
Same problem here. Sorry for my noob question, but how do I edit this file, and where do I find it? Any help much appreciated. My meta is full of notifications 😦
Just to confirm I can also recreate this by accidentally editing the notifications path, and that then creates another one notifications.notifications. Also fixed by editing the base file. I've sent a guide to Rosea to try and help
👍could ypu please create an issue about this? Needs fixing
I just created a new issue for this https://github.com/SignalK/signalk-server/issues/1897
created a fix that should take care of it