Topics created by jkandasa

@hek I see that MySensors logo is missing in the forum

@Yveaux said in serial, Ethernet to MQTT: Of course, but MySensors MQTT gateway runs just as fine when connected over cabled ethernet, as when connected over wifi I do not know that Now on this tool, I do not see much benefit from ethernet to MQTT Still, it is good from serial to MQTT.

Gateway >> Node >> Device >> Metrics Nodes have devices attached and each device has metrics.

@skywatch @mfalkvidd Thank you for your comments. I am using Moteino R4 and RFM69 connected to hardware SPI pins. I tried the same pin with softSPI, but I could not get success. Now I have altered the ADE7763 Arduino library to update SPI settings on every call. And added code to update the only flag on ADE7763 interrupt(like we have in RFM69_new library). Seems all look somewhat ok. I think for RFM69 we use a default clock speed. for ADE7763: SPI_CLOCK_DIV4 Are you using pull up resistors on the CS lines to each device - that might be worth a try too.... Yes, I have

@jkandasa the gateway is stateless, it has no concept of queue.

@jkandasa Any news here? (still have my rfm69 Boards here to check of the range is much better)

@jkandasa Brilliant - thank you!!!

Hi, when using smartsleep parameter of sleep(), a msg is sent before (and after): I_PRE_SLEEP_NOTIFICATION I_POST_SLEEP_NOTIFICATION https://www.mysensors.org/apidocs/group__MyMessagegrp.html#ggaa6f265dd19e9cad90979fef252e17a87a105639edd79e6f1d0104986aa6370de7 https://github.com/mysensors/MySensors/blob/af3452f91c15b60cc7666b6225fa7342f08a6f52/core/MySensorsCore.cpp#L595 https://github.com/mysensors/MySensors/blob/af3452f91c15b60cc7666b6225fa7342f08a6f52/core/MySensorsCore.cpp#L647

I don't know why but now OTA works better; I still get quite some NACKs on the gateway but at least most of the times the OTA is successful even with signing enabled. With ACK enabled the transfer speed is at least 4/5 times slower

High sensitivity: down to -148 dBm. From the datasheet. There probably needs to be some margin, but my experience with Sigfox shows that -130 is quite reliable. After that, packets start go missing. I would guess LoRa is similar.

@jkandasa I just finished a Gateway build with TinyGSM. You can find it here: https://www.openhardware.io/view/567/MySensors-GSM-Gateway

@jkandasa Great! Thanks for pointing me out. I'll take a look. Regards

There is, I have loaded 5 but none work, besides the first time that actually did started the ota transfer

Testing now and so far the mysensors smartsleep etc is working perfectly. What a great controller, thank you for your hard work. I will maybe switch to this in place of Demotic.

@jkandasa Thank you for the update. I will use this controller in production in few days. Eactly what I want. For non-msensors devices I Will use node-red as glue !

@jkandasa said: @pebri86 Yes, I will implement smartSleep feature. But it will take bit more time. may be after release. Please raise a ticket for this feature request to follow. https://github.com/mycontroller-org/mycontroller/issues between what type of actions do we(controller) need to do with smartsleep nodes? Actually all action like reboot, erase configuration, or send values to node since all battery node do sleep all the time and can't response while sleep.

Ok, I feel pretty dumb not to have thought of it before, but I've found the issue. For the sake of anyone running in the same issue, if you are running an ad blocker, try to disable it first. Looking at the request in Chromium, it said "ERR_BLOCKED_BY_CLIENT" Turning off the ad blocker resulted in a dashboard as you would expect it. Sorry for bothering you for something I should have thought of, and thank you for your support.

@hoegaarden_bier said: Question: When my sensor node does a 'requestTime', what time (epoch) does it send back? Is this UTC, localtime???? will send local server time with local timezone. https://github.com/mycontroller-org/mycontroller/blob/development/src/main/java/org/mycontroller/standalone/mysensors/MySensorsMessageEngine.java#L211

@hek said: That's plain wrong. Created a PR here: https://github.com/mysensors/Arduino/pull/316 Thank you @hek !!

@hek I am back from work. In 10 mins I knew what was the problem and you won't believe it Since I was flashing at first the gateway, thus I defined the MY_SOFTSPI and didn't commented it back when I was flashing the relayactuator ! What a mistake !! I'll keep you updated as I'll start development the logic for the gateway using mqtt and the other node. Thanks hek.

@jkandasa I've created the topic there. Thanks.

expensive? 0.30€ each at digikey (not as cheap as 10cents, of course you need to make a min order to not have shipping fee. why not group your needs). or same price at aliexpress (longer delivery, patience is not my biggest quality too). I can't help you sorry, i hope you will find it.

@mvader said: @jkandasa said: Right now it's taking system timezone as timezone. I hope if we give it as configurable option may leads confusion. it seems to default to Version: 0.0.2-alpha5, Timezone: UTC(+0000) i have the TZ set correctly on my rpi2 (i'm EDT timezone) thanks You have to set timezone with the help of raspi-config https://learn.adafruit.com/adafruits-raspberry-pi-lesson-2-first-time-configuration/changing-timezone I believe your rpi still with UTC. If you run date command from your raspberry PI what is the output? i must have had a browser cache issue or something, the next day i came back and it said EDT. so it appears my system clock was indeed set to UTC. One comment on something you said above. " I hope if we give it as configurable option may leads confusion." I think that given the audience here, there isn't much that would confuse people. If you were dealing with people who didn't know anything about electronics, or computers, maybe, but to be honest i can't see how it would confuse anyone, much less anyone here.. just my thoughts.. @mvader Thank you! What I mentioned here is, Say if you are running your system with UTC time (People always set system time as where they are living) and you change MyController time to EDT. Now confusion stars this way. Sunrise/Sunset time (you set latitude and longitude for your location(UTC), time will be displayed in EDT) Message received from sensor will show in EDT, As you are in UTC there is chance to thing like it is old log, etc., While scheduling 'Timer' will get confuse (Will be scheduled in EDT timezone). I believe it is good to go with system time. Top most we have to rewrite the code in many places now to circle around to the firmware issue. the nodes that use dual-optiboot, are mostly the sensebender micro boards. these are typically battery powered devices that sleep most of the time. with the library 1.5, you have an OTA enabled setting and when the device boots, it listens for a defined amount of time for an OTA upgrade signal. I've tested this with MYScontroller and it works. when i reboot the device, the firmware upgrade takes off. I rebooted the device manually and nothing was sent, so it seems like something may still not be working correctly. with your implementation. Thank you for your effort and time on this. Let me check how dual-optiboot works and will check the implementation MyController also.

Yes, this has been on the TO-DO list quite some time.

@artur said: and who will MQTT broker? You are right! I misunderstood something here! I believe I have to create code for MQTT broker with MyController http://forum.mysensors.org/topic/2285/mqtt-broker-support-in-mysensors-1-6

Good to her you found that point . Imo you'd better change also your receive functions to not react on "ack" messages (via "else" prior to message.type-comparison).