Topics created by micah

@hek Oh, I didn't know I needed to use both. Well I tried a million combinations after seemingly reading everything on the subject, and I still couldn't get {int + char + int} converted into a char[] using strcpy and strcat for some reason my brain is just not wrapping itself around the concept today... maybe I'll come back to it tomorrow. In the mean time, I tried the following and it worked. char buf[20]; sprintf(buf, "%d.%d", Alarm1_Time_Local[0], Alarm1_Time_Local[1]); send(MySensors_MSG_Alarm1_Time.set(buf), true); I've read that using sprintf increases the size of your sketch... but for now I'm fine with it, since it works and I can move on to being creative and productive.. lol

UPDATE I think it's a problem with the arduino board itself. So since my previous posts I've tried multiple radios and I've got a 4 working nodes now: Mega + NRF24 UNO R3 + NRF24 DCcEle (clone) + NRF24 Nano DCCduino (clone) + NRF24 Plus the Raspberry Pi 2 as gateway with NRF24L01+ PA/LNA is working. So... it seems like it's a problem with that Uno board.... weird. I've tried multiple radios (specifically ones that worked on the other boards) and none of them work. Like I said before, the board and the Rp2 seem to be communication but not properly. Has anyone ran into a similar problem before?

@micah said: @sundberg84 said: Hard to say. St:fail generally means that you don't get ack from the receiver. This is normally range, power or hardware. There is not a general fix for this but you need to try and learn... i admit its strange I worked for some days. Maybe a radio fried ? Don't have the radios to close to eachother. Try a.couple of meters. Sorry I'm out of more solid ideas. Hey sundberg84, quick question for you. If you look at my debug logs above it looks like the gateway is infact receiving the message but the node thinks it fails. Con you confirm my interpretation of the following two lines? NODE DEBUG send: 42-42-0-0 s=1,c=1,t=0,pt=7,l=5,sg=0,st=fail:20.0 GATEWAY DEBUG 0;255;3;0;9;read: 42-42-0 s=1,c=1,t=0,pt=7,l=5,sg=0:20.0 If that's correct, could that change what the issue might be? Yes, I saw that - it seems to work one way but the ack (return) does not reach back. So its on the edge. But this should update the value in your controller.

@micah said in Can't get OpenHAB2 to see my MQTT messages: I'm still not sure if the second and third line in the mqtt-eventbus.cfg is correct. I don't have MyMQTT anywhere else, so I think I may try different combinations to see what works. MyMQTT should be replaced with brokername (mysensors in this example). openhab will then publish the event to the mqtt broker on its topics (useful if you use f.eks. node-red for openhab rules)

@alexsh1 said: @epierre The only downside is (1) price and (2) it cannot be used with batteries For these factors alone, the Figaro looks very appetizing.

@TheoL you are probably completely correct. I don't actually plan on building it.... it was just an interesting thought exercise.

@micah said: @alexsh1 said: @micah I think you can get a Samsung Class 10 microSD card for like $10 or something. I would avoid using a noname card from eBay/Aliexpress. Saves a lot of time. BTW - this is hardly RPi's fault, isn't it? Your right, it isn't the RPi's fault, although would it kill them to just include an 8gb flash chip on the device Re flash on the device - That's completely different discussion. What needs to be onboard is an endless talk - there are a few of those threads on raspberry.org . Personally, I am fine with the microSD card.

I hate to disappoint you @micah but @Mike-Musskopf has got a point: MQ* sensors are power hungry. You may want to connect everything up to 240V via a small PSU. There is a big thread on mysensors about air quality detection. DHT is not the best sensor for a battery application. Please check BME280 (pressure, temp and hum) or Si7021 (temp and hum) - these would be my favourite sensors for low power consumption. Small tip - your Arduino Pros must be 3.3V and not 5V for the battery usage.