Send Motion-user mailing list submissions to
        motion-user@lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
        motion-user-requ...@lists.sourceforge.net

You can reach the person managing the list at
        motion-user-ow...@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."


Today's Topics:

   1. Re: Getting an Equal Sign (=) into on-Screen Text (John Vaccaro)


----------------------------------------------------------------------

Message: 1
Date: Fri, 27 Nov 2020 20:23:15 -0500
From: John Vaccaro <jvacc...@gmail.com>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] Getting an Equal Sign (=) into on-Screen
        Text
Message-ID: <d9173f35-7671-4884-ce06-7e68087a4...@gmail.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Hello;

My Bash code appends a plus, minus or equal sign to indicate the 
direction of change in the atmospheric pressure. The plus and minus 
signs display just fine, The equal sign does not display. I'm using %3D 
as the symbology to be interpreted by motion as an equal sign.

Has anyone else encountered this feature ;-) My code logs the exact 
string that curl feeds to Motion and everything interprets correctly 
except the equal sign. The percent sign (Hex %25) also is not displayed.

Screen grab:

Log snippet:
*john@arach:~/Dropbox/Code/motionwx$ tail -7 motionwx.log **
*
/Overcast%2055F%20Humidity%3A55%25\nWind%20Northwest@{3}mph%20Press%3A30.08%22%3D//
//Old Pressure Reading: 30.08//
//Pressure Change: %3D=//
//New Pressure Reading:30.08//
//removed 'motionwx.lck'//
//November 27, 2020 - 20:02:07? motionwx (PID:1100338) update of WX to 
send to Motion server FINISHED/

-- 

All the Best?

/John /

On 11/18/20 4:36 AM, tosiara wrote:
> Try to update to 4.3.2
>
> On Wed, Nov 18, 2020 at 1:21 AM John Vaccaro <jvacc...@gmail.com 
> <mailto:jvacc...@gmail.com>> wrote:
>
>     Hello;
>
>     Any update on where this bug stands in the list of priorities and
>     when a fix might be expected?
>
>     If anyone has found a workaround that will let me display the
>     percent sign (%) in the text overlays, I'd be pleased to hear it.
>
>     -- 
>
>     All the Best?
>
>     /John /
>
>     On 10/20/20 7:17 AM, tosiara wrote:
>>     When using curl to communicate with motion, all the params must
>>     be URL-encoded as required by HTTP protocol. Percent symbols is a
>>     special one that is used to encode hex values. In order to use
>>     percent symbol as is it is required to encode it as double
>>     percent: %%, or as a hex value (like you are using) %25
>>
>>     However, the percent symbol is also a reserved special symbol in
>>     motion. So after the URL conversion you will end up having a
>>     string with a trailing percent sign. Which confuses motion as it
>>     expects a specifier to follow.
>>
>>     Registered as a bug:
>>     https://github.com/Motion-Project/motion/issues/1227
>>
>>
>>     On Mon, Oct 12, 2020 at 11:41 PM John Vaccaro <jvacc...@gmail.com
>>     <mailto:jvacc...@gmail.com>> wrote:
>>
>>         Hello Motion Users;
>>
>>         I'm using Motion 4.3.1-1 on a Raspberry Pi 3 Model2? using
>>         PiOS (Raspbian GNU/Linux 10 (buster); Kernel 5.4.51-v7 5.4.51-v7)
>>
>>         All is working as advertised and I have bash code to collect
>>         weather and rainfall stats and put them into the picture
>>         using text_left via /curl/.
>>
>>         The problem I'm encountering is trying to include the Percent
>>         sign (%) after the humidity level.
>>
>>         No amount of jiggering will get the % appended to the
>>         humidity value.
>>
>>         This is the string I am feeding to string_left that works
>>         correctly:
>>         /Partly%20Cloudy%2079F%20Humidity%3A60\nWind:South@{10}mph/
>>
>>         This string gets me an error message from Motion daemon:
>>         /Mostly%20Cloudy%2081F%20Humidity%3A58%25\nWind:South@{11}mph/
>>
>>         The error message is *The server did not understand your
>>         request.*
>>
>>         What do I do to protect the /%/ sign or its hex equivalent
>>         /%25/ from having Motion interpret**the string as a hex code
>>         other than that of the percent sign?*
>>         *
>>
>>         -- 
>>
>>         All the Best?
>>
>>         /John /
>>         _______________________________________________
>>         Motion-user mailing list
>>         Motion-user@lists.sourceforge.net
>>         <mailto:Motion-user@lists.sourceforge.net>
>>         https://lists.sourceforge.net/lists/listinfo/motion-user
>>         https://motion-project.github.io/
>>
>>         Unsubscribe:
>>         https://lists.sourceforge.net/lists/options/motion-user
>>
>>
>>
>>     _______________________________________________
>>     Motion-user mailing list
>>     Motion-user@lists.sourceforge.net  
>> <mailto:Motion-user@lists.sourceforge.net>
>>     https://lists.sourceforge.net/lists/listinfo/motion-user
>>     https://motion-project.github.io/
>>
>>     Unsubscribe:https://lists.sourceforge.net/lists/options/motion-user
>
>
>
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user

-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hhbajaflffnpfdde.png
Type: image/png
Size: 28223 bytes
Desc: not available

------------------------------



------------------------------

Subject: Digest Footer

_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user


------------------------------

End of Motion-user Digest, Vol 173, Issue 14
********************************************

Reply via email to