Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

homeassistant-pyozw==0.1.3 fails to install on FreeBSD #22697

Closed
ryanwinter opened this issue Apr 3, 2019 · 18 comments
Closed

homeassistant-pyozw==0.1.3 fails to install on FreeBSD #22697

ryanwinter opened this issue Apr 3, 2019 · 18 comments
Assignees

Comments

@ryanwinter
Copy link

Home Assistant release with the issue:
0.91

Last working Home Assistant release (if known):
0.90.2

Operating environment (Hass.io/Docker/Windows/etc.):
FreeBSD

Component/platform:
zwave

Description of problem:
The homeassistant_pyozw fails to install which is a required dependency of home assistant 0.91 for using the zwave component.

b"/tmp/pip-install-owewm927/homeassistant-pyozw/openzwave-embed/open-zwave-hass/cpp/src/command_classes/SensorMultilevel.cpp:502:55: error: adding 'uint8' (aka 'unsigned char') to a string does not append to the string [-Werror,-Wstring-plus-int]\n"

The problem stems from a compilation bug introduced into the homeassistant open-zwave fork here.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
zwave:

@ryanwinter
Copy link
Author

I have created a PR to fix.
home-assistant/open-zwave#4

@awarecan
Copy link
Contributor

awarecan commented Apr 4, 2019

@ryanwinter
Copy link
Author

Same of this? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206526

No, this is different. The bug is specific to the home assistant fork of open-zwave.

@ryanwinter
Copy link
Author

Appears to be effecting macosx too:
https://community.home-assistant.io/t/update-ha-to-0-91-zwave-fail/109462/4

@github-actions
Copy link

github-actions bot commented Apr 5, 2019

Hey there @home-assistant/z-wave, mind taking a look at this issue as its been labeled with a integration (zwave) you are listed as a codeowner for? Thanks!

@BazaJayGee66
Copy link

BazaJayGee66 commented Apr 5, 2019

Facing similar issue on Raspbian too, with hass version 0.91.1:

[homeassistant.util.package] Unable to install package homeassistant-pyozw==0.1.3: Failed to restore /test/env/lib/python3.5/site-packages/python_openzwave/ozw_config/__pycache__/
Command "/test/env/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-rdc7590c/homeassistant-pyozw/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-record-zvm5a0u4/install-record.txt --single-version-externally-managed --compile --install-headers /home/home-auto/env/include/site/python3.5/homeassistant-pyozw" failed with error code 1 in /tmp/pip-install-rdc7590c/homeassistant-pyozw/

@ryanwinter
Copy link
Author

ryanwinter commented Apr 6, 2019

This bug is blocking a lot of people running z-wave on different platforms, can we have the PR included for 0.91.1?

@robbiet480
Copy link
Member

@ryanwinter Just randomly noticed your comment on this flying by in Discord's GitHub channel. Made people aware of this, fix should be coming soon. Assigning @pvizeli as he maintains the fork of OZW that this broke in. Also, cc @clementhk, your PR home-assistant/open-zwave#2 seems to have been either improperly applied to the fork or was later broken for *BSD platforms (specific reports of breakage on FreeBSD and macOS which is BSD at heart).

Does anyone know what the consequences would be of just switching back to mainline OZW? Have there been any associated changes in this (home-assistant/home-assistant) repo that would prevent that? I see a couple of cherry picked items onto the fork and a patch or two, so I'm unsure.

@robbiet480 robbiet480 added this to the 0.91.2 milestone Apr 6, 2019
@ryanwinter
Copy link
Author

ryanwinter commented Apr 6, 2019

The main line is missing a couple of fixes such as the cover, rolling back would break a bunch of things and make many people unhappy :)

Applying my PR home-assistant/open-zwave#4 fixes the compilation error, would be prefereable to go that route.

@pvizeli
Copy link
Member

pvizeli commented Apr 6, 2019

Is merged with 0.1.4 - Thanks for PR @ryanwinter

@pvizeli pvizeli closed this as completed Apr 6, 2019
@pvizeli pvizeli removed this from the 0.91.2 milestone Apr 8, 2019
@tom-x1
Copy link

tom-x1 commented Apr 10, 2019

What does this mean for us? Do we have to upgrade to 0.1.4 or whait for a new HA release?

@pvizeli
Copy link
Member

pvizeli commented Apr 10, 2019

Will be in with 0.92.x

@DallasO
Copy link

DallasO commented Apr 10, 2019

What does this mean for us? Do we have to upgrade to 0.1.4 or whait for a new HA release?

I downgraded to 0.90.2. Will wait for 0.92.x with the fix for this.

Using virtualenv install, used command pip3 install --upgrade homeassistant==0.90.2.

@weichensw
Copy link

homeassistant 0.92.0b2 listed homeassistant-pyozw 0.1.4 in requirement. But it still fails installation on raspbian. Is that expected?

@tprelog
Copy link

tprelog commented Apr 23, 2019

A temporary work around for Home Assistant, you can manually edit zwave/__init__.py to use homeassistant-pyozw==0.1.4 as shown here..

@rschuiling
Copy link

I'm wondering, what does it mean the issue was pulled from the 0.91.2 milestone? In what version is this fix planned to be released now?

@kklem0
Copy link

kklem0 commented Apr 29, 2019

@rschuiling I believe there is new release from ~2 days ago.

@tprelog
Copy link

tprelog commented Apr 29, 2019

@rschuiling This has been fixed in the release of HA 92.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests