-
Notifications
You must be signed in to change notification settings - Fork 308
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
setProperty in setupHandler fails with more than 2 properties in 2.0.0-dev #266
Comments
with a small workaround, all values, properties etc. in one node everything works (but its a little bit ugly imho):
|
I have been running into the same problem too. One thing that I am noticing is that when I am in an environment that has a lot of APs the code does not work properly. When I am in an area with few access points the same code works as expected. e.g. 5 APs visible when running the 'WiFiScan' example vs 26 APs. Very frustrating to discover that tested code fails just by being in a different environment. I had to go down to a single HomieNode in this case! |
I don't know what can be done at our level to solve that... Maybe change the Wi-Fi channel? |
I havn't found a relation with the channel or the number of wifis in the neighbourhood. Also with 1.5 the problem doesn't exist. |
Related to #345 |
) * Disabled request body parsing if the handler does nothing. This will save memory and prevent crashes on large POST requests. Signed-off-by: Alexandr Zarubkin <[email protected]> * Marked SPIFFSEditor request handler as non-trivial, as it needs to process POST requests. Signed-off-by: Alexandr Zarubkin <[email protected]>
for testing purposes i extended the TemperatureSensor sketch like this:
as soon as i add the third Node (in my case named pressureNode) the setProperty calls in the setupHandler fail silently for all nodes and the unit property is never propagated. if i remove the pressureNode stuff, the two remaining unit properties for temperatureNode and humidityNode get propagated correctly.
The text was updated successfully, but these errors were encountered: