Pioreactor / Pioreactor/pioreactor
start up jobs not publishing to mqtt if hostname = `pioreactor`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 149
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
After getting #425 working, I noticed that the activity dot was grey. Logs showed that monitor had started, and I could send commands, but MQTT was not being populated by the monitor job (pio mqtt was absent of monitor fields).
Why could this occur? Some observations:
- the MQTT server is local to the leader, so it's not a network issue.
- UI to monitor was working (identify worked, as did starting jobs), so that MQTT connection existing, so it's just publishing problems.
- rebooting didn't fix the problem.
- hostname is
pioreactor, is that a problem? - killing monitor, and then running it manually from the command line worked.
- Looks like mqtt_to_db_streaming isn't publishing either... I see no
x_in_past_minuteevents
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing startup of the monitor and mqtt_to_db_streaming jobs when the hostname is pioreactor, then compare it with launching monitor manually. Trace why monitor fields and x_in_past_minute events are not published; done means both jobs publish their expected MQTT data during startup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, raspberry-pi
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100