Jump to content

BobMic

Members
  • Posts

    50
  • Joined

  • Last visited

About BobMic

  • Birthday 12/05/1955

Profile Information

  • Location
    Simi Valley CA
  • Occupation
    Engineer

Recent Profile Visitors

665 profile views

BobMic's Achievements

New

New (2/6)

8

Reputation

  1. Just had the same issue going from 2.2.3 to 2.2.11 and that was the fix. My symptom was PolyGlot kept trying to restart and fail. Found that with "ps -ef | grep poly". It returned a new process number each time I ran ps. I thought this info may help someone that runs ps and sees it there. The process was running at any given moment but then died and restarted. I had the sane result of not being able to connect to the UI. First time it failed I moved the /home/pi/polyglot/polyglot-v2-linux-armv7.old to polyglot-v2-linux-armv7 and V2.2.3 came back up fine. Now on 2.2.11 thanks to this Openssl fix, thanks!
  2. Update on this. I was again fighting the status of the button LED's not matching what the management console was showing when the scenes were triggered in Mobilinc. It turns out that the older 2486 KPL's don't work correctly. When I select a fan speed in Mobilinc all four button LED's light. The correct speed is set and the management console shows the correct LED lit and the other three off but that is not the case on the KPL, all four are lit. It works perfectly on the 2334 KPL's.
  3. Interesting, that's not the case for irrigation controller. All of the header pins for the daughter board, except for v+ (1) and GND (8), go to IO pins in the PIC microcontroller. The program in the PIC 16F648A must be the same for USB and Serial, it's not on the irrigation base boards. For one thing pin 6 on the header has a 1OOhz 1ms clock pulse. Header pinout 1 - +21v 2 - PIC pin 9 RB2/TX/CK 3 - PIC pin 12 RB5 4 - PIC pin 14 RB7 5 - PIC pin 8 RB1/RX/DT 6 - PIC pin 11 RB4 7 - PIC pin 13 RB6 8 - GND
  4. I tried to use a 2413U base board to replace the base board in a EzFlora and it didn't work. There is a PIC Microcontroller on the base board and for sure it has a different program loaded on the EzFlora. It seems like the daughter boards are just IO interfaces and the programming is in the PIC on the main board.
  5. I just looked at their web site again and have a couple of questions. Are the stations that are selectable on their map (website) ones that are available to choose? How do I chose a specific station or is it just Lat/Long and the closest is the default? It's interesting that they pitch the mob data as giving the ability to compile "personalized forecasts" but your saying that at this time they don't provide them to station owners? Or it it only presented on their app? It seems like a perfect opportunity to track weather patterns as they travel from station to station. Thanks, Bob I'll try the cloud version and also the other two that you listed
  6. Thank you Bob for the clarification on all of those points and also for all of the work you do for our ISY community.
  7. Excellent! I'll try and contact him and give him a rebate to let me get his data. Do the shares get the same access to the data as in will Bob's WFNodeserver work?
  8. I think I should go that way. I looked at their map and there is one a few blocks from me. Can you share the data with other people? The way you said the neighbors love it, makes me thing that might be what you are doing.
  9. What does Aeris cost? I'm not having any luck with OpenWeather.
  10. I just tested my config and double tap of any button does put the fan controller in high and the buttons are out of sync. I think you are right in that the only way to get around that is to use a program that sets the fan and LEDs status for an "on" or "fast-on" to the same appropriate level. That may be what led me to hide all but the "on" button in Mobilinc. Thanks for pointing that out!
  11. Not sure because I don't use the admin console to control them. Most of my problems were related to Mobilinc Pro and that was my motivation to do the testing and write up. I'll test the double tap and report back. Notice I removed all buttons in Mobilinc except for the "on" button which I renamed to "select" because I was getting unreliable results with other buttons so my "select" gave the same results every time.
  12. Thanks, it took quite a while but now I have a standard procedure. Buttons worked fine but I have never been satisfied with the way Mobilinc was controlling it. That's why I decided to push every button and check/uncheck every box to find the closest path to my Mobilinc goal. That's a great addition to my bag of tricks, thanks! I have never tried toggling a fan speed on and off so didn't realize the off is redundant. I like the idea that the fan and light can be controlled by the four buttons and the local up/down dimmer can be used for something else. Another option is an eight button KPL controlling two fan/light systems. Now you need to spend half a day sorting out how to write that up so anyone can understand...?
  13. After reading many posts on keeping status in sync on this setup and having mixed results for a very long time, I have created a step by step of my best results. I welcome all comments and corrections. I am by no means an expert but have tried to explain why I have done things the way I did and what the outstanding issues are. To put all of that in a format that I hope anyone can understand and learn the Intricacies of Mobilinc - KPL LEDs and scenes, ended up quite long. I'm sure the experts will be bored to death but I expect some will get what they need. I also hope the experts will improve on the things that I still struggle with. Fanlinc – KPL keypad – Mobilinc Pro Link Fanlinc controller and Keypad. Check box “remove existing links” box. Create separate folders for the devices and the scenes. Name them to whatever makes sense to you. Move Fanlinc and the five keypad devices into the devices folder. Rename Keypad buttons and Fanlinc devices. – note order in Mobilinc is alpha/numeric so put 1,2,3&4 ahead of 1-High, 2-Med, 3-Low & 4-Off. If you don’t do this the order will be High, Low, Med & Off, alphabetically in Mobilinc. This is the only way I have found to order things in Mobilinc Pro. Set button toggle mode to "all non-toggle on" then set light button to toggle. Create a scene for each button, Light, 1-High, 2-Med, 3-Low & 4-Off. Again, to keep the order correct in Mobilinc, put 1,2,3,4 in front of the scene names. Move the scenes into the scenes folder and build the scenes with the devices and the buttons as follows. Add the Light device to the Light scene and the Fan device to each of the fan scenes as responders. Add the Light button to the Light scene as a controller. Add the Fan 1-High button to the 1-High scene as a controller, add the 2-Med, 3-Low & 4-Off buttons as responders. Add the Fan 2-Med button to the 2-Med scene as a controller, add the 1-High, 3-Low & 4-Off buttons as responders. Add the Fan 3-Low button to the 3-Low scene as a controller, add the 1-High, 2-Med, & 4-Off buttons as responders. Add the Fan 4-Off button to the 4-Off scene as a controller, add the 1-High, 2-Med & 3-Low buttons as responders. The next steps set up the “scenes” items to the desired states when selected in Mobilinc. Click on the 1-High scene, select 2-Med at the top of the page, change it to “off” and click the “update” button on the bottom of the page. Set 3-Low & 4-Off to off the same way. Leave the Fan controller set to high and the 1-High (controller button) set to “default”. The on and off state of the buttons reflects the LED state when the “Scene” is selected in Mobilinc Pro. It does not set the status if the scene is selected with the KPL, we will do that later. Click on the 2-Med scene, select the Fan controller, set to med and click the “update” button at the bottom. Click on the 1-High, 3-Low and 4-Off, switch each to off and update, again leave the controller button set to default. Do the same for the 3-Low and 4-Off scenes respectively. The next steps set up the “scenes” items to the desired states when selected with the buttons on the KPL directly. The settings will be the same as for the scenes settings in the last group but instead of selecting the scene, click on the controller button in each scene and set the states. Click on the 1-High button (the controller) in the scene tree, select 2-Med at the top of the page, change it to “off” and click the “update” button on the bottom of the page. Set 3-Low & 4-Off to off the same way. Leave the Fan controller set to high and the 1-High (controller button) set to “default”. Click on the 2-Med controller button in the scene, select the Fan controller, set to med and click the “update” button at the bottom. Click on the 1-High, 3-Low and 4-Off, switch each to off and update, again leave the controller button set to default. Do the same for the 3-Low and 4-Off scenes respectively. Test buttons on the KPL while watching the fan controller, if they don’t stay in sync check the scene settings for each controller button in each scene. The controller button settings control the scene for button presses. The scene settings only affect the scene triggered by Mobilinc Pro. This took a while to sink in for me so I have repeated it and if it doesn't make sense read it again. This is very important to understand troubleshoots the LEDs when they are not staying in sync. This concludes the set up in the ISY. Mobilinc Pro Setup Make sure “Show Hidden Items” check box is not checked in Mobilinc Configuration. Hide all entries in the “My Devices” folder created above to prevent changes from being made to the fan/light controller or the KPL buttons directly which will get things out of sync with the KPL LEDs. Go into the “My Scenes” and the scene folder made above and select one of the fan button scenes. Choose “Advanced Options” at the bottom. At the top under “Custom Command Names” select and delete the text for each “BRIGHTEN, OFF, DIM, FAST ON and FAST OFF”. This will hide those buttons. Change the text for “ON” to “Select”. This select button is the only control you need to activate the scene. Using any of the other buttons just adds complications and there is no benefit. Change the icon to the fan icon. Select the Light button and advanced, change the icon to the chandelier icon. (my preference, you can use whatever you like) Don’t use the sliders in the Light scene or it will get out of sync. All the buttons will work correctly. Unfortunately, in the Android version of Mobilinc Pro the button icons don’t show the correct status and tapping on the icon does not work correctly. I believe this is caused by how Mobilinc presents a percentage based on all devices in the scene rather than the status of the controller in the scene. The correct status is displayed when you go into a button scene to select it. The icon tap seems to be an on/off toggle. Both the display and icon tap seems to work correctly in the iOS version. I hope this helps someone understand the interaction of these devices. Writing it up has made it very clear to me and I'm now in sync! Bob
  14. It doesn't look like it does the handshake when I plug it in, LED just goes green solid. I have one of their units with the 2412. I thought it was an older version, it's labeled EZRain V1, has a blue LED and doesn't have a removable connector. It's the one I used to replace the problem one. It has a different daughter board also. Much smaller to leave room for the big transformer of the 2412.
  15. Yes I made sure the pins engaged properly and even tested the voltage on the daughter card to male sure they were electrically engaged. I tried to auto link with the event viewer open on level 3 but the EZFlora doesn't go into "link mode" when I hold the set button. I tried one of my other EZFloras and it goes into link mode when the button is held but also didn't show up on the log or linking GUI. Thanks for the try, at least I know it is acting different than the good one by not entering linking mode. Pretty sure linking is a function of the 2413X and not the EZFlora daughter card. I may take the good one apart and test that by swapping the daughter cards.
×
×
  • Create New...