Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Semtech SX1262 LoRa radios please!

cloolalang last edited by

I wonder who is interested to upgrade RF95 to support the improved Lora chips

https://forum.mysensors.org/topic/10724/which-are-the-preferred-lora-modules-now

I dont think RadioHead is doing anything on it.

So far the only one I see is Radiolib

P
Reply Quote 0
1 Reply Last reply

1
Posts

21
Views

Suggested Topics

Increase VAR limit
Feature Requests • • NielBierman

3

0
Votes

3
Posts

36
Views

@NielBierman Why are you using VARs when there are already moisture and temperature categories available to you? Just give each temp and moisture sensor a unique CHILD_ID (simply by adding 1-8 in the name) and you are done!
WiFiNINA
Feature Requests • • Berten Vandebroek

1

0
Votes

1
Posts

24
Views

No one has replied
RPI GW - Configure an ethernet RPI GW that drive an USB Arduino GW
Feature Requests • • barrydou

1

0
Votes

1
Posts

18
Views

No one has replied
Feature Request - Open/Closed
Feature Requests • • skywatch

4

0
Votes

4
Posts

40
Views

@mfalkvidd - Sorry I didn't make it clear but I was thinking of doors, windows, blinds and curtains. Curtains don't usually have UP or DOWN, they are OPEN and CLOSED. Likewise with doors and windows which are normally OPEN or CLOSED. Only if V_ARMED is set true should it send a value of V_TRIPPED. But in normal circumstances they are OPEN or CLOSED (or maybe smoewhere inbetween, but V_PERCENTAGE handles that situation).
Gateway, received message RSSI sent to controller
Feature Requests • • alexelite

3

0
Votes

3
Posts

34
Views

Yes, I read it. I started using your approach, gateway sensor ids representing nodes ids, but from the controller point of view this is not straight forward, I think. The 2 problems remain somehow the same. How to get the controllers to understand that gateway sensors are not actually sensors but RSSI value, and repeaters breaks my current algorithm. Thinking more about this, if it is something the library would benefit, lead me to read about the RF24 and NRF5 radios. I only have RFM69 devices (20 nodes) and it offers RSSI out of the box, same as RFM LoRa version and NRF5. But RF24 lacks this feature. So it somewhat depends on how many are using radios with rssi. Library developers included RSSI functionality, so it has to be of interest. The repeater problem is partially solved because RF24 networks need repeaters, but don't have RSSI. RFM networks should do without repeaters for most applications. For NRF5, I lack this info. But as I passed the rssi from transport to gateway transport, same can be done with actual sender from the header. Maybe in version 3.0.0 something like this can be implemented? My understanding is that controllers get link quality data the same way they get all other data from devices, on other platforms. Mabey a I_LINK_QUALITY type can be added especially for this information? for example my zigbee network: zigbee2mqtt/device {"linkquality":5,"state":"ON"}
Filter node
Feature Requests • • Snyfir

17

0
Votes

17
Posts

72
Views

In all honesty, I'm not quite convinced you'd need two separate networks. Just provide the security sensors, the repeaters, the gateway and your controller - that form the security system - with some sort of ups and they will keep running until the UPS has no more power left. The none security devices will stop working when the power goes out and, unless I don't really understand your problem well. That does what I think you want to achieve? Unless you have combined a lot of sensors within a repeater it would really be my way to go. It wouldn't mean any modifications to your security hardware, because they need to be battery powered or have some sort of UPS anyway, to keep working when the power goes down. But again it's hard to judge when you don't really understand the problem some one is trying to solve.
Can a node request a status from other node?
Feature Requests • • joaoabs

3

0
Votes

3
Posts

35
Views

While it would be possible via request() as @mfalkvidd suggests, I wouldn't recommend to do that in this case. I think it's rather pointless to regularly request variables which only change rarely. It adds a lot of traffic to the network - at least 4 messages (including echos) per request - while the requested values stay unchanged 98% of the time or so. Not to mention that the status LEDs could show a wrong condition for up to 10 minutes if you toggle a light switch right after its state has been requested. I'd suggest to use one of the following alternatives instead: You could have the light nodes send messages to both the gateway and the node with the status LEDs. The status LEDs would update immediately when a light is toggled and there's a lot less unnecessary traffic on the network. Let the controller handle the logic. Whenever a light node sends a state change to the gateway, tell the controller to send a message to the node with the status LEDs. This method has the same benefits as the one before and it's easier maintainable since you don't need to re-upload sketches to multiple nodes if something changes - just reconfigure a script in your controller.
RPI GW - Including build flags somewhere for future reference
Feature Requests • • joaoabs

6

3
Votes

6
Posts

61
Views

@mfalkvidd not necessary. We already have #define MY_GATEWAY_LINUX, so just #ifdef MY_GATEWAY_LINUX to define those constants in runtime at the init stage. As I see it, only SPI driver needs to be defined at compilation, other options could easily be set via config.

Semtech SX1262 LoRa radios please!

Suggested Topics

Increase VAR limit
Feature Requests • • NielBierman

WiFiNINA
Feature Requests • • Berten Vandebroek

RPI GW - Configure an ethernet RPI GW that drive an USB Arduino GW
Feature Requests • • barrydou

Feature Request - Open/Closed
Feature Requests • • skywatch

Gateway, received message RSSI sent to controller
Feature Requests • • alexelite

Filter node
Feature Requests • • Snyfir

Can a node request a status from other node?
Feature Requests • • joaoabs

RPI GW - Including build flags somewhere for future reference
Feature Requests • • joaoabs

80
Online

10.3k
Users

10.7k
Topics

109.6k
Posts

Semtech SX1262 LoRa radios please!

Suggested Topics

Increase VAR limit Feature Requests • • NielBierman

WiFiNINA Feature Requests • • Berten Vandebroek

RPI GW - Configure an ethernet RPI GW that drive an USB Arduino GW Feature Requests • • barrydou

Feature Request - Open/Closed Feature Requests • • skywatch

Gateway, received message RSSI sent to controller Feature Requests • • alexelite

Filter node Feature Requests • • Snyfir

Can a node request a status from other node? Feature Requests • • joaoabs

RPI GW - Including build flags somewhere for future reference Feature Requests • • joaoabs

80Online

10.3kUsers

10.7kTopics

109.6kPosts

Increase VAR limit
Feature Requests • • NielBierman

WiFiNINA
Feature Requests • • Berten Vandebroek

RPI GW - Configure an ethernet RPI GW that drive an USB Arduino GW
Feature Requests • • barrydou

Feature Request - Open/Closed
Feature Requests • • skywatch

Gateway, received message RSSI sent to controller
Feature Requests • • alexelite

Filter node
Feature Requests • • Snyfir

Can a node request a status from other node?
Feature Requests • • joaoabs

RPI GW - Including build flags somewhere for future reference
Feature Requests • • joaoabs

80
Online

10.3k
Users

10.7k
Topics

109.6k
Posts