MyController.org

@manusovich Thank you for the explanation. Yes, it's true nowadays we re using mobile more than computer. We should have modern GUI for mobile too. For this I'm working with the request https://github.com/mycontroller-org/mycontroller/issues/56 Currently analyzing with http://ionicframework.com/

@manusovich said: Hey there! First of all let me say big thank you for everything what you are doing here. That is the most "enterprise" level open-source implementation for home controller which i ever saw. Great job! Can you consider to add one more dashboard item type - static image from disk + refresh period for that on dashboard. It can be worth when we have another systems in our home network and they are producing such images. For example for me it is traffic in the city - i have script which is generating that in rush hours and saving as image on the disk. That will be nice to have that on dashboard. Does it make sense at all? Alex HI Alex, Thank you for your interest with MyController.org. Kindly open a request on github page. https://github.com/mycontroller-org/mycontroller/issues Yes, this looks nice feature and generic one. we can use it for anything.

@sundberg84 Thanks! Ok, this behavior is different from mine. I was hoping we had a similar experience. I just downgraded from the beta to the latest stable release. I'll see if that helps...

Ok thanks, New version demo running well. Nice to see the Dashboard! I will wait for the 0.3 Alpha release. Regards, Al

@mwild95 for now with 0.0.3-alpha1 release you can configure with group payload ON/OFF. but there is a request for this feature. I will implement when I get time. https://github.com/mycontroller-org/mycontroller/issues/47 Thank you!

@bruseisi have you tried with? mycontroller/bin/start.sh

omg thank you so much. i dont know how i missed that

@Kurt said: Thx! Turned out to be a combination of cached data and a power delivery problem at my gateway. All working fine now. Any hints at how to test the (guess alpha) MQTT broker? Kurt @Kurt To use MySensors.org 1.6 dev branch MQTT gateway we should(I guess) have a MQTT broker. So I have added inbuilt MQTT broker to provide easy setup for users. Two options available for MQTT broker. Use MyController.org MQTT broker (by default will be enabled, configuration will be available in mycontroller/conf/mycontroller.properties). You can modify or use default port number(1883) Use external MQTT broker. In this case if you use external MQTT broker on the same machine, you should disable MQTT broker of MyController.org. You have to configure MQTT client details here mycontroller/conf/mycontroller.properties you have to change the following lines based on MySensors.org MQTT gateway configuration mcc.gateway.mqtt.topic.publish=mygateway-in mcc.gateway.mqtt.topic.subscribe=mygateway-out

@doxikus said: Hi, I have problems with SD cards, read/write issues, so I have new one, Jessie is installed, I have running mycontroller over one week on RPI A+ without problems :-). Now my next problem is how to attach sensor getaway over usb hub :-). I have for getaway arduino uno with NRF24L01+ library is uploaded, over serial monitor looks ok, so I would like to know how to connect to RPI :-). Problem is with settings, which serial port I should use!? Right now it is with default settings, mcc.serialport.driver.type=auto mcc.serialport.name=/dev/ttyUSB0 Do I need to change something here!? How to know which serial port I need to use!? dmesg!? Maybe to consider using ethernet gateway!? Thanks again @doxikus Perfect! Yes you have to change this line if you are using serial port. mcc.serialport.name=/dev/ttyUSB0 I believe you have connected your arduino UNO with USB port, If yes, the port will be similar /dev/ttyUSB0, run this command on your RPI, ls -l /dev/ttyUSB* or ls -l /dev/tty* It will list available ports, you can find the odd one out easily! MyController.org supports for Serial, Ethernet, GPIO(RPI) and MQTT(master branch). You can use either. For now you can go with serial as you have the setup ready to go :thumbsup:

@pierremv said: Looking forward to try 0.0.2-alpha6. Will the combination with Mysensor v1.5 work too ? MySesnors v1.5 MQTT will not support for OTA, If you want to go with OTA support via MQTT you should upgrade your MySensors version to v1.6 As I have different other MQTT clients in my network, I'm planning to stay with Mosquitto as MQTT broker. That's also the reason why the MQTT gateway acts as client and not as broker. Nevertheless, I do understand your reasoning to simplify the setup by adding MQTT broker support. MySensors v1.6 MQTT completely redefined. Reference link for further information. MyController 0.0.2-alpha6 version have inbuilt MQTT broker as well as client. You can use inbuilt MQTT broker as like broker you are using outside. It will support for other clients too. That's up to your wish. You can use it or disable it. Thanks for your support, appreciated ! Cheers, Peter

@supagusti Your request has been implemented. Changes will be available in 0.0.2-alpha6 release. Thank you!

@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

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

Thank you

@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 :wink: 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.

@jkandasa said: What are all the languages should we support? Can you add more details on this in github? answered on github

@jkandasa said: https://192.168.6.220:8443 YES!!!!! That was the problem!!! Thanks already working I already added some sensors and its working Beautiful!!!!! Hope you keep developing and keep the good work!!!! Best regards