@buxtronix thanks for the effort! Why not make a PR? 433MHz is a quite unique value proposition of MySensors. I'd recommend a quick search through the open issues on MySensors github, maybe some CC1101 support was requested already. In any way, I'd encourage to raise a PR to the development branch. Who knows, if we get some people engaged, maybe we can release a new official version of MySensors with improved hardware support.
Thx, Dirk.
Posts made by dirkju
-
RE: Support for CC1101 radiosposted in Hardware
-
RE: mysensors on rpi with NRF2401 with Domoticzposted in Domoticz
@goblin feel free to share concrete error messages or questions. We might be able to help on well-described problems. Otherwise - hope ChatGPT can help you

-
RE: mysensors on rpi with NRF2401 with Domoticzposted in Domoticz
Hi goblin, so you got MySGW compiled successfully now using the development branch in git? That's great to hear! I do not have experiences with RPi gateways, neither Domoticz. But I believe choosing the Ethernet option is the easiest to configure (see Domoticz). Does that work for you?
-
RE: mysensors on rpi with NRF2401 with Domoticzposted in Domoticz
@goblin said in mysensors on rpi with NRF2401 with Domoticz:
fatal: destination path 'MySensors' already exists and is not an empty directory
Seems like you're trying to clone the MySensors git repo but there's already an existing MySensors folder. This is a typical git error message.
If you haven't given up yet, you could rename the Mysensors folder to something else and git-clone the development branch as advised by @mfalkvidd.
(As a general advise, if you are unsure, it might be an option to just ask ChatGPT about the error messages, describing your scenario. It knows git and Mysensors ;-))
-
RE: Cannot compile sketch with STM32F1 BluePill boardposted in Troubleshooting
@tnick I know this is an old post, but if it helps you - I've created support for STM32 based on latest STM32duino here. It's currently made to be backward compatible for the existing STM32F1 support, which is what you are struggling. But with a small change you can use the new STM32 HAL support. Let me know if you are interested to give it a try.
The longer term plan is to remove the existing (old) STM32F1 support in favor of the new and more general STM32 support. (If @mfalkvidd agrees ;-))