Event fire meaning

[AlexanderSch90]

Hey, can you tell me what Event Fire 2 is meaning?

07:30:38 INFO  src/yasdi_handler.c:271: Device 329 went online

07:30:38 DEBUG src/yasdi_handler.c:247: Event 0 fired for device 504

07:30:38 INFO  src/yasdi_handler.c:271: Device 504 went online

07:30:40 DEBUG src/yasdi_handler.c:247: Event 0 fired for device 663

07:30:40 INFO  src/yasdi_handler.c:271: Device 663 went online

07:30:48 DEBUG src/yasdi_handler.c:247: Event 2 fired for device 5

07:30:48 DEBUG src/yasdi_handler.c:292: Device detection finished with 5 devices

07:31:05 DEBUG src/yasdi_handler.c:147: Starting device value fetch (sync)...

07:31:20 DEBUG src/yasdi_handler.c:136: yh_loop is going to sleep for 15 seconds...

07:31:35 DEBUG src/yasdi_handler.c:147: Starting device value fetch (sync)...

[pkwagner]

Hi, according to the sources it translates with YASDI_EVENT_DEVICE_SEARCH_END. This also seems to fit the other log messages (and is nothing to worry about).

Did you experience any problems?

[AlexanderSch90]

Yes unfortunately yes, the program ran the last time 100% but somehow it is now suddenly so that an inverter no longer delivers values although in the logs all five inverters are found. From the logs I can not see much more. I have also replaced the Piggy Pack, unfortunately without success. Nie i Set Loglevel = 1. I Post the log tomorrow...

Ps: Your readme says loglevel = 0 for debugging, but you mean = 1 ;-)

[pkwagner]

Did you already try checking out to an older version like yadi2mqtt:1.1? If so, we can at least exclude all software-side errors.

Other problem sources I could think of, ranked by the likelihood I would guess:

1. Is it the last inverter in your RS485 chain? Then maybe the second by the last piggyback fails forwarding the results of the last.
2. There could be an issue with the inverter databus itself, i.e. no data even reaches the plugged in piggyback.
3. There are nasty random errors inside yasdi when using more than 5 inverters, e.g. timing issues with too large payloads. I don't think it's very likely tho.
4. Your OS. Unlikely I'd say.
5. Your RS485 adapter. Also unlikely in my opinion.

[AlexanderSch90]

Thanks for your Ideas...

Version 1.1 with no sucess:

Your Opinion 1: Not the last inverter in my RS485 chain...
2: I think this is the Problem...
3: I don´t think that this is the Problem...
4: I don´t think that this is the Problem...
5: Maybe...

Thanks... i now search the Hardwareproblem... Your software is great!

[AlexanderSch90]

I have one more question: I use the Dockerhub image. How can I change the line "YASDI_DEBUG_OUTPUT" in the Dockerfile when it takes the image from Dockerhub? Wouldn't it be possible for you to set the line via ENV variable? Or is the line synonymous with the ENV variable: "LOG_LEVEL".