-
Notifications
You must be signed in to change notification settings - Fork 20
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
New Release: 0.7.5-beta #62
Comments
This release addresses issues #55, #56 and #57. FYI @stundenblume, @Hofyyy, @GallusMax, @pos-ei-don, @stromibaer |
Version: 0.7.4-beta something is wrong i guess, i have this payload on "device/serverRoom/Status ": { but i get:
|
@SoulRaven Thanks for reporting that. New beta version 0.7.5-beta available. |
thx, now is working, but some things are not setup, also, is it possible to setup the "Name" directly from device topic? L.E.
|
Sorry, can you clarify
|
the Device name is not set also the Firmware version. What i have see in code Firmware Versions contains the value from payload "version" and the device name is the "client id"
Also will be great to have the possibility to setup directly from topic the "Name" of the sensor |
This is just a debug message output by the Venus dbus library, it is always output when initialised.
I don't want to complicate the registration process. Once registered and you have a deviceid you can send a message to |
@Becker884 Thanks for trying it out and spotting this error. I'll update the grid.ini config file to remove the quotes in the next release.
|
Can I correct this on my own? |
Yes, you can. It's services/grid.ini See https://github.com/freakent/dbus-mqtt-devices/blob/Config-Files/services/grid.ini |
ok, but where can I find this file on my RPi2 ? |
/data/drivers/dbus-mqtt-devices-0.7.5-beta/services/grid.ini |
I used the beta with corrected grid.ini @venusos 3.10 ~32 without any problems for the moment. |
same to me with an grid sensor. no firmware, Connection.. doesnt matter for me. |
My concern is that it might affect how these devices are shown in VRM. I need to investigate this issue further. |
@freakent but do not show up on FlashMQ port 1884 using MQTT Explorer. Also looking at dbus-spy the topic/values are missing in all temp and tank sensors Tanks and sensors are missing from the HTML app and new gui-v2 app as well. Most likely due to the missing data in Flash-MQ Tanks and Sensors are appearing on the console Are you seeing the same issues? Best, |
@gharshaw, thanks for your investigations, that's all very interesting. I think I need to figure out if this issue is introduced by my code changes or the new FlashMQ in Venus OS. I think I might have to downgrade my test Raspberry PI and run tests there to be sure. |
@freakent @4000000064ed181437b9fbcc [2023-08-28 21:56:26] [INFO] [OwnerChange] Service appeared: 'com.victronenergy.temperature.mqtt_nr001_t1' with owner ':1.605' |
Do both brokers run parallel ? |
Yes, but in future versions (VenusOS 3.20+) mosquitto will completely replaced by flashmq. |
Great driver, helps me a lot. Upgraded from 0.6.2 to 0.7.5 beta without any problems. Use it to emulate a pv inverter behind a shelly and a grid meter with Hichi/Tasmota. |
@Thxeverybody Thanks for the feedback, I'm glad to hear it is working for you. I don't hunk there will be another Beta release after I have done more testing. |
@freakent I just updated my CCGX to Venus OS v3.11 and dbus-mqtt-driver 0.7.5-beta without any problems. The setup on the CCGX went smoothly and everything appears to be working correctly. Next hurdle, I imagine, will be with dbus-flashmq and the removal of dbus_mqtt. |
If you are using the driver in a production system I highly recommend you use the latest release not the Beta. I don't anticipate the move to FlashMQ is not such an issue. It will require a slight change to the installer that's all. This driver interacts with the dbus directly, not via dbus-Mqtt. |
@freakent Does the latest release remove the YAML dependency? I thought the 0.7.x versions is where you are removing that dependency |
That's correct, 0.6.x uses pyyaml. |
Thank you for your driver, |
Thanks for providing the results of your research. Have you tried running the current release version of this driver (not the beta) on VenusOS 3.20_33? Whilst VenusOS is being switched from Mosquitto to FlashMQ (both are MQTT brokers), I would avoid testing the Beta driver in a beta version of VenusOS, there are too many moving parts. The beta driver is very experimental at this time and not ready for production use. |
Hi freakent, |
Just for debugging purpose: VenusOS 3.20_33, dbus-mqtt-devices config-files branch head. Just restarted Venus and waited for the dbus-mqtt-devices logfiles (/var/log/dbus-mqtt-devices/current) to populate: creation.txt |
I would prefer to figure out why python3-modules is not installing for you. What is the output from opkg install python3-modules? What does the output from opkg list-installed tell you? |
Sorry for the delayed answer. Had some test this morning but had to get my system running again, as it's kind of productive... Here are some files from this evening (no solar at the moment, therefore I can test a little...) |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Dear All,
I have made a new release of the dbus-mqtt-driver that completely removes the YAML dependency from this project. This should address the problems that have plagued this project for months caused by the need to install the PyYaml library on Venus. It should also pave the way to make the driver installable by setuphelper in a subsequent release.
I have switched to using ini files which are natively supported by Python. This feels like quite a substantial change to the internals of the driver, so I am releasing this first version without YAML as a BETA. I have performed a lot of testing myself but I would like to collect feedback from users before making a final release.
To upgrade just follow the install instructions in the v0.7.5-beta readme as before.
https://github.com/freakent/dbus-mqtt-devices/tree/v0.7.5-beta
If you try this release, please comment below whether it works successfully for you or not. All feedback is appreciated.
-- updated release number to v0.7.5-beta
The text was updated successfully, but these errors were encountered: