Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
HmIP-RFUSB docker log shows "Updating Homematic RF-Hardware: HMIP-RFUSB: 4.2.14=>2.8.6, ERROR ( != 2.8.6)"
See original GitHub issueDescribe the issue you are experiencing
After starting the container the docker log shows an error:
Updating Homematic RF-Hardware: HMIP-RFUSB: 4.2.14=>2.8.6, ERROR ( != 2.8.6)
Describe the behavior you expected
I don´t expect any error message.
Steps to reproduce the issue
docker run -d --name ccu \
-v ccu_data:/usr/local:rw -v /lib/modules:/lib/modules:ro \
-v /run/udev/control:/run/udev/control \
-p 8080:80 -p 2001:2001 -p 2010:2010 -p 9292:9292 -p 8181:8181 \
--privileged --stop-timeout 30 \
--hostname homematic-raspi ghcr.io/jens-maus/raspberrymatic:latest
What is the version this bug report is based on?
3.59.6.20211009 3.61.5.20211113
Which base platform are you running?
rpi4 (RaspberryPi4)
Which HomeMatic/homematicIP radio module are you using?
HmIP-RFUSB
Anything in the logs that might be useful for us?
No.
Additional information
No response
Issue Analytics
- State:
- Created 2 years ago
- Comments:107 (43 by maintainers)
Top Results From Across the Web
View container logs - Docker Documentation
The docker service logs command shows information logged by all containers participating in a service. The information that is logged and the format...
Read more >Configure logging drivers - Docker Documentation
Configure logging driver. ... To update the logging driver for a container, the container has to be re-created with the desired options.
Read more >docker container logs
docker container logs: Fetch the logs of a container. ... --since, Show logs since timestamp (e.g. 2013-01-02T13:23:37Z) or relative (e.g. 42m for 42 ......
Read more >docker logs - Docker Documentation
The --since option shows only the container logs generated after a given date. You can specify the date as an RFC 3339 date,...
Read more >docker service logs
docker service logs: The `docker service logs` command batch-retrieves logs ... The --since option shows only the service logs generated after a given...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
My test are showing the same, I can update the old sticks as well as the new sticks and both types switch into App Mode afterwards and are fully detected by the detect-radio-module tool and the HMIPServer.
Hi all, as eQ3 just released a new potentially fixed 4.4.16 firmware for the HmIP-RFUSB (cf. https://github.com/eq-3/occu/commit/a2641df55cdde81239bbdbe7cf4dbcd4e3e62c5b), I retested the upgrade/downgrade procedures again. See here:
Firmware Upgrade 4.2.14->4.4.16 with older device bootloader (1.0.11):
Firmware Upgrade 4.2.14->4.4.16 with latest device bootloader (1.0.24):
So, voila. The issue with 4.4.x firmwares and newer device bootloader versions some users here (and myself) were facing seem to be fixed with the 4.4.16 HmIP-RFUSB firmware. In addition, this is now the latest/newest firmware available for the RFUSB stick series ATM with all Advanced HmIP Routing features included.
Next will be that I integrate this new firmware in the next nightly snapshot and then you all can (re-)test it again with your various HmIP-RFUSB use-cases and then provide some feedback here or even reopen the issue ticket in case the issue isn’t fixed or the new 4.4.16 firmware is not working as expected in your environment.