-
Notifications
You must be signed in to change notification settings - Fork 24
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
Raspberry Pi PyYalm fails on install and with workaround storage + VRM updates breaks on ver 2.92 #37
Comments
@spamajor, thanks for letting me know. I'm pretty sure I had it running on 2.9x. I have now upgraded to the 3.00 beta to get prepare for the next version. You said that PyYaml install fails, do you have any error messages or something that might explain why? |
Thanx in advance and here you go (clean install on sd-card, no incremental update whatsoever) Starting random number generator daemon. |
I do have to make a decision, either stick with YAML or ditch it in favour of JSON or Python classes. I can't have PyYaml corrupting devices. I am hoping that Venus 3.0 might address this problem some how. |
Can you do a |
root@raspberrypi2:/data/drivers/dbus-mqtt-devices-0.5.1/bin# python --version root@raspberrypi2:/data/drivers/dbus-mqtt-devices-0.5.1/bin# python -m pip --version |
Thanks, that's the same as my setup. Still puzzled. |
If you Google the actual error "ModuleNotFoundError: No module named 'dataclasses'" the suggestion is to install dataclasses. On Venus you'd need to do |
Bummer, tried that already. my workaround was this, from the CCGX installer -> wget -qO- https://files.pythonhosted.org/packages/36/2b/61d51a2c4f25ef062ae3f74576b01638bebad5e045f747ff12643df63844/PyYAML-6.0.tar.gz | tar xvz -C $BASE/ext After installing the manual PyYaml your script works, the device is showing up and is very responsive. ERROR: Exception: |
Would you be brave enough to try the Venus 3.0 beta? Is this for a production system? |
Ha I started this adventure on 3.00~15 allas. btw. If you got it working and you have a Raspi2 too, shall i try your sd-image? |
This driver only handles the registration phase. Once you are sending data, your are using Victron's own dbus-Mqtt interface directly. I don't understand how you are able to send data to the correct topics if you are not able to register the device. The deviceinstance id that you get from device registration is the important part of the topic name. |
Hi, the bottomleft nodes subscribe to a topic and report the which I use for the P W U I nodes. |
But I think those topics must include the devicenstance. Without that you could be updating the wrong parameters on the dbus. Do you wait for device registration to complete before sending data values? |
Sorry, I have raspberry pi 4. It's just a fresh install of Venus OS |
Yes, I wait for a reply: The instance + portalid are part of the topic after te reply. As specified. |
@spamajor I tried to shorten your pyyaml install command to the following:
But strangely I still get the same Following your method worked. |
Hi @mtucker502 |
It still does not work. |
Part of it has been solved for me. One of the nodes sent a string instead of int / float. So that broke everything. Thanx for the patience ... PyYalm via Pip keeps complaining moduleNotFoundError: No module named 'dataclasses' error but the manual method works fine the 2nd and 3th time. |
Glad you found the source of your problem. I'm hoping that the pip issue will get resolved in Venus 3. Can we close this issue now? |
@spamajor Please see https://github.com/freakent/dbus-mqtt-devices/blob/python-modules/bin/setup.sh for an updated setup.sh script to address the missing dataclasses issue. I do not recommend using the |
I had the same errors while installing like @spamajor reported. I did this to get it work:
Now the log shows me:
|
Please try this version of the setup script. |
I have a bigger problem now. The mqtt service stopped working and I have no idea what happened. I already tried to delete your script and did a firmware downgrade to 2.92 but it didn't helped. Do you have any tip for me what to check? |
scroll down towards the bottom of the readme, there are troubleshooting tips and instructions on how to check the log file |
Thanks for sending all the logs as you have done, that makes it much easier to debug. You said
What do you mean by mqtt doesn't send any data? What are you expecting to happen? |
By the way, looking at your logs it looks like you are registering the same device twice. It's not a problem, but it is unnecessary. |
I connected the cerbo to my smart home system via mqtt and for debugging I use MQTT Explorer. Now at the moment the communication is dead. No mqtt messages at all. I allready removed the line from rc.local and the link it creates /service/dbus-mqtt-devices, too. after reboot nothing changed, no mqtt messages at all... |
Is the display still working? Can you still ssh to the GX device? |
Yes the remote console and ssh works normal |
Can you send a screen shot of what you do see in MQTT Explorer? |
OK, so you are getting MQTT messageds, otherwise MQTT Explorer would be empty. |
Can try publishing an empty message to R/co619ab2e89d/system/0/Serial? |
Check the dbus-mqtt logs. |
I attached the file: current.txt For me it looks like the dbus-mqtt in a bootloop and doesn't start correct... |
I agree. It's complaining about a dbus service of "/". What's in your services.yml ? Are you using the standard version of a customised version? |
Where do I find this file? I haven't customized anything. But I'm running another script for me ET340 simulation https://github.com/mitchese/shm-et340 |
I had the same issue at the beginning after installing the script from mitchese and this was the solution for the problem: https://community.victronenergy.com/questions/157757/cerbox-gx-mqtt-no-topics-exept-sys.html maybe it helps, finding the issue |
Are you running shm-et340 at the same time now? |
If you are running some other software at the same time I will have to ask you to reset the device, reinstall dbus-mqtt-devices on it's own and then reboot. Judging by the post you shared earlier it sounds like it could be shm-et340 that is causing this problem not dbus-mqtt-devices. See issue mitchese/shm-et340#9 |
I would have prefered you install and test the other way round, install dbus-mqtt-devices but not sun-et340. Have you rebooted yet, since it was rebooting that caused you problems. |
I performed a reboot and mqtt works fine. To reset the whole system is not so easy because this is my productive system that powers my house. Do you have a test system where you can test it maybe? |
At this point in time, I feel dbus-Mqtt-devices is well tested. I haven't seen anything to suggest the problems you are experiencing are caused directly by dbus-Mqtt-devices. Unless you can provide evidence of the contrary, I am sorry, but I will be closing this issue. |
Do you know that MQTT will stop sending data after ~1min? |
Yes i know that. That's why you have to send the keepalive every 55 seconds ;) |
Nothing more I can do here so closing this issue. |
Hi, on my Raspberry Pi PyYalm fails on install and with workaround the storage + VRM updates breaks on ver 2.92. See screetshot:
The text was updated successfully, but these errors were encountered: