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

release 0.9.7 does not connect to MQTT bus #9

Closed
kjkoster opened this issue May 10, 2022 · 0 comments
Closed

release 0.9.7 does not connect to MQTT bus #9

kjkoster opened this issue May 10, 2022 · 0 comments

Comments

@kjkoster
Copy link
Contributor

It seems that release 0.9.7 breaks MQTT in a new way. With the new version, enabling MQTT does not cause data to be published on the revpi/io/# channel.

There is an error message in the logs that seems to relate to this, although I have no proof that is actually the case.

2022-05-04 11:48:26 [ERROR   ] 'Connect' object has no attribute ‘__evt_wdtoggle’

Downgrading to 0.9.6 resolves the problem that data is not written to MQTT, but obviously reintroduces the problem of not committing data to the I/O ports when using the revpi/set/# channels. I am back to running a patched version.

Please see https://revolutionpi.com/forum/viewtopic.php?t=3409 for the report from user GardG, who spotted the problem first.

naruxde added a commit that referenced this issue May 10, 2022
The object scan to find IOs on core devices uses the `__slot__` attribute, which include very private objects. That objects are not accessible by `getattr` - Now we are using `dir()`.
Missing objects from parent classes.
Ignored the export flag from piCtory.

closing #9
@naruxde naruxde closed this as completed May 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants