search

eschava / node-red-contrib-hourglass

Node-red node calculating elapsed time
4 stars 2 forks source link

Persistance ID passed in via Input message #15

Open Adrian-IAconnects opened 3 months ago

Adrian-IAconnects commented 3 months ago

Use case: Room/Desk occupied time tracking.

Issue: We have applications where by we have motion sensors in large quantities of desks or rooms which we are stopping/starting the hourglass node based on the occupied state. With the current implementation we have to have a node per room/desks. Ideally being able to dynamically pass in a persistanceID from the sensor name would mean i only need 1 hourglass node.

Fix: Implement an input as msg.persistantID

eschava commented 3 months ago

Persistence ID is used only for persisting node state to a file but the node also stores its state inside memory structures. So depending on the received persistantID it should behave as multiple nodes and store state for each of them separately This will make its implementation and usage too cumbersome.

Have you considered creating a subflow and reusing it for each room?

Adrian-IAconnects commented 3 months ago

Are you saying that I can pass a persistantID or not at this stage I am a bit confused as you counter your suggestion with it being too cumbersome?

Obviously, I am trying to avoid multiple instances of a node whether it be the hourglass node or a subflow node as we’re talking hundreds here and arranging them on a flow will be painful. Unfortunately, I don’t see you suggestion reducing the quantity of nodes unless I’ve misunderstood.

Thanks

Adrian Grimmett Software Integration Engineer

[cid:iac_horizontal_gradient_c0e2c8fb-1e30-4563-a416-4ed09c9b623f.png]

M: +44 7803 486 651<tel:+44%207803%20486%20651> T: +44(0)1491 845 505<tel:+44(0)1491%20845%20505> @.**@.> | www.iaconnects.co.ukhttp://www.iaconnects.co.uk https://www.facebook.com/user_name_here https://www.linkedin.com/company/user_name_here [cid:003_sm_in_610e655e-a302-4d87-ae26-377ce3e93934.png] https://www.linkedin.com/company/iaconnects https://www.twitter.com/user_name_here [cid:003_sm_twitter_ac632f2d-acfa-45dc-872a-d62866a18eee.png] https://twitter.com/iaconnects https://www.instagram.com/user_name_here [cid:iaconnectsemail2023-general_f49f8225-3735-4d67-82ca-930d95ee7b7a.png] Notice: This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of IAconnects Technology Ltd. If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone. Please contact the sender if you believe you have received this email in error.

IAconnects Technology Limited trading as iaconnects is a company registered in England. ​Registered number: 05079414. Registered office: Chiltern House, 45 Station Road, Henley-On-Thames, Oxfordshire, RG9 1AT.

BuildingSight® is a registered trademark of IAconnects Technology Limited.

From: Eugene Schava @.> Sent: Wednesday, August 28, 2024 1:10 PM To: eschava/node-red-contrib-hourglass @.> Cc: Adrian Grimmett @.>; Author @.> Subject: Re: [eschava/node-red-contrib-hourglass] Persistance ID passed in via Input message (Issue #15)

Persistence ID is used only for persisting node state to a file but the node also stores its state inside memory structures. So depending on the received persistantID it should behave as multiple nodes and store state for each of them separately This will make its implementation and usage too cumbersome.

Have you considered creating a subflow and reusing it for each room?

— Reply to this email directly, view it on GitHubhttps://github.com/eschava/node-red-contrib-hourglass/issues/15#issuecomment-2315150964, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A7OYQL5G5TB4ZHST4PNUS2LZTW4ZDAVCNFSM6AAAAABNID2BNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJVGE2TAOJWGQ. You are receiving this because you authored the thread.Message ID: @.***>

eschava commented 3 months ago

no, I meant that adding this new feature will make the node implementation too difficult

and if you already have hundreds of sensor nodes you can combine them with their hourglass nodes using subflows