shart

i may be stupid, im not a code guy so this is unfamiliar territory for me,
im getting in the message log
> Recieved 'Trigger' message (subaddress: '|openhangar')
> Unknown subaddress '|openhangar'

i have put the subaddresses in the custom data as such
; EXAMPLE:
; ----------------------------------------
; Receive timer subaddresses=
; |primary,Timer Block 1
; |secondary,Timer Block 2
; |tertiary,Timer Block 3
Receive timer subaddresses=
|openhangar,crumphangar
|opensilo,opensilo

this is on the recieving grid,

code version"1.3.4"

i may be missing something obvious, sorry for being the first person to be confused at how to use this in 2 years

Originally posted by Flop:

i may be stupid, im not a code guy so this is unfamiliar territory for me,
im getting in the message log
> Recieved 'Trigger' message (subaddress: '|openhangar')
> Unknown subaddress '|openhangar'

i have put the subaddresses in the custom data as such
; EXAMPLE:
; ----------------------------------------
; Receive timer subaddresses=
; |primary,Timer Block 1
; |secondary,Timer Block 2
; |tertiary,Timer Block 3
Receive timer subaddresses=
|openhangar,crumphangar
|opensilo,opensilo

this is on the recieving grid,

code version"1.3.4"

i may be missing something obvious, sorry for being the first person to be confused at how to use this in 2 years

The subaddress is "openhangar", not "|openhangar". Remove the pipe symbol.

Thank you, i feel stupid now, but at least my hangar opens when i press a button now. thank you

Hi,

First of all I wanted to thank you for this great script. I much prefer this over the hassle of setting up multiple action relays.I wanted to bring up a small potential issue though. This concerns version 1.3.4.

I was playing with the script and setting up sub-addresses. However, I initially had trouble getting the correct timer to trigger with this custom data fragment:


Looking through your code, I found out that the issue was the whitespace between the comma and the timer block name. You are not currently trimming any whitespace (lines 397 and 398). Admittedly, whitepace in block names is a valid thing, so wholesale trimming may not be desirable per se.

Would it be possible to add a note to the documentation? It seems like one could easily and unintentionally add the space, since a space after a comma is very common. Alternatively, perhaps opting for trimming would work instead? I feel adding a comma (compared to intentionally adding whitespace to block names) would be more common.

Originally posted by jodev:

Hi,

First of all I wanted to thank you for this great script. I much prefer this over the hassle of setting up multiple action relays.I wanted to bring up a small potential issue though. This concerns version 1.3.4.

I was playing with the script and setting up sub-addresses. However, I initially had trouble getting the correct timer to trigger with this custom data fragment:

Receive timer subaddresses= |rig-ice-start, Timer Start Tap |rig-ice-stop, Timer Stop Tap

Looking through your code, I found out that the issue was the whitespace between the comma and the timer block name. You are not currently trimming any whitespace (lines 397 and 398). Admittedly, whitepace in block names is a valid thing, so wholesale trimming may not be desirable per se.

Would it be possible to add a note to the documentation? It seems like one could easily and unintentionally add the space, since a space after a comma is very common. Alternatively, perhaps opting for trimming would work instead? I feel adding a comma (compared to intentionally adding whitespace to block names) would be more common.

Note added to documentation. Whitespace sensitivity is desired and I don't want to complicate the parsing logic by adding quotation support.

Now that was quick. Thanks for the quick documentation update!