This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Changes to Zones and Notifications
#1
Raspberry pi 5, Openplotter4. Recently updated to Signalk 2.22.1 and node 22.22. I tried to change a threshold in @signalk/Zones app but it comes up with an error message when you try to save. I get that it is now redundant, and has been removed from the App Store. Metadata via Databrowser works fine once Zones app is removed (because it is not in the App Store you cannot just uninstall it). But. The Notification app starts now with an error message asking where Zones is, and now when my cpu warms up past its metadata threshold value, (state: warm) I get a notification with the message about environment.cpu.temperature, as I should, but the bilge alarm,  via gpio18 going low set in notifications   for propulsion.engine.bilge.raw, (state:Alarm), now goes off.  Why?
Reply
#2
An AI explanation is that the path propulsion.engine.bilge.raw, and other paths, is sent from SensESP via esp32 only when the engine is running. It does not contain metadata zones. These were in the old @signalk/zones app. If that app is removed, since otherwise redundant, the actions that were set up for this path in Notifications become orphaned, and can become associated with other notification events.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)