Yep I think it would be a good idea to have a the link int the SolarPV guide too.
Simon
Yep I think it would be a good idea to have a the link int the SolarPV guide too.
Simon
Can the Home icon be added back?
It was one click to get to the âlatestâ topics by clicking the Home. Now itâs a few clicks or scrolling to the top and then clicking Community.
Thank you! Jon
PS - I really like the new changes. The Archived was a good idea to get to the old forum!
Hi @Jon , Iâve put it back. Thanks for the feedback.
I have read through the Electricity Monitoring section of Learn again, reviewing the content, fixing broken links and adding âstatusâ notes to some of the older content in the other software section. I have also tried to improve the structure and ordering with numbering and âadvancedâ labels in the navigation. Im generally happy now with all sections and I think its a large improvement over building blocks. I think the main questions / development points I still have are:
Is CT Sensor installation better suited for the guide?
I have updated the page on RFM12/69, I think it could still be better put together as a more comprehensive guide but perhaps sufficient for now
The RTD sensing page in the temperature sensing section is perhaps a little bit away from the standard OEM approach and the design and guide does probably need some more thorough work around calibration, lookup tables etc that I never worked more on as I switched to DS18B20 temperature sensors. It may be better to drop this section if there is agreement that its usefulness is limited. Perhaps a page for a personal github notebook.
In the Emoncms internals section: Architecture provides a good overview of how the basic framework of emoncms is built providing a build from scratch tutorial which fits well with learns intention. Global variables and Developing a new module are perhaps better suited to emoncms documentation rather than Learn but there is overlap here that may make it better just to have this section all in one place. The Input processing has been written as more a Learn type first principles guide.
In the Other Software section: I think there is useful content here on android app development that may provide a useful starting point for someone â they are perhaps a bit out of date now, Iâm not familiar with how the latest android and iOS apps have been built to evaluate.
All together we have removed the following pages that are currently in building blocks:
http://openenergymonitor.org/emon/buildingblocks
Trystan hi,
I took a look at the front page again today and itâs looking great. Congratulations on a great job.
The reason I was there was to track down emonESP for the STM32 discussion but I had difficulty finding it. I could find the community discussions about the firmware etc. but couldnât find how to set one up. Could you add this somewhere?
Also when I clicked on energy use I landed in the guide and then couldnât get back to the main page. Shouldnât there be a home button on the lower pages like there is on the community page. And also should there be a search?
Simon
Most of the emonesp info is on GitHub
Yeah, found it there Paul but thought it might be something that should be more upfront. At least a link to it. Maybe where Trystan has been revising the comms as this is an option to rfm and serial, so should be mentioned there.
Simon
Do you mean EmonESP for ESP8266? The STM32 is a separate platform, that EmonESP does not support.
EmonESP is intentionally not upfront since itâs still in development and not âofficiallyâ released. We donât sell any units with EmonESP pre-installed yet. Feel free to have a play, it works well itâs just not ready yet. Much more documentation and user guide will be added before we launch a unit with EmonESP software onboard.
Glyn, it was obviously late when you read my post - I said âemonESP for the STM32 discusssionâ. Obviously the emonESP has nothing to do with an STM32 platform.
emonESP is like the serial connection, it is an alternative to the rfm comms solution between the pi and emonTX/TH nodes. So it should be in the guides and learning section âas isâ. It might not be âreadyâ for you guys to make money out of but as you say in your reply, âit works wellâ, so should be included in the guides. The 2 solar diversion solutions work well but arenât part of the commercial enterprise but they are in the guides and learning sections because they are valuable resources.
Apologies, I was not aware of the STM32 discussion.
Yup, I agree it would be good to get it into the learn section. IHowever the emonESP is still under active development and not at all finalised. Itâs not about making money; itâs more a support issue. The EmonESP code may well change significantly in the near future as we develop the platform, we havenât got the resources to support it or document it extensively in its current beta state.
Neither is Martinâs solar diversion code⌠Let people see whatâs there. The emonESP in itâs current incarnation is a great bit of community development and should be highlighted even if it may change.
Simon
Can you explain?
If I go here â Home | OpenEnergyMonitor
and then the link at the bottom of the page to PV diversion, both the versions of the diversion schemes are there and are not supported except through the community. So I donât get the idea that because the emonESP code isnât developed enough to be made into a product it shouldnât be alongside the other methods of connecting emonTX/THs to Piâs i.e. alongside the info on rfm and serial. As Glyn says in his post it works pretty well as it is, so some people may find it useful and it rounds out the section on comms.
TBH I donât really care either way except that things that are useful should be easy to find. emonESP isnât currently, so I thought Iâd give you guys a heads up that you while you are making the improvements to the site, this might be one you would want to fix.
Simon
I detect a theme in your reply that I find a little disturbing. For the record, neither I (particularly as I contributed the documentation about the types of PV diversion, fully documented Martin Robertsâ diverter, contributed part of Robim Emleyâs diverter, and a lot of Building Blocks) nor any of the other moderators are in the pay of OEM, nor do we control what is published here.
In the particular case of Martin Robertsâ diverter, it was developed and published long before ESP made an appearance, and I doubt that Martin wants to rehash his design now. So Iâm still not sure why you lumped it in with a comment about not being able to find anything about ESP.
If you want to modify Martinâs or any other code to work another way or with a different interface to the outside world, feel free to do so and while youâre at it, document it and publish it.
Robert, not sure where youâre getting the hump from but apologies if Iâve said anything that might offend. Given as you say, you are a moderator and donât control whatâs published on the new front page and learn.openenergy, maybe it would be better to let Glyn decide if they want to put the emonESP in the comms section.
I know very well that Martinâs code was published before the ESP - and Iâm sure no one would want to rehash the design to fit on an ESP alone as it wonât hack it. The emonESP is to quote from GtiHub âESP8266 WIFI serial to emoncms linkâ. It only does the comms. Takes in the serial output from an emonTX or emonTH and sends it by WiFi to emoncms.
My comment about Martinâs code was as an example of community developments that have been published on the new learn and resources pages and was in response to Glynâs suggestion that it was still under development therefore shouldnât be published even though it did work pretty well.
Finally I have modified Martinâs code and have on several occasions made my changes (to handle more temperature sensors) available to folks discussing the code on the old forum.
Simon
I understand your point @Bramco about highlighting potentially useful content. EmonESP is one such development that has perhaps now reached a level that for the advanced user is useful to know about. We need to think about the best location for it and how to best add it in and then write the suitable documentationâŚ
I also note your point about linking to the SolarPV diversion from the SolarPV guide, a note perhaps of the form "You may also be interested in PV Diversion see Learn: PV Diversion "
I feel there also needs to be a place to link things that are still in development. A list of ongoing OpenEnergyMonitor development projects - where no requirements are made of documentation quality, support etc
We have updated http://openenergymonitor.org to point to the new home page today and Iâve implemented the redirect map on the old building blocks so that URLâs map through to the correct locations in Learn.
Im logging failed redirects so that we can fix any that Iâve missed.
That would be a great idea, or maybe even if you could include things like emonESP (and maybe it might be better to rename it to avoid the sort of confusion above) but have some way of indicating that they are still in development, e.g. an * or some other symbol.
I mentioned putting the emonTX link in with rfm and serial because I seem to remember seeing a section on this on the new site. Iâve not been through all of the pages of course and may be wrong but something along the lines of⌠Anyone having issues with rfm connections could try the serial connection or emonESPâŚ
Anyway, great work and very nice design - itâs a credit to whoever has done all the hard work.
Simon
Talking to @glyn.hudson suggested that a sticky thread on the top of the labs forum listing all active developments could work providing a page that was much like the intention of this old labs page: Home | OpenEnergyMonitor
Hereâs the new home page now live at https://openenergymonitor.org
As @TrystanLea mentioned above the building block links are being re-directed to learn
, e.g:
https://openenergymonitor.org/emon/buildingblocks/ct-sensors-introduction
now re-directs to
https://learn.openenergymonitor.org/electricity-monitoring/ac-power-theory/introduction
A note alerting the user has is added to the top of the page if itâs visited via a re-direct:
Please us know if you spot any errors