MicroPython Forum (Archive)

Thanks for the replies. You were on point in that the source of the problem was that the two sources had a different 0 point for their start point. As @dhylands suggested I can take the timestamp of 2000, 01, 01 00:00:00 in the 1976 epoch to convert to one utime.localtime() can use. Since I don't ne...

I would like to make requests to an API, but one of the required parameters is a date string. My workaround for not having a RTC is to get a timestamp from timezonedb.com and convert it to a string. My issue is that, when I pass the timestamp through utime.localtime it returns a date 30 years in the...

Thanks @pythoncoder, that was giving me trouble and I was sure there was a solution.

BigL3g wrote:If your code is cleaned up for sharing will you post it as a working example?

Here you go: https://github.com/andrewlrogers/Microp ... mp-Display

Hopefully this will work for you.

However, all this is speculation I guess to really solve this mystery, we need to code of both units and possibly the MQTT broker config file I have been planning on posting my code on github for everyone to take a look at. However, before posting I wanted to have clean code with nice comments. Whi...

The display unit is the one that fails to connect. The sensor unit appears to be chugging along just fine.

EDIT:
Both feathers had different client id's in the initialization

Thank you for the response and apologies for any confusion. I am using the broker on the rpi as an intermediary and I have had success in various tests. I am able to take data from the temp sensor on one feather, pass it via MQTT to the rpi broker and read it on a laptop. Similarly, I am able to tak...

First, I am very new to programming, microcontollers, and networking so please be gentle. I currently have two Adafruit Feather Huzzah's; Feather1 has a temperature sensor attached to it, Feather2 has a 7 segment display attached to it. I also have a Raspberry Pi running as an MQTT broker. The end g...