Recent Posts

Pages: [1] 2 3 ... 10
1
Okay, it looks like FPP 2.4.2 is almost perfect.  I can start FPPD now and it attempts to connect to my local Hass.io-based Mosquitto broker using a username/password.  However, the broker blocks the connection because the client id is "dangerous".  Here's the error I get:
Code: [Select]
1542345274: New connection from 192.168.##.## on port 1883.
[INFO] found fppmqtt on local database
1542345275: New client connected from 192.168.##.## as mosq/43:Ripw]uf_@Shb7hK (c1, k60, u'fppmqtt').
1542345275: ACL denying access to client with dangerous client id "mosq/43:Ripw]uf_@Shb7hK"
1542345275: ACL denying access to client with dangerous client id "mosq/43:Ripw]uf_@Shb7hK"


I don't know c++ but I was able to parse out that in mqtt.cpp in the MosquittoClient::Init function, the fallback if it can't find a HostName is to use nullptr, which generates the crazy client id.  I hard-coded the fallback to "falconchristmas" like so:

Code: [Select]
int MosquittoClient::Init(const std::string &username, const std::string &password)
{                                                                                                                                                                                                                 
        mosquitto_lib_init();                                                                                                                                                                                     
                                                                                                                                                                                                                   
    std::string host = getSetting("HostName");
    if (host != "") {
        m_mosq = mosquitto_new(host.c_str(), true, NULL);
    } else {
        m_mosq = mosquitto_new("falconchristmas", true, NULL);
    }
I was able to "make optimize" and am now successfully using MQTT to control FPP!


Thanks so much for this whole thing!
-Andrew
2
Falcon Player (FPP) / Re: Stupid Question Time -FPP-
« Last post by aknflyer on Today at 10:53:48 PM »
I agree. I am sticking v1.10 this year. Changes are happening to fast on v2.x for me to keep up. And I know v1.10 works for me. No need to mess up all my setup just before deployment.
What tune to issues are you having?
3
F48 Pixel Controller / Re: Lights flickering
« Last post by David Pitts on Today at 10:52:04 PM »
Are you using v2.04? If not upgrade.
4
Showing Off / Re: My New F16V3 Build
« Last post by Bos Lights on Today at 09:53:36 PM »
Nicely done 👌
5
Falcon Player (FPP) / Re: Pi sound cards from hifiberry
« Last post by jtrpop on Today at 09:05:26 PM »
Hi All,
With FPP 2.x (I'm on 2.4) it has a new audio stack and any latency issues in FPP 1.x are gone. Be sure to select the Sound Blaster as your sound card in FPP, and set volume to 70 or you will clip the output. Also be sure to set your levels on all your devices properly or all this is for not! There are more scientific ways to do this, but here is the quick & dirty version:
1. Plug in good headphones to audio output, pick a loud song and turn volume up till it distorts (70 is good for FPP with Sound Blaster Play 3), then back it down until distortion goes away.
2. Plug in audio to FM transmitter and turn on radio and put radio volume low. Now playing the same song turn up FM that gain until you hear distortion, then back gain down until it goes away.

I have attached a 100hz tone set to 0db which you can use to test with. You have now maximized your signal to noise ratio for maximum performance!
6
Falcon Player (FPP) / Upload to Falcon controller
« Last post by Cogs on Today at 09:00:25 PM »
Hi All,I am very new, haven't seen any lights flash yet.
I have wifi to fpp and eth to F48 and no problems accessing either on browser.
I'm using Xlights.
I started messing around with uploading channel map to controller and I think I broke something.
I went to Upload to Controller, E131 input definition, Falcon, it asked for IP, I gave IP of controller. Then did the same with output. 
My first upload went through but since it was my first time,,, it was wrong.
Now I went through all of my models and setup and am pretty sure its right.
I tried to upload again and it's not working.
I started playing with FPP connect and uploaded to FPP but could not upload to controller.I'm confusing myself atm and don't understand uploading to FPP vs going straight to controller.
Much appreciation
 
2018-11-15 17:07:28,368 140700374831168 log_base [INFO] Start Time: 2018-10-15_17-07-28-104. 2018-11-15 17:07:28,368 140700374831168 log_base [INFO] Log4CPP config read from /usr/share/xLights/xlights.linux.properties. 2018-11-15 17:07:28,368 140700374831168 log_base [INFO]      : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN 2018-11-15 17:07:28,368 140700374831168 log_base [INFO]     log_base : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN 2018-11-15 17:07:28,368 140700374831168 log_base [INFO]     log_conversion : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN 2018-11-15 17:07:28,368 140700374831168 log_base [INFO]     log_generatecustommodel : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN 2018-11-15 17:07:28,368 140700374831168 log_base [INFO]     log_jobpool : ALERT CRIT EMERG ERROR FATAL INFO NOTICE WARN 2018-11-15 17:07:28,368 140700374831168 log_base [INFO]     log_opengl : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN 2018-11-15 17:07:28,368 140700374831168 log_base [INFO]     log_opengl_trace : ALERT CRIT EMERG ERROR FATAL INFO NOTICE WARN 2018-11-15 17:07:28,368 140700374831168 log_base [INFO]     log_pianodata : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN 2018-11-15 17:07:28,368 140700374831168 log_base [INFO]     log_prepcustommodel : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN 2018-11-15 17:07:28,368 140700374831168 log_base [INFO]     log_render_log : ALERT CRIT EMERG ERROR FATAL NOTICE WARN 2018-11-15 17:07:28,368 140700374831168 log_base [INFO] ******* XLights main function executing. 2018-11-15 17:07:28,368 140700374831168 log_base [INFO] Main: Starting wxWidgets ... 2018-11-15 17:07:28,387 140700374831168 log_base [INFO] Start Time: 2018-10-15_17-07-28-123. 2018-11-15 17:07:28,387 140700374831168 log_base [INFO] Log4CPP config read from /usr/share/xLights/xlights.linux.properties. 2018-11-15 17:07:28,387 140700374831168 log_base [INFO]      : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN 2018-11-15 17:07:28,387 140700374831168 log_base [INFO]     log_base : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN 2018-11-15 17:07:28,387 140700374831168 log_base [INFO]     log_conversion : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN 2018-11-15 17:07:28,387 140700374831168 log_base [INFO]     log_generatecustommodel : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN 2018-11-15 17:07:28,387 140700374831168 log_base [INFO]     log_jobpool : ALERT CRIT EMERG ERROR FATAL INFO NOTICE WARN 2018-11-15 17:07:28,387 140700374831168 log_base [INFO]     log_opengl : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN 2018-11-15 17:07:28,387 140700374831168 log_base [INFO]     log_opengl_trace : ALERT CRIT EMERG ERROR FATAL INFO NOTICE WARN 2018-11-15 17:07:28,387 140700374831168 log_base [INFO]     log_pianodata : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN 2018-11-15 17:07:28,387 140700374831168 log_base [INFO]     log_prepcustommodel : ALERT CRIT DEBUG EMERG ERROR FATAL INFO NOTICE WARN 2018-11-15 17:07:28,387 140700374831168 log_base [INFO]     log_render_log : ALERT CRIT EMERG ERROR FATAL NOTICE WARN 2018-11-15 17:07:28,387 140700374831168 log_base [INFO] ******* OnInit: XLights started. 2018-11-15 17:07:28,387 140700374831168 log_base [INFO] Version: 2018.44 2018-11-15 17:07:28,387 140700374831168 log_base [INFO] Bits: 64bit 2018-11-15 17:07:28,387 140700374831168 log_base [INFO] Build Date: November 11, 2018 2018-11-15 17:07:28,387 140700374831168 log_base [INFO] Machine configuration:
7
Falcon Player (FPP) / Re: More scripts!!!
« Last post by robbiet on Today at 08:19:09 PM »
Bueller...  Bueller...


Sent from my iPhone using Tapatalk
8
Alright, noob question here.  I got the master file but don't know how to install that.  Etcher does not recognize it as an image.

The "best" / easiest way to switch to the Master Branch that Dan is referring to is to burn the v2.4 image and boot. Then open the \developer.php page (by typing that after the IP address). Choose Master from the drop down and wait patiently - may take 4 or 5 minutes - until the Version showing at the top changes to v2.x-master.
9
DMX/E1.31 / Xlights/F4V3 Setup Help
« Last post by Powelln on Today at 08:09:23 PM »
I could really use some help understanding universes and setting up a sequence in Xlights, to Fpp to F4V3. I thought I had a good general understanding but strands don't come on that should and colors all backwards. This is where I gave up in the screen captures. Whats really tripping me up is the star with 270 nodes and what that means for universes and such. If you could take a look at the screen captures and tell me how you would do set this up, I would be so great full.
10
Falcon Player (FPP) / Re: FPP 2.4 Now Available
« Last post by Cjlocey on Today at 08:00:12 PM »
expanded with USB drive.
Root free space - 686.53 MiB (23%)
When I go to the developer page the highest version is v2.3
Any other suggestions on upgrading a stubborn 2.3?
Pages: [1] 2 3 ... 10
Back to top