PiDome Domotica/Home Automation
-
@Francois I have continued the normal development path of this feature. Otherwise i would be "hacking" the code and then remove this to be able to continue normally. I do have a quick build ready, could you check the latest build (510) if it is working for you?
-
@Francois Good!
@tortoisedoc Are you able to use the node assignment? -
@John I must say that you product is getting better with every release. This new discovery process that you now add is making things ever easier to add sensors to the system Thanks for all the hard work that you are putting into this project. I real appreciate this. Keep up the good work. You product just work and I don't have to worries about it.
-
@John I must say that you product is getting better with every release. This new discovery process that you now add is making things ever easier to add sensors to the system Thanks for all the hard work that you are putting into this project. I real appreciate this. Keep up the good work. You product just work and I don't have to worries about it.
@Francois Thanks for your kind words! Too bad you didn't download the release on the builder this evening, you have fallen in a test sequence ;).
When the routine is completely implemented i will post a follow up on this feature.
-
@Francois Good!
@tortoisedoc Are you able to use the node assignment?@John said:
@tortoisedoc Are you able to use the node assignment?
Unfortunately not.
See here: appLog.txt
At this point, im starting to suspect about the PI. The miniterm shows correctly the gateway startup tho. -
@John said:
@tortoisedoc Are you able to use the node assignment?
Unfortunately not.
See here: appLog.txt
At this point, im starting to suspect about the PI. The miniterm shows correctly the gateway startup tho.@tortoisedoc The only thing i see is a gateway ready message, i do not see any node presenting or asking for a node address. I suspect that this information is also not available in miniterm. If it is, you have to try again without miniterm cause this then is interfering.
-
@ceburge Is this a fresh install or an update? If this is an update please clear the browser cache and re-open the browser
@John said:
@ceburge Is this a fresh install or an update? If this is an update please clear the browser cache and re-open the browser
It was indeed an update. The clearing of the browser cache did the trick. Thanks alot.
By the way. Love your work you are doing with PiDome. It is user friendly and something that most people can funtion in. Keep up
the good work. -
@John said:
@ceburge Is this a fresh install or an update? If this is an update please clear the browser cache and re-open the browser
It was indeed an update. The clearing of the browser cache did the trick. Thanks alot.
By the way. Love your work you are doing with PiDome. It is user friendly and something that most people can funtion in. Keep up
the good work.@ceburge Thanks! And that's exactly the thought behind the project (not in the beginning because it was a personal thingy, but has grown in to), try to create something most people would be able to use. It still needs a lot of work, but it's getting there. We have planned very exciting stuff!
PiDome relies heavily on the browser cache, one of the reasons why it responds relatively quick in most situations. So if there is any error with title "Interface error", clear the cache ;).
Cheers!
P.S. the reason for this error is due to the fact the messaging has been optimized, where possible device values which can be updated are now in one single message instead of four (if a device has four controls and/or data fields).
-
@tortoisedoc The only thing i see is a gateway ready message, i do not see any node presenting or asking for a node address. I suspect that this information is also not available in miniterm. If it is, you have to try again without miniterm cause this then is interfering.
@John said:
@tortoisedoc The only thing i see is a gateway ready message, i do not see any node presenting or asking for a node address. I suspect that this information is also not available in miniterm. If it is, you have to try again without miniterm cause this then is interfering.
@John Ok, here more logging:
appLog.txtThere is actually data coming in - but the visual part is empty both in the driver's section as well as the "new" section for non-discovered devices.
PS I tested this in Chrome as well as in Firefox;
and the result is empty :
-
I believe there may be something wrong with the serial driver now. It was working like a charm in a previous build. Not sure what that build was though. I decided to update to the 510 version build due to the fact that I could never get my MQTT Gateway to auto discover devices. However I decided to go ahead and test what I already had working in the new build and it doesn't function correctly.
I am including an image of the drivers page I now see when using a serial connection. App log i there to if you want to look at it
-
@John said:
@tortoisedoc The only thing i see is a gateway ready message, i do not see any node presenting or asking for a node address. I suspect that this information is also not available in miniterm. If it is, you have to try again without miniterm cause this then is interfering.
@John Ok, here more logging:
appLog.txtThere is actually data coming in - but the visual part is empty both in the driver's section as well as the "new" section for non-discovered devices.
PS I tested this in Chrome as well as in Firefox;
and the result is empty :
@tortoisedoc and @ceburge The builds on the build server are still test builds regarding discovery and driver web front end API. They are getting more stable but is still a work in progress. The builds which are following up are tests to test the progress of the current development roadmap regarding these.
This is a known issue and am working on it while the development progresses.
Excuse for any inconvenience, hope to have this functionality done asap.
P.S. I'm looking into the possibility to also have the node address requests being passed to the discovery collection page, all though it is a complete different internal process trying to make it coherent.
-
@tortoisedoc and @ceburge The builds on the build server are still test builds regarding discovery and driver web front end API. They are getting more stable but is still a work in progress. The builds which are following up are tests to test the progress of the current development roadmap regarding these.
This is a known issue and am working on it while the development progresses.
Excuse for any inconvenience, hope to have this functionality done asap.
P.S. I'm looking into the possibility to also have the node address requests being passed to the discovery collection page, all though it is a complete different internal process trying to make it coherent.
@John said:
@tortoisedoc and @ceburge The builds on the build server are still test builds regarding discovery and driver web front end API. They are getting more stable but is still a work in progress. The builds which are following up are tests to test the progress of the current development roadmap regarding these.
This is a known issue and am working on it while the development progresses.
Excuse for any inconvenience, hope to have this functionality done asap.
P.S. I'm looking into the possibility to also have the node address requests being passed to the discovery collection page, all though it is a complete different internal process trying to make it coherent.
Sounds great !
Thank you for your efforts! -
@John said:
@tortoisedoc and @ceburge The builds on the build server are still test builds regarding discovery and driver web front end API. They are getting more stable but is still a work in progress. The builds which are following up are tests to test the progress of the current development roadmap regarding these.
This is a known issue and am working on it while the development progresses.
Excuse for any inconvenience, hope to have this functionality done asap.
P.S. I'm looking into the possibility to also have the node address requests being passed to the discovery collection page, all though it is a complete different internal process trying to make it coherent.
Sounds great !
Thank you for your efforts!@tortoisedoc It has to work correctly, so will continue on it until it does.
Today there will be sequential builds which will introduce new discovery options. The new method will also include discovery of mysensors devices which do not have an address assigned yet.
Build number 511 (just build) will/should include the visibility of these nodes, but can not be added yet. It is safe to use build 511 as long as predefined node addresses are used. This will be included in build 512 (which i hope will be available on a couple of hours).
-
Build 513 is out there (it includes the inclusion mode available for testing).
Please be notified about the fact that this build has to be tested. More builds can become available in a rapid tempo, When the MySensors transition to the new discovery method is complete i will post it here.
-
Maybe I'm not understanding how this works correctly. I have used the alpha build for a while now and it just worked flawlessly with an MySensors serial gateway. Was this part re-constructed in the latest build? My device shows up in the peripherals page and I can set the connection then save set and start. However when I go to the drivers page I see my device but when I click on it to view device info, all I get is a blank page. I can't get any of the last 3 builds to recognize that there is even a gateway connected in the drivers menu.
-
Maybe I'm not understanding how this works correctly. I have used the alpha build for a while now and it just worked flawlessly with an MySensors serial gateway. Was this part re-constructed in the latest build? My device shows up in the peripherals page and I can set the connection then save set and start. However when I go to the drivers page I see my device but when I click on it to view device info, all I get is a blank page. I can't get any of the last 3 builds to recognize that there is even a gateway connected in the drivers menu.
@ceburge Yes, it is being overhauled. The discovery of devices is being moved to one single page. All drivers which are able to report new devices will be showing these device in this new page. I;m doing this for a couple of reasons:
- To let a driver show a device you have to program this separately for every driver. Now a driver just has to provide a couple of details to a centralized environment which will take care of all the visuals and possible options. Creating this takes a couple of days, but results in massive winnings of time in future developments,
- If there is one page, one single command to retrieve discovered devices i can finally incorporate this functionality in clients. In other words you do not need the web interface to add devices. Just take your tablet or phone (client is in development),
- It saves server memory (currently this function already saved 2 MB ram without devices in the discovery table),
- It splits functionality and makes the driver page only necessary when there is need for debugging, or driver settings. In the future you can assign user rights, yes add devices, no driver details.
- It now is possible to inform users when a new device is found on the fly without refreshing pages, displays or other visual presentations enhancing experience.
- I'm busy finalizing the programmers API, this means quick programming work needs to become stable en reliable. Using this method will introduce more reliability when it is done.
It is correct that in the current hot-fix/hot-off the press features things can go wrong. Keep in mind that the build server is for creating a quick build for testing! it can contain fixes, but also fails. The regular download page contains the download which is the most stable hot-build which got more intensive testing. This will stay like this until the moment the first Beta/Release Candidates comes out which will be the most intensive tested ones.
The gateway connected page will come back!
