• Categories
    • Recent
    • Tags
    • Popular
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics
    • All categories
    • skywatchS

      [SOLVED] Serial problem

      Troubleshooting
      • • • skywatch
      57
      0
      Votes
      57
      Posts
      5532
      Views

      skywatchS

      @avamander Thank you for your suggestions.

      Your advice is good and I have already done a lot of what you suggested. I didn't put a scope on it, I may make another portable system and try that then as I do not see any pullups on the pro mini nor on the pi3 schematics. That could well be the centre of my problems.

      I also stumbled upon this page ...... https://spellfoundry.com/2016/05/29/configuring-gpio-serial-port-raspbian-jessie-including-pi-3/

      This also seems to pinpoint issues with serial on the Raspberry Pi 3B, and why they happen. Seems the foundation made changes that have had a detrimental effect on serial comms stability. It would explain why this happened after 'upgrading' from Pi 2B to Pi 3B. It seems conclusive to me that the issue is with the RPi 3B serial port not working correctly.....Live and learn I guess πŸ˜‰

      Still, for the last 4 days I have been running with a serial to usb adapter and no ghost nodes and no data spikes on the graphs. I wonder if there are pullups on the board? It's difficult to see clearly with the plastic wrapper on it!
      Things are looking very hopeful right now though...

      The only issue I still face is random loss of data from some nodes. The outages can be just one value report missing (Most nodes send data once every 5 minutes), right up to over 6 hours of data loss. Then suddenly it all starts working again. I might have more time now to look into that a bit morenow the system is stable again, but it is so random.

      I did also find quite a few 'less than good' dupont cables (from China) - So I have soldered directly a lot of connections now or modified/re-crimped the cables that were 'iffy'.

      Thanks again to you and Jkandasa for the support and help. I am nearly there with this now and can build some more nodes with confidence. πŸ™‚

    • J

      miscellaneous question

      General Discussion
      • • • JeeLet
      50
      0
      Votes
      50
      Posts
      417
      Views

      J

      on the drawing I forgot to put also the
      start/end the mini/maxi 0/50

      🍺

    • Y

      OTA firmware update with external MQTT broker

      General Discussion
      • • • yd
      46
      0
      Votes
      46
      Posts
      28714
      Views

      jkandasaJ

      @Marcel Thank you for your patience!

      OTA works in the following way,

      send available firmware details(version, checksum, etc.,) to the node If node thinks, it is a different sketch, it will request block by block. MyController sends firmware block data(requested block)

      When I have a new node, this will publish an auto node ID. Then I cannot upload new firmware because if I do this the default firmware will be loaded? I am not sure if that is even possible with manually assigned numberings of nodes.

      Assigning node ID is a different process than OTA. So do not get confuse with node ID assignment.

      So the next step is that I press edit on the new node and assign the firmware to it (that I added to utilities\firmware tab) and save this and the press the above button upload firmware? This seems to work but I am not sure if this is the correct process as I find this not very logical.

      Yes, this is the correct way to upload firmware and it is by design. You can keep any number of version of the firmware and assign a version to a particular node.

      When I would like to update a node, I add the software again to the utilities\firmware tab, edit the specific node and assign this new software and do the upload firmware again? Correct?

      Yes, correct

      The part where it did goes wrong is that I put the default switch on for firmware as I saw errors in the logging about this. Then this will upload software (which is already on another node) to the new node and you get duplicated node numbers.

      Default firmware should not contain node id statically. It is mainly used when we use MYSBootloader. With this boot loader, we may not have any firmware. So we can keep default firmware for the first time. and later we can switch to new firmware by assigning manually.

      That is up to our convenience. We can go without default firmware also.
      You can disable it as follows,
      461787f1-c759-4063-9c35-8af7e073c66d-image.png

      So preferable, I would like to see. Add also the possibility that you have a split menu. Upload Assigned/default firmware or upload firmware where you get a popup and select the one you would like to upload to your node.

      Yes, nice feedback/enhancement request. Could you please create a ticket in GitHub?

      Secondly, I had a problem with my boot software. The first time it advertises itself and after the upload of the new firmware, I could never upload new firmware again. I have downloaded the MySensors Bootloader and recompiled it for my hardware (slim node atMega328p 8MHz) and this bootloader seems to work okay πŸ™‚

      Great! I hope you have mentioned MYSBootloader ^^

    • EmenikeE

      Frustrated Newbie - Help with Nodes and Sensors

      Troubleshooting
      • • • Emenike
      46
      0
      Votes
      46
      Posts
      2636
      Views

      jkandasaJ

      @Emenike I do not find a variable Status in your variable repository screenshot, But you are trying to access it,

      var LoopThroughValves = mcApi.variable().get("Status");
    • jkandasaJ

      Mycontroller 2.x ideas

      General Discussion
      • • • jkandasa
      44
      2
      Votes
      44
      Posts
      5804
      Views

      skywatchS

      @jkandasa Here is another suggestion to think of for version 2.0.......

      It would be nice to have a feature that could be enabled or disabled with a click that will perform the following......

      Random Action - I am thinking of lights here for security purposes and making a building look more occupied than ordinary timers will allow. So a feature that allows random on times and random off times, within a specified portion (or portions) of the day/week/etc.

      Example
      Kitchen lights should be randomly turned on for minimum 2 minutes and maximum 5 minutes from 6am to 7.30am AND between 5pm -10pm.
      Bedroom lights should be turned on randomly for minimum 10 minutes and mazimum 20 minutes betwee 5.30am and 6.30am AND between 8pm and 11pm.
      And so on for different zones of lights.

      Once the vatiable are set then it should simply be a matter of enabling all when going away and perhaps you can even add a nice auto-disable for when you are away for a known number of days..... ?

      This could also apply to turning on/off radio etc to enhance the effect.

      πŸ™‚

    • jkandasaJ

      Custom widget

      Dashboard
      • custom widget guage dashboard • • jkandasa
      43
      0
      Votes
      43
      Posts
      23868
      Views

      jkandasaJ

      @fsgrazzutti Great catch! Thanks.

    • skywatchS

      Final 1.0.0 errors and crash report....

      Troubleshooting
      • mysgw • • skywatch
      40
      1
      Votes
      40
      Posts
      6006
      Views

      skywatchS

      @Tag
      See update here....

      https://forum.mycontroller.org/topic/224/booting-rpi3-mycontroller-from-usb-only

    • J

      Armbian - MyC V2 - install

      General Discussion
      • • • JeeLet
      37
      0
      Votes
      37
      Posts
      593
      Views

      J

      myC_2.x and influxDB1.8
      OdroidC2 and Armbian 23.02.2 Focal with Linux 6.1.11-meson64

      info helper/helper.go:29 welcome to MyController server :) info helper/helper.go:33 version information {"versionInfo": "{version:2.0.0-devel, buildDate:2023-03-24T15:27:53+00:00, gitCommit:7e4cd9f569fbf1b0894465bcdc023fe98704aad6, goVersion:go1.20.2, compiler:gc, platform:linux, arch:arm64, h> info backup/restore.go:170 executing import job {"sourceDir": "mc_home/data/storage/memory_db/yaml", "fileType": "yaml"} info helper/server_defaults.go:30 error on fetching system settings, assuming it is fresh install and populating default details. if not, report this issue {"error": "no documents in result"} error api.settings_api settings/update_geo_location.go:69 error on getting geo location, updating location details with default values and disabling auto update {"error": "Get \"https://ipinfo.io/json\": dial tcp: lookup ipinfo.io > info api.settings_api settings/update_geo_location.go:85 location data to be updated {"location": {"autoUpdate":false,"locationName":"Namakkal","latitude":11.2222469,"longitude":78.1650174}} info helper/server_defaults.go:104 there is no user available in the storage database. creating default user 'admin' info helper/server.go:401 checking for upgrade {"lastUpgradePatch": "2.0.0-1"} info route_handler http_router/handler.go:111 secure share directory included {"directory": "mc_home/secure_share", "handlerPath": "/secure_share"} info route_handler http_router/handler.go:116 insecure share directory included {"directory": "mc_home/insecure_share", "handlerPath": "/insecure_share"} info gateway_service gateway/listener.go:22 gateway service filter config {"filter": {"Disabled":false,"MatchAll":false,"Types":[],"IDs":[],"Labels":{"location":"server"}}} info handler_service handler/service_listener.go:86 handler service filter config {"filter": {"Disabled":false,"MatchAll":false,"Types":[],"IDs":[],"Labels":{"location":"server"}}} info system_jobs_service system_jobs/job_telemetry.go:41 telemetry data reporter job scheduled {"cron": "0 48 3 * * *"} info system_jobs_service system_jobs/job_telemetry.go:45

      bybye

    • jkandasaJ

      0.0.3.Final pre-release - volunteers required to test

      Announcements
      • pre-release release • • jkandasa
      33
      0
      Votes
      33
      Posts
      18820
      Views

      E

      Thanks, it is working for me now!

    • R

      MQTT sample setup on ESP8266

      MyControllerDevice (ESP8266)
      • • • ragflyer
      29
      1
      Votes
      29
      Posts
      23091
      Views

      Stephan35S

      Here is some good news !!!

      First after getting update from github , here is some screen shot from GUI

      0_1487795384107_Capture d’écran_2017-02-22_21-29-34.png

      We can see that MyController is in the list !

      Also, Esp send correctly data to mosquitto (which i use by default)

      0_1487795639762_Capture d’écran_2017-02-22_21-33-47.png

      0_1487795522154_Capture d’écran_2017-02-22_21-31-14.png

      Now , i have to test and learn to send data , like temperature or lighmeter .

      Thank you for your time and your support.

      πŸ˜†

    • J

      Scratch Analytics enabled

      Troubleshooting
      • • • JeeLet
      29
      0
      Votes
      29
      Posts
      346
      Views

      jkandasaJ

      @jeelet

      I realize that I give you a lot of work, I will try to reduce my requests.

      until it is a valid request, no worries
      I can work only on the request, when I get enough free time.

      So Bravo for the launching of the themes step, I test in the day, I will make a report this evening or tomorrow (a video ? πŸ™‚ )

      do it when you have free time

      ps: message notification finally works

      good to know

    • skywatchS

      1.1.0-snapshot, still having problems...

      Troubleshooting
      • • • skywatch
      28
      0
      Votes
      28
      Posts
      4695
      Views

      skywatchS

      8 Days and looking good - no errors, no crashes. Just a couple of nodes that misbehave sometimes......

      On that note, today I noticed one node had not sent data for many hours and when I got to it, the led connected to pin 13 was rapidly flashing. This is not normally the case, but I can't spare the laptop to monitor the serial port for a week+ just in case it happens again - any ideas? This was using the standard MYS prog for bmp180 pressure sensor. Running on mains powered 5v pro mini.

    • jkandasaJ

      MyController 1.2.0-SNAPSHOT version with major provider changes and supports for ack

      Announcements
      • snapshot ack provider • • jkandasa
      28
      1
      Votes
      28
      Posts
      5029
      Views

      T

      @jkandasa

      Cool!, Thx! will give it a try on the snapshot version.
      :thumbs_up:

    • jkandasaJ

      MyController agent for Raspberry PI

      General Discussion
      • raspberry pi agent mycontroller • • jkandasa
      24
      0
      Votes
      24
      Posts
      9165
      Views

      jkandasaJ

      @tag Thank you for the feedback.

      the CPU temp is shown as 0.049c instead of 49c

      I have filed an issue with pi4j. Seems it's fixed. Let me check with recent version and update.
      https://github.com/Pi4J/pi4j/issues/356

      Which image do you use (in my opinion armbian jesse is still the best..)

      Yes, I too use armbian. Which is super cool image for Orange PI

      and what is "hot" πŸ™‚ can you keep your finger on the cpu for a minute?

      Sure, Will update you πŸ™‚

    • jkandasaJ

      0.0.3-Alpha2 pre-release - volunteers required to test

      Announcements
      • pre-release alpha • • jkandasa
      23
      0
      Votes
      23
      Posts
      16748
      Views

      hotibH

      Hi Jeeva!

      I would like to test Alpha2!

      Thanks
      Tibi

    • N

      Mesh network and gateway?

      General Discussion
      • • • njbuch
      23
      0
      Votes
      23
      Posts
      14507
      Views

      N

      Yes it does. Thanks

    • jkandasaJ

      MyController 2.0 is ready for testing

      General Discussion
      • 2.0 • • jkandasa
      22
      0
      Votes
      22
      Posts
      507
      Views

      jkandasaJ

      @rmf69 said in MyController 2.0 is ready for testing:

      {"error": "Get "https://ipinfo.io/json": dial tcp 0.0.0.0:443: connect: connection refused"}

      This error may be due to you do not have internet access of your firewall blocks https://ipinfo.io/json
      To avoid this error disable auto location detection feature and enter your location details manually.
      169ca077-f371-43f9-9e8d-36b9f9ac47a8-image.png

      I do not see any error in the docker run. Can you please double check the availability of the mycontroller.yaml on your host machine?

      enter into the docker container and verify the file

      # docker exec -it mycontroller2b /bin/sh /app # cat /app/mycontroller.yaml
    • jkandasaJ

      Widget - Sensor custom buttons

      Dashboard
      • dashboard widgets custom buttons • • jkandasa
      21
      1
      Votes
      21
      Posts
      7414
      Views

      skywatchS

      @jkandasa I've just added the JSON settings for the amp, it was missing in the first post....Opps! πŸ˜‰

      Thank you for making it all possible! πŸ™‚

    • T

      I can't add a widget to a dashboard

      General Discussion
      • • • TomG
      21
      0
      Votes
      21
      Posts
      2260
      Views

      T

      @jkandasa Thanks much.

    • E

      custom widget: send command to node

      Dashboard
      • • • elgarfo
      21
      0
      Votes
      21
      Posts
      1368
      Views

      R

      @jkandasa Sorry... I thought I'd edited or deleted that reply saying it didn't work. It now works... I'd taken the sensor ID from the summary page and not the edit page as you pointed me to in your last reply.

      So its working now... my mistake, thanks for your patience.