MQTT IO v2.0.0 beta testing #178

flyte · 2020-10-18T16:29:52Z

flyte
Oct 18, 2020
Maintainer

I've spent quite a while rebuilding the project using asyncio, which I'd like people to help me test before I inflict it on the general public. It's on PyPI as mqtt-io. The code for it exists within feature/asyncio, and for the most part, it should work with existing config files.

This version only supports Python 3.6+, so if you're on a Raspberry Pi, you'll either need to make sure you're using python3, or if your version of Raspbian is too old, you might need to upgrade to a newer version of Raspberry Pi OS.

Please use this discussion or Discord to give feedback and discuss your experiences.

Installation

pip3 install mqtt-io

Usage

Run the program, replacing config.yml with the path to your config file:

python3 -m mqtt_io config.yml

Config Changes

See the new documentation.

Existing config files are mostly compatible, but I've taken the liberty of making some improvements:

MQTT section

Moved the Home Assistant discovery options into their own ha_discovery section.

All IO sections

These changes affect the digital_inputs, digital_outputs and sensor_inputs sections.

Added <IO section>.*.ha_discovery section as documented here (digital_inputs), here (digital_outputs) and here (sensor_inputs).

Sensors

Removed sensor_inputs.*.unit_of_measurement in favour of adding it implicitly sensor_inputs.*.ha_discovery.unit_of_measurement
Moved sensor_inputs.*.expire_after explicitly to sensor_inputs.*.ha_discovery.expire_after.

Streams

Removed stream_reads and stream_writes in favour of just listing streams in stream_modules with read and write booleans to enable or disable the functionality.

Logging

If you use a logging section, you'll need to update the mqtt_gpio logger to mqtt_io as the module name has changed.

logging:
  version: 1
  handlers:
    console:
      class: logging.StreamHandler
      formatter: default
      level: DEBUG
  formatters:
    default:
      format: "%(asctime)s %(name)s [%(levelname)-8s] %(message)s"
      datefmt: "%Y-%m-%d %H:%M:%S"
  loggers:
    mqtt_io:  # <-- this!
      level: DEBUG
      handlers:
        - console
      propagate: yes

BenjiU · 2020-11-05T19:53:19Z

BenjiU
Nov 5, 2020
Collaborator

Hi @flyte,

I just gave it a try:

the requirements.txt need a fix, i think. pip3 install hbmqtt fixed it

pi@bennibustest:~/pi-mqtt-gpio $ python3 -m mqtt_io config.stdio.yml 
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/local/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/pi/pi-mqtt-gpio/mqtt_io/__main__.py", line 7, in <module>
    from .server import MqttGpio
  File "/home/pi/pi-mqtt-gpio/mqtt_io/server.py", line 9, in <module>
    from hbmqtt.client import ClientException, MQTTClient
ModuleNotFoundError: No module named 'hbmqtt'

On cancel with STRG+C i got this error. But not every time.

^C2020-11-05 19:40:17 mqtt_io.server [WARNING ] Received exit signal SIGINT
2020-11-05 19:40:17 mqtt_io.server [INFO    ] Waiting for main task to complete...
2020-11-05 19:40:17 mqtt_io.server [INFO    ] Cancelling 2 remaining tasks
2020-11-05 19:40:17 mqtt_io.server [INFO    ] Waiting for 2 remaining tasks to complete...
^C2020-11-05 19:40:18 mqtt_io.server [WARNING ] Received exit signal SIGINT
2020-11-05 19:40:18 mqtt_io.server [INFO    ] Waiting for main task to complete...
2020-11-05 19:40:19 mqtt_io.server [INFO    ] Cancelling 2 remaining tasks
2020-11-05 19:40:19 mqtt_io.server [INFO    ] Waiting for 2 remaining tasks to complete...
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/local/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/pi/pi-mqtt-gpio/mqtt_io/__main__.py", line 30, in <module>
    main()
  File "/home/pi/pi-mqtt-gpio/mqtt_io/__main__.py", line 26, in main
    mqtt_gpio.run()
  File "/home/pi/pi-mqtt-gpio/mqtt_io/server.py", line 423, in run
    self.loop.run_until_complete(self._init_mqtt())
  File "/usr/local/lib/python3.6/asyncio/base_events.py", line 467, in run_until_complete
    return future.result()
concurrent.futures._base.CancelledError

python2 (Python 2.7.13) does not work, but python3.6 is okay:

pi@bennibustest:~/pi-mqtt-gpio $ python -m mqtt_io config.stdio.yml 
Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 163, in _run_module_as_main
    mod_name, _Error)
  File "/usr/lib/python2.7/runpy.py", line 114, in _get_module_details
    return _get_module_details(pkg_main_name)
  File "/usr/lib/python2.7/runpy.py", line 119, in _get_module_details
    code = loader.get_code(mod_name)
  File "/usr/lib/python2.7/pkgutil.py", line 283, in get_code
    self.code = compile(source, self.filename, 'exec')
  File "/home/pi/pi-mqtt-gpio/mqtt_io/__main__.py", line 19
    print(str(e), file=sys.stderr)
                      ^
SyntaxError: invalid syntax
pi@bennibustest:~/pi-mqtt-gpio $ python --version
Python 2.7.13

But my temp, humidity and distance module work and sending mqtt messages.

7 replies

flyte Feb 28, 2021
Maintainer Author

Hmm, interesting. I'll have a look through and see if I can work out how that might happen.

Do you think that maybe where was a retained message to that set_on_ms topic? I can't think why else it would randomly pick 7500ms if it didn't actually pick up a message from MQTT.

your really performing on that topic

Yeah, I'm trying to push it over the line finally!

BenjiU Mar 2, 2021
Collaborator

Hi flyte, my wife reproduced it running state, not only at startup. Thanks for totally confusing her. Was very funny ;-)

Let me show you my config.xml (i2c currently not used):
Outputs: Licht, LED (timed_set_ms) and Blumenlicht

mqtt:
  host: 10.10.10.1
  port: 1883
  user: "xxx"
  password: "xxx"
  topic_prefix: Arbeitszimmer

gpio_modules:
  - name: raspberrypi
    module: raspberrypi

#sensor_modules:
#  - name: lm75
#    module: lm75
#    i2c_bus_num: 1
#    chip_addr: 0x48

digital_outputs:
  - name: Licht
    module: raspberrypi
    pin: 6
    on_payload: "an"
    off_payload: "aus"
    retain: yes # This option value controls if the message is retained. Default is no.

  - name: LED
    module: raspberrypi
    pin: 26
    on_payload: "an"
    off_payload: "aus"
    initial: low 
    retain: yes
    timed_set_ms: 7500

  - name: Blumenlicht
    module: raspberrypi
    pin: 19
    on_payload: "an"
    off_payload: "aus"
    retain: yes # This option value controls if the message is retained. Default is no.

digital_inputs:
  - name: LichtSchalterLinks
    module: raspberrypi
    pin: 17
    on_payload: "1"
    off_payload: "0"
    pullup: yes
    pulldown: yes

  - name: LichtSchalterRechts
    module: raspberrypi
    pin: 4
    on_payload: "1"
    off_payload: "0"
    pullup: yes
    pulldown: no

My openhab has the rule, when Arbeitszimmer/input/LichtSchalterRechts changes, LED and Blumenlicht are toggled (on/off).

You can see that in the "mqtt capture":

# from mqtt_io:
Arbeitszimmer/input/LichtSchalterRechts 1
# to mqtt_io:
Arbeitszimmer/output/LED/set an
Arbeitszimmer/output/Blumenlicht/set aus
# from mqtt_io:
Arbeitszimmer/output/LED an
Arbeitszimmer/output/Blumenlicht aus

And after 7,5 sek, "Blumenlicht" gets changed again, althoug it is configured in "LED". LED though, is not changed after 7,5s.

# from mqtt_io:
Arbeitszimmer/output/Blumenlicht an

You also see that in mqtt_io log file:

2021-03-02 07:43:53 mqtt_io.server [INFO] Digital input 'LichtSchalterRechts' value changed to True
2021-03-02 07:43:53 mqtt_io.server [INFO] Digital output 'LED' set to True (on)
2021-03-02 07:43:53 mqtt_io.server [INFO] Digital output 'Blumenlicht' set to False (off)
2021-03-02 07:44:01 mqtt_io.server [INFO] Setting digital output 'Blumenlicht' back to its previous value after configured 'timed_set_ms' delay of 7500ms
2021-03-02 07:44:01 mqtt_io.server [INFO] Digital output 'Blumenlicht' set to True (on)

I'm using latest raspberryIO on "Raspberrypi B+ V1.2":
Linux Arbeitszimmer 5.4.83+ #1379 Mon Dec 14 13:06:05 GMT 2020 armv6l GNU/Linux

Have fun investigating this :-) I also may provide new logfiles, if you need more debug infos or may not reproduce it.

BenjiU Mar 2, 2021
Collaborator

When I change the order in openhab rule (old: LED then Blumenlicht; new: Blumenlicht then LED) it "works":

# from mqtt_io:
Arbeitszimmer/input/LichtSchalterRechts 1
# to mqtt_io:
Arbeitszimmer/output/Blumenlicht/set aus
Arbeitszimmer/output/LED/set an
# from mqtt_io:
Arbeitszimmer/output/Blumenlicht aus
Arbeitszimmer/output/LED an

And after 7,5s:
Arbeitszimmer/output/LED aus

BenjiU Mar 11, 2021
Collaborator

Hi @flyte , I found the "error":

the following stripped code shows the variable out_conf in digital_output_loop:

    async def digital_output_loop()
        while True:
            out_conf, payload = await queue.get()

            async def reset_timer() -> None:

                await self.set_digital_output(module, out_conf, not value)

            task = self.loop.create_task(reset_timer())
            self.transient_tasks.append(task)

When my LED output is set to high, it is stored in out_conf and a task is created for calling reset_timer(). reset_timer() waits for the specified time and sets the output stored in out_conf to the opposite value.
If a new output mqtt message arrives before the waittime is over, out_conf is set to new output Blumenlicht and reset_timer() uses this new set out_conf (Blumenlicht) to toggle the output, instead of the original one.

When out_conf is provided as parameter to reset_timer(), it works for me:

           async def reset_timer(output_config: ConfigType) -> None:
                """
                Reset the output to the opposite value after x ms.
                """
                await asyncio.sleep(msec / 1000.0)
                _LOG.info(
                    (
                        "Setting digital output '%s' back to its previous value after "
                        "configured 'timed_set_ms' delay of %sms"
                    ),
                    output_config["name"],
                    msec,
                )
                await self.set_digital_output(module, output_config, not value)
     
            task = self.loop.create_task(reset_timer(out_conf))

Do you fix it or shall I commit it?

flyte Mar 12, 2021
Maintainer Author

Thanks for totally confusing her. Was very funny ;-)

I've been confusing women for years, it just comes naturally 😅

I found the "error"

Ah yes! The late-binding closure strikes again! Well spotted and well done to your wife for being MQTT IO tester of the month 🏆 😁

Do you fix it or shall I commit it?

I'll commit a fix just now, as I have a slightly different convention for doing the same thing.

PS. Sorry, I didn't notice your messages on this topic 10 days ago. This discussion format is actually a bit tricky to keep up on.

Arsenal10108 · 2021-02-25T18:25:07Z

Arsenal10108
Feb 25, 2021

Hey @flyte, Got it swapped over and it appears to be working, however it doesn't appear to be using the log file that's defined in the conf file (same log as the old version actually)

8 replies

Arsenal10108 Feb 26, 2021

It's wired right in. I removed all IPv6 from it. Its actually a pi2b so it doesn't have built in wireless. Once crashed the software would not recover. Only way I could get it to come back is configure A timer on home assistant that resets with every Mqtt message, if no messaged received by the time the timer runs out then it would issue a shell command to SSH into it and reboot the pi, that brings it back up. I suppose I could also tell it to kill the program with supervisor and then restart it but simplicity sake sudo reboot was faster.

Arsenal10108 Feb 26, 2021

After changing the logging config over it looks like my sensor readings are all out of whack, The LM75 is actually the one on the 3m long cable and interestingly the BH1750 is only a few cm away from the Pi and that is the one seeing weird values. This could be because I slowed down the i2c clock to 1khz. My i2c extender came in so I will try to install that and bump the clock back up to 100khz and see fi that resolves it
I did not see that level of information on the old version so we are moving forward!

2021-02-26 09:39:05,082 mqtt_io.server (INFO): Subscribed to topic: 'home/output/garageheat/set_on_ms'
2021-02-26 09:39:05,083 mqtt_io.server (INFO): Subscribed to topic: 'home/output/garageheat/set_off_ms'
2021-02-26 09:39:05,332 mqtt_io.server (INFO): Subscribed to topic: 'home/output/garagedooropener/set'
2021-02-26 09:39:05,333 mqtt_io.server (INFO): Subscribed to topic: 'home/output/garagedooropener/set_on_ms'
2021-02-26 09:39:05,334 mqtt_io.server (INFO): Subscribed to topic: 'home/output/garagedooropener/set_off_ms'
2021-02-26 09:39:14,253 mqtt_io.server (INFO): Read sensor 'bh1750_lux' value of 4906.67
2021-02-26 09:39:19,253 mqtt_io.server (INFO): Read sensor 'temperature' value of 9.5625
2021-02-26 09:39:24,265 mqtt_io.server (INFO): Read sensor 'bh1750_lux' value of 4906.67
2021-02-26 09:39:34,264 mqtt_io.server (INFO): Read sensor 'temperature' value of 9.5625
2021-02-26 09:39:34,277 mqtt_io.server (INFO): Read sensor 'bh1750_lux' value of 8960.0
2021-02-26 09:39:44,288 mqtt_io.server (INFO): Read sensor 'bh1750_lux' value of 5120.0
2021-02-26 09:39:49,275 mqtt_io.server (INFO): Read sensor 'temperature' value of 9.5625
2021-02-26 09:39:54,299 mqtt_io.server (INFO): Read sensor 'bh1750_lux' value of 5333.33
2021-02-26 09:40:04,287 mqtt_io.server (INFO): Read sensor 'temperature' value of 9.5625
2021-02-26 09:40:04,310 mqtt_io.server (INFO): Read sensor 'bh1750_lux' value of 9173.33
2021-02-26 09:40:14,321 mqtt_io.server (INFO): Read sensor 'bh1750_lux' value of 5333.33
2021-02-26 09:40:19,297 mqtt_io.server (INFO): Read sensor 'temperature' value of 9.5625
2021-02-26 09:40:24,332 mqtt_io.server (INFO): Read sensor 'bh1750_lux' value of 5973.33

Arsenal10108 Mar 1, 2021

Had the i2c extender installed for over 24 hours and haven't had a single blip. Been rock solid. So I am sure that was my issue with the sensors Dropping. I will add in some comments on the bug on the old version.

There is one other thing I noticed, it seems as though the scale for the BH1750 could be off? almost seems like its to a power of 10. On the old version where i was getting about 10 lumens report the new version is reporting about 1000. Trying to use the interior lights as a constant, when had them on I was reporting about 650ish lumens and now and seeing about 6000ish. Its never an actual constant number. Not really a big deal as I just changed the Home assistant stuff to adapt to the new numbers.

kapratt Mar 1, 2021

I also was having the same issue with the BH1750. I took a look at the code and I think it's normalizing of the values in the code. In the original version:

    def get_value(self, config):
        """Get the light value from the sensor."""
        value = self.bus.read_i2c_block_data(self.address, ONE_TIME_HIGH_RES_MODE_1)
        value = (value[1] + (256 * value[0])) / 1.2
        return value

And in the Asyncio version:

        with self.SMBus(self.bus_num) as bus:
            return float(bus.read_word_data(self.address, ONE_TIME_HIGH_RES_MODE_1)) / 1.2

I haven't tested with the old code to see if that produces more valid numbers or not yet however.

flyte Mar 2, 2021
Maintainer Author

Ah yes, so I was hoping that was equivalent code. All the original code is doing is reading a load of bytes, then taking one of them, shifting them up by 8 (multiplying by 256) and adding them to another. This is just to get a 16 bit value (two bytes / one word).

My version is just using the "right" function in the first place that does it for you. At least that's what I was hoping! Of course I wrote it blind though since I don't have that sensor.

I'll have to have another look at it and see if I can get one to test with.

kapratt · 2021-02-26T18:14:53Z

kapratt
Feb 26, 2021

While testing install on a Pi Zero W I came up with this error:

      File "Cython/Plex/Machines.py", line 124, in Cython.Plex.Machines.Node.__hash__
    OverflowError: Python int too large to convert to C ssize_t
    
    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-install-yzjpfh74/PyYAML/

I found a solution to be able to bypass it by doing the following:

sudo pip3 install --no-cache-dir --no-binary pyyaml pyyaml
pip3 install --pre mqtt-io

Just an FYI!

11 replies

flyte Mar 1, 2021
Maintainer Author

It seems like it's the --pre part that's breaking the PyYAML installation:

With --pre

Click to expand

flyte@debian:~$ python3.7 -m venv ve
flyte@debian:~$ . ve/bin/activate
(ve) flyte@debian:~$ pip install --no-cache --pre pyyaml
Collecting pyyaml
  Downloading https://files.pythonhosted.org/packages/a0/a4/d63f2d7597e1a4b55aa3b4d6c5b029991d3b824b5bd331af8d4ab1ed687d/PyYAML-5.4.1.tar.gz (175kB)
    100% |████████████████████████████████| 184kB 5.1MB/s 
  Installing build dependencies ... done
    Complete output from command python setup.py egg_info:
    running egg_info
    creating pip-egg-info/PyYAML.egg-info
    writing pip-egg-info/PyYAML.egg-info/PKG-INFO
    writing dependency_links to pip-egg-info/PyYAML.egg-info/dependency_links.txt
    writing top-level names to pip-egg-info/PyYAML.egg-info/top_level.txt
    writing manifest file 'pip-egg-info/PyYAML.egg-info/SOURCES.txt'
    cythoning yaml/_yaml.pyx to yaml/_yaml.c
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-install-pa6jd6hc/pyyaml/setup.py", line 295, in <module>
        python_requires='>=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*, !=3.4.*, !=3.5.*',
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/setuptools/__init__.py", line 153, in setup
        return distutils.core.setup(**attrs)
      File "/usr/lib/python3.7/distutils/core.py", line 148, in setup
        dist.run_commands()
      File "/usr/lib/python3.7/distutils/dist.py", line 966, in run_commands
        self.run_command(cmd)
      File "/usr/lib/python3.7/distutils/dist.py", line 985, in run_command
        cmd_obj.run()
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/setuptools/command/egg_info.py", line 299, in run
        self.find_sources()
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/setuptools/command/egg_info.py", line 306, in find_sources
        mm.run()
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/setuptools/command/egg_info.py", line 541, in run
        self.add_defaults()
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/setuptools/command/egg_info.py", line 577, in add_defaults
        sdist.add_defaults(self)
      File "/usr/lib/python3.7/distutils/command/sdist.py", line 228, in add_defaults
        self._add_defaults_ext()
      File "/usr/lib/python3.7/distutils/command/sdist.py", line 312, in _add_defaults_ext
        self.filelist.extend(build_ext.get_source_files())
      File "/tmp/pip-install-pa6jd6hc/pyyaml/setup.py", line 197, in get_source_files
        self.check_extensions_list(self.extensions)
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/Cython/Distutils/old_build_ext.py", line 193, in check_extensions_list
        ext.sources = self.cython_sources(ext.sources, ext)
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/Cython/Distutils/old_build_ext.py", line 344, in cython_sources
        full_module_name=module_name)
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/Cython/Compiler/Main.py", line 626, in compile
        return compile_single(source, options, full_module_name)
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/Cython/Compiler/Main.py", line 575, in compile_single
        return run_pipeline(source, options, full_module_name)
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/Cython/Compiler/Main.py", line 494, in run_pipeline
        pipeline = Pipeline.create_pyx_pipeline(context, options, result)
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/Cython/Compiler/Pipeline.py", line 252, in create_pyx_pipeline
        create_pipeline(context, mode, exclude_classes=exclude_classes),
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/Cython/Compiler/Pipeline.py", line 144, in create_pipeline
        from .ParseTreeTransforms import WithTransform, NormalizeTree, PostParse, PxdPostParse
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/Cython/Compiler/ParseTreeTransforms.py", line 1632, in <module>
        class AnalyseDeclarationsTransform(EnvTransform):
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/Cython/Compiler/ParseTreeTransforms.py", line 1640, in AnalyseDeclarationsTransform
        """, level='c_class', pipeline=[NormalizeTree(None)])
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/Cython/Compiler/TreeFragment.py", line 235, in __init__
        mod = t = parse_from_strings(name, fmt_code, fmt_pxds, level=level, initial_pos=initial_pos)
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/Cython/Compiler/TreeFragment.py", line 75, in parse_from_strings
        scope = scope, context = context, initial_pos = initial_pos)
      File "Cython/Compiler/Scanning.py", line 306, in Cython.Compiler.Scanning.PyrexScanner.__init__
      File "Cython/Compiler/Scanning.py", line 35, in Cython.Compiler.Scanning.get_lexicon
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/Cython/Compiler/Lexicon.py", line 147, in make_lexicon
        (Eof, Method('eof_action'))
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/Cython/Plex/Lexicons.py", line 129, in __init__
        nfa, default_initial_state, spec, token_number)
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/Cython/Plex/Lexicons.py", line 162, in add_token_to_machine
        match_bol=1, nocase=0)
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/Cython/Plex/Regexps.py", line 301, in build_machine
        re.build_machine(m, s1, s2, match_bol, nocase)
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/Cython/Plex/Regexps.py", line 340, in build_machine
        initial_state = self.build_opt(m, initial_state, BOL)
      File "/tmp/pip-build-env-500bl74s/lib/python3.7/site-packages/Cython/Plex/Regexps.py", line 136, in build_opt
        initial_state.link_to(s)
      File "Cython/Plex/Machines.py", line 86, in Cython.Plex.Machines.Node.link_to
      File "Cython/Plex/Machines.py", line 82, in Cython.Plex.Machines.Node.add_transition
      File "Cython/Plex/Transitions.py", line 60, in Cython.Plex.Transitions.TransitionMap.add
      File "Cython/Plex/Machines.py", line 124, in Cython.Plex.Machines.Node.__hash__
    OverflowError: Python int too large to convert to C ssize_t
    
    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-install-pa6jd6hc/pyyaml/

Without --pre

flyte@debian:~$ python3.7 -m venv ve
flyte@debian:~$ . ve/bin/activate
(ve) flyte@debian:~$ pip install --no-cache pyyaml
Collecting pyyaml
  Downloading https://files.pythonhosted.org/packages/a0/a4/d63f2d7597e1a4b55aa3b4d6c5b029991d3b824b5bd331af8d4ab1ed687d/PyYAML-5.4.1.tar.gz (175kB)
    100% |████████████████████████████████| 184kB 2.4MB/s 
  Installing build dependencies ... done
Installing collected packages: pyyaml
  Running setup.py install for pyyaml ... done
Successfully installed pyyaml-5.4.1

Turns out you can actually install the prerelease version of mqtt-io without specifying --pre anyway, so I'll update the instructions and never speak of this again 😁

Click to expand

flyte@debian:~$ python3.7 -m venv ve
flyte@debian:~$ . ve/bin/activate
(ve) flyte@debian:~$ pip install --no-cache mqtt-io
Collecting mqtt-io
  Downloading https://files.pythonhosted.org/packages/21/71/d68f3fc222282274f6026ef07ee44d36a6624873a25321e096033e4403c0/mqtt_io-2.0.0b8-py3-none-any.whl (63kB)
    100% |████████████████████████████████| 71kB 2.8MB/s 
Collecting typing-extensions<4.0.0,>=3.7.4 (from mqtt-io)
  Downloading https://files.pythonhosted.org/packages/60/7a/e881b5abb54db0e6e671ab088d079c57ce54e8a01a3ca443f561ccadb37e/typing_extensions-3.7.4.3-py3-none-any.whl
Collecting Cerberus<2.0.0,>=1.3.2 (from mqtt-io)
  Downloading https://files.pythonhosted.org/packages/90/a7/71c6ed2d46a81065e68c007ac63378b96fa54c7bb614d653c68232f9c50c/Cerberus-1.3.2.tar.gz (52kB)
    100% |████████████████████████████████| 61kB 6.6MB/s 
Collecting asyncio-mqtt<0.9.0,>=0.8.1 (from mqtt-io)
  Downloading https://files.pythonhosted.org/packages/7a/c7/02372db3f34f15a1aed25a0f71505d9cd54aaed54c0fef3211c2cc7ba1af/asyncio_mqtt-0.8.1-py3-none-any.whl
Collecting PyYAML>=5.3.1 (from mqtt-io)
  Downloading https://files.pythonhosted.org/packages/a0/a4/d63f2d7597e1a4b55aa3b4d6c5b029991d3b824b5bd331af8d4ab1ed687d/PyYAML-5.4.1.tar.gz (175kB)
    100% |████████████████████████████████| 184kB 5.8MB/s 
  Installing build dependencies ... done
Requirement already satisfied: setuptools in ./ve/lib/python3.7/site-packages (from Cerberus<2.0.0,>=1.3.2->mqtt-io) (40.8.0)
Collecting paho-mqtt>=1.5.0 (from asyncio-mqtt<0.9.0,>=0.8.1->mqtt-io)
  Downloading https://files.pythonhosted.org/packages/32/d3/6dcb8fd14746fcde6a556f932b5de8bea8fedcb85b3a092e0e986372c0e7/paho-mqtt-1.5.1.tar.gz (101kB)
    100% |████████████████████████████████| 102kB 4.1MB/s 
Installing collected packages: typing-extensions, Cerberus, paho-mqtt, asyncio-mqtt, PyYAML, mqtt-io
  Running setup.py install for Cerberus ... done
  Running setup.py install for paho-mqtt ... done
  Running setup.py install for PyYAML ... done
Successfully installed Cerberus-1.3.2 PyYAML-5.4.1 asyncio-mqtt-0.8.1 mqtt-io-2.0.0b8 paho-mqtt-1.5.1 typing-extensions-3.7.4.3

flyte Mar 1, 2021
Maintainer Author

TL;DR

Don't use the --pre flag on your pip install command, so use this instead:

pip install mqtt-io

kapratt Mar 1, 2021

I'll try reinstalling to get the full error log again. When doing the --no-binary the software works perfectly fine so far.

flyte Mar 1, 2021
Maintainer Author

No need, @kapratt - It's all sorted, just needed to not use the --pre flag with pip. Cheers!

kapratt Mar 1, 2021

Thanks @flyte ! Glad you got it sorted out while I was sleeping.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

MQTT IO v2.0.0 beta testing #178

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 3 comments 26 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

MQTT IO v2.0.0 beta testing #178

flyte Oct 18, 2020 Maintainer

Installation

Usage

Config Changes

MQTT section

All IO sections

Sensors

Streams

Logging

Replies: 3 comments · 26 replies

BenjiU Nov 5, 2020 Collaborator

flyte Feb 28, 2021 Maintainer Author

BenjiU Mar 2, 2021 Collaborator

BenjiU Mar 2, 2021 Collaborator

BenjiU Mar 11, 2021 Collaborator

flyte Mar 12, 2021 Maintainer Author

flyte Mar 2, 2021 Maintainer Author

flyte Mar 1, 2021 Maintainer Author

With --pre

Without --pre

flyte Mar 1, 2021 Maintainer Author

TL;DR

flyte Mar 1, 2021 Maintainer Author

flyte
Oct 18, 2020
Maintainer

Replies: 3 comments 26 replies

BenjiU
Nov 5, 2020
Collaborator

flyte Feb 28, 2021
Maintainer Author

BenjiU Mar 2, 2021
Collaborator

BenjiU Mar 2, 2021
Collaborator

BenjiU Mar 11, 2021
Collaborator

flyte Mar 12, 2021
Maintainer Author

flyte Mar 2, 2021
Maintainer Author

flyte Mar 1, 2021
Maintainer Author

flyte Mar 1, 2021
Maintainer Author

flyte Mar 1, 2021
Maintainer Author